search for: 433780

...oled and xenstored stopping unhandled by init script There is no source info for the package 'xen-utils-common' at version '4.0.1-2' with architecture '' Unable to make a source version for version '4.0.1-2' Marked as found in versions 4.0.1-2. > forcemerge 628912 433780 Bug #628912 [xen-utils-common] xenconsoled and xenstored stopping unhandled by init script Bug #628912 [xen-utils-common] xenconsoled and xenstored stopping unhandled by init script There is no source info for the package 'xen-utils-common' at version '4.0.1-2' with architecture ...

Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal There should be a clean and clearly defined way to restart all the Xen daemons in the case of error. If the file /var/lib/xenstored/tdb is corrupt then you must stop xenstored, rm the file, and then restart it. Currently there is no defined way of doing this so the solution is to kill -9 the process, rm the file, and then reboot. --

Package: xen-utils-common Version: 3.4.2-3 Severity: normal If one daemon is running but the others are not then the stop script will fail. It should use the pid file for each daemon and try to stop them independently. Note that the fact that Xen shouldn't get into this state is not relevant, daemons do periodically fail, relevant system control scripts should be able to stop them even