intechfs
asked on
Perl daemon crashing with kernel error messages
I have a Perl script that runs on many servers as a daemon.
I have compiled it using Par::Packer and the daemon is running using the module Proc::Daemon.
Almost all the systems running it are working fine, but one of them (which had been fine) now crashes it out as soon as it loads and fills up the messages log.
I have attached the messages I get everytime it crashes, but I don't understand them at all.
If someone could please explain what they might mean, and what I might be able to do to debug that'd be great.
I have compiled it using Par::Packer and the daemon is running using the module Proc::Daemon.
Almost all the systems running it are working fine, but one of them (which had been fine) now crashes it out as soon as it loads and fills up the messages log.
I have attached the messages I get everytime it crashes, but I don't understand them at all.
If someone could please explain what they might mean, and what I might be able to do to debug that'd be great.
Apr 7 11:13:55 df-bk-applyv13l kernel: Process yams.bin (pid: 15952, threadinfo=d118c000 task=ce85a570)
Apr 7 11:13:55 df-bk-applyv13l kernel: Stack: <0>cbc05d94 00000008 45a9b2b4 cb3a6011 45a9b2b4 d2fa45d8 cb3a6011 d118df3c
Apr 7 11:13:55 df-bk-applyv13l kernel: c0155292 d118de28 d118de1c d118df3c d72e40c0 45a9b2b4 d2fa45d8 cb3a6011
Apr 7 11:13:55 df-bk-applyv13l kernel: d118df3c c0156d4f cb3a6019 00000000 00000101 d12c8090 23ef1325 49db2763
Apr 7 11:13:55 df-bk-applyv13l kernel: Call Trace:
Apr 7 11:13:55 df-bk-applyv13l kernel: [<c0155292>] do_lookup+0x24/0x135
Apr 7 11:13:55 df-bk-applyv13l kernel: [<c0156d4f>] __link_path_walk+0x6da/0xaec
Apr 7 11:13:55 df-bk-applyv13l kernel: [<c011b015>] current_fs_time+0x40/0x4b
Apr 7 11:13:55 df-bk-applyv13l kernel: [<c01571a8>] link_path_walk+0x47/0xb9
Apr 7 11:13:55 df-bk-applyv13l kernel: [<c01574c9>] do_path_lookup+0x198/0x1e6
Apr 7 11:13:55 df-bk-applyv13l kernel: [<c0157d69>] __path_lookup_intent_open+0x42/0x72
Apr 7 11:13:55 df-bk-applyv13l kernel: [<c0157de8>] path_lookup_open+0xf/0x13
Apr 7 11:13:55 df-bk-applyv13l kernel: [<c0157eab>] open_namei+0x62/0x509
Apr 7 11:13:55 df-bk-applyv13l kernel: [<c01498d2>] do_filp_open+0x1d/0x32
Apr 7 11:13:55 df-bk-applyv13l kernel: [<c0149925>] do_sys_open+0x3e/0xb0
Apr 7 11:13:55 df-bk-applyv13l kernel: [<c01499c4>] sys_open+0x16/0x18
Apr 7 11:13:55 df-bk-applyv13l kernel: [<c010299b>] sysenter_past_esp+0x54/0x79
Apr 7 11:13:55 df-bk-applyv13l kernel: Code: 39 42 04 75 20 8b 42 08 8b 4c 24 04 8b 54 24 0c e8 29 74 04 00 85 c0 75 0c f6 43 04 10 75 20 ff 03 89 d8 eb 1c 8b 3f 85 ff 74 14 <8b> 07 0f 18 00 90 8d 5f f4 8b 4c 24 08 39 4b 18 75 e8 eb 9b 31
Apr 7 11:14:08 df-bk-applyv13l kernel: <1>Unable to handle kernel paging request at virtual address ffff0000
Apr 7 11:14:08 df-bk-applyv13l kernel: printing eip:
Apr 7 11:14:08 df-bk-applyv13l kernel: c015d0b8
Apr 7 11:14:08 df-bk-applyv13l kernel: *pde = 00002067
Apr 7 11:14:08 df-bk-applyv13l kernel: Oops: 0000 [#20]
Apr 7 11:14:08 df-bk-applyv13l kernel: last sysfs file: /devices/pci0000:00/0000:00:0f.0/resource
Apr 7 11:14:08 df-bk-applyv13l kernel: Modules linked in: cls_u32 sch_sfq sch_htb ipv6 snd_pcm_oss snd_mixer_oss snd_seq_midi snd_seq_midi_event snd_seq vmhgfs button battery ac apparmor aamatch_pcre loop dm_mod uhci_hcd snd_ens1371 usbcore intel_agp agpgart gameport shpchp snd_rawmidi snd_seq_device ide_cd snd_ac97_codec cdrom pci_hotplug snd_ac97_bus i2c_piix4 snd_pcm i2c_core snd_timer snd pcnet32 soundcore mii snd_page_alloc parport_pc lp parport reiserfs edd fan thermal processor sg ide_generic mptspi mptscsih mptbase scsi_transport_spi piix sd_mod scsi_mod ide_disk ide_core
Apr 7 11:14:08 df-bk-applyv13l kernel: CPU: 0
Apr 7 11:14:08 df-bk-applyv13l kernel: EIP: 0060:[<c015d0b8>] Tainted: P U VLI
Apr 7 11:14:08 df-bk-applyv13l kernel: EFLAGS: 00010286 (2.6.16.21-0.25-default #1)
Apr 7 11:14:08 df-bk-applyv13l kernel: EIP is at __d_lookup+0xa1/0xbf
Apr 7 11:14:08 df-bk-applyv13l kernel: eax: 0000790d ebx: 9e25cf3a ecx: 00000010 edx: c12f4180
Apr 7 11:14:08 df-bk-applyv13l kernel: esi: ca8a684c edi: ffff0000 ebp: cebade44 esp: cebaddd8
Apr 7 11:14:08 df-bk-applyv13l kernel: ds: 007b es: 007b ss: 0068
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the help
ASKER
I think its probably going to be the hardware then as this is a virtual machine and may well have become corrupted.
I will try replacing it and see if that helps. Thanks for the advice.