Thanks for the added in-depth analysis Rodrigo. I'll close out the
apache2 task for now, feel free to reopen it if further discoveries
suggest changes needed there.
Based on past experience tinkering with the apache2 reload/graceful
command API, it gets tricky since with it supporting both systemd and
apachectl for managing the server system processes even slight changes
in behavior of one or the other can break a lot of users that have their
own styles of usage. So if we consider adjustments to apache2 we need
to be super cautious and very, very broad in testing plans.
** Changed in: apache2 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/2106500
Title:
logrotate script definition forces application restart
Status in OpenStack Compute (nova):
New
Status in apache2 package in Ubuntu:
Invalid
Bug description:
We are running into issues in Canonical OpenStack where apache2 is
used for the API services such as Nova and everyday at midnight the
logrotate script runs and reloads apache2 forcing the services to
restart, causing disruption and side-effects such as half-completed
volume attachment calls leaving resources dangling/orphaned.
This is the line in /etc/logrotate.d/apache2 that causes issue:
invoke-rc.d apache2 reload 2>&1 | logger -t apache2.logrotate
In the apache2 source package it is in debian/apache2.logrotate so I
believe this is an issue with this package customization since 2004 in
commit d965556aa of the ubuntu package source.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/2106500/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
