LinuxQuestions.org - Please check log system on Centos 5

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - Please check log system on Centos 5 (https://www.linuxquestions.org/questions/linux-newbie-8/please-check-log-system-on-centos-5-a-835146/)

Please check log system on Centos 5

Dear All,

Im using a server hosting and I just can work on the server via SSH.
Today, the server was died and I contacted ISP to find out the problem.
ISP said that the network were okay, please check log the server to find the reason.

But I don't know how to check...
I checked in /var/log/boot.log, it is empty.
And in /var/log/message and /var/log/dmesg: i don't understand... :(

Please help me...

Quote:

Originally Posted by chobong (Post 4112405)

...

But I don't know how to check...
I checked in /var/log/boot.log, it is empty.
And in /var/log/message and /var/log/dmesg: i don't understand... :(

Please help me...

What is it you do not understand?

So far you seem to be on the right track - checking the logs is a good step in the right direction to try to determine what happened to the server.

Are /var/log/messages and /var/log/dmesg and /var/log/syslog and /var/log/kernel all empty? Or do they contain stuff and you don't understand the data in the logs?

There could/should be a fairly large amount of data in these logs; you may or may not have every one of the files I mention, but those that are present, you want to examine the records leading up to the shutdown, and try to figure out what happened.

Please explain more thoroughly what it is you don't understand. Thanks!

Cheers.

Thanks GrapefruiTgirl

Sorry for I didn't explain clearly.
There is data in the /var/log/mesage and /var/log/dmesg but I don't know lines which relate the problem.

The file is too long, and I cannot paste in the forum... :(

Quote:

Originally Posted by chobong (Post 4112405)

Dear All,
Today, the server was died and I contacted ISP to find out the problem.

Server died means?You were not able to ssh it?
You were doing ssh from which system?
Where is server located?
Please let us know what that died means?
Which services were installed on the server?You mean to say those services not running on the server?

Quote:

Sorry you guys. Im really confused these days :(

The server is located in Germany, not in my country.
I couldn't connect by ssh,ping from my computer to server in some hours, so I contacted to ISP and then ISP rebooted the server.
Now the server is working fine but i don't know the reason why server was die.
I checked in /var/log folder with boot.log (empty), messages, dmesg but I really didn't find anything.
(Actually, dmesg and messages is long, and I can't understand all contents in these files)

Is there any other way to check this...?

Quote:

Originally Posted by chobong (Post 4113505)

(Actually, dmesg and messages is long, and I can't understand all contents in these files)

Check from timestamp when server shutdown (upload this to somewhere or paste into pastebin.com). Also check with dmesg command (not /var/log/dmesg).

Quote:

Check from timestamp when server shutdown (upload this to somewhere or paste into pastebin.com). Also check with dmesg command (not /var/log/dmesg).

Sorry, you mean what's "timestamp"?

When I run dmesg, it displayed these lines ( have no in /var/log/dmesg )

Code:

powernow-k8: Found 1 Quad-Core AMD Opteron(tm) Processor 1385 processors (4 cpu cores) (version 2.20.00)

powernow-k8:    0 : fid 0x0 gid 0x0 (2700 MHz)

powernow-k8:    1 : fid 0x0 gid 0x0 (2000 MHz)

powernow-k8:    2 : fid 0x0 gid 0x0 (1500 MHz)

powernow-k8:    3 : fid 0x0 gid 0x0 (800 MHz)

ip_tables: (C) 2000-2006 Netfilter Core Team

Netfilter messages via NETLINK v0.30.

ip_conntrack version 2.4 (8192 buckets, 65536 max) - 304 bytes per conntrack

tg3: eth0: Link is up at 100 Mbps, full duplex.

tg3: eth0: Flow control is off for TX and off for RX.

NET: Registered protocol family 10

lo: Disabled Privacy Extensions

IPv6 over IPv4 tunneling driver

eth0: no IPv6 routers present

TCP: Treason uncloaked! Peer 84.183.92.114:49202/80 shrinks window 3016473706:3016512272. Repaired.

TCP: Treason uncloaked! Peer 217.15.116.126:20826/80 shrinks window 2256082214:2256082215. Repaired.

TCP: Treason uncloaked! Peer 217.15.116.126:20829/80 shrinks window 2258868427:2258868428. Repaired.

TCP: Treason uncloaked! Peer 217.15.116.126:20829/80 shrinks window 2258868427:2258868428. Repaired.

TCP: Treason uncloaked! Peer 217.15.116.126:20831/80 shrinks window 2269474238:2269474239. Repaired.

TCP: Treason uncloaked! Peer 217.15.116.126:20831/80 shrinks window 2269474238:2269474239. Repaired.

TCP: Treason uncloaked! Peer 213.209.163.110:55613/80 shrinks window 2150450065:2150450066. Repaired.

TCP: Treason uncloaked! Peer 213.209.163.110:55716/80 shrinks window 2189063760:2189063761. Repaired.

TCP: Treason uncloaked! Peer 213.209.163.110:55733/80 shrinks window 2191591743:2191591744. Repaired.

TCP: Treason uncloaked! Peer 213.209.163.110:55716/80 shrinks window 2189063760:2189063761. Repaired.

TCP: Treason uncloaked! Peer 79.240.204.161:52413/80 shrinks window 50105669:50119288. Repaired.

TCP: Treason uncloaked! Peer 79.240.204.161:52413/80 shrinks window 50105669:50119288. Repaired.

TCP: Treason uncloaked! Peer 79.240.204.161:49511/80 shrinks window 63916317:63926585. Repaired.

TCP: Treason uncloaked! Peer 79.240.204.161:47734/80 shrinks window 61463495:61477015. Repaired.

TCP: Treason uncloaked! Peer 79.240.204.161:33088/80 shrinks window 148229886:148230440. Repaired.

TCP: Treason uncloaked! Peer 208.78.63.100:1681/80 shrinks window 207850964:207850965. Repaired.

TCP: Treason uncloaked! Peer 208.78.63.100:1818/443 shrinks window 1274838439:1274838440. Repaired.

TCP: Treason uncloaked! Peer 208.78.63.100:1818/443 shrinks window 1274838439:1274838440. Repaired.

TCP: Treason uncloaked! Peer 208.78.63.100:1825/443 shrinks window 1306784212:1306784213. Repaired.

TCP: Treason uncloaked! Peer 208.78.63.100:1825/443 shrinks window 1306784212:1306784213. Repaired.

TCP: Treason uncloaked! Peer 208.78.63.100:1841/443 shrinks window 1393472894:1393472895. Repaired.

My server crashed two times, and after reboot, found no problem in the log file :( .
The cause can be
- kernel panic?
- network problem?
- hardware problem?
- software problem?

I don't know when it will be crashed and how to fix it...

Please help me ...
Thank you so much!