[Rather than adding to an existing thread (which discusses AVCs from crontab among other things, this is starting from a clean slate to reduce confusion.] 1. I run httpd via systemd for a small personal web service. This works. 2. I suspend my system overnight and wake it automatically in the morning). This turns out to be irrelevant, because the problem reported here occurs even when I do it manually. 3. On resuming, everything is up *except* httpd. 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. A similar thing seems to happen to certbot, though I haven't looked at it in detail. Here's the relevant section from the journal: Sep 21 13:04:12 Bree systemd[1]: httpd.service: Deactivated successfully. Sep 21 13:04:12 Bree systemd[1]: httpd.service: Consumed 2.980s CPU time. Sep 21 13:04:14 Bree NetworkManager[1214]: <info> [1726920254.0080] device (enp12s0): carrier: link connected Sep 21 13:04:14 Bree kernel: r8169 0000:0c:00.0 enp12s0: Link is Up - 1Gbps/Full - flow control rx/tx I assume there's a systemd mechanism for getting httpd to wait for the network before resuming, but I've no idea how to accomplish this. poc -- _______________________________________________ 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
