sconos
2012-11-28 14:35:44 UTC
sconos [http://community.zenoss.org/people/sconos] created the discussion
"zendevicedump errors"
To view the discussion, visit: http://community.zenoss.org/message/70199#70199
--------------------------------------------------------------
Running Zenoss 3.2.1 - trying to get a devicedump to import to 4.2.0SP1
[***@zenoss2 zenoss]$ ./bin/zendevicedump --outfile=/opt/zenoss/backups/mydevicelist.xml
Traceback (most recent call last):
 File "/opt/zenoss/Products/ZenRelations/ExportDevices.py", line 229, in <module>
   ex.export()
 File "/opt/zenoss/Products/ZenRelations/ExportDevices.py", line 215, in export
   doc = parseString(buffer.getvalue())
 File "/opt/zenoss/lib/python/_xmlplus/dom/minidom.py", line 1925, in parseString
   return expatbuilder.parseString(string)
 File "/opt/zenoss/lib/python/_xmlplus/dom/expatbuilder.py", line 942, in parseString
   return builder.parseString(string)
 File "/opt/zenoss/lib/python/_xmlplus/dom/expatbuilder.py", line 223, in parseString
   parser.Parse(string, True)
xml.parsers.expat.ExpatError: not well-formed (invalid token): line 930314, column 7
[***@zenoss2 zenoss]$
It creates the outfile .. but its 0 bytes ... so I'm assuming the traceback is from a python script failure before anything gets to the write function stage.
Just looked at /opt/zenoss/Products/ZenRelations/ExportDevices.py", line 229 ... its the end of this particular python script
ex.export()
line 215 is
| Â | # Create an XML document tree that we clean up and then export |
| Â Â Â | doc = parseString(buffer.getvalue()) |
Does anyone have any ideas on how to troubleshoot this issue?
TIA
Mike
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70199#70199]
Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
"zendevicedump errors"
To view the discussion, visit: http://community.zenoss.org/message/70199#70199
--------------------------------------------------------------
Running Zenoss 3.2.1 - trying to get a devicedump to import to 4.2.0SP1
[***@zenoss2 zenoss]$ ./bin/zendevicedump --outfile=/opt/zenoss/backups/mydevicelist.xml
Traceback (most recent call last):
 File "/opt/zenoss/Products/ZenRelations/ExportDevices.py", line 229, in <module>
   ex.export()
 File "/opt/zenoss/Products/ZenRelations/ExportDevices.py", line 215, in export
   doc = parseString(buffer.getvalue())
 File "/opt/zenoss/lib/python/_xmlplus/dom/minidom.py", line 1925, in parseString
   return expatbuilder.parseString(string)
 File "/opt/zenoss/lib/python/_xmlplus/dom/expatbuilder.py", line 942, in parseString
   return builder.parseString(string)
 File "/opt/zenoss/lib/python/_xmlplus/dom/expatbuilder.py", line 223, in parseString
   parser.Parse(string, True)
xml.parsers.expat.ExpatError: not well-formed (invalid token): line 930314, column 7
[***@zenoss2 zenoss]$
It creates the outfile .. but its 0 bytes ... so I'm assuming the traceback is from a python script failure before anything gets to the write function stage.
Just looked at /opt/zenoss/Products/ZenRelations/ExportDevices.py", line 229 ... its the end of this particular python script
ex.export()
line 215 is
| Â | # Create an XML document tree that we clean up and then export |
| Â Â Â | doc = parseString(buffer.getvalue()) |
Does anyone have any ideas on how to troubleshoot this issue?
TIA
Mike
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70199#70199]
Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]