Infos Crash serveur 1&1

Nouveau WRInaute
Bonjour,

je voudrais savoir si, quand un serveur crash, il est possible de récupérer un log avec les informations concernant le crash. Je parle plus particulièrement d'un serveur dédié sur 1&1.
Merci
 
WRInaute impliqué
Tu n'auras pas "le serveur a planté parce que ..." dans les logs, si c'est ce que tu veux savoir.

Tu peux toujours regarder les différents logs: du système (syslog), du noyau (kern ou kernel), Apache, MySQL ...
Et regarder aux alentours de l'heure du crash si il y a une information pertinente. Mais notamment dans le syslog, ça sera de l'info brut de décoffrage, il faut savoir l'analyser après.

Sous Debian, les différents logs sont dans /var/log/
 
Nouveau WRInaute
merci FloBaoti !
je suis allé dans /var/log mais je n'ai pas trouvé de syslog.

dossierlogti8.png



le serveur a crashé ce week end. En fait, il crash à peu près 5 à 6 fois par an et j'aimerais bien savoir pourquoi.
 
Nouveau WRInaute
j'ai ouvert le fichier messages. Voici le code correspondant à la période du crash.

ça vous parle ? parce que moi, j'y connais pas grand chose en log...

Code:
May  2 06:19:48 s15264876 last message repeated 4 times
May  2 06:20:52 s15264876 last message repeated 6 times
May  2 06:21:58 s15264876 last message repeated 4 times
May  2 06:23:12 s15264876 last message repeated 5 times
May  2 06:24:17 s15264876 last message repeated 7 times
May  2 06:24:28 s15264876 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
May  2 06:24:28 s15264876 dhclient: DHCPACK from 87.106.137.250
May  2 06:24:28 s15264876 dhclient: bound to 87.106.142.132 -- renewal in 83167 seconds.
May  2 07:47:59 s15264876 xinetd[2826]: START: smtp pid=27801 from=203.210.249.157
May  2 07:48:36 s15264876 xinetd[2826]: EXIT: smtp status=0 pid=27801 duration=37(sec)
May  2 07:49:03 s15264876 xinetd[2826]: START: smtp pid=27804 from=89.44.142.26
May  2 07:49:04 s15264876 xinetd[2826]: EXIT: smtp status=1 pid=27804 duration=1(sec)
May  2 12:48:29 s15264876 xinetd[2826]: START: smtp pid=29392 from=122.164.120.243
May  2 12:49:04 s15264876 xinetd[2826]: EXIT: smtp status=0 pid=29392 duration=35(sec)
May  2 17:08:49 s15264876 xinetd[2826]: START: smtp pid=30404 from=213.91.205.244
May  2 17:09:22 s15264876 xinetd[2826]: EXIT: smtp status=0 pid=30404 duration=33(sec)
May  2 21:05:47 s15264876 xinetd[2826]: START: ftp pid=31345 from=87.106.134.139
May  2 21:05:47 s15264876 proftpd[31345]: s15264876.onlinehome-server.info (87.106.134.139[87.106.134.139]) - FTP session opened. 
May  2 21:05:47 s15264876 proftpd[31345]: s15264876.onlinehome-server.info (87.106.134.139[87.106.134.139]) - FTP session closed. 
May  2 21:05:47 s15264876 xinetd[2826]: EXIT: ftp status=0 pid=31345 duration=0(sec)
May  2 21:10:50 s15264876 xinetd[2826]: START: ftp pid=31376 from=87.106.134.139
May  2 21:10:50 s15264876 proftpd[31376]: s15264876.onlinehome-server.info (87.106.134.139[87.106.134.139]) - FTP session opened. 
May  2 21:10:50 s15264876 proftpd[31376]: s15264876.onlinehome-server.info (87.106.134.139[87.106.134.139]) - FTP session closed. 
May  2 21:10:50 s15264876 xinetd[2826]: EXIT: ftp status=0 pid=31376 duration=0(sec)
May  2 22:25:51 s15264876 proftpd[32247]: s15264876.onlinehome-server.info (69.65.49.213[69.65.49.213]) - FTP session opened. 
May  2 22:25:51 s15264876 xinetd[2826]: START: ftp pid=32247 from=69.65.49.213
May  2 22:25:52 s15264876 proftpd[32247]: s15264876.onlinehome-server.info (69.65.49.213[69.65.49.213]) - FTP session closed. 
May  2 22:25:52 s15264876 xinetd[2826]: EXIT: ftp status=0 pid=32247 duration=1(sec)
May  5 11:41:28 s15264876 syslogd 1.4.1: restart.
May  5 11:41:28 s15264876 kernel: klogd 1.4.1, log source = /proc/kmsg started.
May  5 11:41:28 s15264876 kernel: Bootdata ok (command line is auto BOOT_IMAGE=lxser ro root=901 console=tty0 console=ttyS0,57600 panic=30)
May  5 11:41:28 s15264876 kernel: Linux version 2.6.16.53-070731a (root@buildd-amd64) (gcc version 3.3.5 (Debian 1:3.3.5-13)) #1 SMP Tue Jul 31 10:46:54 CEST 2007
May  5 11:41:28 s15264876 kernel: BIOS-provided physical RAM map:
May  5 11:41:28 s15264876 kernel:  BIOS-e820: 0000000000000000 - 000000000009e000 (usable)
May  5 11:41:28 s15264876 kernel:  BIOS-e820: 000000000009e000 - 00000000000a0000 (reserved)
May  5 11:41:28 s15264876 kernel:  BIOS-e820: 00000000000d0000 - 0000000000100000 (reserved)
May  5 11:41:28 s15264876 kernel:  BIOS-e820: 0000000000100000 - 000000003ef10000 (usable)
May  5 11:41:28 s15264876 kernel:  BIOS-e820: 000000003ef10000 - 000000003ef16000 (ACPI data)
May  5 11:41:28 s15264876 kernel:  BIOS-e820: 000000003ef16000 - 000000003ef80000 (ACPI NVS)
May  5 11:41:28 s15264876 kernel:  BIOS-e820: 000000003ef80000 - 0000000040000000 (reserved)
May  5 11:41:28 s15264876 kernel:  BIOS-e820: 00000000fc000000 - 00000000fe000000 (reserved)
May  5 11:41:28 s15264876 kernel:  BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
May  5 11:41:28 s15264876 kernel:  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
May  5 11:41:28 s15264876 kernel:  BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
May  5 11:41:28 s15264876 kernel: Scanning NUMA topology in Northbridge 24
May  5 11:41:28 s15264876 kernel: Number of nodes 1
May  5 11:41:28 s15264876 kernel: Node 0 MemBase 0000000000000000 Limit 000000003ef10000
May  5 11:41:28 s15264876 kernel: Using node hash shift of 63
May  5 11:41:28 s15264876 kernel: Bootmem setup node 0 0000000000000000-000000003ef10000
 
Discussions similaires
Haut