New server and problems

K

kilobit

Verified User
Joined
Feb 8, 2006
Messages
22
Hello, i just upgraded computers to a faster computer with more space and did a scratch install of da. Everything went smoothly. After that i went home and configured a clients site (basic webpage). Well about 3am the server went down and did not come back up untill 10:30am the next day. I cannot for the life of me figure out why. This is a minimal install of centos and then the da install. After that i intalled the apf firewall script posted in this board, then i installed imagemagick. Thats it. Here is my log when it happened.

Code: 
Jan  8 02:37:48 server named[2912]: lame server resolving 'NEGAI.NET' (in 'NEGAI.NET'?): 8.7.49.254#53
Jan  8 02:37:56 server named[2912]: lame server resolving 'AUTOELECTRICMOTORS.COM' (in 'AUTOELECTRICMO
TORS.com'?): 74.52.58.162#53
Jan  8 02:37:56 server named[2912]: lame server resolving 'AUTOELECTRICMOTORS.COM' (in 'AUTOELECTRICMO
TORS.com'?): 74.52.58.163#53
Jan  8 02:38:22 server named[2912]: client 82.165.148.17#2164: error sending response: host unreachabl
e
Jan  8 03:29:43 server shutdown: shutting down for system halt
Jan  8 03:29:43 server init: Switching to runlevel: 0
Jan  8 03:29:44 server shutdown: shutting down for system halt
Jan  8 03:29:44 server last message repeated 7 times
Jan  8 03:29:45 server cups-config-daemon: cups-config-daemon -TERM succeeded
Jan  8 03:29:45 server haldaemon: haldaemon -TERM succeeded
Jan  8 03:29:45 server messagebus: messagebus -TERM succeeded
Jan  8 03:29:45 server shutdown: shutting down for system halt
Jan  8 03:29:45 server last message repeated 5 times
Jan  8 03:29:45 server atd: atd shutdown succeeded
Jan  8 03:29:45 server cups: cupsd shutdown succeeded
Jan  8 03:29:45 server xfs[3414]: terminating
Jan  8 03:29:45 server xfs: xfs shutdown succeeded
Jan  8 03:29:45 server gpm: gpm shutdown succeeded
Jan  8 03:29:45 server proftpd[5769]: server.data-donkey.com - ProFTPD killed (signal 15)
Jan  8 03:29:45 server proftpd[5769]: server.data-donkey.com - ProFTPD 1.2.10 standalone mode SHUTDOWN

Jan  8 03:29:45 server proftpd: proftpd shutdown succeeded
Jan  8 03:29:46 server vm-pop3d: vm-pop3d shutdown succeeded
Jan  8 03:29:46 server directadmin: directadmin shutdown succeeded
Jan  8 03:29:46 server sshd: sshd -TERM succeeded
Jan  8 03:29:46 server da-popb4smtp: da-popb4smtp shutdown succeeded
Jan  8 03:29:46 server exim: Shutting down exim:
Jan  8 03:29:46 server exim:
Jan  8 03:29:46 server rc: Stopping exim:  succeeded
Jan  8 03:29:46 server smartd[3203]: smartd received signal 15: Terminated
Jan  8 03:29:46 server smartd[3203]: smartd is exiting (exit status 0)
Jan  8 03:29:46 server smartd: smartd shutdown succeeded
Jan  8 03:29:46 server named[2912]: shutting down
Jan  8 03:29:46 server named[2912]: stopping command channel on 127.0.0.1#953
Jan  8 03:29:46 server named[2912]: stopping command channel on ::1#953
Jan  8 03:29:46 server named[2912]: no longer listening on 127.0.0.1#53
Jan  8 03:29:46 server named[2912]: no longer listening on 216.54.211.82#53
Jan  8 03:29:46 server named[2912]: no longer listening on 216.54.211.83#53
Jan  8 03:29:46 server named[2912]: no longer listening on 216.54.211.84#53
Jan  8 03:29:46 server named[2912]: no longer listening on 216.54.211.85#53
Jan  8 03:29:46 server named[2912]: no longer listening on 216.54.211.86#53
Jan  8 03:29:46 server named[2912]: exiting
Jan  8 03:29:46 server named: named shutdown succeeded
Jan  8 03:29:47 server xinetd[6221]: Exiting...
Jan  8 03:29:47 server xinetd: xinetd shutdown succeeded
Jan  8 03:29:47 server acpid: acpid shutdown succeeded
Jan  8 03:29:47 server crond: crond shutdown succeeded
Jan  8 03:29:47 server rpc.statd[3101]: Caught signal 15, un-registering and exiting.
Jan  8 03:29:47 server nfslock: rpc.statd shutdown succeeded
Jan  8 03:29:47 server irqbalance: irqbalance shutdown succeeded
Jan  8 03:29:47 server portmap: portmap shutdown succeeded
Jan  8 03:29:47 server kernel: Kernel logging (proc) stopped.
Jan  8 03:29:47 server kernel: Kernel log daemon terminating.
Jan  8 03:29:49 server syslog: klogd shutdown succeeded
Jan  8 03:29:49 server exiting on signal 15
Jan  8 10:28:51 server syslogd 1.4.1: restart.
Jan  8 10:28:51 server syslog: syslogd startup succeeded
Jan  8 10:28:51 server kernel: klogd 1.4.1, log source = /proc/kmsg started.
Jan  8 10:28:51 server kernel: Linux version 2.6.9-42.ELsmp (buildcentos@build-i386) (gcc version 3.4.
6 20060404 (Red Hat 3.4.6-3)) #1 SMP Sat Aug 12 09:39:11 CDT 2006
Jan  8 10:28:51 server kernel: BIOS-provided physical RAM map:
Jan  8 10:28:51 server kernel:  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
Jan  8 10:28:51 server kernel:  BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
Jan  8 10:28:51 server kernel:  BIOS-e820: 00000000000e6000 - 0000000000100000 (reserved)
Jan  8 10:28:51 server kernel:  BIOS-e820: 0000000000100000 - 000000003f72f800 (usable)
Jan  8 10:28:51 server kernel:  BIOS-e820: 000000003f72f800 - 000000003f730000 (ACPI NVS)
Jan  8 10:28:51 server kernel:  BIOS-e820: 000000003f730000 - 000000003f740000 (ACPI data)
Jan  8 10:28:51 server kernel:  BIOS-e820: 000000003f740000 - 000000003f7f0000 (ACPI NVS)
Jan  8 10:28:51 server kernel:  BIOS-e820: 000000003f7f0000 - 000000003f800000 (reserved)
Jan  8 10:28:51 server kernel:  BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
 
That looks like what you'd get if someone was logged in as root and typed system -h now.

(Don't do that unless you want to make a trip to the data center.)

The only way to bring a system up from a halt is to powercyle it.

See this line:
Code: 
Jan  8 10:28:51 server syslogd 1.4.1: restart.
???

That's what you get when you restart the server by power-cycling it.

Jeff
 
This is kind of a serious matter for me. 2 things could have happened. There was a guy at the datacenter that night but i seriously doubt he would do that but he could have it the power button making it halt. Then W.O.L could have woke it up but that wouldnt explain me having tried it that morning at 7am then it woke it 10.30?

Second what would have happened if the usb drive i had plugged into it temporarily cause the computer to shut down in the middle of the night? Or what if the power button stuck on the machine at that time?

I am really concerned for my server and if it wasnt something from da and a new machine which a hard root pass is used, i dont see how that could have been cracked considering there were no logs from ssh?

Very weird and i had the guy at the datacenter look at it and he thought it was very strange himself.
 
You must log in or register to reply here.
Back
Top