OK thanks for this.
It’s not normal though, it doesn’t actually restart - it just crashes.
/bin/systemctl reload httpd seems to work OK when I run it as root, the server restarts.
So I’m still a little confused. Does anyone have any suggestions?
> On 7. Nov 2018, at 15:52, Roger Heflin <rogerheflin@xxxxxxxxx> wrote:
>
> this is the daily logrotate process. it rotates the log files and
> reloads httpd. It is normal. A number of other process will also
> restart at the same time.
>
> See:
> cat /etc/logrotate.d/httpd
> /var/log/httpd/*log {
> missingok
> notifempty
> sharedscripts
> delaycompress
> postrotate
> /bin/systemctl reload httpd.service > /dev/null 2>/dev/null || true
> endscript
> }
> On Wed, Nov 7, 2018 at 5:53 AM Andy Blanchard <zocalo@xxxxxxxxx> wrote:
>>
>> On Wed, 7 Nov 2018 at 10:40, Scott van Looy via users
>> <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
>>> Since the upgrade to F29 my HTTPD has been shutting down around 3am every night. I’d like to try and investigate why, but the only thing in the log is:
>>> [mpm_event:notice] [pid 1096508:tid 140027704744192] AH00492: caught SIGWINCH, shutting down gracefully
>>>
>>> These all happen at roughly the same time, but not the exact same time - around 3am
>>
>> Semi-regular times like "around 3am" generally imply something being
>> governed by Anacron's variable task scheduler which will randomise the
>> time of cron jobs. Since this is daily, I'd start by taking a look at
>> your daily crons and see if any of them might relate to the issue -
>> most likely a log rotation tool or something along those lines.
>>
>> SIGWINCH isn't one of the more common signals you'll interact with
>> like TERM, but it supposedly relates to "WINdow CHange", or a change
>> in the size of the controlling terminal's window size - e.g. to tell a
>> shell like bash that the terminal emulator window has been resized and
>> it now needs to wrap at a different number of characters. However it
>> seems Apache doesn't use it entirely correctly so it may be that your
>> log rotation tool is actually stopping the daemon rather than HUPing
>> it as it should.
>>
>> Andy
>> _______________________________________________
>> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
>> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
