Posts

• RE: XO unresponsive when Remote storage is offline.

  Great! I think this is really the best possible approach to make it clean

  posted in Management

  O

  olivierlambert
  
• RE: XO unresponsive when Remote storage is offline.

  Hi,

  The best approach is first to unplug the PBD (or disable the remote) while the storage is UP, and then shutdown the target/storage node itself.

  The opposite is 100% causing issues due to the nature itself of a network storage.

  You can use the REST or JSON-RPC API to disable the remote and then send the shutdown order. This way, no problem.

  posted in Management

  O

  olivierlambert
  
• RE: Potential bug with Windows VM backup: "Body Timeout Error"

  Thanks for the logs @ph7, that helps narrow it down.

  Some context on what this error actually means: XO's XAPI client kills the connection if it receives nothing from the pool master for 5 minutes during the transfer. So the BodyTimeoutError on a metadata backup means the /pool/xmldbdump response from your master went silent. Either xapi stalled while producing the dump, or the connection died silently somewhere in between (a NAT/firewall/VPN dropping the connection state would look exactly like this). Note that your XO config backup succeeding right before doesn't rule out a network issue: the config backup only talks to the remote, it never touches the pool master.

  To figure out which side is failing, could you check a few things?

  1. On your backup remote, look at the file left behind by the failed run: xo-pool-metadata-backups/<scheduleId>/<poolUuid>/<date>/data. What size is it, compared to the same file from a successful run? If it's empty or tiny, the master stalled. If it looks complete, the data actually arrived and only the end-of-connection signal got lost, which would point at the network path.
  2. On the pool master, grab /var/log/xensource.log around the failure time. There should be a task named "Export pool metadata" and the xmldbdump HTTP handler. We'd like to know if it completed on the xapi side.
  3. Is there anything between your XO and the pool master, like NAT, a firewall or a VPN?
  4. Does it fail every run, or intermittently?

  @Tristis-Oris the same questions apply to your setup. The fact that it hits different pools one after the other makes me suspect something shared in the network path.

  posted in Backup

  O

  olivierlambert
  
• RE: Potential bug with Windows VM backup: "Body Timeout Error"

  Hi,

  Would be nice to have the entire log

  Could it be possible that the master or the pool was not reachable at the time of the metadata backup?

  posted in Backup

  O

  olivierlambert