|
Bugzilla – Full Text Bug Listing |
| Summary: | /etc/init.d/xend status | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Andreas Klein <asklein> |
| Component: | Other | Assignee: | Charles Coffing <ccoffing> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | locilka, lslezak, vetter, yast2-maintainers |
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Andreas Klein
2005-08-18 20:42:18 UTC
Andreas, you confuse me: If the package is not installed /etc/init.d/xend is not there. The package is installed. Yast says it is not installed, if you try to stop the service :-) Hmm, is this a YaST bug then? Lukas? It seems that the package "xen" needs to be installed to appear in the
runlevel-editor (tested).
The second thing is, that the XEN still doesn't work in Beta2 (lslezak?).
See: /etc/init.d/xend line 27: xend status
`which xend`
`/usr/sbin/xend status` -->
--- cut ---
ERROR: Could not obtain handle on privileged command interface (2 = No such file
or directory)
Traceback (most recent call last):
File "/usr/sbin/xend", line 36, in ?
from xen.xend.server import SrvDaemon
File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 29,
in ?
import channel
File "/usr/lib/python2.4/site-packages/xen/xend/server/channel.py", line 6, in ?
import xen.lowlevel.xc; xc = xen.lowlevel.xc.new()
xen.lowlevel.xc.error: (2, 'No such file or directory')
--- cut ---
seems to be a problem in '/usr/sbin/xend' script
OK, I'll have a look. Hmm, this should be fixed in http://www.suse.de/~garloff/linux/xen/RPMs-100/6458/ Can you check, please? No, doesn't help. What am I doing wrong so I can't reproduce this? root@tpkurt:~ [0]# /etc/init.d/xend status Checking status of xend (pid 6756 6762 6763 6764 6765 6766 6901) running root@tpkurt:~ [0]# rcxend stop Stopping xend (pid 6756 6762 6763 6764 6765 6766 6901) done root@tpkurt:~ [0]# /etc/init.d/xend status Checking status of xend unused root@tpkurt:~ [3]# And on a machine that is not running a xen kernel: root@prescott:~ [0]# /etc/init.d/xend status xend root@prescott:~ [5]# The return code should 3 instead of 5 I guess anbd the mesage could be improved, but that does not explain what you are seeing, does it? This should be fixed in the update packages. Can you confirm? A little bit. The xend service is not shown as running. That's correct now. When trying to stop the not running service still shows the same error-message. I thing this is not lsb-compliant? Stopping a not running service must be successfull, or am I wrong? Yes, it must be successful (see /etc/init.d/skeleton file, there are usefull comments). Charles Coffing has been doing some /etc/init.d/xend work and asked me to assign this to him to see if it is already fixed with his latest work. Fixed in 3.0_8659. Retest in beta 3. changing to FIXED |