Zenoss ZenTech Community

HI Guys, Setting up Zenoss , when using snmp it works fine but trying to use Windows zenpack i get errors when trying to model device.

2014-04-28 10:58:35,545 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
2014-04-28 10:58:35,742 ERROR zen.PythonClient: Error on 172.17.2.114: (('Unspecified GSS failure. Minor code may provide more information', 851968), ('Cannot determine realm for numeric host address', -1765328141))
2014-04-28 10:58:35,768 ERROR zen.PythonClient: Error on 172.17.2.114: (('Unspecified GSS failure. Minor code may provide more information', 851968), ('Cannot determine realm for numeric host address', -1765328141))
2014-04-28 10:58:35,792 ERROR zen.PythonClient: Error on 172.17.2.114: (('Unspecified GSS failure. Minor code may provide more information', 851968), ('Cannot determine realm for numeric host address', -1765328141))
2014-04-28 10:58:35,817 ERROR zen.PythonClient: Error on 172.17.2.114: (('Unspecified GSS failure. Minor code may provide more information', 851968), ('Cannot determine realm for numeric host address', -1765328141))
2014-04-28 10:58:35,843 ERROR zen.PythonClient: Error on 172.17.2.114: (('Unspecified GSS failure. Minor code may provide more information', 851968), ('Cannot determine realm for numeric host address', -1765328141))
2014-04-28 10:58:35,869 ERROR zen.PythonClient: Error on 172.17.2.114: (('Unspecified GSS failure. Minor code may provide more information', 851968), ('Cannot determine realm for numeric host address', -1765328141))
2014-04-28 10:58:35,895 ERROR zen.PythonClient: Error on 172.17.2.114: (('Unspecified GSS failure. Minor code may provide more information', 851968), ('Cannot determine realm for numeric host address', -1765328141))
2014-04-28 10:58:35,920 ERROR zen.PythonClient: Error on 172.17.2.114: (('Unspecified GSS failure. Minor code may provide more information', 851968), ('Cannot determine realm for numeric host address', -1765328141))
2014-04-28 10:58:35,945 ERROR zen.PythonClient: Error on 172.17.2.114: (('Unspecified GSS failure. Minor code may provide more information', 851968), ('Cannot determine realm for numeric host address', -1765328141))
2014-04-28 10:58:35,970 ERROR zen.PythonClient: Error on 172.17.2.114: (('Unspecified GSS failure. Minor code may provide more information', 851968), ('Cannot determine realm for numeric host address', -1765328141))

Can anyone pint me in the right direction.
All i want is CPU and HDD to be monitored correctly and graphed.

Subject:	DNS Issue
Author:	[Not Specified]
Posted:	2014-04-28 08:43

Looks like a DNS issue, where zenoss can't resolve the hostname to an IP. Try changing the device to be monitored by IP to see what happens!

Hydruid

Subject:	Thanks Mate that was indeed
Author:	[Not Specified]
Posted:	2014-04-29 19:35

Thanks Mate that was indeed the issue

Subject:	Same issue - Cannot Get Windows Zenpack to work correctly
Author:	[Not Specified]
Posted:	2014-05-06 17:03

I'm facing the exact same issue as Smakked. When modeling the device, I see several entries like this one:

Error on 10.0.0.90: (('Unspecified GSS failure. Minor code may provide more information', 851968), ('Cannot determine realm for numeric host address', -1765328141)).

Where exactly can I change the device to be monitored by IP When I added de device, it was added by IP, not by name, so I would assume that it is being monitored by IP.

The log posted by Smakked confuses me a bit, since it says "Error on 172.17.2.114", which makes me think that the device was also added by IP, but later he said that changing the device to be monitored by IP solved the problem.

Can you guys shed some light on this

Thank you.

Subject:	Additional detail
Author:	[Not Specified]
Posted:	2014-05-06 17:39

@Hydruid: I found your blog post (http://hydruid-blog.com/p=916) a few moments ago, but everything was already set up like you suggested (I'm assuming it's the same Hydruid :) ). I can successfully model the device using the last suggestion (using only the user name), but I believe that is making zenoss authenticate using a local user, and I want to do it using a domain account.

Any additional suggestions are very welcome.

Thanks!

Subject:	More info
Author:	[Not Specified]
Posted:	2014-05-06 18:55

The error is in fact DNS-related. The correct nameserver was not configured at the OS level. Once that was taken care of, I was able to model the device using a domain account, but I'm still not clear why name resolution is necessary if the device is being monitored by IP address (which I think is the case here), but that bring us back to my first doubt in this question: how do I tell Zenoss to monitor a device by IP address

Subject:	One thing i forgot to mention
Author:	[Not Specified]
Posted:	2014-05-07 06:39

One thing i forgot to mention to get mine to work is to list one of my PDC's in the field "zWinKDC". After i did this all has worked well since.

Subject:	I think you misunderstood
Author:	[Not Specified]
Posted:	2014-05-07 08:38

I think you misunderstood Carlosdlg, sorry about that. I suggested that he change all the Configuration Properties to an IP address instead of a hostname (e.g. zWinKDC, zWin*). That helps to eliminate or bypass any DNS issues.

By default Zenoss monitors all devices by IP unless you specifically configure it to use the hostname.

Glad you found my post and I hope it helped! Obviously we're both the same hydruid :)

Hydruid

Subject:	Thanks
Author:	[Not Specified]
Posted:	2014-05-07 10:49

Thank you both, guys.

Everything was set up using IP addresses, and the zWinKDC property was correctly set to the domain controller IP address, but for some reason it fails if the device's IP address is not resolvable through DNS (which doesn't make much sense to me).

Subject:	Cannot Get Windows Zenpack to work correctly
Author:	[Not Specified]
Posted:	2014-04-27 20:01

Cannot Get Windows Zenpack to work correctly