|
|
| Subject: | WinRM Failed collection Cannot determine realm from numeric host address |
| Author: | [Not Specified] |
| Posted: | 2016-01-05 14:53 |
So everything was working just fine, but randomly, Zenoss 5 fails WinRM collection with the error above.
When logged into the Zenoss host, I can do an nslooukp 10.85.129.30 and it resolves fine.
[root@ghq-1dmonap02 zenpacks]# nslookup 10.85.129.30
Server: 10.85.128.13
Address: 10.85.128.13#53
30.129.85.10.in-addr.arpa name = gshqspsql01.globalspec.net.
I then go into the Zenoss docker container and issue an nslookup and get (172.17.42.1 is my host):
[root@ebd24717ba86 /]# nslookup 10.85.129.30
Server: 172.17.42.1
Address: 172.17.42.1#53
** server can't find 30.129.85.10.in-addr.arpa.: NXDOMAIN
Why is Zenoss unable to resolve the hostname when the docker host can just fine
| Subject: | this is likely a DNS |
| Author: | Andrew Kirch |
| Posted: | 2016-01-19 12:23 |
this is likely a DNS misconfiguration in docker. You may need to add nameservers to docker.
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 ZenPack needed for Nettwork Device Interface Monitoring |
Next vSphere SDK for Perl Install Zenoss Core 5 |
> |