[cobalt-users] The ongoing saga of the dying RaQ3

[Chae <chae@xxxxxxxxxxxx>]

Hi Yah,

If you remember I have the RaQ3 that keeps dying on me - well not dying the 
servers still up but no-one can access it via http, ftp or ssh, logcheck 
still shows that when the servers unaccessible active monitor still does it 
thing, as does mailscanner switching off and then on every four hours and 
also FCheck shows up on the hour. After a reboot's done everything is back 
to normal, the server doesn't go down at the same time and it doesn't go 
down when rotating logs either.

A lot of you suggested that it could be a network connection problem, loose 
connection, faulty network card etc.

Spoke to my colo and sent them copies of the logs and snippets from my 
emails sent here and explained the scenario to them and this is all I got 
back from them :(

"...that's an internal sendmail error. 127.0.0.1 is the loopback ip. it's 
not a "network" per say. just a virtual ip that daemons use to refer back 
to themselves.
if any program has problems connecting to 127.0.0.1 it is definitely a 
problem with the daemon/daemon configuration."

So I'm back to square one again or I have a colo who doesn't want to open 
up the RaQ3 to check the network card etc or doesn't want to go to the 
bother of doing it :(

Anyone any suggestions on how I can pin-point the problem myself - can't 
access this server as it's half-way round the world.

Regards

Chae