Jump to content
Updated Privacy Statement

Keith Woodworth

Legacy Group
  • Posts

    16
  • Joined

  • Last visited

Posts posted by Keith Woodworth

  1. Hi. You are right in that this is not an XCP-ng issue.

     

    XCP-rrdd a system process and it was chewing up RAM for some reason.

    Like so much RAM that XenCenter was throwing errors about that host

    being very low on free memory every 30 mins, then it would clear for a bit.

     

    When I finally tracked down what was causing it, and this being the

    master of the pool, I just restarted the xcp-rrdd process. This fixed the

    memory low alarms.

     

    I have two other hosts in the pool and are fine. Just this one started

    having low memory alarms due to xcp-rrdd suddenly using most of

    the memory.

     

    Thanks,

    Keith

  2. Xenserver 7.2.

     

    /sbin/xcp-rrdd suddenly taking up a lot of RAM.

     

    Can i just do a:

     

    systemctl restart xcp-rrdd

     

    on the CLI to restart it? It seems like this process is for gathering/displaying process/perf information.

     

    Thanks.

     

     

  3. Xenserver 7.2.

     

    Master server has thousands of lines and fulling up /var/log:

     

    XenServer1-10 tap-ctl[612]: tap-err:tap_ctl_connect: couldn't connect to /var/run/blktap-control/ctl7539: Connection refused

     

    That is just one of the lines but they are all the same except for the /var/run/blktap-contral/ctl<number>

     

    It looks like every few seconds tap-ctl fires up and tries to connect to everything in /var/run/blktap-control of which everything

    throws a connection refused.

     

    [root@XenServer1-10 blktap-control]# ls -l | wc -l
    1549

     

    There is 1500+ files in there, but on the other two Xen hosts there are only files that pertain to the VM's that are running

    on that host.

     

    I cannot find much info about this. There are currently only 4 VM's on this host so I would have expected only

    4 files or so.

     

    How to clean this up and fix it? I'm thinking migrating the VM's to the other hosts, making another host master

    then rebooting this server.

     

    This is the Master host of the 3 in the pool.

     

    Thanks,

    Keith

     

     

  4. Hello.

    Thank you for answering my questions.

     

    Final update.

     

    I found a topic thread very similar to what I was seeing:

     

    https://discussions.citrix.com/topic/389164-xenserver-host-disabled-after-pool-master-migration/page/2/

     

    Main diff, I didn't do anything with pool-master before this happened.

     

    One of the people in that thread just restarted their server. That seemed my easiest route rather than changing and

    renaming files on the server.

     

    So that's what I did, just hit the console and did a reboot. Took a while (forgot how long it can take to restart

    one of these) but it eventually came back up and rejoined the pool automatically.

     

    Though I'm still without network stats on the console directly, but xsconsole shows all the network and

    management info.

     

    Thank you.

    Keith

     

     

     

  5. Hi.

    So update to this as I don't like leaving these things hanging.

     

    I have managed to move all the VM's that were still running on this host to other

    xenserver hosts.

     

    I followed instructions on this link:

     

    https://www.serveroperations.net/citrix/start-a-xenserver-vm-that-throws-vdi-not-available-error-when-you-attempt-to-start

     

    and was able to restart each VM on a new Xen host.

     

    The Xen host is still not in the pool and the only option is to destroy the host from Xencenter.

     

    Thing is, everything else on this Xen host seems ok, xsconsole from CLI works, I can see all network

    interfaces, ssh into the Xen host, restart xentoolstack, restart xapi, but it is dropped from pool.

     

    I'd like to try this:

     

    https://support.citrix.com/article/CTX221207

     

    But it is from an older version of Xen and not sure if it will work as the network stack seems to be

    fully working.

     

    Anything else I can try to get this host to rejoin the pool? One last, I have not actually restarted this

    Xen host yet. Is this something that should be ok to do?

     

    Thank you.

    • Like 1
  6. I did try on a test VM I have running on that host.

     

    First I did:

     

    xe vm-list resident-on=9b86ecc6-7a97-4c71-b507-9785cd72a1c2 (UUID being Host 3)

     

    To get the list of VM UUID's.

     

    Then did on Host 3:

    xe vm-reset-powerstate uuid=a8b5fc05-07bc-c67e-339e-66e4110c7d32 force=true


    Should this have been done from the master?

     

    It shutdown the VM and now shows up as a powered off VM, but in reality the VM is still

    running but it has disassociated the VDI and get a VDI is not available when trying to start

    the VM in Xencenter on another host.

     

    Is there a different xe cli to do a forced reset associate the VDI back to the VM?

    Thank you.

    Keith

  7. Hi folks, not sure where to post this but will try this in the CLI Forum.

     

    Xenserver 7.2, 3 hosts in a pool.

    Host 3 in the pool has become unresponsive/disconnected in XenCenter. Red dot with white line through it.

    Currently there are 4 VM's running on that host. All hosts are up and working as normal, except one which I

    have managed to put into a state where VDI is not available, but is still running and can SSH to that VM.

     

    Not in HA

    can ssh to disconnected host 3,

    toolstack-restart works on that host 3

    xapi is running and have restarted it on host 3

    4 VM's running on host 3

    xe host-list  on master and slaves all show the 3 Xenserver hosts in the list.

    Pool.conf on host 3 shows correct: slave:10.11.32.230 for the master.

     

    Xencenter shows ram and cpu usage for disconnected host.

    I can list all the VM's running via CLI on host 3.

    From /var/xapi the state.db file shows last update on Sept 21 @ 15:28.

    All NTP times are in sync, DNS works.

     

    I have not had a server in a pool do this before and did a command line shutdown of a test VM

    so I could restart it on one of the other hosts.

     

    I ran this CLI on Host 3:

    xe vm-reset-powerstate uuid=a8b5fc05-07bc-c67e-339e-66e4110c7d32 force=true

     

    I can now see this VM in Xencenter now but it is shutdown and is not longer in the CLI

    list of VMs running on host 3.

     

    But now I cannot start that VM as VDI is not available but it is still running as I can ssh

    to that VM and do DNS queries against it. (test DNS server), so the powerstate command

    did not shutdown the machine properly.

     

    Can I issue a shutdown on the VM CLI? CentOS 7.latest, was fully patched last week.

     

    So I have Host 3 disconnected in XenCenter, the VMs on the host are running and accessible

    but one VM is now VDI not available.

     

    How to reattach the VDI to the VM? Tons of articles, all slightly different and so far have not been able

    to reconnect VDI to the VM.

     

    I see this article: https://support.citrix.com/article/CTX221207

    This link lists steps to reconnect a host into a pool, but it doesn't mention anything about any VMs

    that might be running on a host.

     

    All VM's in shared NFS mounted Netapp, no data on local SR of Host 3.

     

    Some promising links in discussions.citrix.com are no longer working. Anyone have some

    links to help reconnect host 3 and reattach the VDI to my VM?

     

    Thank you,

    Keith

     

     

  8. Have a chance to purchase a couple of R420's with Two E5-2430v2 CPU's.

     

    HCL list does not cover this CPU or the version of XenServer 7.2 that I want to run.

     

    I have seen mentioned that this CPU seems to be supported as I have read others that have used this model CPU.

     

    This is just for a lab for testing some stuff out with XenServer 7.2, which has been completely

    been pulled from any mention on the Citrix site or from any downloads. Anyone know why that

    is?

     

    But at any rate, just wondering if these CPU's will work ok?

     

    Thanks,

    Keith

×
×
  • Create New...