Russell Coker
2007-Apr-01 23:39 UTC
[Pkg-xen-devel] Bug#417243: xen-utils-common: Should display a usable error message when there is a config file error
Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal When a block device name is wrong (the device does not exist) it should say "block device /dev/foo/bar does not exist" instead of waiting for ages and giving the following error: Using config file "/etc/xen/ha2". Error: Device 768 (vbd) could not be connected. Hotplug scripts not working. Also the following parsing error is inadequate, it should at least give the user a clue as to where the error lies. What does "22" mean, is it a config file line number? It doesn't even say that the error is in /etc/xen/foo. Error: (22, 'Invalid argument') -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-xen-686 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Versions of packages xen-utils-common depends on: ii lsb-base 3.1-23.1 Linux Standard Base 3.1 init scrip ii udev 0.105-4 /dev/ and hotplug management daemo xen-utils-common recommends no packages. -- no debconf information
Debian Bug Tracking System
2012-May-06 13:48 UTC
[Pkg-xen-devel] Bug#417243: marked as done (xen-utils-common: Should display a usable error message when there is a config file error)
Your message dated Sun, 6 May 2012 15:46:39 +0200 with message-id <20120506134639.GD11813 at wavehammer.waldi.eu.org> and subject line fixed has caused the Debian Bug report #417243, regarding xen-utils-common: Should display a usable error message when there is a config file error to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 417243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=417243 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Russell Coker <russell at coker.com.au> Subject: xen-utils-common: Should display a usable error message when there is a config file error Date: Mon, 02 Apr 2007 09:38:42 +1000 Size: 3354 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20120506/2fd3acda/attachment-0002.mht> -------------- next part -------------- An embedded message was scrubbed... From: Bastian Blank <waldi at debian.org> Subject: fixed Date: Sun, 6 May 2012 15:46:39 +0200 Size: 1543 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20120506/2fd3acda/attachment-0003.mht>
Seemingly Similar Threads
- Bug#418245: xen-utils-common: race condition in "xm list" when destroying domains.
- Bug#433780: xen-utils-common: /etc/init.d/xend restart should restart xenstored and xenconsole
- Bug#597403: xen-utils-common: need to run restorecon in /etc/init.d/xend on SE Linux systems
- Bug#503044: xen-utils-common: should make the loopback device default to supporting more nodes
- Bug#513842: xen-utils-common: please make pygrub available