[Bug 1197421] New: Logrotate needs to use systemctl
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1197421
Bug ID: 1197421
Summary: Logrotate needs to use systemctl
Product: Fedora EPEL
Version: epel7
Component: rabbitmq-server
Severity: medium
Assignee: lemenkov(a)gmail.com
Reporter: bwong(a)fastmail.fm
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org,
hubert.plociniczak(a)gmail.com, jeckersb(a)redhat.com,
josh(a)fornwall.com, lemenkov(a)gmail.com,
rjones(a)redhat.com, s(a)shk.io
Description of problem:
The package rabbitmq-server-3.3.5-4.el7.noarch installs a logrotate
configuration file that uses /sbin/service. Log rotation does not run
successfully because the postrotate parameter needs to be updated.
The message received from logrotate (via cron):
/etc/cron.hourly/logrotate:
The service command supports only basic LSB actions (start, stop, restart,
try-restart, reload, force-reload, status). For other actions, please try to
use systemctl.
error: error running shared postrotate script for '/var/log/rabbitmq/*.log '
Version-Release number of selected component (if applicable):
rabbitmq-server-3.3.5-4.el7.noarch
How reproducible:
Consistently
Steps to Reproduce:
1. Install rabbitmq-server.
2. View logrotate configuration file /etc/logrotate.d/rabbitmq-server
3.
Actual results:
All I can confirm is the error message from logrotate, whether the rabbitmq
logs actually get rotated, I cannot say for sure at this time.
Expected results:
A working postrotate command
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 7 months
[Bug 1148444] New: logrotation fails
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1148444
Bug ID: 1148444
Summary: logrotation fails
Product: Fedora EPEL
Version: epel7
Component: rabbitmq-server
Assignee: lemenkov(a)gmail.com
Reporter: Jan.van.Eldik(a)cern.ch
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org,
hubert.plociniczak(a)gmail.com, jeckersb(a)redhat.com,
josh(a)fornwall.com, lemenkov(a)gmail.com,
rjones(a)redhat.com, s(a)shk.io
Description of problem:
Logrotation fails 100% because of old-style post-rotate command
Version-Release number of selected component (if applicable):
rabbitmq-server-3.1.5-7.el7.noarch
How reproducible:
100%
Steps to Reproduce:
[root@jcentos7-01 tmp]# logrotate -f /etc/logrotate.conf
The service command supports only basic LSB actions (start, stop, restart,
try-restart, reload, force-reload, status). For other actions, please try to
use systemctl.
error: error running shared postrotate script for '/var/log/rabbitmq/*.log '
[root@jcentos7-01 tmp]# cat /etc/logrotate.d/rabbitmq-server
/var/log/rabbitmq/*.log {
weekly
missingok
rotate 20
compress
delaycompress
notifempty
sharedscripts
postrotate
/sbin/service rabbitmq-server rotate-logs > /dev/null
endscript
}
[root@jcentos7-01 tmp]# /sbin/service rabbitmq-server rotate-logs > /dev/null
The service command supports only basic LSB actions (start, stop, restart,
try-restart, reload, force-reload, status). For other actions, please try to
use systemctl.
[root@jcentos7-01 tmp]# echo $?
2
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 7 months
[Bug 1259564] New: rabbitmq-server stops (instead of restart) during update to rabbitmq-server-3.3.5-5.el7.noarch
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1259564
Bug ID: 1259564
Summary: rabbitmq-server stops (instead of restart) during
update to rabbitmq-server-3.3.5-5.el7.noarch
Product: Fedora EPEL
Version: epel7
Component: rabbitmq-server
Assignee: lemenkov(a)gmail.com
Reporter: ivan.mironov(a)infra-it.ru
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org,
hubert.plociniczak(a)gmail.com, jeckersb(a)redhat.com,
josh(a)fornwall.com, lemenkov(a)gmail.com,
rjones(a)redhat.com, s(a)shk.io
Description of problem:
During update to rabbitmq-server-3.3.5-5.el7.noarch, rabbitmq-server service
stops, while it should be restarted.
/var/log/yum.log:
...
Sep 03 07:42:06 Updated: rabbitmq-server-3.3.5-5.el7.noarch
...
journalctl -u rabbitmq-server:
...
Sep 03 07:41:59 devenv-msk-09 systemd[1]: Stopping RabbitMQ broker...
Sep 03 07:41:59 devenv-msk-09 rabbitmqctl[29552]: Stopping and halting node
'rabbit@devenv-msk-09' ...
Sep 03 07:42:05 devenv-msk-09 rabbitmqctl[29552]: ...done.
Sep 03 07:42:05 devenv-msk-09 systemd[1]: Stopped RabbitMQ broker.
Version-Release number of selected component (if applicable):
rabbitmq-server-3.3.5-5.el7.noarch
How reproducible:
This happened on two different servers.
Steps to Reproduce:
1. Install previous version of rabbitmq-server
2. systemctl enable rabbitmq-server && systemctl start rabbitmq-server
3. Update using yum
Actual results:
rabbitmq-server is not running after update.
Expected results:
rabbitmq-server should be up and running.
Additional info:
N/A
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 7 months
[Bug 1264083] New: rabbitmq-server stops (instead of restart) during update
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1264083
Bug ID: 1264083
Summary: rabbitmq-server stops (instead of restart) during
update
Product: Red Hat OpenStack
Version: 7.0
Component: rabbitmq-server
Assignee: jeckersb(a)redhat.com
Reporter: jeckersb(a)redhat.com
QA Contact: yeylon(a)redhat.com
CC: apevec(a)redhat.com, erlang(a)lists.fedoraproject.org,
extras-qa(a)fedoraproject.org,
hubert.plociniczak(a)gmail.com,
ivan.mironov(a)infra-it.ru, jeckersb(a)redhat.com,
josh(a)fornwall.com, lemenkov(a)gmail.com, lhh(a)redhat.com,
rjones(a)redhat.com, s(a)shk.io, yeylon(a)redhat.com
Depends On: 1259564
Group: redhat
+++ This bug was initially created as a clone of Bug #1259564 +++
Description of problem:
During update to rabbitmq-server-3.3.5-5.el7.noarch, rabbitmq-server service
stops, while it should be restarted.
/var/log/yum.log:
...
Sep 03 07:42:06 Updated: rabbitmq-server-3.3.5-5.el7.noarch
...
journalctl -u rabbitmq-server:
...
Sep 03 07:41:59 devenv-msk-09 systemd[1]: Stopping RabbitMQ broker...
Sep 03 07:41:59 devenv-msk-09 rabbitmqctl[29552]: Stopping and halting node
'rabbit@devenv-msk-09' ...
Sep 03 07:42:05 devenv-msk-09 rabbitmqctl[29552]: ...done.
Sep 03 07:42:05 devenv-msk-09 systemd[1]: Stopped RabbitMQ broker.
Version-Release number of selected component (if applicable):
rabbitmq-server-3.3.5-5.el7.noarch
How reproducible:
This happened on two different servers.
Steps to Reproduce:
1. Install previous version of rabbitmq-server
2. systemctl enable rabbitmq-server && systemctl start rabbitmq-server
3. Update using yum
Actual results:
rabbitmq-server is not running after update.
Expected results:
rabbitmq-server should be up and running.
Additional info:
N/A
--- Additional comment from Fedora Update System on 2015-09-03 12:12:38 EDT ---
rabbitmq-server-3.5.4-3.fc23 has been submitted as an update to Fedora 23.
https://bodhi.fedoraproject.org/updates/FEDORA-2015-15005
--- Additional comment from Fedora Update System on 2015-09-03 12:17:32 EDT ---
rabbitmq-server-3.5.4-3.fc22 has been submitted as an update to Fedora 22.
https://bodhi.fedoraproject.org/updates/FEDORA-2015-15009
--- Additional comment from Fedora Update System on 2015-09-03 12:21:30 EDT ---
rabbitmq-server-3.3.5-6.el7 has been submitted as an update to Fedora EPEL 7.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7918
--- Additional comment from John Eckersberg on 2015-09-03 12:26:19 EDT ---
The fix here is to:
1) remove service stop from %pre
2) add service try-restart in %postun
Which means that upgrading to the fixed package will not stop the service, but
it also will not restart the service because the old package does not have the
%postun scriptlet.
However, all future upgrades after the first will contain the %postun scriptlet
and will restart properly.
--- Additional comment from Fedora Update System on 2015-09-04 03:29:32 EDT ---
rabbitmq-server-3.5.4-3.fc22 has been pushed to the Fedora 22 testing
repository. If problems still persist, please make note of it in this bug
report.\nIf you want to test the update, you can install it with \n su -c 'yum
--enablerepo=updates-testing update rabbitmq-server'. You can provide feedback
for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-15009
--- Additional comment from Fedora Update System on 2015-09-04 03:33:36 EDT ---
rabbitmq-server-3.5.4-3.fc23 has been pushed to the Fedora 23 testing
repository. If problems still persist, please make note of it in this bug
report.\nIf you want to test the update, you can install it with \n su -c 'yum
--enablerepo=updates-testing update rabbitmq-server'. You can provide feedback
for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-15005
--- Additional comment from Fedora Update System on 2015-09-04 15:17:44 EDT ---
rabbitmq-server-3.3.5-6.el7 has been pushed to the Fedora EPEL 7 testing
repository. If problems still persist, please make note of it in this bug
report.\nIf you want to test the update, you can install it with \n su -c 'yum
--enablerepo=updates-testing update rabbitmq-server'. You can provide feedback
for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7918
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1259564
[Bug 1259564] rabbitmq-server stops (instead of restart) during update to
rabbitmq-server-3.3.5-5.el7.noarch
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 7 months
[Bug 1206714] New: CVE-2015-2774 erlang: Erlang/OTP is vulnerable to Poodle in its TLS-1.0 implementation [epel-all]
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1206714
Bug ID: 1206714
Summary: CVE-2015-2774 erlang: Erlang/OTP is vulnerable to
Poodle in its TLS-1.0 implementation [epel-all]
Product: Fedora EPEL
Version: el6
Component: erlang
Keywords: Security, SecurityTracking
Severity: high
Priority: high
Assignee: rjones(a)redhat.com
Reporter: fleite(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, gemi(a)bluewin.ch,
rjones(a)redhat.com, s(a)shk.io
Blocks: 1206712 (CVE-2015-2774)
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora EPEL.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora EPEL. While
only one tracking bug has been filed, please correct all affected versions
at the same time. If you need to fix the versions independent of each
other, you may clone this bug as appropriate.
[bug automatically created by: add-tracking-bugs]
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1206712
[Bug 1206712] CVE-2015-2774 Erlang/OTP is vulnerable to Poodle in its
TLS-1.0 implementation
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 8 months
[Bug 1206713] New: CVE-2015-2774 erlang: Erlang/OTP is vulnerable to Poodle in its TLS-1.0 implementation [fedora-all]
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1206713
Bug ID: 1206713
Summary: CVE-2015-2774 erlang: Erlang/OTP is vulnerable to
Poodle in its TLS-1.0 implementation [fedora-all]
Product: Fedora
Version: 21
Component: erlang
Keywords: Security, SecurityTracking
Severity: high
Priority: high
Assignee: lemenkov(a)gmail.com
Reporter: fleite(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, lemenkov(a)gmail.com,
rhbugs(a)n-dimensional.de, s(a)shk.io
Blocks: 1206712 (CVE-2015-2774)
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time. If you need to fix the versions independent of each other,
you may clone this bug as appropriate.
[bug automatically created by: add-tracking-bugs]
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1206712
[Bug 1206712] CVE-2015-2774 Erlang/OTP is vulnerable to Poodle in its
TLS-1.0 implementation
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 8 months