jmp242 wrote:
> Generally, BAD WMI STATE will clear up by itself after several hours. In 
> 2.2 alphas, they are testing more WMI fixes, so you might be affected by 
> that interaction bug, in which case you could try a testing build if you 
> feel adventurous, or wait for 2.2 which should include these fixes.
> --
> James Pulver
> Information Technology Area Supervisor
> LEPP Computer Group
> Cornell University
> 
> 
> 
> rlund wrote:
> 
> > when I do zenwinmodeler run -d devicename
> > 
> > I get
> > 
> > 
> > INFO:zen.zenwinmodeler:Starting zenwinmodeler
> > WARNING:zen.zenwinmodeler:Reconnected to ZenHub
> > INFO:zen.zenwinmodeler:Setting configCycleInterval to 360
> > INFO:zen.zenwinmodeler:Setting winmodelerCycleInterval to 60
> > INFO:zen.zenwinmodeler:No WMI plugins found for 10.220.0.1
> > WARNING:zen.zenwinmodeler:skipping pc1 has bad wmi state
> > WARNING:zen.zenwinmodeler:skipping pc2 has bad wmi state
> > WARNING:zen.zenwinmodeler:skipping pc3 has bad wmi state
> > WARNING:zen.zenwinmodeler:skipping pc4 has bad wmi state
> > WARNING:zen.zenwinmodeler:skipping pc5 has bad wmi state
> > WARNING:zen.zenwinmodeler:skipping pc6 has bad wmi state
> > WARNING:zen.zenwinmodeler:skipping pc7 has bad wmi state
> > WARNING:zen.zenwinmodeler:skipping pc8 has bad wmi state
> > WARNING:zen.zenwinmodeler:skipping pc9 has bad wmi state
> > INFO:zen.zenwinmodeler:No WMI plugins found for router1
> > INFO:zen.zenwinmodeler:No WMI plugins found for router2
> > INFO:zen.zenwinmodeler:No WMI plugins found for switch1
> > INFO:zen.zenwinmodeler:No WMI plugins found for switch2
> > INFO:zen.zenwinmodeler:No WMI plugins found for switch3
> > INFO:zen.zenwinmodeler:No WMI plugins found for switch4
> > INFO:zen.zenwinmodeler:No WMI plugins found for switch5
> > INFO:zen.zenwinmodeler:No WMI plugins found for switch6
> > INFO:zen.zenwinmodeler:No WMI plugins found for switch7
> > WARNING:zen.zenwinmodeler:skipping pc10 has bad wmi state
> > WARNING:zen.zenwinmodeler:skipping pc11 has bad wmi state
> > WARNING:zen.zenwinmodeler:skipping pc12 has bad wmi state
> > WARNING:zen.zenwinmodeler:skipping pc13 has bad wmi state
> > INFO:zen.zenwinmodeler:No WMI plugins found for ups1
> > INFO:zen.zenwinmodeler:No WMI plugins found for ups2
> > INFO:zen.zenwinmodeler:No WMI plugins found for workstation1
> > INFO:zen.zenwinmodeler:No WMI plugins found for workstation2
> > INFO:zen.zenwinmodeler:No WMI plugins found for workstation2
> > INFO:zen.zenwinmodeler:No WMI plugins found for swtich8
> > INFO:zen.zenwinmodeler:Daemon zenwinmodeler shutting down
> > INFO:zen.zenwinmodeler:zenwinmodeler shutting down
> > 
> > 
> > I change the host names to protect my self. but what problem am i running 
> > in to?
> > 
> > I get nothing for winbservices under any servers under 
> > /device/server/windows
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > zenoss-users mailing list
> > [email protected]
> > http://lists.zenoss.org/mailman/listinfo/zenoss-users
> > 
> _______________________________________________
> zenoss-users mailing list
> [email protected]
> http://lists.zenoss.org/mailman/listinfo/zenoss-users


I upgrade this to the latest sprint build, but the server has been running with 
the devices added since the sprint was released.




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

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

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



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

Reply via email to