Zenoss ZenTech Community

New Zenoss Deployment - Modeling fails for Windows devices

Subject:	New Zenoss Deployment - Modeling fails for Windows devices
Author:	anthony rabbito
Posted:	2017-07-14 13:35

I have just setup the new Zenoss server to test with and i can't get a single Windows device to be polled properly. I've set all of the global variables for the domain/user/password/etc. below is a modeler output from a test device. any assistance would be greatly appreciated.

2017-07-14 21:21:49,484 INFO zen.ZenModeler: Connecting to localhost:8789
2017-07-14 21:21:49,513 INFO zen.ZenModeler: Connected to the zenhub/0 instance
2017-07-14 21:21:49,618 INFO zen.ZenModeler: Starting collector loop #001...
2017-07-14 21:21:49,619 INFO zen.ZenModeler: Collecting for device DC01.XXX.XXX
2017-07-14 21:21:49,619 INFO zen.ZenModeler: Got 1 devices to be scanned during collector loop #001
2017-07-14 21:21:49,872 INFO zen.ZenModeler: Filled collection slots for 1 of 1 devices during collector loop #001
2017-07-14 21:21:49,872 INFO zen.ZenModeler: skipping WMI-based collection, PySamba zenpack not installed
2017-07-14 21:21:49,872 INFO zen.ZenModeler: Collect on device DC01.XXX.XXX for collector loop #001
2017-07-14 21:21:49,882 INFO zen.ZenModeler: Python collection device DC01.XXX.XXX
2017-07-14 21:21:49,883 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.HardDisks
2017-07-14 21:21:49,891 INFO zen.ZenModeler: No command plugins found for DC01.XXX.XXX
2017-07-14 21:21:49,891 INFO zen.ZenModeler: SNMP monitoring off for DC01.XXX.XXX
2017-07-14 21:21:49,892 INFO zen.ZenModeler: No portscan plugins found for DC01.XXX.XXX
2017-07-14 21:21:49,903 ERROR zen.PythonClient: Error on DC01.XXX.XXX: Server not found in Kerberos database: HTTP@192.168.XXX.XXX
2017-07-14 21:21:49,905 ERROR zen.PythonClient: Error on DC01.XXX.XXX: Server not found in Kerberos database: HTTP@192.168.XXX.XXX
2017-07-14 21:21:49,907 ERROR zen.PythonClient: Error on DC01.XXX.XXX: Server not found in Kerberos database: HTTP@192.168.XXX.XXX
2017-07-14 21:21:49,908 ERROR zen.PythonClient: Error on DC01.XXX.XXX: Server not found in Kerberos database: HTTP@192.168.XXX.XXX
2017-07-14 21:21:49,909 ERROR zen.PythonClient: Error on DC01.XXX.XXX: Server not found in Kerberos database: HTTP@192.168.XXX.XXX
2017-07-14 21:21:49,910 ERROR zen.PythonClient: Error on DC01.XXX.XXX: Server not found in Kerberos database: HTTP@192.168.XXX.XXX
2017-07-14 21:21:49,911 ERROR zen.PythonClient: Error on DC01.XXX.XXX: Server not found in Kerberos database: HTTP@192.168.XXX.XXX
2017-07-14 21:21:49,912 ERROR zen.PythonClient: Error on DC01.XXX.XXX: Server not found in Kerberos database: HTTP@192.168.XXX.XXX
2017-07-14 21:21:49,917 ERROR zen.PythonClient: Error on DC01.XXX.XXX: Server not found in Kerberos database: HTTP@192.168.XXX.XXX
2017-07-14 21:21:49,918 ERROR zen.PythonClient: Error on DC01.XXX.XXX: Server not found in Kerberos database: HTTP@192.168.XXX.XXX
2017-07-14 21:21:49,931 ERROR zen.PythonClient: Error on DC01.XXX.XXX: Server not found in Kerberos database: HTTP@192.168.XXX.XXX
2017-07-14 21:21:49,944 ERROR zen.PythonClient: Error on DC01.XXX.XXX: Server not found in Kerberos database: HTTP@192.168.XXX.XXX
2017-07-14 21:21:49,956 ERROR zen.PythonClient: Error on DC01.XXX.XXX: Server not found in Kerberos database: HTTP@192.168.XXX.XXX
2017-07-14 21:21:49,957 INFO zen.PythonClient: Python client finished collection for DC01.XXX.XXX
2017-07-14 21:21:49,958 WARNING zen.ZenModeler: The plugin zenoss.winrm.CPUs returned no results.
2017-07-14 21:21:49,958 WARNING zen.ZenModeler: The plugin zenoss.winrm.FileSystems returned no results.
2017-07-14 21:21:49,958 WARNING zen.ZenModeler: The plugin zenoss.winrm.Services returned no results.
2017-07-14 21:21:49,959 WARNING zen.ZenModeler: The plugin zenoss.winrm.Processes returned no results.
2017-07-14 21:21:49,959 WARNING zen.ZenModeler: The plugin zenoss.winrm.Software returned no results.
2017-07-14 21:21:49,959 WARNING zen.ZenModeler: The plugin zenoss.winrm.HardDisks returned no results.
2017-07-14 21:21:49,959 WARNING zen.ZenModeler: The plugin zenoss.winrm.OperatingSystem returned no results.
2017-07-14 21:21:49,960 WARNING zen.ZenModeler: The plugin zenoss.winrm.Interfaces returned no results.
2017-07-14 21:21:49,960 INFO zen.ZenModeler: No change in configuration detected
2017-07-14 21:21:49,960 INFO zen.ZenModeler: Finished processing client within collector loop #001
2017-07-14 21:21:49,960 INFO zen.ZenModeler: Scan time: 0.34 seconds for collector loop #001
2017-07-14 21:21:49,961 INFO zen.ZenModeler: Scanned 1 of 1 devices during collector loop #001
2017-07-14 21:21:49,963 INFO zen.ZenModeler: Daemon ZenModeler shutting down
2017-07-14 21:21:49,981 INFO zen.publisher: publishing failed: Connection was closed cleanly.

------------------------------
Anthony
------------------------------

Subject:	RE: New Zenoss Deployment - Modeling fails for Windows devices
Author:	Jason Olson
Posted:	2017-07-14 17:22

Try using the IP address of the KDC rather than the host name, and see if that helps. Also, check that there's a PTR record for the system you're trying to monitor, and add it if not.

Subject:	RE: New Zenoss Deployment - Modeling fails for Windows devices
Author:	Jay Stanley
Posted:	2017-07-18 09:07

Yeah, make sure zWinKDC is set and zWinRMServerName.

DNS lookups matter. Like Jason said, make sure there is a record. Issues we ran into before was bad DNS entries. When doing multiple lookups we would notice the reverse lookup would return different domains at times.

------------------------------
jstanley
------------------------------

Previous
Serviced backup Broken due to input/output error

Next
Looking for event transforms on oracle tablespace percent utilization