Differences

This shows you the differences between two versions of the page.

--- virtualization:xenserver:xenserver_troubleshoot [2014/11/23 10:04]
gcooper
+++ virtualization:xenserver:xenserver_troubleshoot [2019/04/30 06:34] (current)
gcooper
@@ Line 1: / Line 1: @@
-====== Citrix XenServer Troubleshooting Notes ======
+====== Citrix XenServer Troubleshooting ======
+**Tools for XenServer Troubleshooting**: http://blogs.citrix.com/2011/05/06/tools-for-xenserver-troubleshooting/
+**How to Collect Diagnostic Information for XenServer**: http://support.citrix.com/article/CTX125372
+**Helpful XenServer Commands**: http://support.randomsolutions.nl/432213-Helpfull-XenServer-Commands
 ===== Kernel Panic (Hang on Boot) =====
@@ Line 9: / Line 15: @@
 ==== RAID Metadata on Disk ====
-If you are installing to disks that previously had been used in RAID configurations, you may get a kernel panic (hang on boot).
+See also **[[computing:storage:raid_metadata_removal|RAID Metadata Removal]]**
-In the case of Intel (integrated) RAID:
+:!: If you are installing to disks that previously had been used in RAID configurations, you may get a **kernel panic** (hang on boot).
-  - Configure the SATA in the host BIOS to RAID mode
+:!: You probably won't see the kernel panic (hang on boot) until **after installing SP1** (XenServer 6.2).
-  - Enter the RAID configuration (Control-I)
-  - Delete the RAID volumes
-  - If the RAID configuration (metadata) is 'messed up'
-    - Recreate a RAID volume
-    - Reboot and go back into the RAID configuration (Control-I) again
-    - Delete the RAID volume just created
-    - Reboot again
-  - Install XenServer normally
-:!: You probably won't see the kernel panic (hang on boot) until after installing SP1 (XenServer 6.2).
+==== Check Disk Space ====
+<file>
+df -h | grep "/$" | head -n 1
+</file>
+Looking for files bigger than a given size (specify path and size):
+<file>
+find / -mount -type f -size +20M -exec ls -lh {} \; | awk '{ print $9 ": " $5 }'
+</file>
+:!: You can pretty much ignore anything in ''/var/run/sr-mount/'' as it's not on the local filesystem.
+:!: Take special care when using wildcards with the ''rm'' command!
+The first step might be to delete all files such as downloaded patches from ''/root'':
+<file>
+ls -al /root
+rm -rf /root/*
+</file>
 ===== File System on Control Domain Full =====
+https://support.citrix.com/article/CTX202821
 http://xenserver.org/component/easyblog/entry/xenserver-root-disk-maintenance.html?Itemid=179
-Check disk space:
+===== Detach a VHD from the Control Domain =====
+<note important>It is suggested to rename the REAL virtual disk so you DO NOT delete the wrong one!  Rename the real one because you can't rename the one connected to the control domain.  You can rename the REAL one back to the original name when you are done.</note>
+List out the VBD (connector object between VM and VDI) based on the VDI UUID:
 <file>
-df -h | grep "/$" | head -n 1
+xe vdi-list | grep -B1 -A5 -i "part-of-vm-name"
+xe vdi-list name-label="<VDI-name-label>"
+xe vbd-list vdi-uuid=<UUID of VDI>
 </file>
+<note important>Verify the VBD is the one connected to control domain!
+</note>
-Looking for files bigger than a given size (specify path and size):
+Once done, you want to first try to make VBD inactive (it may already be inactive),
 <file>
-find / -mount -type f -size +20M -exec ls -lh {} \; | awk '{ print $9 ": " $5 }'
+xe vbd-unplug uuid=<UUID of VBD>
 </file>
-:!: You can pretty much ignore anythin in ''/var/run/sr-mount/'' as it's not on the local filesystem.
+Once done, you can then break the connection:
+<file>
+xe vbd-destroy uuid=<UUID of VBD>
+</file>
+Check in XenCenter to verify and delete the virtual disk.
+===== Log Partition Full =====
 Delete rotated log files:
@@ Line 47: / Line 87: @@
 <file>
 find /var/log/ -type f -name *.gz -exec rm -f {} \;
+</file>
+Delete ''tapdisk'' log files:
+<file>
+rm -f /var/log/blktap/*
 </file>
@@ Line 76: / Line 122: @@
 <file>
-umount /mnt/backup
+umount /mnt/backup && rm -rf /mnt/backup/*
-rm -rf /mnt/backup/*
 mount -a
 </file>
+===== XAPI Database Parsing Tools =====
+Windows Version: http://support.citrix.com/article/CTX129070
+Linux Version: http://support.citrix.com/article/CTX129217
+===== XenTools =====
+FIXME Incomplete and needs verification
+This is a procedure to fix XenTools networking issues:
+  - Remove network interface via XenCenter
+  - Uninstall all Citrix XenTools packages from Add/Remove Programs
+  - Remove Citrix from filesystem and registry
+    * ''c:\program files\citrix''
+    * ''c:\program files (x86)\citrix''
+    * ''HKLM\Software\Citrix''
+  - Run in an admin command shell
+    * Stop all running XenTools services
+    * ''sc delete xenlite''
+    * ''winmgmt /resetrepository''
+  - Reboot
+  - Check things out and remove any 'ghosted' or hidden network adapters
+  - Reboot again
+  - Add network adapter in XenCenter
+  - Reconfigure the networking until it works properly again
+  - Reboot
+  - Reinstall XenTools patiently

Virtual Architects Support Wiki

User Tools

Site Tools

Differences

Page Tools