I believe I might have an answer.

I remember seeing something in the ticket system for a bug regarding support 
for devices that have strange characters in names. 

That error looks like the bug in question. I'm not a Zenoss dev though so I 
could be wrong.

You could try removing any extended ascii/unicode characters from the device 
wherever they might be. Also it looks like the error comes from the 
InterfaceMap collector plugin so for a temporary fix you could try removing the 
collector from that device.

You might want to check the releasenotes for the new Sprint release and see if 
they fixed that bug. Of course its not production ready from what I've heard 
but you could always find the ticketnumber from the notes and lookup that 
ticket and manually apply the fix from the diff.

Thats the best I can do for ya at the moment. Good luck

Cheers,
Zach Davis




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

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

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



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

Reply via email to