Xenserver – xe-toolstack restart – i lost connection from xencenter

citrixvirtualizationxenxenserver

After Xencenter-toolstack restart i lost connection from xencenter

I try to restart using ssh – putty following message is showing and i lost the browser access also …………

All xe command is not working and postponed on ssh ….

@xs01p04 log]# xe-toolstack-restart
Stopping xapi: [ OK ]
Stopping the v6 licensing daemon: [ OK ]
Stopping the memory ballooning daemon: [ OK ]
Stopping perfmon: [FAILED]
Stopping the xenopsd daemon: [ OK ]
Stopping the XCP RRDD daemon: [ OK ]
Stopping the XCP networking daemon: [ OK ]
Stopping the fork/exec daemon: [ OK ]
Starting the fork/exec daemon: [ OK ]
Starting the XCP networking daemon: . [ OK ]
Starting the XCP RRDD daemon: [ OK ]
Starting the xenopsd daemon: [ OK ]
Starting perfmon: [ OK ]
Starting the memory ballooning daemon: [ OK ]
Starting the v6 licensing daemon: [ OK ]
Starting xapi: OK [ OK ]

Thank Advance …

Update #1

@yagmoth555

1) i try to migrate one vm to another storage location that time some unexpected error occurred and yello state is appear Then i create new vm from snapshot

Dead vm still there

After one week 2) yesterday i try to reboot a vm and its again yellow state ( its not previous one)

Then i try to restart xentoolstack from xencenter after few minute i lost xencenter connection I cannot connect through xencenter

But https:ip is appearing

Then i login through ssh and restart toollstack through command line After that i lost http acess also

Nom XE command is hanged up but Vm are still working

Update #2 @yagmoth555 Thanks advance

tail -n 15 /var/log/messages

Oct 16 20:08:30 xs01p04 ovsdb-server: 01993|reconnect|INFO|ssl:10.101.2.52:6632: waiting 8 seconds before reconnect

Oct 16 20:08:33 xs01p04 fe: 26045 (/usr/bin/ovs-appctl bond/show bond2) exitted with code 2

Oct 16 20:08:33 xs01p04 xcp-networkd: [error|xs01p04|1|monitor_thread|network_utils] Call '/usr/bin/ovs-appctl bond/show bond2' exited with code 2 [stdout = ''; stderr = 'no such bond ovs-appctl: ovs-vswitchd: server returned reply code 501 ']

Oct 16 20:08:38 xs01p04 ovsdb-server: 01994|reconnect|INFO|ssl:10.101.2.52:6632: connecting…

Oct 16 20:08:38 xs01p04 ovsdb-server: 01995|reconnect|WARN|ssl:10.101.2.52:6632: connection attempt failed (No route to host)

Oct 16 20:08:38 xs01p04 ovsdb-server: 01996|reconnect|INFO|ssl:10.101.2.52:6632: waiting 8 seconds before reconnect

Oct 16 20:08:38 xs01p04 fe: 26054 (/usr/bin/ovs-appctl bond/show bond2) exitted with code 2
Oct 16 20:08:38 xs01p04 xcp-networkd: [error|xs01p04|1|monitor_thread|network_utils] Call '/usr/bin/ovs-appctl bond/show bond2' exited with code 2 [stdout = ''; stderr = 'no such bond ovs-appctl: ovs-vswitchd: server returned reply code 501 ']

Oct 16 20:08:43 xs01p04 fe: 26063 (/usr/bin/ovs-appctl bond/show bond2) exitted with code 2

Oct 16 20:08:43 xs01p04 xcp-networkd: [error|xs01p04|1|monitor_thread|network_utils] Call '/usr/bin/ovs-appctl bond/show bond2' exited with code 2 [stdout = ''; stderr = 'no such bond ovs-appctl: ovs-vswitchd: server returned reply code 501 ']

Oct 16 20:08:46 xs01p04 ovsdb-server: 01997|reconnect|INFO|ssl:10.101.2.52:6632: connecting…

Oct 16 20:08:46 xs01p04 ovsdb-server: 01998|reconnect|WARN|ssl:10.101.2.52:6632: connection attempt failed (No route to host)

Oct 16 20:08:46 xs01p04 ovsdb-server: 01999|reconnect|INFO|ssl:10.101.2.52:6632: waiting 8 seconds before reconnect

Oct 16 20:08:48 xs01p04 fe: 26081 (/usr/bin/ovs-appctl bond/show bond2) exitted with code 2

Oct 16 20:08:48 xs01p04 xcp-networkd: [error|xs01p04|1|monitor_thread|network_utils] Call '/usr/bin/ovs-appctl bond/show bond2' exited with code 2 [stdout = ''; stderr = 'no such bond ovs-appctl: ovs-vswitchd: server returned reply code 501 ']

Update #3 @yagmoth555 Thanks advance
xe-toolstack-restart
Stopping xapi: [ OK ]

Stopping the v6 licensing daemon: [ OK ]

Stopping the memory ballooning daemon: [ OK ]

Stopping perfmon: [FAILED]

Stopping the xenopsd daemon: [ OK ]

Stopping the XCP RRDD daemon: [ OK ]

Stopping the XCP networking daemon: [ OK ]

Stopping the fork/exec daemon: [ OK ]

Starting the fork/exec daemon: [ OK ]

Starting the XCP networking daemon: . [ OK ]

Starting the XCP RRDD daemon: [ OK ]

Starting the xenopsd daemon: [ OK ]

Starting perfmon: [ OK ]

Starting the memory ballooning daemon: [ OK ]

Starting the v6 licensing daemon: [ OK ]

Starting xapi: OK [ OK ]

service xapissl restart

which: no stunnel4 in (/sbin:/usr/sbin:/bin:/usr/bin)
Stopping xapi SSL:
Starting xapi SSL:

Best Answer

xe toolstack-restart will always cut your xencenter connection. (but the vm continue to run correctly on the host)

Please log in normal console (iDRAC, iLO, etc..), as that mean your XAPI can't restart and your server state is unknown.

I would check with dmesg or in /var/log for xensource.log for any errors.

Related Solutions

Citrix XenServer: how to add RAM to a guest VM without XenCenter

In XenServer 6.0, this can be done with the vm-memory-limits-set command:

[root@localhost 1274]# xe help vm-memory-limits-set
command name            : vm-memory-limits-set
        reqd params     : static-min, static-max, dynamic-min, dynamic-max
        optional params : <vm-selectors>
        description     : Configure the memory limits of a VM. The simplest way to select the VM on which the operation is to be performed is by supplying the argument 'vm=<name or uuid>'. VMs can also be specified by filtering the full list of VMs on the values of fields. For example, specifying 'power-state=halted' will select all VMs whose power-state field is equal to 'halted'. Where multiple VMs are matching, the option '--multiple' must be specified to perform the operation. The full list of fields that can be matched can be obtained by the command 'xe vm-list params=all'. If no parameters to select VMs are given, the operation will be performed on all VMs.

Assuming the VM is powered down, here is an example of actually using it:

[root@localhost 1274]# xe vm-list name-label=Local-PerformanceVM params=all |grep memory
                 memory-actual ( RO): 0
                 memory-target ( RO): <expensive field>
               memory-overhead ( RO): 4194304
             memory-static-max ( RW): 268435456
            memory-dynamic-max ( RW): 268435456
            memory-dynamic-min ( RW): 268435456
             memory-static-min ( RW): 16777216
               recommendations ( RO): <restrictions><restriction field="memory-static-max" max="34359738368" /><restriction field="vcpus-max" max="8" /><restriction property="number-of-vbds" max="7" /><restriction property="number-of-vifs" max="7" /></restrictions>
                        memory (MRO):
[root@localhost 1274]# xe vm-memory-limits-set dynamic-max=300000000 dynamic-min=300000000 static-max=300000000 static-min=16777216 name-label=Local-PerformanceVM
[root@localhost 1274]# xe vm-list name-label=Local-PerformanceVM params=all |grep memory
                 memory-actual ( RO): 0
                 memory-target ( RO): <expensive field>
               memory-overhead ( RO): 5242880
             memory-static-max ( RW): 300000000
            memory-dynamic-max ( RW): 300000000
            memory-dynamic-min ( RW): 300000000
             memory-static-min ( RW): 16777216
               recommendations ( RO): <restrictions><restriction field="memory-static-max" max="34359738368" /><restriction field="vcpus-max" max="8" /><restriction property="number-of-vbds" max="7" /><restriction property="number-of-vifs" max="7" /></restrictions>
                        memory (MRO):
[root@localhost 1274]#

XenCenter can’t connect to XCP server after restart

If anyone stumbles across the same phenomenon, here's what I found out (spoiler: I'm stupid):

Of course, what should have immediately raised an alarm was the fact that I wrote openwsmand when the xapi process is actually responsible for handling connection attempts from XenCenter and the likes. What happened here was that I just did a simple netstat -plant and noticed that openwsmand was listening at port 443, which I knew was the port that XenCenter tried to connect to, so I assumed this was the right process.

But of course, XenCenter can't connect to openwsmand because this is a tool of the OpenManage Suite by Dell. I suppose that when I first installed OpenManage, openwsmand tried to bind to port 443, but this was already in use by xapi, so it gave up and I was still able to connect.

When I restarted the machine, however, the openwsmand service was started before xapi, so it occupied port 443, leaving me with no possibility to connect using XenCenter.

A simple

$ service openwsmand stop
$ xe-toolstack-restart
$ service openwsmand start

fixed the problem. Currently running VMs won't be affected by this operation.

Best Answer

Related Solutions

Citrix XenServer: how to add RAM to a guest VM without XenCenter

XenCenter can’t connect to XCP server after restart

Related Topic