Over the past week we've seen this happening twice on different machines (virtual machines, KVM-qemu, by the way):
Code:
Jun 28 13:30:28 ispconfig kernel: [2261270.357488] mydns[24252]: segfault at 0 ip 0804bb38 sp bf8e2e30 error 4 in mydns[8048000+33000]
Jun 28 13:30:30 ispconfig kernel: [2261272.364809] mydns[24264]: segfault at 0 ip 0804bb38 sp bf8e2e30 error 4 in mydns[8048000+33000]
Jun 28 13:30:31 ispconfig kernel: [2261273.547787] mydns[24319]: segfault at 0 ip 0804bb38 sp bf8e2e30 error 4 in mydns[8048000+33000]
And about 40 more lines of that, at which point MyDNS completely stops working.
Code:
messages.0:Jun 25 14:46:20 ispconfig kernel: [66694.721223] mydns[8031]: segfault at 0 ip 0804bb38 sp bf9bc760 error 4 in mydns[8048000+33000]
messages.0:Jun 25 14:46:20 ispconfig kernel: [66694.845825] mydns[8035]: segfault at 0 ip 0804bb38 sp bf9bc760 error 4 in mydns[8048000+33000]
messages.0:Jun 25 14:46:20 ispconfig kernel: [66695.049560] mydns[8042]: segfault at 0 ip 0804bb38 sp bf9bc760 error 4 in mydns[8048000+33000]
messages.0:Jun 25 14:46:20 ispconfig kernel: [66695.296392] mydns[8055]: segfault at 0 ip 0804bb38 sp bf9bc760 error 4 in mydns[8048000+33000]
messages.0:Jun 25 14:46:21 ispconfig kernel: [66695.600034] mydns[8063]: segfault at 0 ip 0804bb38 sp bf9bc760 error 4 in mydns[8048000+33000]
And about 40 more lines. Same as above.
Is this just a fluke, or something to worry about? By the way the hardware in this server has worked fine for nearly two years, I'm fairly sure this shouldn't be the issue. Also it happened on two different physical servers.
Recent comments
9 hours 51 min ago
19 hours 19 min ago
20 hours 8 min ago
23 hours 42 min ago
1 day 4 hours ago
1 day 4 hours ago
1 day 6 hours ago
1 day 16 hours ago
1 day 21 hours ago
1 day 23 hours ago