Quack,
Xavier, I see no such fix in Debian stable (where my problem lies).
Additionally I had a look at the sources for 2.4.41-1~bpo10+1, 2.4.43-1,
as well as the git master content, and I see no such thing. Are you sure
you pushed that work and it got included?
\_o<
--
Marc Dequènes
On 2019-08-23 01:20, Xavier wrote:
The "After=network-online.target" may be enough to fix this issue,
isn't it?
I honestly did not think about such scenario. I think it should be fine
according to the systemd.unit manpage, but I just cannot reboot my
server every so often to check it.
Le 22/08/2019 à 17:57, Xavier a écrit :
> Le 22/08/2019 à 17:38, Marc Dequènes (duck) a écrit :
>> Quack,
>>
>> I also hit this problem recently on Buster. I also do have specific
>> Listen directives on this machine but all my IPs (4 and 6) are
>> statically defined in /etc/network/interfaces.
Quack,
I also hit this problem recently on Buster. I also do have specific
Listen directives on this machine but all my IPs (4 and 6) are
statically defined in /etc/network/interfaces.
I looked at the systemd service file and I believe that
After=network.target is not enough.
According to
Package: apache2
Version: 2.4.25-3+deb9u5
Severity: important
Dear Maintainer,
when I reboot my server, most of the time, I then have to manually restart
apache because it seems unable to reliably initialize upon boot.
The problem only occurs since I configured apache to listen on certain
5 matches
Mail list logo
