We have a problem machine that keeps freezing, linux says exiting on signal 15, whats signal 15?

Thanks

In general signal 15 is another word for the command kill...

Signal 15 is the general term for politely kiling a proccess...

Whats the context of the error message?

....
Jul 17 03:28:39 www rpc.statd[602]: Caught signal 15, un-registering and exiting.
Jul 17 03:28:39 www nfslock: rpc.statd shutdown succeeded
Jul 17 03:28:40 www portmap: portmap shutdown succeeded
Jul 17 03:28:40 www kernel: Kernel logging (proc) stopped.
Jul 17 03:28:40 www kernel: Kernel log daemon terminating.
Jul 17 03:28:41 www syslog: klogd shutdown succeeded
Jul 17 03:28:41 www exiting on signal 15

And this is during normal run-time?...

Nothing before that log that you provided shows any other errors?

The term "Caught signal 15" means that it is the machine is getting a command to shutdown from somewhere..... I really can't tell where from that...

Anyone seen this problem before?

Now it just freezes for now reason - total lockup - keyboard the works.
I've run diagnostic software on all the ram chips and the hardrives. Its in a 1u case, is it possible that its just overheating and shuts down? It has a cpu fan and 5 case fans.. thanks

Whats the chipset and mobo?...

This really does sound like a hardware problem....
Depending on your mobo it could account for the shutdowns. If the mobo and OS communicate when the chip temp would get too high it would shutdown (Signal 15 the OS) to protect itself.

Just a theory....

The MB is SuperMicro 370 DLI

Well that Mobo is Pentium III specific... So it probably interfaces very welll w/ it... Don't know any techincal specs off the top of my head for it....

But, this is beginning to sound a little like a CPU problem...

Has the unit been moved or bumped around recently?
If so the heatsink or fan might have been moved off the CPU. Also check to see if the CPU fan is working. If this happens when the chip will begin to heat up to the point until it will freeze itself to protect itself...

Check the heat sink is seated properly on the CPU... Make sure the CPU fan starts.

When does it freeze? On boot? During heavy load? After sitting idle?...

There is no load - its not an active server its standing by - the only activity is me logging into ssh

I know the cpu fan works and turns on and is in place - but its a 1u case and the fan goes right upto the top so im guessing now that it is probably overheating....
now the problem is, this mb is extra large(?) and wont fit in our standard atx cases, so we had to put it in the 1u and cut off the backplate of the 1u - :(

We have another mb shipment coming this week, ill put it in an atx case and let you know

I installed a software watchdog however i dont think it will work in this situation :)

Thanks :)

Hardware issues are always weird. Just because you can't get the visual feedback of a software problem...

I've spent alot of time dealing w/ weirder issues than this, so feel lucky, I guess :D.....

Good luck.

lol, it could be alot worse
I just sent a Tyan MB back to them for replacement, woulnt boot with dual cpu's first, then after a day it did. Then raid would give errors while syncing the disks in their bios and if i tried it in linux... both hds work and are verified good (same with ram) - then the power switch wouldnt work and it would freeze at random times, (wouldnt run for 24 hours) and finally, it wont boot at all now so i sent it back...

What have you gone through :)?

Just recently had a weird an currently un-explained problem w/ ATX power supply (I think, I still don't know what is causing it)...

It will run great for days on end. Uptime of 125 days at max. Shut down to strap in another HD turned it back on, after about 3 seconds (not even half way through the BIOS POST proccess) it would simply just power off....

So I unplug the new HD turn back on. Same problem. Check (not unplug or move any of the connectors) the power supply cables to all the connections. Turn it back on... Boots perfectly...

Plug the new HD back in. Boots perfectly.

Runs fine. Another month goes by. Servers got a few too many zombie proccesses for my liking and don't feel like manually killing them. Power off to cold boot (don't know why, just felt like it) turn back on, same problem again. On for a few seconds then cuts off.

I got extremly frustrated at this point. Turned it on and start recording the POST codes off the Mobo and start researching their meanings... Nothing signifigant. During this time it's just sitting there off.... When I come back w/ no answers I turn it back on. Boots fine...

I still have no clue why or what is causng it... I just refused to turn it off :D... Just reboot instead of powering off.....