Koozali.org: home of the SME Server

server crashed help

darren

server crashed help
« on: December 03, 2001, 04:29:11 AM »
server crashed a 3am on 1st dec and i can't find out why

Chris O'Donovan

Re: server crashed help
« Reply #1 on: December 03, 2001, 05:26:44 AM »
Post the last few dozen entries from /var/log/messages from just before the crash as well as any details on what the server was doing at the time. The server's configuration would also be helpful.

Without further information there is little that anyone can do to help.

Spontaneous crashes are often caused by hardware failure or power fluctuations. Have you added any hardware to the machine in the past week or so and is the server on a UPS?

Also, was anyone around at 3am such as cleaners? Could they have unplugged the server?

Chris

darren

Re: server crashed help
« Reply #2 on: December 03, 2001, 06:02:38 AM »
basically when checked the machine all the lights were on but knowbody was home couldn't gain access from any terminals or even direct access the monitor wouldn't power up untill i reset the server then i had to fsck /dev/hda6 to fix all the errors.
I also have a ups on the server.



Nov 30 11:38:14 server named[1327]: "ravantivirus.com IN MX" points to a CNAME (mx1.gecadsoftware.com)
Nov 30 11:38:14 server named[1327]: "ravantivirus.com IN MX" points to a CNAME (mx2.gecadsoftware.com)
Nov 30 21:38:15 server identd[30841]: Successful lookup: 4580 , 25 : qmailr.qmail
Nov 30 22:47:01 server identd[30984]: Successful lookup: 4617 , 25 : qmailr.qmail
Nov 30 22:47:03 server identd[30986]: Successful lookup: 4618 , 25 : qmailr.qmail
Nov 30 23:35:30 server dhcpd: DHCPREQUEST for 192.168.1.21 from 00:40:c7:2e:1d:df via eth0
Nov 30 23:35:30 server dhcpd: DHCPACK on 192.168.1.21 to 00:40:c7:2e:1d:df via eth0
Dec  1 02:29:32 server dhcpd: DHCPREQUEST for 192.168.1.29 from 00:48:54:64:54:06 via eth0
Dec  1 02:29:32 server dhcpd: DHCPACK on 192.168.1.29 to 00:48:54:64:54:06 via eth0
Dec  1 02:40:34 server identd[31413]: Successful lookup: 4684 , 25 : qmailr.qmail
Dec  1 11:03:13 server syslogd 1.3-3: restart.


i also found this in the cron log which shows the server was working till 4:40

Dec  1 02:20:00 server CROND[31385]: (root) CMD (   /sbin/rmmod -as)
Dec  1 02:30:00 server CROND[31395]: (root) CMD (/bin/nice /sbin/e-smith/awstats-pp -s -n)
Dec  1 02:30:00 server CROND[31396]: (root) CMD (   /sbin/rmmod -as)
Dec  1 02:40:00 server CROND[31408]: (root) CMD (   /sbin/rmmod -as)
Dec  1 02:50:00 server CROND[31430]: (root) CMD (   /sbin/rmmod -as)
Dec  1 03:00:00 server CROND[31436]: (root) CMD (/bin/nice /sbin/e-smith/awstats-pp -s -n)
Dec  1 03:00:00 server CROND[31437]: (root) CMD (   /sbin/rmmod -as)
Dec  1 03:01:00 server CROND[31439]: (root) CMD (run-parts /etc/cron.hourly)
Dec  1 03:10:00 server CROND[31446]: (root) CMD (   /sbin/rmmod -as)
Dec  1 03:20:00 server CROND[31451]: (root) CMD (   /sbin/rmmod -as)
Dec  1 03:30:00 server CROND[31455]: (root) CMD (/bin/nice /sbin/e-smith/awstats-pp -s -n)
Dec  1 03:30:00 server CROND[31456]: (root) CMD (   /sbin/rmmod -as)
Dec  1 03:40:00 server CROND[31458]: (root) CMD (   /sbin/rmmod -as)
Dec  1 03:50:00 server CROND[31461]: (root) CMD (   /sbin/rmmod -as)
Dec  1 04:00:00 server CROND[31473]: (root) CMD (/bin/nice /sbin/e-smith/awstats-pp -s -n)
Dec  1 04:00:00 server CROND[31474]: (root) CMD (   /sbin/rmmod -as)
Dec  1 04:01:00 server CROND[31476]: (root) CMD (run-parts /etc/cron.hourly)
Dec  1 04:02:00 server CROND[31484]: (root) CMD (run-parts /etc/cron.daily)
Dec  1 04:02:01 server anacron[31488]: Updated timestamp for job cron.daily' to 2001-12-01
Dec  1 04:10:00 server CROND[31537]: (root) CMD (   /sbin/rmmod -as)
Dec  1 04:20:00 server CROND[31539]: (root) CMD (   /sbin/rmmod -as)
Dec  1 04:30:00 server CROND[31546]: (root) CMD (/bin/nice /sbin/e-smith/awstats-pp -s -n)
Dec  1 04:30:00 server CROND[31547]: (root) CMD (   /sbin/rmmod -as)
Dec  1 04:40:00 server CROND[31549]: (root) CMD (   /sbin/rmmod -as)
Dec  1 11:03:18 server crond[692]: (CRON) STARTUP (fork ok)

Chris O'Donovan

Re: server crashed help
« Reply #3 on: December 04, 2001, 07:07:30 AM »
darren wrote:

> even direct access the monitor wouldn't power up untill i
> reset the server


Is power saving enabled in the bios?

darren

Re: server crashed help
« Reply #4 on: December 04, 2001, 08:19:38 AM »
i had been running 4.12 for about 4 months and had the server running for 8 days before it crashed
to my knowledge the power saving is not on.
i did find an error in the cron.weekly (to update the dns)
exec /sbin/e-smith/events/actions/update-dns
to exec /etc/e-smith/events/actions/update-dns

Richard Emory

Re: server crashed help
« Reply #5 on: December 05, 2001, 08:42:10 PM »
My server is also now having random crashes.  The internal network is shut-off but I can still access the server from the outside via-SSH telnet.  Internally there is no access to SSH, SMB, SMTP or TCP/IP http.

How would I narrow it down to the NIC or HUB or something inside the server?

How would I give you the server's configuration?

Sean

Re: server crashed help
« Reply #6 on: December 15, 2001, 11:57:57 PM »
Also having random lockups.  Cannot access the system from the LAN or even the Monitor and Keyboard.  I originaly thought it was a conflict with the CDROM drive and disabled it in the BIOS but still locks up.  The only non-standard thing with my server is I have enabled IPSEC Masquerading.  I am using a Checkpoint Client to accessmy company throught a Checkpoint Firewall.  It only seems to crash after the VPN client has been up and running for a long period of time.

Could this be a Freeswan problem???

Sean

Re: server crashed help
« Reply #7 on: December 15, 2001, 11:57:58 PM »
Also having random lockups.  Cannot access the system from the LAN or even the Monitor and Keyboard.  I originaly thought it was a conflict with the CDROM drive and disabled it in the BIOS but still locks up.  The only non-standard thing with my server is I have enabled IPSEC Masquerading.  I am using a Checkpoint Client to accessmy company throught a Checkpoint Firewall.  It only seems to crash after the VPN client has been up and running for a long period of time.

Could this be a Freeswan problem???