Serveur de fichier qui plante (2 fois en 2 mois)
C'est un serveur de fichiers, allumé en permanence, configuré en RAID5
pour le stockage des fichiers de la boite.
Ca fait la deuxième fois qu'il plante, pour une raison que je n'arrive
pas à comprendre.
C'est une version d'ubuntu server sans LAMP installé, avec le minimum de
services (pas d'interface graphique, juste webmin et cups pour le gérer
à distance)
quand il plante, les PC clients (sous windowsXP) ne trouvent plus le
serveur, mais peuvent faire un ping et acceder à l'interface de webmin.
Par contre webmin ne semble pas arriver a redémarrer correctement Samba,
il faut donc que j'aille dans la salle ou se trouve le serveur et le
redémarrer en pressant le bouton reset, car je n'arrive plus à me loguer
dessus.
Même si j'ai peu d'espoir, voici le syslog:
Dec 14 15:42:10 filesserver kernel: [1369508.137447] smbd[15341] trap
invalid opcode rip:2ae448440e80 rsp:7fff630bcee8 error:0
Dec 14 15:48:10 filesserver kernel: [1369867.935099] Unable to handle
kernel NULL pointer dereference at 0000000000000008 RIP:
Dec 14 15:48:10 filesserver kernel: [1369867.935260]
<ffffffff881c8a64>{:ext3:walk_page_buffers+52}
Dec 14 15:48:10 filesserver kernel: [1369867.948783] PGD 211cf067 PUD
f6f6067 PMD 0
Dec 14 15:48:10 filesserver kernel: [1369867.953544] Oops: 0000 [1] SMP
Dec 14 15:48:10 filesserver kernel: [1369867.958363] CPU 0
Dec 14 15:48:10 filesserver kernel: [1369867.963189] Modules linked in:
iptable_filter ip_tables x_tables ipv6 sbp2 lp tsdev snd_hda_intel
snd_hda_codec usblp snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd
soundcore serio_raw psmouse parport_pc parport sg snd_page_alloc floppy
evdev pcspkr shpchp pci_hotplug ext3 jbd raid5 md_mod xor usbhid
forcedeth ohci1394 ieee1394 ehci_hcd ohci_hcd usbcore ide_generic ide_cd
cdrom generic amd74xx sd_mod sata_nv libata scsi_mod thermal processor
fan vesafb capability commoncap vga16fb cfbcopyarea vgastate cfbimgblt
cfbfillrect fbcon tileblit font bitblit softcursor
Dec 14 15:48:10 filesserver kernel: [1369868.009168] Pid: 211, comm:
pdflush Not tainted 2.6.17-10-generic #2
Dec 14 15:48:10 filesserver kernel: [1369868.014949] RIP:
0010:[_end+129542756/2130452480]
<ffffffff881c8a64>{:ext3:walk_page_buffers+52}
Dec 14 15:48:10 filesserver kernel: [1369868.020684] RSP:
0018:ffff810037e9bb98 EFLAGS: 00010246
Dec 14 15:48:10 filesserver kernel: [1369868.031607] RAX:
0000000000000000 RBX: 0000000000000000 RCX: 0000000000001000
Dec 14 15:48:10 filesserver kernel: [1369868.042843] RDX:
0000000000000000 RSI: 0000000000000000 RDI: ffff810028b193d8
Dec 14 15:48:10 filesserver kernel: [1369868.054032] RBP:
0000000000000000 R08: 0000000000000000 R09: ffffffff881c8ad0
Dec 14 15:48:10 filesserver kernel: [1369868.065555] R10:
0000000000000000 R11: 0000000000000000 R12: 0000000000000000
Dec 14 15:48:10 filesserver kernel: [1369868.077153] R13:
0000000000000000 R14: ffff8100238fc730 R15: 0000000000000000
Dec 14 15:48:10 filesserver kernel: [1369868.089059] FS:
00002ae4498ba080(0000) GS:ffffffff805f3000(0000) knlGS:0000000000000000
Dec 14 15:48:10 filesserver kernel: [1369868.101356] CS: 0010 DS: 0018
ES: 0018 CR0: 000000008005003b
Dec 14 15:48:10 filesserver kernel: [1369868.107626] CR2:
0000000000000008 CR3: 0000000027365000 CR4: 00000000000006e0
Dec 14 15:48:10 filesserver kernel: [1369868.120238] Process pdflush
(pid: 211, threadinfo ffff810037e9a000, task ffff810037e3ee20)
Dec 14 15:48:10 filesserver kernel: [1369868.133041] Stack:
ffffffff881c8ad0 0000000000001000 ffff810028b193d8 ffff81003f8f11b0
Dec 14 15:48:10 filesserver kernel: [1369868.139727]
0000000028b193d8 ffff8100238fc730 ffff810028b193d8 ffff810037e9be48
Dec 14 15:48:10 filesserver kernel: [1369868.152806]
000000000000000e ffffffff881cc113
Dec 14 15:48:10 filesserver kernel: [1369868.159286] Call Trace:
<ffffffff881c8ad0>{:ext3:bget_one+0}
<ffffffff881cc113>{:ext3:ext3_ordered_writepage+243}
Dec 14 15:48:10 filesserver kernel: [1369868.172075]
<ffffffff8021d564>{mpage_writepages+468}
<ffffffff881cc020>{:ext3:ext3_ordered_writepage+0}
Dec 14 15:48:10 filesserver kernel: [1369868.184691]
<ffffffff881cc020>{:ext3:ext3_ordered_writepage+0}
<ffffffff8020c97a>{bit_waitqueue+74}
Dec 14 15:48:10 filesserver kernel: [1369868.196932]
<ffffffff80263cf9>{do_writepages+41}
<ffffffff802320af>{__writeback_single_inode+495}
Dec 14 15:48:10 filesserver kernel: [1369868.208782]
<ffffffff80221737>{sync_sb_inodes+487}
<ffffffff802a38b0>{keventd_create_kthread+0}
Dec 14 15:48:10 filesserver kernel: [1369868.220238]
<ffffffff80257b68>{writeback_inodes+152} <ffffffff80269d9f>{thread_return+0}
Dec 14 15:48:10 filesserver kernel: [1369868.231304]
<ffffffff8025e380>{pdflush+0} <ffffffff802bb9a6>{wb_kupdate+150}
Dec 14 15:48:10 filesserver kernel: [1369868.242058]
<ffffffff8025e4c4>{pdflush+324} <ffffffff802bb910>{wb_kupdate+0}
Dec 14 15:48:10 filesserver kernel: [1369868.252468]
<ffffffff80235459>{kthread+217} <ffffffff8026665a>{child_rip+8}
Dec 14 15:48:10 filesserver kernel: [1369868.262473]
<ffffffff802a38b0>{keventd_create_kthread+0} <ffffffff80235380>{kthread+0}
Dec 14 15:48:10 filesserver kernel: [1369868.272070]
<ffffffff80266652>{child_rip+0}
Dec 14 15:48:10 filesserver kernel: [1369868.281113]
Dec 14 15:48:10 filesserver kernel: [1369868.281114] Code: 4c 8b 6e 08
41 8d 1c 14 76 0b 89 d8 44 29 e0 3b 44 24 08 72
Dec 14 15:48:10 filesserver kernel: [1369868.295838] RIP
<ffffffff881c8a64>{:ext3:walk_page_buffers+52} RSP <ffff810037e9bb98>
Dec 14 15:48:10 filesserver kernel: [1369868.306053] CR2: 0000000000000008
Dec 14 15:56:06 filesserver init: tty2 process (4275) killed by signal 15
Dec 14 15:56:06 filesserver init: tty1 process (4450) killed by signal 15
Dec 14 15:56:06 filesserver init: tty3 process (4276) killed by signal 15
Dec 14 15:56:06 filesserver init: tty4 process (4277) killed by signal 15
Dec 14 15:56:06 filesserver init: tty5 process (4278) killed by signal 15
Dec 14 15:56:06 filesserver init: tty6 process (4279) killed by signal 15
Dec 14 15:56:10 filesserver exiting on signal 15
Merci d'avance pour toute aide.
Reply to: