[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-API] xapi will no longer start - what are my options?

Here you go:

[root@xcp-hoppe ~]# /sbin/service xapissl restart
Stopping xapi SSL:
Starting xapi SSL:ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ [Â OKÂ ]
[root@xcp-hoppe ~]# echo $?
0


[root@xcp-hoppe ~]# /sbin/service xapissl stop
Stopping xapi SSL: .
[root@xcp-hoppe ~]# ps aux | grep stunnel
rootÂÂÂÂÂ 9745Â 0.0Â 0.1ÂÂ 5100ÂÂ 716 pts/8ÂÂÂ S+ÂÂ 17:24ÂÂ 0:00 grep stunnel

So nothing to kill there.

[root@xcp-hoppe ~]# ps axf | grep xapi
Â7598 ?ÂÂÂÂÂÂÂ SÂÂÂÂ 32:46 /opt/xensource/libexec/

cdrommon /dev/xapi/cd/sr0
Â6840 pts/8ÂÂÂ S+ÂÂÂÂ 0:00Â |ÂÂÂÂÂÂ \_ grep xapi
24767 ?ÂÂÂÂÂÂÂ Z<lÂÂ 88:38 [xapi] <defunct>


There's a zombie process there I can't kill. I have a hunch this is the problem.


[root@xcp-hoppe ~]# ps -fe | grep xapi
rootÂÂÂÂÂ 7598ÂÂÂÂ 1Â 0Â 2011 ?ÂÂÂÂÂÂÂ 00:32:46 /opt/xensource/libexec/cdrommon /dev/xapi/cd/sr0
rootÂÂÂÂÂ 8401ÂÂÂÂ 1Â 0 16:52 ?ÂÂÂÂÂÂÂ 00:00:00 /usr/sbin/stunnel /var/xapi/xapi-ssl.conf
rootÂÂÂÂÂ 8737ÂÂÂÂ 1Â 0 17:07 ?ÂÂÂÂÂÂÂ 00:00:00 /opt/xensource/bin/xapi -daemon -writereadyfile /var/run/xapi_startup.cookie -writeinitcomplete /var/run/xapi_init_complete.cookie
rootÂÂÂÂÂ 8739Â 8737Â 0 17:07 ?ÂÂÂÂÂÂÂ 00:00:02 /opt/xensource/bin/xapi -daemon -writereadyfile /var/run/xapi_startup.cookie -writeinitcomplete /var/run/xapi_init_complete.cookie
rootÂÂÂÂÂ 9480ÂÂÂÂ 1Â 0 17:15 ?ÂÂÂÂÂÂÂ 00:00:00 /usr/bin/python /etc/xapi.d/plugins/vmpr <methodCall><methodName>protect</methodName><params><param><value>OpaqueRef:5212aed4-a93b-3012-3988-e4aad29c5bbd</value></param><param><value><struct/></value></param></params></methodCall>
rootÂÂÂÂÂ 9614Â 6638Â 0 17:21 pts/8ÂÂÂ 00:00:00 grep xapi
rootÂÂÂÂ 24767ÂÂÂÂ 1Â 1 Jan15 ?ÂÂÂÂÂÂÂ 01:28:38 [xapi] <defunct>




On 20 January 2012 17:21, Dave Scott <Dave.Scott@xxxxxxxxxxxxx> wrote:

Hi,

Â

Thanks for the updated pastebin. The last line says:

Â

[20120120T14:48:18.726Z|debug|xcp-hoppe|0 thread_zero|bringing up management interface D:c515ea9445f2|xapi] Restarting stunnel

Â

Which correlates with some of the original /var/log/messages lines you posted

Â

Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.852Z||2301|Args after replacement = [/sbin/service;xapissl;restart]
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.852Z||2301|I've received the following fds: [2;1]Â
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:26.942Z||2301|Caught unexpected exception: Unix.Unix_error(31, "write", "")

Â

I suggest a quick experimentâ if you run:

Â

 /sbin/service xapissl restart

 echo $?

Â

Does it succeed and print â0â?

Â

Another quick experiment would be:

Â

 /sbin/service xapissl stop

Â

Then check to see if stunnel really has gone away. If not (it might be stuck somehow) Iâd recommend shutting it down with âkill -9 <pid>â. Then

Â

 /sbin/service xapissl start

Â

After that I would try

Â

/sbin/service xapi stop

Â

Then make sure that all xapis really have gone away. If not (they might also be stuck somehow) Iâd recommend shutting them down with âkill -9 <pid>â. Then

Â

 /sbin/service xapi start

Â

Cheers,

Dave

Â

From: Lars Seeliger [mailto:meesterlars@xxxxxxxxx]
Sent: 20 January 2012 15:37


To: Dave Scott
Cc: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-API] xapi will no longer start - what are my options?

Â

Here you go:

[root@xcp-hoppe ~]# ps axf | grep xapi
Â7598 ?ÂÂÂÂÂÂÂ SÂÂÂÂ 32:46 /opt/xensource/libexec/cdrommon /dev/xapi/cd/sr0
Â6840 pts/8ÂÂÂ S+ÂÂÂÂ 0:00Â |ÂÂÂÂÂÂ \_ grep xapi
24767 ?ÂÂÂÂÂÂÂ Z<lÂÂ 88:38 [xapi] <defunct>Â <<<<<<<<<<<< defunct??????
Â6757 ?ÂÂÂÂÂÂÂ S<sÂÂÂ 0:00 /usr/sbin/stunnel /var/xapi/xapi-ssl.conf

[root@xcp-hoppe ~]# ps axf | grep stunnel
Â6677 pts/8ÂÂÂ S+ÂÂÂÂ 0:00ÂÂÂÂÂÂÂÂÂ \_ grep stunnel
Â6397 ?ÂÂÂÂÂÂÂ S<sÂÂÂ 0:00 /usr/sbin/stunnel /var/xapi/xapi-ssl.conf

There is something listening on port 443, though my skills don't allow me to ascertain what. Same goes for 80:

[root@xcp-hoppe ~]# netstat -an
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local AddressÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Foreign AddressÂÂÂÂÂÂÂÂÂÂÂÂ State
tcpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 127.0.0.1:199ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 0.0.0.0:*ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ LISTEN
tcpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 127.0.0.1:5900ÂÂÂÂÂÂÂÂÂÂÂÂÂ 0.0.0.0:*ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ LISTEN
tcpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 127.0.0.1:5901ÂÂÂÂÂÂÂÂÂÂÂÂÂ 0.0.0.0:*ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ LISTEN
tcpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 127.0.0.1:5902ÂÂÂÂÂÂÂÂÂÂÂÂÂ 0.0.0.0:*ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ LISTEN
tcpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 127.0.0.1:5903ÂÂÂÂÂÂÂÂÂÂÂÂÂ 0.0.0.0:*ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ LISTEN
tcpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 127.0.0.1:111ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 0.0.0.0:*ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ LISTEN
tcpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 0.0.0.0:22ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 0.0.0.0:*ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ LISTEN
tcpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 0.0.0.0:600ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 0.0.0.0:*ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ LISTEN
tcpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 192.168.1.10:443ÂÂÂÂÂÂÂÂÂÂÂ 0.0.0.0:*ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ LISTEN
tcpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 127.0.0.1:443ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 0.0.0.0:*ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ LISTEN
tcpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 0.0.0.0:3551ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 0.0.0.0:*ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ LISTEN
tcpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 192.168.1.10:22ÂÂÂÂÂÂÂÂÂÂÂÂ 192.168.1.1:4930ÂÂÂÂÂÂÂÂÂÂÂ ESTABLISHED
tcpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 192.168.1.10:51388ÂÂÂÂÂÂÂÂÂ 192.168.1.1:445ÂÂÂÂÂÂÂÂÂÂÂÂ ESTABLISHED
tcpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 192.168.1.10:22ÂÂÂÂÂÂÂÂÂÂÂÂ 10.168.1.9:61784ÂÂÂÂÂÂÂÂÂÂÂ ESTABLISHED
tcpÂÂÂÂÂÂÂ 1ÂÂÂÂÂ 0 127.0.0.1:80ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 127.0.0.1:48318ÂÂÂÂÂÂÂÂÂÂÂÂ CLOSE_WAIT
tcpÂÂÂÂÂÂÂ 0ÂÂÂÂ 52 192.168.1.10:22ÂÂÂÂÂÂÂÂÂÂÂÂ 192.168.1.1:1093ÂÂÂÂÂÂÂÂÂÂÂ ESTABLISHED
udpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 0.0.0.0:58882ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 0.0.0.0:*
udpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 0.0.0.0:161ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 0.0.0.0:*
udpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 0.0.0.0:600ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 0.0.0.0:*
udpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 0.0.0.0:601ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 0.0.0.0:*
udpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 127.0.0.1:111ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 0.0.0.0:*
udpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 192.168.1.10:123ÂÂÂÂÂÂÂÂÂÂÂ 0.0.0.0:*
udpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 127.0.0.1:123ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 0.0.0.0:*
udpÂÂÂÂÂÂÂ 0ÂÂÂÂÂ 0 0.0.0.0:123ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 0.0.0.0:*

netstat -an | grep stunnel returns nothing.

[root@xcp-hoppe ~]# netstat -an | grep xapi
unix 2 [ ACC ] STREAM LISTENING 708872842 /var/run/openvswitch/xapi1.snoop
unix 2 [ ACC ] STREAM LISTENING 708872844 /var/run/openvswitch/xapi1.mgmt
unix 2 [ ACC ] STREAM LISTENING 834141817 /var/xapi/forker/main
unix 2 [ ACC ] STREAM LISTENING 834141947 /var/xapi/v6
unix 2 [ ] STREAM CONNECTED 831867057 /var/xapi/xapi
unix 2 [ ] STREAM CONNECTED 831832667 /var/xapi/xapi
unix 2 [ ] STREAM CONNECTED 831831438 /var/xapi/xapi
unix 2 [ ] STREAM CONNECTED 831825575 /var/xapi/xapi
unix 2 [ ] STREAM CONNECTED 827814254 /var/xapi/forker/main
unix 2 [ ] STREAM CONNECTED 806731261 /var/xapi/forker/main
unix 2 [ ] STREAM CONNECTED 797242460 /var/xapi/forker/main

New pastebin is up, with 1749 lines. Enjoy :p

http://pastebin.com/gHTeNqXb

Thanks!

On 20 January 2012 16:21, Dave Scott <Dave.Scott@xxxxxxxxxxxxx> wrote:

Hi,

Â

Thanks for the info.

Â

Could you check whether stunnel is running in âps axfâ? Also check in ânetstat âanâ to see whether something is listening on port 443 (should be stunnel) and port 80 (should be xapi).

Â

The pastebin text stops at line 310, which looks inoccuous. Is there anything after that?

Â

Cheers,

Dave

Â

Â

Â

From: Lars Seeliger [mailto:meesterlars@xxxxxxxxx]
Sent: 20 January 2012 14:50


To: Dave Scott
Cc: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-API] xapi will no longer start - what are my options?

Â

It's a full install from an XCP CD.

# service xapissl status
xapissl (pid 2323) is running...

I performed a restart of xapissl anyway, and xe-toolstack-restart still fails starting the xapi service. Any other ideas? What would happen if I were to restart the system or perform a reinstall?

Our customer and us are pretty nervous now, as they have not had a successful backup since last week Friday. So what else can I try?

Thanks, Dave!

On 20 January 2012 15:41, Dave Scott <Dave.Scott@xxxxxxxxxxxxx> wrote:

Hi,

Â

I should have asked earlier: is this a host installed via the XCP CD, or is this a Debian system running the xcp- packages?

Â

It looks like xapi canât find a running stunnel, and it looks like the xe-toolstack-restart failed to run â/sbin/service xapissl restartâ. Do you have stunnel running, and listening on port 443? On a system installed via the XCP CD, âservice xapissl restartâ should start stunnel. On a Debian system â I believe â the xapi init.d script itself starts stunnel.

Â

Dave

Â

From: Lars Seeliger [mailto:meesterlars@xxxxxxxxx]
Sent: 20 January 2012 12:15
To: Dave Scott
Cc: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-API] xapi will no longer start - what are my options?

Â

Hey, Dave

Thanks for the prompt response. For fear of not including enough info, I've pasted the entire xensource.log contents here:
http://pastebin.com/AW12gfM0

If you need anything else, just shout; this problem has ruined my day! :p

On 20 January 2012 12:53, Dave Scott <Dave.Scott@xxxxxxxxxxxxx> wrote:

Hi Lars,

Â

Have a look in the main xapi logs (in the confusingly-named file /var/log/xensource.log). Start from the bottom and reverse-search to the string âXAPI SERVER STARTINGâ. The lines after that will show how far the startup sequence got.

Â

Cheers,

Dave

Â

Â

Â

From: xen-api-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-api-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Lars Seeliger
Sent: 20 January 2012 10:23
To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] xapi will no longer start - what are my options?

Â

Hi there

A scripted backup running on one of our XCP installations failed a few days ago, while exporting a snapshot. After the failure I tried to delete the snapshot in question, to no avail (something about the VDI being in use).

Anyway, I thought an xe-toolstack-restart would reset any lock on that file, allowing me to delete the no longer needed snapshot. Unfortunately, xapi is now unable to start.

I've just tried again, and this appears in /var/log/messages:

Jan 20 11:01:21 xcp-hoppe xapi: [ info|xcp-hoppe|0 thread_zero||watchdog] (Re)starting xapi...
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.850Z||1172|About to bind to /var/xapi/forker/fd_e8f89481-9aae-05a5-1d73-fbb713f58ea3
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.850Z||1172|bound, listening
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.851Z||2300|Child here!
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.851Z||2301|Grandchild here!
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.851Z||2301|Started: state.cmdargs = [/sbin/service;xapissl;restart]
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.851Z||2301|Started: state.env = [PATH=/sbin:/usr/sbin:/bin:/usr/bin]
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.852Z||2301|Selecting in handle_comms_no_fd_sock2
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.852Z||2301|Done
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.852Z||2301|fd sock
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.852Z||2301|Selecting in handle_comms_with_fd_sock2
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.852Z||2301|Done
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.852Z||2301|fd sock2
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.852Z||2301|Received fd named: ed350b47-3eb6-63e0-38c5-3beaaefb65dd - duping to 1 (from 6)
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.852Z||2301|Selecting in handle_comms_with_fd_sock2
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.852Z||2301|Done
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.852Z||2301|fd sock2
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.852Z||2301|Received fd named: d810a903-961d-bb1e-aeb7-b39c98e5eefa - duping to 2 (from 6)
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.852Z||2301|Selecting in handle_comms_with_fd_sock2
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.852Z||2301|Done
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.852Z||2301|comms sock
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.852Z||2301|Exec
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.852Z||2301|Finished...
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.852Z||2301|Args after replacement = [/sbin/service;xapissl;restart]
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:25.852Z||2301|I've received the following fds: [2;1]Â
Jan 20 11:04:26 xcp-hoppe fe: 20120120T10:04:26.942Z||2301|Caught unexpected exception: Unix.Unix_error(31, "write", "")
Jan 20 10:05:41 xcp-hoppe HVM5652[12007]:ÂÂÂ XENNET: WARNING: No handler for oid 0xffda0014.
Jan 20 10:05:41 xcp-hoppe HVM5652[12007]:ÂÂÂ XENNET: WARNING: No handler for oid 0xffa0ffa1.
Jan 20 10:05:41 xcp-hoppe HVM5652[12007]:ÂÂÂ XENNET: WARNING: Bad tcp task offload header?
Jan 20 10:05:41 xcp-hoppe HVM5652[12007]:ÂÂÂ XENNET: WARNING: Bad tcp task offload header?
Jan 20 11:06:16 xcp-hoppe snmpd[15173]: Received SNMP packet(s) from UDP: [192.168.1.1]:2227
Jan 20 11:06:16 xcp-hoppe snmpd[15173]: Received SNMP packet(s) from UDP: [192.168.1.1]:2228
Jan 20 11:06:17 xcp-hoppe snmpd[15173]: Received SNMP packet(s) from UDP: [192.168.1.1]:2229
Jan 20 11:06:17 xcp-hoppe snmpd[15173]: Received SNMP packet(s) from UDP: [192.168.1.1]:2230
Jan 20 11:06:25 xcp-hoppe python: PERFMON: caught socket.error: (111 Connection refused) - restarting XAPI session
Jan 20 10:08:36 xcp-hoppe HVM5652[12007]: Time offset set 3569, added offset -1
Jan 20 11:08:54 xcp-hoppe python: PERFMON: Caught signal 15 - exiting
Jan 20 11:08:54 xcp-hoppe python: PERFMON: 11 Resource temporarily unavailable
Jan 20 11:08:54 xcp-hoppe python: PERFMON: Traceback (most recent call last):
Jan 20 11:08:54 xcp-hoppe python: PERFMON:ÂÂ File "/opt/xensource/bin/perfmon", line 930, in ?ÂÂÂÂ rc = main()
Jan 20 11:08:54 xcp-hoppe python: PERFMON:ÂÂ File "/opt/xensource/bin/perfmon", line 880, in mainÂÂÂÂ cmd = cmdsock.recv(cmdmaxlen)
Jan 20 11:08:54 xcp-hoppe python: PERFMON: error: (11, 'Resource temporarily unavailable')
Jan 20 11:08:54 xcp-hoppe python: PERFMON: caught socket.error: (111 Connection refused) - restarting XAPI session
Jan 20 11:08:55 xcp-hoppe v6d: [ info|xcp-hoppe|0||watchdog] (Re)starting v6d...
Jan 20 11:08:55 xcp-hoppe xapi: [ info|xcp-hoppe|0 thread_zero||watchdog] (Re)starting xapi...
Jan 20 10:10:45 xcp-hoppe HVM5641[28792]: Time offset set 3563, added offset -1
Jan 20 11:13:45 xcp-hoppe python: PERFMON: caught socket.error: (111 Connection refused) - restarting XAPI session


/var/log/SMI contains:

[2598] 2012-01-20 11:08:55.277830ÂÂÂ VASSR run ['/opt/xensource/sm/VASSR', '<methodCall><methodName>sr_get_driver_info</methodName><params><param><value><struct><member><name>host_ref</name><value>OpaqueRef:NULL</value></member><member><name>command</name><value>sr_get_driver_info</value></member><member><name>args</name><value><array><data/></array></value></member><member><name>device_config</name><value><struct/></value></member></struct></value></param></params></methodCall>']
[2598] 2012-01-20 11:08:55.278332ÂÂÂ Warning: vdi_[de]activate present for vastsky
[2619] 2012-01-20 11:08:55.858537ÂÂÂ Warning: vdi_[de]activate present for dummy

Not sure there's anything of value in those logs...

I'm somewhat desperate, as I'm unable to perform any xe commands and am worried a reboot of the server will not magically bring xapi back online, meaning the VMs will not start. This XCP host is critical to one of our customer's infrastructure. It's Friday and I could possibly go there this evening and perform tasks necessary to bring everything back online, I just don't quite know what my options are, aside from reboot and perhaps an in-place install of XCP.

Does anyone have any bright ideas? I'm all ears!

Â

Â

Â


_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

 

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.