I run freeBSD on my server and I have a big problem. THe server often suddenly reboots. Just without any warning in the logs or what soever. It's very frustrating because it reboots about 10 times a day without chronological order.

And with every reboot the server is for 3 minutes unaccesseble.

Anyone know what it could be?! (my memory is fine, already checked that)

Check out your power supply, and NIC's sounds like an overheating problem or short with something inside.

How much bw is the server pushing? If you dont set the network buffer large enough it will cut all inet activity when the buffer is reached, possibly rebooting the server.

Server is only pushing 200 kb/sec so that shouldn't be an problem. Overheating, could be someone is checking out the system tempretature.

Maybe your box has been compromised ;)
What do your log files say about this ? :)

What does compromized exactly mean? (sorry I'm Dutch).

In my logs (that I checked) I couldn't find anything. :(

logs checked:
-httpd-error.log
-exim.log
-messages.log
-cron.log

Starhost,

Have you tried running 'dmesg -a' to see what kind of errors you may be having? I would imagine there would be some kind of kernel panic or some other event happening before the reboot.

Good luck,

Scott

I didn't do that. I now have done it and putted the result online ( http://phobos.starhost.nl/dmesg )

I don't understand much of it, so if you would be so kind to have a look at it, please

Starhost,

Sorry, dmesg -a only shows current stuff and since your machine is up right now, it is unlikely very effective. Try looking at /var/log/dmesg.today and /var/log/dmesg.yesterday, they may be more helpful and they may not be at all helpful.

Scott

I also putted them online:

http://phobos.starhost.nl/dmesg_today

I fixed the sendmail configure problem, but that isn't the problem.

Darn, sorry Starhost there isn't any evidence to your problem in there.

No kernel panic = no crash analysis = a clueless me. Good luck with this one, I believe you gots a hardware problem.

Scott

Noël,

Check the messages.log file again. Look for the last time it rebooted. What does it say just before the copyright line ? It might just say something about what's going on.
I killed my freebsd kernel some days ago (scott: you know why :) ) and it said this in the messages log:
Feb 4 18:51:40 VC2 /kernel: panic: page fault
Feb 4 18:51:40 VC2 /kernel:
Feb 4 18:51:40 VC2 /kernel: syncing disks... 13 1 1
Feb 4 18:51:40 VC2 /kernel: done

Btw starhost, I'm dutch too. Compromised means that someone broke into it. But if it doesn't say anything about this in the messages log, it is probably a hardware problem, because I think most crackers would reboot a server (IF they ever do this, because most of them want to stay unnoticed) by just running 'reboot'.

Nothing to find :(

T_E_O have you got ICQ or MSN? Talks better :)

Further more nothing to find in my /var/log/messages
Below a few lines from it:
See also: http://phobos.starhost.nl/messages


###########################################

Feb 7 18:01:34 phobos qpopper[5830]: Stats: admin 0 0 0 0 kabel213075.kabel.utwente.nl 130.89.213.75
Feb 7 18:01:35 phobos qpopper[5831]: Stats: hoststar 1 31639 0 0 kabel213075.kabel.utwente.nl 130.89.213.75
Feb 7 18:01:50 phobos qpopper[5832]: Stats: bestelling 0 0 5 61660 5dyndyn248.ogt.casema.net 213.17.122.248
Feb 7 18:02:00 phobos qpopper[5837]: (null) at phobos.starhost.nl (80.247.195.71): -ERR POP EOF or I/O Error
Feb 7 18:02:00 phobos qpopper[5837]: I/O error flushing output to client at phobos.starhost.nl [80.247.195.71]: Operation not perm
itted (1)
Feb 7 18:02:00 phobos qpopper[5837]: I/O error flushing output to client at phobos.starhost.nl [80.247.195.71]: Operation not perm
itted (1)
Feb 7 18:04:00 phobos qpopper[5853]: (null) at phobos.starhost.nl (80.247.195.71): -ERR POP EOF or I/O Error
Feb 7 18:04:00 phobos qpopper[5853]: I/O error flushing output to client at phobos.starhost.nl [80.247.195.71]: Operation not perm
itted (1)
Feb 7 18:04:00 phobos qpopper[5853]: I/O error flushing output to client at phobos.starhost.nl [80.247.195.71]: Operation not perm
itted (1)
Feb 7 18:05:00 phobos proftpd[5876]: phobos.starhost.nl (212.92.65.6[212.92.65.6]) - no such GID '100'
Feb 7 18:05:00 phobos proftpd[5876]: phobos.starhost.nl (212.92.65.6[212.92.65.6]) - no such GID '100'
Feb 7 18:05:00 phobos proftpd[5876]: no modules loaded for `ftp' service
Feb 7 18:05:00 phobos proftpd[5876]: phobos.starhost.nl (212.92.65.6[212.92.65.6]) - PAM(jslemmer): Permission denied.
Feb 7 18:05:00 phobos proftpd[5876]: phobos.starhost.nl (212.92.65.6[212.92.65.6]) - USER jslemmer: Login successful.
Feb 7 18:08:54 phobos /kernel: Copyright (c) 1992-2002 The FreeBSD Project.
Feb 7 18:08:54 phobos /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Feb 7 18:08:54 phobos /kernel: The Regents of the University of California. All rights reserved.

Try replacing the hard drive. We had the same problem and replacing the hard drive fixed it.

Tha harddrive? Was it broken? Or did it just work fine on another OS.
And what type of harddrive was it?

I'm using:

2* 20gb Maxtor U-100 5400r
raid mirroring by:
3ware6200 RAID strorage controller

The problem is solved, it turned out be be currept memory. Replacing it resolved our problem. hanx all who helped me.