|
|
| Subject: | struggling with WinRM collector |
| Author: | [Not Specified] |
| Posted: | 2015-10-09 17:39 |
I have dug through the forum and found several other threads that seemed the same but didn't solve my problem.
Zenoss Community v5.06 on a Red Hat 7.2 server trying to collect data from Windows 2012R2 domain. krb5-workstation is installed...
# rpm -q krb5-workstation
krb5-workstation-1.12.2-15.el7_1.x86_64
WinRM works. I can get an administrative power shell on Windows server and access other servers using winrs commands.
As Zenoss user within the docker container, I can get a kerberos ticket no problem.
]$ klist
Ticket cache: FILE:/tmp/krb5cc_1337
Default principal: zenoss@STT-XXXXX.LOCAL
Valid starting Expires Service principal
10/09/15 18:47:28 10/10/15 04:47:28 krbtgt/STT-XXXXX.LOCAL@STT-XXXXX.LOCAL
renew until 10/10/15 18:47:22
From the Zenoss server, as the zenoss user, I can telnet to any of the Windows boxes on port 5985 so I know there are no firewall issues.
I have configured the 'configuration properties' using the same zWinRMUser, zWinRMPassword as the ticket, configured the zWinKDC appropriately and configured zWinRMServer to various domain controllers but the collectors always fail.
2015-10-09 22:34:55,738 WARNING zen.PythonClient: Error in zenoss.winrm.CPUs: attempted Windows connection to non-Windows device
2015-10-09 22:34:55,738 WARNING zen.PythonClient: Error in zenoss.winrm.FileSystems: attempted Windows connection to non-Windows device
2015-10-09 22:34:55,738 WARNING zen.PythonClient: Error in zenoss.winrm.IIS: attempted Windows connection to non-Windows device
2015-10-09 22:34:55,738 WARNING zen.PythonClient: Error in zenoss.winrm.Interfaces: attempted Windows connection to non-Windows device
2015-10-09 22:34:55,738 WARNING zen.PythonClient: Error in zenoss.winrm.OperatingSystem: attempted Windows connection to non-Windows device
2015-10-09 22:34:55,739 WARNING zen.PythonClient: Error in zenoss.winrm.Processes: attempted Windows connection to non-Windows device
2015-10-09 22:34:55,739 WARNING zen.PythonClient: Error in zenoss.winrm.Routes: attempted Windows connection to non-Windows device
2015-10-09 22:34:55,739 WARNING zen.PythonClient: Error in zenoss.winrm.Services: attempted Windows connection to non-Windows device
2015-10-09 22:34:55,739 INFO zen.PythonClient: Python client finished collection for XXX.XXX.XXX.XXX
I have gone over and over the documentation to no avail.
what magic potion am I missing
| Subject: | still struggling |
| Author: | [Not Specified] |
| Posted: | 2015-10-13 11:45 |
I have completely gone through this linked PDF
https://support.zenoss.com/hc/en-us/articles/202432249-How-To-Monitor-Wi...
and still the same errors.
Anyone
| Subject: | Try to setup correct local |
| Author: | Jan Garaj |
| Posted: | 2015-10-13 12:43 |
Try to setup correct local zproperty zWinRMServer for your monitored device.
Devops Monitoring Expert advice:
Dockerize/automate/monitor all the things.
DevOps stack:
Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform /
Elasticsearch
| Subject: | assuming zProperty you are referring to is actually... |
| Author: | [Not Specified] |
| Posted: | 2015-10-13 13:17 |
assuming zProperty you are referring to is actually zWinRMServerName - I have tried that at various times. I set it now to one of the domain controllers (the same domain controller I am configuring individually for testing) but it doesn't change the error messages (still "attempted Windows connection to non-Windows device" for any of the winrm services).
Wish I knew how to get more verbose logging going so I had a chance to figure out where it is going wrong. My local Windows 'expert' also gave up.
| Subject: | zWinRMServerName |
| Author: | [Not Specified] |
| Posted: | 2015-10-13 14:10 |
Yes, it's a monitored device. The DC is a monitored device and it works (WinRM) but not via Zenoss. I shouldn't have to configure it according to the documentation but regardless of what server I set it to, the outcome doesn't change. I thought I mentioned that in the first post of this forum thread.
example of winrm working (from AD3) powershell...
PS C:\Users\zenoss> winrs -r:ad1 dir c:\
Volume in drive C has no label.
Volume Serial Number is 5E24-CF2B
Directory of c:\
10/08/2015 10:36 PM
| < |
Previous how to re-install zenoss 5.x ? |
Next Zenoss5 MIBS |
> |