Hi Folks,
Something seems to be borked up with the cherrypi server at aws.openmpi.org.
If one tries to get a identifier via the cpy/api/serial, the cherrypy
server experiences some kind of meltdone and reports this back as the HTTP
response:
Traceback (most recent call last):
File
"/mnt/data/mtt.open-mpi.org/mtt/server/php/cherrypy/src/env/local/lib/python2.7/site-packages/cherrypy/_cprequest.py",
line 670, in respond
response.body = self.handler()
File
"/mnt/data/mtt.open-mpi.org/mtt/server/php/cherrypy/src/env/local/lib/python2.7/site-packages/cherrypy/lib/encoding.py",
line 220, in __call__
self.body = self.oldhandler(*args, **kwargs)
File
"/mnt/data/mtt.open-mpi.org/mtt/server/php/cherrypy/src/env/local/lib/python2.7/site-packages/cherrypy/lib/jsontools.py",
line 61, in json_handler
value = cherrypy.serving.request._json_inner_handler(*args, **kwargs)
File
"/mnt/data/mtt.open-mpi.org/mtt/server/php/cherrypy/src/env/local/lib/python2.7/site-packages/cherrypy/_cpdispatch.py",
line 66, in __call__
raise sys.exc_info()[1]
HTTPError: (404, None)
We haven't done any updates to the cherrypy server running at aws.open-mpi.org
recently. We think we started seeing this behavior last week.
Thanks for any suggestions on how to go about debugging this problem.
Howard
_______________________________________________
mtt-devel mailing list
mtt-devel@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/mtt-devel
