Rabbitmq is sending stderr to /dev/null
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mirantis OpenStack |
Confirmed
|
Medium
|
Dmitry Mescheryakov | ||
| 9.x |
Confirmed
|
Medium
|
Dmitry Mescheryakov | ||
Bug Description
Detailed bug description:
Rabbitmq is sending stderr messages to /dev/null instead of sending them to log file
Steps to reproduce:
1. Navigate to controller node
2. Execute:
# htop
Expected results:
Rabbitmq is sending all error messages to log file
Actual result:
Rabbitmq is sending all error messages to /dev/null (see attachment)
Environment:
[root@nailgun ~]# shotgun2 short-report
cat /etc/fuel_build_id:
495
cat /etc/fuel_
495
cat /etc/fuel_release:
9.0
cat /etc/fuel_
mitaka-9.0
rpm -qa | egrep 'fuel|astute|
fuel-nailgun-
fuel-provision
fuel-notify-
shotgun-
fuel-release-
python-
fuel-misc-
fuel-agent-
python-
fuel-bootstrap
fuel-migrate-
fuel-ui-
nailgun-
network-
fuel-utils-
fuelmenu-
fuel-library9.
fuel-mirror-
fuel-ostf-
fuel-openstack
rubygem-
fuel-9.
fuel-setup-
| Sergii Turivnyi (sturivnyi) wrote | #1 |
| Changed in mos: | |
| importance: | Undecided → Critical |
| assignee: | nobody → Dmitry Mescheryakov (dmitrymex) |
| Changed in mos: | |
| status: | New → Confirmed |
| Dmitry Mescheryakov (dmitrymex) wrote | #2 |
| Changed in mos: | |
| importance: | Critical → Medium |
| summary: |
- Rabbitmq is sending all error messages to /dev/null + Rabbitmq is sending stderr to /dev/null |
| description: | updated |
| Changed in mos: | |
| milestone: | 9.1 → 9.2 |
Lowering priority to medium - only stderr is missing. It is needed only in cases when RabbitMQ server process refuses to start. Otherwise all errors are logged in log log file.