[arch-general] Apache dead after kernel update - make_sock: could not bind to address [::]:443 - (Solved by 2nd Reboot)
Guys, I don't know what's up here, but I updated the system ( no [testing] ), and rebooted to load the new kernel, and http was dead. On start, the error said it couldn't bind to port 443 because it was already taken -- Huh? Here are what little details I could come up with: [23:28 nirvana:/home/david] # lsof -i | grep 443 [23:28 nirvana:/home/david] # apachectl stop httpd (no pid file) not running [23:28 nirvana:/home/david] # apachectl start (98)Address already in use: make_sock: could not bind to address [::]:443 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:443 no listening sockets available, shutting down Unable to open logs First time I've seen this one. The latest system update completed fine, so I should be up to date. Apache is: apache 2.2.15-2 php-apache 5.3.2-6 the kernel is: kernel26-2.6.33.2-1-x86_64.pkg.tar.xz kernel26-headers-2.6.33.2-1-x86_64.pkg.tar.xz I have a second x86_64 Arch box where the hardware and config is close to what I have on the problem box and apache it was working fine. I don't know what the issue was because the problem cured itself on reboot. This is just fyi in case anyone else experiences the same issue. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On 12/04/10 07:53, David C. Rankin wrote:
Guys,
I don't know what's up here, but I updated the system ( no [testing] ), and rebooted to load the new kernel, and http was dead. On start, the error said it couldn't bind to port 443 because it was already taken -- Huh?
Here are what little details I could come up with:
[23:28 nirvana:/home/david] # lsof -i | grep 443 I'm not sure what could have happened there but, to see what's running on a port, you'll want to use netstat instead: `netstat -ntpl | grep :443` you may need to run as root in order to see the process name but it should at least show you if something is listening on a particular port.
participants (2)
-
David C. Rankin
-
Nathan Wayde