> side-effects such as half-completed volume attachment calls leaving
resources dangling/orphaned.
this feels odd, as `apache2 reload` should be calling `apachectl
graceful`. Reading the man page:
> graceful Gracefully restarts the Apache daemon by sending it a
> SIGUSR1. If the daemon is not running, it is started. This differs from a
> normal restart in that currently open connections are not aborted. A side
> effect is that old log files will not be closed immediately. This means that
> if used in a log rotation script, a substantial delay may be necessary to
> ensure that the old log files are closed before processing them. This
> command automatically checks the configuration files via apache2ctl
> configtest before initiating the restart to to catch the most obvious
> errors. However, it is still possible for the daemon to die because of
> problems with the configuration.
The key to me being:
> This differs from a normal restart in that currently open connections
are not aborted.
so it seems like there's a link in openstack services to apache2 running
_continuously_ or else those services lost a handle? I'm guessing
there's a dependency chain in the systemd units for specific openstack
services?
A bit more digging, it looks like apache _requires_ the graceful reload
to pick up the rotated logfile properly.
Could you provide more info on the following:
* what openstack services are running into issues
* journal outputs from the logrotate journal entry. they should be tagged as
`apache2.logrotate` in the journal.
* journal output from openstack services that are having issues at the same
time as the apache2 reload
* any helpful openstack unit files or information that can show the relation
between the services and apache2
right now i can't tell if there's something more that can be done in
apache2 that package vs. an apache2 deployment within the specific
context (default behaviour vs. specific system expectations)
** Changed in: apache2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106500
Title:
logrotate script definition forces application restart
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/2106500/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
