I have an older revision of Zenoss loaded right now, and I got a tag mismatch 
error (invalid XML). This is obviously not a good sign. Here is my interactive 
session:

Code:

>>> from xmlrpclib import ServerProxy 
>>> s = ServerProxy('http://admin:[EMAIL 
>>> PROTECTED]:8080/zport/dmd/DeviceLoader') 
>>> dev = {'deviceName':"127.0.0.1",'devicePath':"/Server/Linux", 
>>> 'discoverProto': 'none'} 
>>> s.loadDevice(dev) 
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File 
"/Library/Frameworks/Python.framework/Versions/2.4//lib/python2.4/xmlrpclib.py",
 line 1096, in __call__
    return self.__send(self.__name, args)
  File 
"/Library/Frameworks/Python.framework/Versions/2.4//lib/python2.4/xmlrpclib.py",
 line 1383, in __request
    verbose=self.__verbose
  File 
"/Library/Frameworks/Python.framework/Versions/2.4//lib/python2.4/xmlrpclib.py",
 line 1147, in request
    return self._parse_response(h.getfile(), sock)
  File 
"/Library/Frameworks/Python.framework/Versions/2.4//lib/python2.4/xmlrpclib.py",
 line 1281, in _parse_response
    p.feed(response)
  File 
"/Library/Frameworks/Python.framework/Versions/2.4//lib/python2.4/xmlrpclib.py",
 line 527, in feed
    self._parser.Parse(data, 0)
xml.parsers.expat.ExpatError: mismatched tag: line 22, column 10




After running the python debugger, I see that when accessing the DeviceLoader 
via XML-RPC, the response is not structured XML, but rather an HTML page. This 
is not right. It should be like ZenEventManager, which does actually return a 
valid XML response.

I'll upgrade my Zenoss instance and then give it another shot to see if I can 
duplicate the errors you guys are getting.

------------------------
 Duncan McGreggor




-------------------- m2f --------------------

Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=4503#4503

-------------------- m2f --------------------



_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to