Server Crash Due to /etc/webmin/status/monitor.pl

Hi All,

I am a newbie running a home server and noticed that my server is crashing after about 30 mins to an hour after being turned on. I reviewed the syslog and found that /etc/webmin/status/monitor.pl is causing a kernel error. The computer ran for almost 900 hours w/ no issues prior to March 5th. My system auto install updates so I am not sure what was installed since that time. I have since turned of the chron for this process in hopes to keep the server running but I am not sure whats the function of it in the first place. Any advise would be welcomed and appreciated!

Here is a snippet of the syslog.

Apr 16 19:50:01 debian CRON[10744]: (root) CMD (/etc/webmin/status/monitor.pl)
Apr 16 19:52:03 debian systemd[1]: /lib/systemd/system/spamassassin.service:6: PIDFile= references path below legacy directory /var/run/, updating /var/run/spamd.pid → /run/spamd.pid; please update the unit file accordingly.
Apr 16 19:52:04 debian systemd[1]: /lib/systemd/system/spamassassin.service:6: PIDFile= references path below legacy directory /var/run/, updating /var/run/spamd.pid → /run/spamd.pid; please update the unit file accordingly.
Apr 16 19:52:04 debian systemd[1]: /lib/systemd/system/spamassassin.service:6: PIDFile= references path below legacy directory /var/run/, updating /var/run/spamd.pid → /run/spamd.pid; please update the unit file accordingly.
Apr 16 19:52:04 debian systemd[1]: /lib/systemd/system/spamassassin.service:6: PIDFile= references path below legacy directory /var/run/, updating /var/run/spamd.pid → /run/spamd.pid; please update the unit file accordingly.
Apr 16 19:52:05 debian kernel: [ 2080.496077] BUG: unable to handle kernel paging request at ffffe04f97e49588
Apr 16 19:52:05 debian kernel: [ 2080.496145] PGD 0 P4D 0
Apr 16 19:52:05 debian kernel: [ 2080.496170] Oops: 0000 [#1] SMP PTI
Apr 16 19:52:05 debian kernel: [ 2080.496202] CPU: 4 PID: 11515 Comm: php7.3-fpm Not tainted 4.19.0-8-amd64 #1 Debian 4.19.98-1
Apr 16 19:52:05 debian kernel: [ 2080.496274] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./P67 Performance, BIOS P2.20 05/11/2012
Apr 16 19:52:05 debian kernel: [ 2080.496363] RIP: 0010:___slab_alloc+0x4e/0x500
Apr 16 19:52:05 debian kernel: [ 2080.496401] Code: 89 74 24 38 89 54 24 3c 48 89 4c 24 30 4d 85 f6 0f 84 86 00 00 00 83 7c 24 3c ff 74 0d 49 8b 06 48 c1 e8 3a 39 44 24 3c 75 5c <49> 8b 56 08 48 8d 42 ff 83 e2 01 49 0f 44 c6 48 8b 00 a8 40 75 39
Apr 16 19:52:05 debian kernel: [ 2080.496555] RSP: 0018:ffffba310a32bc30 EFLAGS: 00010046
Apr 16 19:52:05 debian kernel: [ 2080.496600] RAX: 0000000000000246 RBX: 0000000000000246 RCX: ffffffffacc1468b
Apr 16 19:52:05 debian kernel: [ 2080.496659] RDX: 00000000ffffffff RSI: 0000000000400200 RDI: ffff9a443eab9080
Apr 16 19:52:05 debian kernel: [ 2080.496719] RBP: ffffba310a32bce0 R08: ffffda30ffd1beb0 R09: ffff9a443418b930
Apr 16 19:52:05 debian kernel: [ 2080.496779] R10: 00000000000001ba R11: 00000000000265c0 R12: ffffffffacc1468b
Apr 16 19:52:05 debian kernel: [ 2080.496839] R13: ffffda30ffd1beb0 R14: ffffe04f97e49580 R15: ffff9a443eab9080
Apr 16 19:52:05 debian kernel: [ 2080.496899] FS: 00007f7d63cdd580(0000) GS:ffff9a4446b00000(0000) knlGS:0000000000000000
Apr 16 19:52:05 debian kernel: [ 2080.496967] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 16 19:52:05 debian kernel: [ 2080.497016] CR2: ffffe04f97e49588 CR3: 0000000507860004 CR4: 00000000000606e0
Apr 16 19:52:05 debian kernel: [ 2080.497076] Call Trace:
Apr 16 19:52:05 debian kernel: [ 2080.497104] ? pte_alloc_one+0x36/0x40
Apr 16 19:52:05 debian kernel: [ 2080.497138] ? __pte_alloc+0xb0/0x110
Apr 16 19:52:05 debian kernel: [ 2080.497170] ? anon_vma_clone+0x5b/0x180
Apr 16 19:52:05 debian kernel: [ 2080.497206] ? _cond_resched+0x15/0x30
Apr 16 19:52:05 debian kernel: [ 2080.497239] ? copy_page_range+0x83e/0xc30
Apr 16 19:52:05 debian kernel: [ 2080.497275] ? anon_vma_clone+0x5b/0x180
Apr 16 19:52:05 debian kernel: [ 2080.497310] __slab_alloc+0x1c/0x30
Apr 16 19:52:05 debian kernel: [ 2080.497341] kmem_cache_alloc+0x192/0x1c0
Apr 16 19:52:05 debian kernel: [ 2080.497377] anon_vma_clone+0x5b/0x180
Apr 16 19:52:05 debian kernel: [ 2080.497410] anon_vma_fork+0x2d/0x120
Apr 16 19:52:05 debian kernel: [ 2080.497444] copy_process.part.37+0x164c/0x1dc0
Apr 16 19:52:05 debian kernel: [ 2080.497486] _do_fork+0xf2/0x3f0
Apr 16 19:52:05 debian kernel: [ 2080.497516] ? __do_pipe_flags+0x54/0xd0
Apr 16 19:52:05 debian kernel: [ 2080.497550] ? do_pipe2+0x7c/0xb0
Apr 16 19:52:05 debian kernel: [ 2080.497582] do_syscall_64+0x53/0x110
Apr 16 19:52:05 debian kernel: [ 2080.497615] entry_SYSCALL_64_after_hwframe+0x44/0xa9
Apr 16 19:52:05 debian kernel: [ 2080.497660] RIP: 0033:0x7f7d63be17be
Apr 16 19:52:05 debian kernel: [ 2080.497691] Code: db 0f 85 25 01 00 00 64 4c 8b 0c 25 10 00 00 00 45 31 c0 4d 8d 91 d0 02 00 00 31 d2 31 f6 bf 11 00 20 01 b8 38 00 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 b6 00 00 00 41 89 c4 85 c0 0f 85 c3 00 00

That’s a kernel panic. User space applications cannot “cause” a kernel panic. Only kernel bugs or hardware problems can cause a kernel panic. So, make sure you have the latest kernel from your OS, and check memory/disk/temperatures.

Thank you for your reply. I swap out the heat sinks and tested the ram. Found out 1 of the 4 ram chips is bad. Still trying to find out which one it is as it finishes the windows memory test but it still would crash if I had all 4 ram sticks in place. It’ll be just trail and error testing from here on. Thanks for your help!

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.