Opened 12 years ago

Closed 12 years ago

#129 closed (fixed)

when gmoc.py tries to submit data, it should store the response it gets in a variable

Reported by: chaos@bbn.com Owned by: somebody
Priority: major Milestone: GEC15 demo
Component: Clients Version:
Keywords: v1.1.0 Cc:
Dependencies:

Description

When gmoc.py tries to submit relational or measurement data, it prints parts of the response it gets, if invoked in verbose mode. In addition to this, gmoc.py should also store those responses in variables belonging to the object, so that if the calling program wants to print things at a different granularity from the gmoc.py defaults, it can.

Change History (3)

comment:1 Changed 12 years ago by chaos@bbn.com

Provisionally listing this as "GEC15" because sites need it for debugging submissions and i think it is very easy. If it is not very easy, it can slip.

comment:2 Changed 12 years ago by chaos@bbn.com

Keywords: v1.1.0 added

This is still active in v1.1.0.

comment:3 Changed 12 years ago by chaos@bbn.com

Resolution: fixed
Status: newclosed

As of v1.1.4, the code:

result = data.storeMeasurements(
           reporter=aggregate,
           obj=pop,
         )
if result != 0:
  print "Attempted to submit agg measurement data, but received: %s" % result
  print "HTTP status code was: %d" % data.resultStatus
  print "Error message was: %s" % data.errorMessage
  sys.exit(1)

on a failing submission yields:

tau-verde,[~],22:56(1)$ sudo -u ganglia ./report_relations   
Attempted to submit agg measurement data, but received: 16
HTTP status code was: 500
Error message was: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>500 Internal Server Error</title>
</head><body>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error or
misconfiguration and was unable to complete
your request.</p>
<p>Please contact the server administrator,
 root@localhost and inform them of the time the error occurred,
and anything you might have done that may have
caused the error.</p>
<p>More information about this error may be available
in the server error log.</p>
<hr>
<address>Apache/2.2.3 (Red Hat) Server at gmoc-db2.grnoc.iu.edu Port 443</address>
</body></html>

So this is fixed.

Note: See TracTickets for help on using tickets.