|
|
|
|
|
|
|
|
|
|
xen-users
[Xen-users] Xen-u domain crashed
Today I had something strange.
A xen-server with 2 domU's on it.
- 1 was doing fine
- 2 was not responding to http, ftp or ssh, however networking was up (I
could ping to that server)
Going to the console resulted in a blank screen (no info)
xm list give me something like this:
Name ID Mem VCPUs State Time(s)
Domain-0 0 746 1 r----- 101.6
arrow-server 1 128 1 ------ 27.7
compu-server 2 128 1 ------ 56.4
First question:
why wasn't (isn't) there a state in the domU's?
Then I tried to reboot the not-responding server.
xm reboot compu-server
But that command hanged, after this also xm list didn't respond at all.
This time I had something in the xend-log-file:
[2008-01-29 10:26:44 4509] DEBUG (__init__:1094)
XendDomainInfo.shutdown(reboot)
[2008-01-29 10:26:44 4509] DEBUG (__init__:1094)
XendDomainInfo.handleShutdownWatch
[2008-01-29 10:27:14 4509] INFO (__init__:1094) Domain shutdown timeout
expired: name=compu-server id=2
I tried then to destroy the domU but that command also hanged.
Trying to restart xend give me an error in the log
Exception starting xend ((98, 'Address already in use'))
..but I think this is because the dom-U's where not shutdown.
After that I rebooted the whole server en created the domains again
without a problem.
Next Question:
How can I normally come out of this lock?
Can I kill processes manually?
Last Question:
How can I debug a domain to prevent that it's not responding?
On dom-0 xend.log messages syslog didn't record anything.
On dom-U messages syslog didn't record anything.
Best regards,
Pascal
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-users] Xen-u domain crashed,
Pascal Nobus <=
|
|
|
|
|