![]() |
![]() |
Subject: | DNS Lookup failing for MicrosoftWindows ZenPack. Was previously working |
Author: | Larry |
Posted: | 2015-02-02 15:14 |
We have a new install of Zenoss 4.2.4 (unpatched) running on Centos 6.4. We configured several devices with the MicrosoftWindows ZenPack using WinRM to collect data. We are not using SNMP. Our graphs initially had gaps in data (10-100+ minutes). I checked the forums and found that it might be a resource issue. I increased memory & CPU, and then we completely stopped getting data. I found that /etc/resolv.conf was reset from the reboot, so I changed it to point to our DCs/DNS. We're still not getting any graph data though. The "model device" command nslookup both look good. Log and other information is below. Any ideas
Thanks,
Larry
[zenoss@ip-10-0-2-218 tmp]$ nslookup win2008test.ipc.local
Server: 10.0.1.31
Address: 10.0.1.31#53
Name: win2008test.ipc.local
Address: 10.0.3.24
Model Device:
-----------------
2015-02-02 20:44:35,354 INFO zen.ZenModeler: Connecting to localhost:8789
2015-02-02 20:44:35,360 INFO zen.ZenModeler: Connected to ZenHub
2015-02-02 20:44:35,490 INFO zen.ZenModeler: Collecting for device 10.0.3.24
2015-02-02 20:44:35,633 INFO zen.ZenModeler: skipping WMI-based collection, PySamba zenpack not installed
2015-02-02 20:44:35,642 INFO zen.ZenModeler: Python collection device 10.0.3.24
2015-02-02 20:44:35,643 INFO zen.ZenModeler: plugins: zenoss.winrm.OperatingSystem, zenoss.winrm.CPUs, zenoss.winrm.FileSystems, zenoss.winrm.Interfaces,zenoss.winrm.Services, zenoss.winrm.Processes, zenoss.winrm.Software, zenoss.winrm.IIS, zenoss.winrm.Routes
2015-02-02 20:44:35,700 INFO zen.ZenModeler: No command plugins found for 10.0.3.24
2015-02-02 20:44:35,700 INFO zen.ZenModeler: SNMP monitoring off for 10.0.3.24
2015-02-02 20:44:35,701 INFO zen.ZenModeler: No portscan plugins found for 10.0.3.24
2015-02-02 20:44:47,652 INFO zen.PythonClient: Python client finished collection for 10.0.3.24
2015-02-02 20:44:47,653 WARNING zen.ZenModeler: The plugin zenoss.winrm.IIS returned no results.
2015-02-02 20:44:47,653 INFO zen.ZenModeler: Modeler zenoss.winrm.Routes processing data for device 10.0.3.24
2015-02-02 20:44:47,655 INFO zen.ZenModeler: Modeler zenoss.winrm.FileSystems processing data for device 10.0.3.24
2015-02-02 20:44:47,656 INFO zen.ZenModeler: Modeler zenoss.winrm.CPUs processing data for device 10.0.3.24
2015-02-02 20:44:47,657 INFO zen.ZenModeler: Modeler zenoss.winrm.Services processing data for device 10.0.3.24
2015-02-02 20:44:47,661 INFO zen.ZenModeler: Modeler zenoss.winrm.Processes processing data for device 10.0.3.24
2015-02-02 20:44:47,690 INFO zen.ZenModeler: Modeler zenoss.winrm.OperatingSystem processing data for device 10.0.3.24
2015-02-02 20:44:47,691 INFO zen.ZenModeler: Modeler zenoss.winrm.Software processing data for device 10.0.3.24
2015-02-02 20:44:47,692 INFO zen.ZenModeler: Modeler zenoss.winrm.Interfaces processing data for device 10.0.3.24
2015-02-02 20:44:48,050 INFO zen.ZenModeler: No change in configuration detected
2015-02-02 20:44:48,051 INFO zen.ZenModeler: Scan time: 12.56 seconds
2015-02-02 20:44:48,053 INFO zen.ZenModeler: Daemon ZenModeler shutting down
zenmodeler.log:
---------------
2015-02-02 19:57:37,371 ERROR zen.PythonClient: Error on 10.0.3.24: DNS lookup failed: win2008test.ipc.local.
2015-02-02 19:57:37,377 ERROR zen.PythonClient: Error on 10.0.3.24: DNS lookup failed: win2008test.ipc.local.
2015-02-02 19:57:37,383 ERROR zen.PythonClient: Error on 10.0.3.24: DNS lookup failed: win2008test.ipc.local.
zenpython.log
-------------
2015-02-02 20:41:02,637 ERROR winrm: win2008test.ipc.local DNS lookup failed: win2008test.ipc.local.
2015-02-02 20:41:02,637 ERROR zen.MicrosoftWindows: WindowsServiceLog: failed collection - DNS lookup failed: win2008test.ipc.local. 10.0.3.24
2015-02-02 20:42:04,825 ERROR winrm: win2008test.ipc.local DNS lookup failed: win2008test.ipc.local.
2015-02-02 20:42:04,825 ERROR zen.MicrosoftWindows: WindowsServiceLog: failed collection - DNS lookup failed: win2008test.ipc.local. 10.0.3.24
2015-02-02 20:42:33,988 ERROR winrm: win2008test.ipc.local DNS lookup failed: win2008test.ipc.local.
2015-02-02 20:42:33,989 ERROR zen.MicrosoftWindows: WindowsServiceLog: failed collection - DNS lookup failed: win2008test.ipc.local. 10.0.3.24
2015-02-02 20:44:03,461 ERROR winrm: win2008test.ipc.local DNS lookup failed: win2008test.ipc.local.
2015-02-02 20:44:03,461 ERROR zen.MicrosoftWindows: WindowsServiceLog: failed collection - DNS lookup failed: win2008test.ipc.local. 10.0.3.24
2015-02-02 20:45:18,955 ERROR winrm: win2008test.ipc.local DNS lookup failed: win2008test.ipc.local.
2015-02-02 20:45:18,955 ERROR zen.MicrosoftWindows: WindowsServiceLog: failed collection - DNS lookup failed: win2008test.ipc.local. 10.0.3.24
2015-02-02 20:46:25,476 ERROR winrm: win2008test.ipc.local DNS lookup failed: win2008test.ipc.local.
2015-02-02 20:46:25,477 ERROR zen.MicrosoftWindows: WindowsServiceLog: failed collection - DNS lookup failed: win2008test.ipc.local. 10.0.3.24
2015-02-02 20:46:26,964 WARNING zen.windows: Error on 10.0.3.24: win2008test.ipc.local
Subject: | Problem solved |
Author: | Larry |
Posted: | 2015-02-04 08:36 |
We were able to "freeze" the /etc/resolv.conf file yesterday to keep it from being changed by DCHP. We're getting data for the graphs now. Still seeing gaps though.
Subject: | Are you seeing gaps or no |
Author: | Andrew Kirch |
Posted: | 2015-02-04 11:07 |
Are you seeing gaps or no data at all You may need to delete/recreate the device.
Andrew Kirch
akirch@gvit.com
Need Zenoss support, consulting or custom development Look no further. Email or PM me!
Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard
< |
Previous Still Struggling with WinRM incomplete information |
Next Problem Layer2 |
> |