Web Hosting Talk







View Full Version : Sun CObalt RaQ4 - Major Problem, Server down - Please Help...


platinum112
08-04-2004, 04:59 PM
I have a Sun Cobalt RaQ4; apparently the root partiton has filled up. This has happened before, but I wasn't here when it happened.

I have not rebooted the machine yet.

Port 21 is OPEN, but if I connect to it, it disconnects me immedietly.
Port 80 is no longer open.
Port 53 is open, and works correctly.
Port 25 is open, and works correctly.
Port 110 is open, but disconnects immedietly.
SSH2 port is open, and if I try to telnet to it, it'll give me the OpenSSH2 message. If i use my normal SSH2 client (SecureCRT) which I've been using succesfully, I cannot connect to the box.

No users have been created or modified, so the user files should still be intact, since the cobalt generally won't currupt those files until theyre modified.

Last time this happened, I remember the person here had to use a Serial cable to get into it and delete some files from it, but I don't know what steps you have to take to use a serial connection.

I already have a laptop and a serial cable in there by the server connected, but I'm not getting anything. I'm assuming I'll have to restart the box for that to happen.

Any help would be greatly appreciated.

Thanks!!

Joe

galacnet
08-06-2004, 04:53 AM
Are you still able to enter the command prompt via the SSH or TelNet?
I had something like tis happen when one of the user's mail/spool was filled up and started to make the unit go crazy.
The user was a administrative user thats why...
Check if your httpd, root or admin user is full.

huck
08-06-2004, 09:28 AM
You may need to connect through the console and clear up some space. I advice shutting the system down until you can clear out some space. Once you clear some space, things should return to normal. I have, however, seen file corruption due to a full / partition. This mainly happens if you use the control panel to edit settings -- the raq does not have room to rewrite the file properly and can cause errors.

blacknight
08-29-2004, 12:34 PM
If it is refusing connections but still responding to ping it could be that the load is too high. If you have physical access to the machine you should be able to connect to it directly using a console, or get someone in the data center to do it. If it is load related then a reboot followed by shutting down as many services as possible from the console should help. Once you can gain access to the server over ssh you'll need to move files off the root partition.