I get the same error, I'm test checking out zenoss, added a network, discovered 
some devices, reclassified 5 of them has windows server, the first one I did 
worked fine, the next 4 all failed with the same wmi error has above.

I did some testing running wmic and found that for the 4 hosts that failed, 
wmic produced the following error.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
INTERNAL ERROR: Signal 11 in pid 30937 (4.0.0tp4-SVN-build-UNKNOWN)
Please read the file BUGS.txt in the distribution
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
PANIC: internal error
BACKTRACE: 25 stack frames:
 #0 ./wmic(call_backtrace+0x26) [0x835e3d6]
 #1 ./wmic(smb_panic+0x164) [0x835e5dc]
 #2 ./wmic [0x835e734]
 #3 [0xffffe420]
 #4 ./wmic [0x82dee44]
 #5 ./wmic [0x830e15c]
 #6 ./wmic [0x830e25f]
 #7 ./wmic(event_loop_once+0xf) [0x830dacb]
 #8 ./wmic(composite_wait+0x47) [0x830d5ff]
 #9 ./wmic(dcerpc_pipe_connect_b_recv+0x21) [0x81eacc5]
 #10 ./wmic(dcerpc_pipe_connect_b+0x3e) [0x81ead5a]
 #11 ./wmic(dcom_get_pipe+0x2ba) [0x80a2256]
 #12 ./wmic(dcom_get_pipe_recv+0x2a) [0x80a2712]
 #13 ./wmic(dcom_proxy_async_call_recv_pipe_send_rpc+0x43) [0x80a28fb]
 #14 ./wmic [0x830d692]
 #15 ./wmic [0x830dfd0]
 #16 ./wmic [0x830e271]
 #17 ./wmic(event_loop_once+0xf) [0x830dacb]
 #18 ./wmic(composite_wait+0x47) [0x830d5ff]
 #19 ./wmic(IWbemLevel1Login_NTLMLogin_recv+0x25) [0x809f705]
 #20 ./wmic(IWbemLevel1Login_NTLMLogin+0x47) [0x809f7a3]
 #21 ./wmic(WBEM_ConnectServer+0x1d1) [0x8092f59]
 #22 ./wmic(main+0x100) [0x809291c]
 #23 /lib/libc.so.6(__libc_start_main+0xdc) [0xb7e6787c]
 #24 ./wmic(dlopen+0x31) [0x8091c09]
Aborted

when using the FQDN, when I used just the host name it worked fine. in zenoss I 
renamed the devices to just their hostname and the wmi started working. what's 
strange is that the first device I added works fine with both hostname and FQDN.




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

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

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



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

Reply via email to