Server down "no listening sockets available, shutting down"
============================================
no listening sockets available, shutting down
Unable to open logs
[FAILED]
Starting crond: [ OK ]
Starting xfs: [ OK ]
[ OK ] atd: [ OK ]
Starting Avahi daemon… [FAILED]
CentOS release 5.8 (Final)
Kernel 2.6.18.8-linode22 on an i686
localhost login:
============================================
Now, I could spend a lot of time trying to troubleshoot this, but I'm not that knowledgeable (yet), so I think my best solution is to just take my losses and rebuild to the newer CentOS and start over. However… there are files I need to back up, and without FTP access, I don't know how to get my files off. So, my question is… it's okay if the sites stay down for now, but how do I logon to get my files? Also, any ideas as to what caused this would be helpful, so when rebuilding I can keep an eye out for whatever the trouble was.
As you can tell, I'm somewhat of a newbie to this, but am willing to work at it.
Thanks for any ideas/help.
Joyce.
10 Replies
Via Lish - stop the httpd service (chkconfig httpd off) then reboot.
If it boots ok, then you know that was the problem. Either roll back to a previous copy of httpd.conf, or troubleshoot what's causing the sockets available error (probably the Listen 80 line got messed up).
I setup a backup, but not sure if that will be a help, as whatever the problem is will be included in the backup
-Joyce.
[1271634] Emergency Reboot - atlanta19
Hello,
The host your Linode resides on (atlanta19) became unresponsive to our monitoring, and required a host reboot to resolve. Our system administrators are currently working to bring the host back online, and we'll let you know once they've completed this.
Regards,
Then, this.
Hello,
The host that your Linode resides on has been successfully rebooted. Your Linode will return to its last state shortly (running or powered off).
There is no need to issue boot jobs for your Linode at this time.
Thank you for your patience and understanding. Please feel free to update this ticket in the event that you have any additional questions or concerns about this matter.
Regards,
This seems to be about the time things went wrong, but didn't follow up, as it was considered resolved (my bad). Will follow up with them.
-Joyce.
@jah013:
This seems to be about the time things went wrong, but didn't follow up, as it was considered resolved (my bad). Will follow up with them.
no, the issue with the host is very likely fixed. your linode probably has a configuration problem that is preventing it from booting. Look in lish and see what the first thing to fail is.
-Joyce.
Thanks,
-Joyce.
Thanks to all who gave suggestions. It's good to know there is such a valuable resource as these forums. Thanks again.
-Joyce.