Merge pull request #94 from vatesfr/errors-and-troubleshooting
Common errors and troubleshootting
This commit is contained in:
@@ -15,4 +15,8 @@ ACLs will thus apply only on "users".
|
||||
|
||||
> Any account created by an external authentication process (LDAP, SSO...) will be a **user** without any permission.
|
||||
|
||||
Also, you don't have to create an external user by yourself: it will be created automatically in Xen Orchestra after its first connection.
|
||||
Also, you don't have to create an external user by yourself: it will be created automatically in Xen Orchestra after its first connection.
|
||||
|
||||
## Debugging
|
||||
|
||||
If you can't log in with your LDAP/SAML/Github/Google settings, please check the logs of `xo-server` while you attempt to connect. It will give you hints about the error encountered. You can do that with a `tail -f /var/log/syslog -n 100` on your XOA.
|
||||
|
||||
@@ -39,3 +39,7 @@ Workarounds:
|
||||
* wait for Citrix to release thin provisioning on LVM
|
||||
* wait for Citrix to allow another mechanism than snapshot to be able to export disks
|
||||
* use less than 50% of SR space or don't backup all VMs
|
||||
|
||||
### Could not find the base VM
|
||||
|
||||
This message appears when the previous replicated VM has been deleted on the target side which breaks the replication. To reset the process it's necessary to delete VM snapshot related to this CR job on the original VM. The name of this snapshot is: `XO_DELTA_EXPORT: <name label of target SR> (<UUID of target SR>)`
|
||||
|
||||
36
docs/general-troubleshooting.md
Normal file
36
docs/general-troubleshooting.md
Normal file
@@ -0,0 +1,36 @@
|
||||
# Common errors and troubleshooting
|
||||
|
||||
## Recommendation
|
||||
If you think you have a problem with your XOA, start by typing`xoa check`command in your terminal:
|
||||
|
||||
```
|
||||
$ xoa check
|
||||
✔ Node version
|
||||
✔ Disk space for /var
|
||||
✔ Disk space for /
|
||||
✔ XOA version
|
||||
✔ xo-server config syntax
|
||||
✔ Appliance registration
|
||||
✔ Internet connectivity
|
||||
```
|
||||
If the result you have is completely different from that, or if error messages are displayed, lost packets, etc., you have, indeed, a problem. The next step should be to check in this document if there is an existing troubleshooting for the problem you have.
|
||||
|
||||
> You can also access the log by using this command: `$ tail -f /var/log/syslog` ([learn more](https://xen-orchestra.com/docs/logs.html))
|
||||
|
||||
## General
|
||||
|
||||
* [Empty page after login](https://xen-orchestra.com/docs/troubleshooting.html#empty-page-after-login)
|
||||
* [Network issues](https://xen-orchestra.com/docs/troubleshooting.html#network-issues)
|
||||
* [Out of memory](https://xen-orchestra.com/docs/troubleshooting.html#memory)
|
||||
* [Transparent proxy and updater](https://xen-orchestra.com/docs/troubleshooting.html#behind-a-transparent-proxy)
|
||||
* [SSL self-signed certificate expired](https://xen-orchestra.com/docs/troubleshooting.html#updating-ssl-self-signed-certificate)
|
||||
* [User authentication](https://xen-orchestra.com/docs/authentication.html#debugging)
|
||||
|
||||
## Backup troubleshooting
|
||||
|
||||
* [Unhealthy VDI chain](https://xen-orchestra.com/docs/backup_troubleshooting.html#unhealthy-vdi-chain)
|
||||
* [SR_backend_failure_44](https://xen-orchestra.com/docs/backup_troubleshooting.html#srbackendfailure44-insufficient-space)
|
||||
* [Could not find the base VM](https://xen-orchestra.com/docs/backup_troubleshooting.html#could-not-find-the-base-vm)
|
||||
|
||||
## You haven't found a solution here?
|
||||
Open a ticket concerning your issue on your personal space [here](https://xen-orchestra.com/#!/member/support)
|
||||
@@ -13,3 +13,7 @@ Better the plan, faster the support with higher priority.
|
||||
If you are using Xen Orchestra via the sources, you can ask questions on our forum. However, there isn't any guarantee about answers nor when someone will be there to help you.
|
||||
|
||||
If Xen Orchestra is used in production, please subscribe to a plan.
|
||||
|
||||
## Open a ticket
|
||||
|
||||
You can open a ticket describing your issue directly from your personnal space [here](https://xen-orchestra.com/#!/member/support)
|
||||
|
||||
Reference in New Issue
Block a user