Re: HTTPD shutting down every night
So httpd survived Tuesday without crashing but crashed again yesterday and today.
In /var/log/messages I can see:
Nov 14 03:26:57 novak systemd[1]: Reloading The Apache HTTP Server.
Nov 14 03:26:57 novak systemd[739346]: httpd.service: Failed to set up mount namespacing:
No such file or directory
Nov 14 03:26:57 novak systemd[739346]: httpd.service: Failed at step NAMESPACE spawning
/usr/sbin/httpd: No such file or directory
Nov 14 03:26:57 novak systemd[1]: httpd.service: Control process exited, code=exited
status=226
And then a little later
Nov 14 03:26:58 novak systemd[1]: httpd.service: Killing process 230630 (nss_pcache) with
signal SIGKILL.
Nov 14 03:26:58 novak systemd[1]: httpd.service: Failed with result 'exit-code'.
Nov 14 03:26:58 novak systemd[1]: Reload failed for The Apache HTTP Server.
Nov 14 03:26:58 novak audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295
subj=system_u:system_r:init_t:s0 msg='unit=httpd comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Nov 14 03:26:58 novak logrotate[739362]: ALERT exited abnormally with [1]
Googling the NAMESPACE error I find a post about /tmp or /var/tmp being symbolic links.
Neither are.
Yesterday I reinstalled httpd from scratch, last night it crashed again in the same way.
Does anyone know what user logrotate runs as? I’ve tried /bin/systemctl reload
httpd.service as root and it reloads as expected and am wondering if there’s something
else weird going on here?
Regards,
Scott
On 12. Nov 2018, at 16:32, Scott van Looy via users
<users(a)lists.fedoraproject.org> wrote:
Thanks for this.
Certwatch is uninstalled now, it just tells me if any of my certs have expired and as I
don’t have any on that box any more it’s kinda pointless :)
I’ve removed the stuff to hide the output from the apache restart in logrotate so I’m
going to let it run tonight and see if anything exciting gets logged
Regards,
Scott
> On 12. Nov 2018, at 16:08, Andy Blanchard <zocalo(a)gmail.com> wrote:
>
> Of that bunch, autodld (downloading RPMs) and rkhunter (scanning the
> filesystem, taking checksums, and looking for changes) are both
> passive, certwatch probably shouldn't be updating certificates every
> 24 hours (but could do, so worth checking!), and logwatch just parses
> the existing logfiles - it shouldn't touch the daemons. That leaves
> logrotate as the prime suspect, IMHO, as that definitely HUPs/restarts
> daemons after it rotates logfiles. However, it also tracks when it
> was last run and won't cycle a logfile and HUP a daemon if it doesn't
> need to - since it's already cycled the logs at 03:54, it won't do so
> again when you're trying to run it manually unless you tweak the file
> "/var/lib/logrotate.status" first.
>
> Note also that httpd exited within the window for logrotate, which
> also seems to point the finger at logrotate, so I'd definitely make
> sure that was in tonight's list of disabled scripts, and it might be
> worth double checking what update cycle certwatch is using too.
>
> Andy
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> 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@lists.fedoraproject.org
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org