http://bugzilla.novell.com/show_bug.cgi?id=561595 http://bugzilla.novell.com/show_bug.cgi?id=561595#c Jason Douglas changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jdouglas@novell.com AssignedTo|jdouglas@novell.com |jfehlig@novell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=561595 http://bugzilla.novell.com/show_bug.cgi?id=561595#c2 Tamás Németh changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|nice@titanic.nyme.hu | --- Comment #2 from Tamás Németh 2009-12-14 18:07:16 UTC --- (In reply to comment #1)

I don't see a problem. Does pidof return expected results when xend is running and not running?

Try to stop it completely and then start it again. I observed many times that the script "/etc/init.d/xend" detected itself instead of "/sbin/xend" (Because they have the same name, but this shouldn't happen, so it's probably a bug of pidof). Sometimes I even observed that /etc/init.d/xend was not willing to /sbin/xend, because it thought that it's already running, however the runnning "xend" process was ITSELF. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=561595 http://bugzilla.novell.com/show_bug.cgi?id=561595#c4 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |nice@titanic.nyme.hu --- Comment #4 from James Fehlig 2009-12-14 19:28:05 UTC --- I tried stop followed by start and xend was in fact started: xen32: # /etc/init.d/xend stop Stopping xend (pid 30400 30280 30277) done xen32: # /etc/init.d/xend start Starting xend (already running pid 30417) done xen32: # xm li Name ID Mem VCPUs State Time(s) Domain-0 0 7553 8 r----- 26222.1 sles10sp2-hvm 512 4 0.0 .. Wouldn't get a domain listing unless xend is running. Note that the "already running pid ..." message occurs on my system as well. But look at the code in xend init script: case "$1" in start) check $1 echo -n "Starting xend " if [ ! -z "$XEND" ]; then echo -n "(already running pid $XEND) " else cleanup fi ... The detected pid only causes this message to be displayed. The logic to handle other potential instances of the daemon is handled in /usr/sbin/xend itself. In fact, the detected pid is only used for informational messages throughout the init script AFAICS. Is xend really not running after executing start/restart on the init script? Can you use the xm command (a client of xend) at all after these operations? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=561595 http://bugzilla.novell.com/show_bug.cgi?id=561595#c6 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME --- Comment #6 from James Fehlig 2009-12-14 21:10:00 UTC --- Ok, thanks. As I mentioned above, the messages printed as result of detected pid are harmless and should not affect actual starting and stopping of xend daemon. I'm going to close this bug now. Please reopen if you can reproduce, i.e. the init script actually fails to start xend. Also provide /var/log/xen/xend.log in that case. Thanks! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.