From owner-freebsd-xen@freebsd.org Fri Jan 29 01:11:14 2021 Return-Path: Delivered-To: freebsd-xen@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6F04F4F404B for ; Fri, 29 Jan 2021 01:11:14 +0000 (UTC) (envelope-from buhrow@nfbcal.org) Received: from nfbcal.org (ns.NFBCAL.ORG [157.22.230.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "nfbcal.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DRfRj13T8z3Gpb for ; Fri, 29 Jan 2021 01:11:12 +0000 (UTC) (envelope-from buhrow@nfbcal.org) Received: from nfbcal.org (localhost [127.0.0.1]) by nfbcal.org (8.15.2/8.14.1-NFBNETBSD) with ESMTPS id 10T1B4qS020606 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 28 Jan 2021 17:11:05 -0800 (PST) Received: (from buhrow@localhost) by nfbcal.org (8.15.2/8.12.11) id 10T1B4Br019488; Thu, 28 Jan 2021 17:11:04 -0800 (PST) Message-Id: <202101290111.10T1B4Br019488@nfbcal.org> From: Brian Buhrow Date: Thu, 28 Jan 2021 17:11:04 -0800 X-Mailer: Mail User's Shell (7.2.6 beta(4.pl1)+dynamic 20000103) To: freebsd-xen@freebsd.org Subject: Corruption in xenstored tdb file? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (nfbcal.org [127.0.0.1]); Thu, 28 Jan 2021 17:11:05 -0800 (PST) X-Rspamd-Queue-Id: 4DRfRj13T8z3Gpb X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of buhrow@nfbcal.org designates 157.22.230.125 as permitted sender) smtp.mailfrom=buhrow@nfbcal.org X-Spamd-Result: default: False [1.50 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; ARC_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[157.22.230.125:from]; R_SPF_ALLOW(-0.20)[+a:ns.nfbcal.org]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[nfbcal.org]; NEURAL_SPAM_MEDIUM(1.00)[1.000]; NEURAL_SPAM_SHORT(0.80)[0.802]; SPAMHAUS_ZRD(0.00)[157.22.230.125:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:7091, ipnet:157.22.0.0/16, country:US]; MAILMAN_DEST(0.00)[freebsd-xen] X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2021 01:11:14 -0000 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