Ik heb een virtual server met Debian bij leaseweb die af en toe even (enkele minuten) unavailable is.
Na wat in de logs te hebben gekeken kwam ik kernel fouten tegen en heb dit bij support gemeld.
Van wat ik uit de fouten opmaak is het een hardware probleem, kan natuurlijk ook aan de virtualisatie liggen.
Maar nu zegt Leaseweb dat het daar niet aan ligt en dat ze het niet op kunnen lossen.
Enige optie die zij zien is dat ik een backup maak en dat zij weer een clean install neerzetten.
Tuurlijk is dat een mogelijkheid, maar het kost mij weer tijd om de zaak uit te zoeken in te richten.
Mijn verwachting was dat problemen op OS nivo en helemaal op Kernel nivo wel door leaseweb zouden worden opgelost.
Verder heb ik ook geen schokkende dingen geinstalleerd behalve misschien Virtualmin, maar het lijkt me sterk dat die deze problemen veroorzaakt.
Heeft iemand een tip, of misschien een idee wat het probleem is?
Dit is het soort fout wat ik in de logs tegenkom:
Code:Mar 8 00:27:15 debian kernel: [31010.092479] Modules linked in: quota_v2 quota_tree ext2 loop joydev usbhid hid snd_pcm uhci_hcd ehci_hcd sg snd_timer sr_mod snd usbcore soundcore i2c_piix4 psmouse cdrom serio_raw snd_page_alloc processor e1000 nls_base floppy i2c_core virtio_balloon pcspkr evdev button ext4 mbcache jbd2 crc16 dm_mod sd_mod crc_t10dif ata_generic ata_piix libata virtio_pci virtio_ring thermal virtio scsi_mod thermal_sys Mar 8 00:27:15 debian kernel: [31010.092479] CPU 0: Mar 8 00:27:15 debian kernel: [31010.092479] Modules linked in: quota_v2 quota_tree ext2 loop joydev usbhid hid snd_pcm uhci_hcd ehci_hcd sg snd_timer sr_mod snd usbcore soundcore i2c_piix4 psmouse cdrom serio_raw snd_page_alloc processor e1000 nls_base floppy i2c_core virtio_balloon pcspkr evdev button ext4 mbcache jbd2 crc16 dm_mod sd_mod crc_t10dif ata_generic ata_piix libata virtio_pci virtio_ring thermal virtio scsi_mod thermal_sys Mar 8 00:27:15 debian kernel: [31010.092479] Pid: 228, comm: scsi_eh_0 Not tainted 2.6.32-5-amd64 #1 KVM Mar 8 00:27:15 debian kernel: [31010.092479] RIP: 0010:[<ffffffff8104eb2b>] [<ffffffff8104eb2b>] vprintk+0x31c/0x364 Mar 8 00:27:15 debian kernel: [31010.092479] RSP: 0018:ffff88002fe719e0 EFLAGS: 00000246 Mar 8 00:27:15 debian kernel: [31010.092479] CPU 0: Mar 7 17:46:42 debian kernel: [ 6977.206798] [<ffffffffa000db1a>] ? scsi_error_handler+0x10e/0x5b5 [scsi_mod] Mar 8 00:27:15 debian kernel: [31010.092479] RAX: 000000000000ffd8 RBX: ffffffff81646296 RCX: 00000000000081bf Mar 8 00:27:15 debian kernel: [31010.092479] RDX: ffff880001800000 RSI: 0000000000000086 RDI: 0000000000000246 Mar 8 00:27:15 debian kernel: [31010.092479] RBP: ffffffff8101166e R08: 000000000000747c R09: 000000000000000a Mar 8 00:27:15 debian kernel: [31010.092479] R10: 0000000000000000 R11: 0000000100000000 R12: 0000000000000032 Mar 8 00:27:15 debian kernel: [31010.092479] R13: ffffffff814bca00 R14: ffffffff81195a84 R15: 0000000000000000 Mar 8 00:27:15 debian kernel: [31010.092479] FS: 0000000000000000(0000) GS:ffff880001800000(0000) knlGS:0000000000000000 Mar 8 00:27:15 debian kernel: [31010.092479] CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b Mar 8 00:27:15 debian kernel: [31010.092479] CR2: 0000000001ea9618 CR3: 0000000007c44000 CR4: 00000000000006f0 Mar 8 00:27:15 debian kernel: [31010.092479] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Mar 8 00:27:15 debian kernel: [31010.092479] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Mar 8 00:27:15 debian kernel: [31010.092479] Call Trace: Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffff81193c76>] ? number+0x132/0x22e Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffff812faef2>] ? printk+0x4e/0x5c Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffff811955be>] ? vsnprintf+0x9e/0x449 Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffff8104e5af>] ? release_console_sem+0x17e/0x1af Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffff811959ba>] ? sprintf+0x51/0x59 Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffffa0063f8c>] ? ata_eh_report+0x909/0xc9b [libata] Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffff81195fd9>] ? delay_tsc+0x30/0x73 Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffff81195fd9>] ? delay_tsc+0x30/0x73 Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffffa00673b8>] ? ata_sff_check_status+0x10/0x13 [libata] Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffff81195fd9>] ? delay_tsc+0x30/0x73 Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffffa00673b8>] ? ata_sff_check_status+0x10/0x13 [libata] Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffffa0067498>] ? ata_bmdma_start+0x10/0x23 [libata] Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffffa0067d10>] ? ata_sff_qc_issue+0xeb/0x208 [libata] Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffffa005b329>] ? ata_qc_issue+0x2fe/0x347 [libata] Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffffa005fbcf>] ? ata_scsi_rw_xlat+0x0/0x1bd [libata] Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffffa0060959>] ? __ata_scsi_queuecmd+0x185/0x1dc [libata] Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffffa006230c>] ? ata_ering_map+0x36/0x55 [libata] Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffffa0064a9a>] ? ata_eh_link_autopsy+0x4c4/0x63d [libata] Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffffa00692a8>] ? ata_sff_softreset+0x0/0x130 [libata] Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffffa00678c8>] ? ata_sff_postreset+0x0/0x73 [libata] Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffffa00692a8>] ? ata_sff_softreset+0x0/0x130 [libata] Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffffa008e578>] ? piix_pata_prereset+0x0/0x51 [ata_piix] Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffffa0065c71>] ? ata_do_eh+0x24/0x82 [libata] Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffffa00665b7>] ? ata_scsi_error+0x342/0x67a [libata] Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffffa0009389>] ? __scsi_iterate_devices+0x5e/0x6a [scsi_mod] Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffffa000da0c>] ? scsi_error_handler+0x0/0x5b5 [scsi_mod] Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffffa000db1a>] ? scsi_error_handler+0x10e/0x5b5 [scsi_mod] Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffffa000da0c>] ? scsi_error_handler+0x0/0x5b5 [scsi_mod] Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffff81064d5d>] ? kthread+0x79/0x81 Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffff81011baa>] ? child_rip+0xa/0x20 Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffff81064ce4>] ? kthread+0x0/0x81 Mar 8 00:27:15 debian kernel: [31010.092479] [<ffffffff81011ba0>] ? child_rip+0x0/0x20 Mar 8 00:27:15 debian kernel: [31010.111448] ata1: soft resetting link Mar 8 00:27:16 debian kernel: [31011.648538] ata1.00: configured for MWDMA2 Mar 8 00:27:16 debian kernel: [31011.648544] ata1.00: device reported invalid CHS sector 0 Mar 8 00:27:16 debian kernel: [31011.648583] ata1: EH complete