search

GENI-NSF / geni-tools

Omni, stitcher, GCF sample aggregate manager, and other GENI tools.
Other
11 stars 15 forks source link

rare XMLRPC Expat error causes Omni call to fail #244

Open ahelsing opened 9 years ago

ahelsing commented 9 years ago

Josh saw his Omni call to SliverStatus fail cryptically:

$ omni -a https://lan.sdn.uky.edu:12369/protogeni/xmlrpc/am sliverstatus jbs16
  INFO:omni:Loading config file /home/jbs/.gcf/omni_config
  INFO:omni:Using control framework gpolab
  INFO:omni:Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+jbs16 expires on 2013-06-15 23:00:00 UTC
  INFO:omni:Status of Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+jbs16:
  ERROR:omni.protogeni:Call for SliverStatus of urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+jbs16 at https://lan.sdn.uky.edu:12369/protogeni/xmlrpc/am failed.: ExpatError: not well-formed (invalid token): line 266, column 27
  ERROR:omni.protogeni:    ..... Run with --debug for more information
  INFO:omni: ------------------------------------------------------------
  INFO:omni: Completed sliverstatus:

    Options as run:
                  aggregate: ['https://lan.sdn.uky.edu:12369/protogeni/xmlrpc/am']
                  framework: gpolab

    Args: sliverstatus jbs16

    Result Summary: Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+jbs16 expires on 2013-06-15 23:00:00 UTC

  Failed to get SliverStatus on jbs16 at AM https://lan.sdn.uky.edu:12369/protogeni/xmlrpc/am: ExpatError: not well-formed (invalid token): line 266, column 27 (missing result)
  Returned status of slivers on 0 of 1 possible aggregates. 
  INFO:omni: ============================================================

Imported from trac ticket #244, created by ahelsing on 02-22-2013 at 16:48, last modified: 10-17-2014 at 15:23

ahelsing commented 9 years ago

tracing this back shows that the error had to happen in the call to doSSL (that is where the error message 'Call for %s of' is created).

And indeed, unknown exceptions return a result of none (hence the string "(missing result)") plus the string representation of the error.

This begs the question of what in the XMLRPC call / library could have raised this error, of course.

Trac comment by ahelsing on 02-22-2013 at 16:50