ReliableServers
03-16-2002, 07:52 PM
I have a Freebsd server that crashes at random it seems. Thing are fine and then it just dies. I have checked the logs and havent found anything helpful in them. Today when it crashed I got this error on my ssh session "Command terminated on signal 11." Any ideas what could be causing this.....ram gone bad? Over heating? etc...?
Thanks
Shyne
03-16-2002, 07:58 PM
Signal 11 is a hardware problem, so yes try to replace the ram.
cperciva
03-16-2002, 08:04 PM
Well, sig 11 isn't always a hardware problem... but yes, it most likely is. (Try running a make buildworld; if you get sig 11s then it's a pretty clear sign of a hardware error.)
Bad memory often causes this, but so does inadequate cpu cooling. On rare occasions it will even be caused by poorly seated IDE cables.
ReliableServers
03-17-2002, 12:00 AM
Thanks for the replys, I will test those things out. The harddisk is a 10K rpm scsi, if its get hot could this shut off and cause the problem possibly too? I didnt have any problems for a few months until last week I moved the server to be between 2 others to make more space(1u servers)so heat is first what came to my mind.
Thanks
ReliableServers
03-17-2002, 05:04 PM
Mar 17 12:05:34 www2 /kernel: CRC Value Mismatch
Mar 17 12:05:34 www2 /kernel: (da0:ahc0:0:0:0): READ(10). CDB: 28 0 0 a6 f2 8f 0 0 20 0
Mar 17 12:05:34 www2 /kernel: (da0:ahc0:0:0:0): ABORTED COMMAND asc:48,0
Mar 17 12:05:34 www2 /kernel: (da0:ahc0:0:0:0): Initiator detected error message received
Mar 17 12:05:34 www2 /kernel: (da0:ahc0:0:0:0): parity error detected in Data-in phase. SEQADDR(0x8b) SCSIRATE(0xc2)
Found this in the /var/log/messages today after/durring its crash.
The box is up, and I see these lines being inserted while the server is online...
Thanks