Bug 1193931
Summary: | Messages file is flooded by systemd messages regarding rabbitmq. | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Leonid Natapov <lnatapov> |
Component: | rabbitmq-server | Assignee: | John Eckersberg <jeckersb> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | yeylon <yeylon> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.0 (Juno) | CC: | abeekhof, apevec, lhh, srevivo, tshefi, yeylon |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | 7.0 (Kilo) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-09-11 17:29:20 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Leonid Natapov
2015-02-18 15:09:06 UTC
If this is happening in a pacemaker environment, the latest pacemaker packaegs will take care of it. Otherwise, you need something like the following patch: main.c- /* The presence of this variable allegedly controls whether child main.c- * processes like httpd will try and use Systemd's sd_notify main.c- * API main.c- */ main.c: unsetenv("NOTIFY_SOCKET"); I've confirmed that the error about "systemd: Cannot find unit for notify message ..." is fixed using newer pacemaker (I've got pacemaker-1.1.12-22.el7_1.2.x86_64 currently). However note that the other systemd messages about "Starting/Started Session" are still present, and that is expected behavior. I think this is as quiet as it's going to get, so I'm going to go ahead and close this. |