|
On 20/08/14 17:40, Firma Averlon wrote:
Hi,
what do you mean with "message-cli". When typing this as command
on the shell it does return nothing.
I get this sort of thing:
mirage@cubietruck:~/buildroot$ message-cli diag
Switch uptime: 42329119 ms
Permanent queues
org.xen.xcp.memory next update expected: 1631 ms
org.xen.xcp.storage next update expected: 1680 ms
org.xen.xcp.xenops.classic next update expected: 911 ms
5: from: xapi%3A7231 age: 3238042 ms
{\"method\": \"UPDATES.get\", \"params\":
[\"org.xen.xcp.xenops.classi
reply_to: xapi%3A7231
org.xen.xcp.storage.dummy next update expected: 1540 ms
org.xen.xcp.storage.nfs next update expected: 1536 ms
org.xen.xcp.networkd next update expected: 910 ms
org.xen.xcp.storage.ocfsohba next update expected: 1676 ms
org.xen.xcp.storage.lvmoiscsi next update expected: 1542 ms
org.xen.xcp.storage.file next update expected: 1539 ms
org.xen.xcp.storage.lvmohba next update expected: 1587 ms
org.xen.xcp.storage.udev next update expected: 1534 ms
org.xen.xcp.storage.iso next update expected: 1403 ms
org.xen.xcp.storage.hba next update expected: 1666 ms
org.xen.xcp.xenops.xenlight next update expected: 912 ms
5: from: xapi%3A29752 age: 3220923 ms
{\"method\": \"UPDATES.get\", \"params\":
[\"org.xen.xcp.xenops.xenlig
reply_to: xapi%3A29752
org.xen.xcp.storage.ocfsoiscsi next update expected: 1670 ms
org.xen.xcp.storage.iscsi next update expected: 1583 ms
org.xen.xcp.storage.ext next update expected: 1539 ms
org.xen.xcp.storage.ffs next update expected: 911 ms
org.xen.xcp.storage.lvm next update expected: 1540 ms
Transient queues
xapi%3A29752 next update expected: 1681 ms
Did you run the 'xenserver-install-wizard' script? It's not just
xapi that needs to be started but many other services (fe, rrdd,
message-switch, xenopsd, etc)?
Jon
|
