Re: Apache2 fails on boot, starts from cli

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> ● apache2.service - The Apache HTTP Server
> Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
> Active: failed (Result: exit-code) since Sun 2025-08-31 22:46:13 UTC; 51s ago
> Docs: https://httpd.apache.org/docs/2.4
> Process: 965 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)
> 
> Aug 31 22:46:12 server systemd[1]: Starting The Apache HTTP Server...
> Aug 31 22:46:13 server apachectl[1002]: (99)Cannot assign requested address: AH00072: make_sock:
> could not bind to address 192.168.0.95:8442


It seems that systemd can start apache httpd manually but not automatically on boot because it could not bind to address 192.168.0.95:8442 . May be the apache systemd unit starts too early, before the network or your IP is ready on the system.
Try to add this on your apache systemd unit file just behind [Unit]
After=network.target remote-fs.target nss-lookup.target

Then systemctl daemon-reload

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx





[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux