On Thu, 2023-09-14 at 03:03 +0930, Tim via users wrote:
> On Fri, 2023-09-01 at 12:36 +0100, Patrick O'Callaghan wrote:
> > I've noticed recently that Apache often (or perhaps always) doesn't
> > respond after a system hibernate/resume cycle. After restarting it
> > ('apachectl restart') all is well.
> >
> > I could script an automatic restart after resuming, but I wondered
> > if
> > this is a well-known problem with a simpler solution.
> >
>
> Just wondering if simply having a delayed restart would work?
> Perhaps
> something else isn't ready in time.
>
> A wait for a network? The general unhibernate/resume triggering a
> restart after a little while?
It's definitely an AVC error, and as far as I can see from the journal
the network is already up. In any case, a delayed start would be as
fussy to arrange as my work-around, and no more elegant.
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
