Date: Thu, 28 Jan 2021 17:11:04 -0800 From: Brian Buhrow <buhrow@nfbcal.org> To: freebsd-xen@freebsd.org Subject: Corruption in xenstored tdb file? Message-ID: <202101290111.10T1B4Br019488@nfbcal.org>
next in thread | raw e-mail | index | archive | help
hello. Recently One of my FreeBSD-xen servers went down hard due to a power failure. When it came back up, one of the domus' came up, but with no network interface. Dmesg messages show the following errors. To fix the issue, I removed the /var/lib/xenstored/tdb file and rebooted. Before that, I couldn't get this domu to boot with a network interface. My question is, is it reasonable to take this action when such an error occurs and, further, might it be better to remove that file before attempting to start xen on reboots, just in case something didn't go down cleanly? -thanks -Brian Jan 28 02:07:17 xen-lothlorien kernel: xnb(xnb_frontend_changed:1397): frontend_state=Initialised, xnb_state=InitWait Jan 28 02:07:17 xen-lothlorien kernel: xnb1: Error 2 Unable to retrieve ring information from frontend /local/domain/7/device/vif/0. Unable to connect. Jan 28 02:07:17 xen-lothlorien kernel: xnb1: Fatal error. Transitioning to Closing State Jan 28 02:07:17 xen-lothlorien kernel: xnb(xnb_frontend_changed:1397): frontend_state=Connected, xnb_state=Closing Jan 28 02:07:17 xen-lothlorien kernel: xnb(xnb_connect_comms:793): rings connected! Jan 28 02:07:17 xen-lothlorien kernel: xnb(xnb_frontend_changed:1397): frontend_state=Closed, xnb_state=Connected
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202101290111.10T1B4Br019488>