On Sep 21, 2024, at 09:35, Francis.Montagnac@xxxxxxxx wrote: > > HI. > >> On Sat, 21 Sep 2024 13:16:49 +0100 Patrick O'Callaghan wrote: >> 4. The journal (see below) shows that httpd does resume with the rest >> of the system, but then is immediately deactivated. The reason for this >> is not stated (there's no error message), but may be because on the >> system resume the network is not yet up. > > Look perhaps in /var/log/http/error_log. I can’t see any evidence that anyone actually looked at httpd’s log to see the error it produces, everything else is speculation at this point. If you’re not seeing any logs at all, then I don’t think the script you use to restart the daemon is actually starting ant anything at all. To heap on even more speculation, I seem to recall if you have DNS names in your httpd.conf or associated conf.d settings, and httpd can’t resolve those names upon startup, it will fail out. If DNS resolution isn’t working shortly after resume, that might be contributing to the problem. But as I said, without actual errors, my guess is as good as anyone’s. -- Jonathan Billings -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
