Re: http failing on boot

[Jack Craig <jack.craig.aptos@xxxxxxxxx>]

whats in /var/log/httpd/access_log  ???

maybe ..

cat /var/log/httpd/access_log

35.185.73.152 - - [21/Feb/2020:09:14:33 -0800] "GET /robots.txt HTTP/1.0" 301 250 "-" "ZoominfoBot (zoominfobot at zoominfo dot com)"
35.185.73.152 - - [21/Feb/2020:09:14:34 -0800] "GET /robots.txt HTTP/1.1" 404 208 "-" "ZoominfoBot (zoominfobot at zoominfo dot com)"
35.185.73.152 - - [21/Feb/2020:09:14:34 -0800] "GET / HTTP/1.0" 301 240 "-" "ZoominfoBot (zoominfobot at zoominfo dot com)"
35.185.73.152 - - [21/Feb/2020:09:14:34 -0800] "GET /robots.txt HTTP/1.0" 404 208 "-" "ZoominfoBot (zoominfobot at zoominfo dot com)"
35.185.73.152 - - [21/Feb/2020:09:14:34 -0800] "GET / HTTP/1.0" 200 1154 "-" "ZoominfoBot (zoominfobot at zoominfo dot com)"
35.185.73.152 - - [21/Feb/2020:09:22:52 -0800] "GET /robots.txt HTTP/1.0" 301 246 "-" "ZoominfoBot (zoominfobot at zoominfo dot com)"
35.185.73.152 - - [21/Feb/2020:09:22:52 -0800] "GET / HTTP/1.0" 301 236 "-" "ZoominfoBot (zoominfobot at zoominfo dot com)"
194.33.127.25 - - [21/Feb/2020:09:27:02 -0800] "GET / HTTP/1.1" 200 1154 "-" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36"
128.14.134.170 - - [21/Feb/2020:09:27:26 -0800] "GET / HTTP/1.1" 200 1154 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36"
18.219.84.33 - - [21/Feb/2020:10:26:27 -0800] "GET / HTTP/1.1" 301 236 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.87 Safari/537.36"

On Fri, Feb 21, 2020 at 1:20 AM Scott van Looy via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

This is probably something super simple, but…

My httpd is failing on boot.

The server has 3x adaptors, all are static IPs and don’t require DHCP or anything. Addresses, etc are specified in the config files. All are present once boot has ended. All are managed by NetworkManager, yet I get this error in the log

Feb 21 07:40:15 <server> systemd[1]: Starting The Apache HTTP Server...

Feb 21 07:40:16 <server> httpd[1012]: [Fri Feb 21 07:40:16.208953 2020] [so:warn] [pid 1012:tid 140114180026688] AH01574: module ssl_module is already loaded, skipping

Feb 21 07:40:16 <server> httpd[1012]: (99)Cannot assign requested address: AH00072: make_sock: could not bind to address <my ip>:80

Feb 21 07:40:16 <server> httpd[1012]: no listening sockets available, shutting down

Feb 21 07:40:16 <server> httpd[1012]: AH00015: Unable to open logs

Feb 21 07:40:16 <server> systemd[1]: httpd.service: Main process exited, code=exited, status=1/FAILURE

Feb 21 07:40:16 <server> systemd[1]: httpd.service: Failed with result 'exit-code'.

Feb 21 07:40:16 <server> systemd[1]: Failed to start The Apache HTTP Server.

It’s like httpd is starting too early.

Looking at the service info I can see it’s supposed to start after network.target. Looking at its critical chain using systemd-analyze it seems to be doing this correctly. I’m kinda at a loss. Does anyone have any suggestions as to what I can try?

Scott

_______________________________________________
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

_______________________________________________
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