|
|
| Subject: | Zenoss 5 and WinRM |
| Author: | [Not Specified] |
| Posted: | 2016-03-24 19:36 |
Hello,
We are currently running Zenoss 5.0.7 and currently have 115 windows servers being monitored. 110 of those we are monitoring via WinRM. 5 of them are virtual, Windows 2012 Guest machines on VMWare hosts (not sure of our VMWare version) that are using SNMP.Those 5, if switched to be monitored by WinRM become inaccessible, the CPU usage climbs to 100% and they are unresponsive. Oddly, Zenoss doesn't show them as 'down' because they still respond to ping, but file shares and RDP no longer respond. These are not our only virtual serverswe have, others in a seperate location can be monitored by WinRM without issue, and all of our physical servers can be monitered via WinRM. Has anyone experienced anything similiar, or have some ideas on anything that we can check
Thank,
ThatOneGuy
| Subject: | could you paste zenmodeler |
| Author: | Andrew Kirch |
| Posted: | 2016-03-25 12:44 |
could you paste zenmodeler output for one of those servers
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
| Subject: | Sorry it took so long to get |
| Author: | [Not Specified] |
| Posted: | 2016-04-01 08:36 |
Sorry it took so long to get back, I had to wait for a good time to try. I moved the device to the class that uses WinRM and told it to Model the device. The first time I tried, the server locked up and had to be rebooted. The second time, it was able to model it. Here's the output:
2016-04-01 13:28:41,311 INFO zen.ZenModeler: Connecting to localhost:8789
2016-04-01 13:28:41,316 INFO zen.ZenModeler: Connected to ZenHub
2016-04-01 13:28:41,468 INFO zen.ZenModeler: Collecting for device 172.17.0.35
2016-04-01 13:28:41,572 INFO zen.ZenModeler: skipping WMI-based collection, PySamba zenpack not installed
2016-04-01 13:28:41,583 INFO zen.ZenModeler: Python collection device 172.17.0.35
2016-04-01 13:28:41,583 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
2016-04-01 13:28:41,659 INFO zen.ZenModeler: No command plugins found for 172.17.0.35
2016-04-01 13:28:41,659 INFO zen.ZenModeler: SNMP monitoring off for 172.17.0.35
2016-04-01 13:28:41,660 INFO zen.ZenModeler: No portscan plugins found for 172.17.0.35
2016-04-01 13:29:09,651 INFO zen.PythonClient: Python client finished collection for 172.17.0.35
2016-04-01 13:29:09,651 WARNING zen.ZenModeler: The plugin zenoss.winrm.IIS returned no results.
2016-04-01 13:29:09,652 INFO zen.ZenModeler: Modeler zenoss.winrm.FileSystems processing data for device 172.17.0.35
2016-04-01 13:29:09,652 INFO zen.ZenModeler: Ignoring A: on 172.17.0.35 because it matches zFileSystemMapIgnoreTypes
2016-04-01 13:29:09,652 INFO zen.ZenModeler: Ignoring E: on 172.17.0.35 because it matches zFileSystemMapIgnoreTypes
2016-04-01 13:29:09,652 INFO zen.ZenModeler: Modeler zenoss.winrm.Services processing data for device 172.17.0.35
2016-04-01 13:29:09,657 INFO zen.ZenModeler: Modeler zenoss.winrm.Software processing data for device 172.17.0.35
2016-04-01 13:29:09,659 INFO zen.ZenModeler: Modeler zenoss.winrm.CPUs processing data for device 172.17.0.35
2016-04-01 13:29:09,659 INFO zen.ZenModeler: Modeler zenoss.winrm.OperatingSystem processing data for device 172.17.0.35
2016-04-01 13:29:09,660 INFO zen.ZenModeler: Modeler zenoss.winrm.Interfaces processing data for device 172.17.0.35
2016-04-01 13:29:09,661 INFO zen.ZenModeler: Modeler zenoss.winrm.Processes processing data for device 172.17.0.35
2016-04-01 13:29:16,237 INFO zen.ZenModeler: Changes in configuration applied
2016-04-01 13:29:16,237 INFO zen.ZenModeler: Scan time: 34.77 seconds
2016-04-01 13:29:16,238 INFO zen.ZenModeler: Daemon ZenModeler shutting down
| Subject: | ThatOneGuy, |
| Author: | [Not Specified] |
| Posted: | 2016-04-21 02:40 |
ThatOneGuy,
I've seen some cases where the Zenoss suggested WinRM config acctually opens up serious performance problems.
Consider the 'suggested' configuration:
Most of these are quite excessive. In most cases performance issues with WinRM during modeling and polling can be resovlved by dramatically limiting the number of sessions, processes and reducing the shell timeout.
Give that a try and let me know if you have any success.
Take care!
ZenMaster Shane William Scott (Hackman238)
CTO
GoVanguard Inc.
sscott@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
| Subject: | Thanks, I'll test adjusting |
| Author: | [Not Specified] |
| Posted: | 2016-04-21 11:39 |
Thanks, I'll test adjusting the values, and see how it goes.
| Subject: | ThatOneGuy, |
| Author: | [Not Specified] |
| Posted: | 2016-04-21 11:41 |
ThatOneGuy,
Good luck man. If it doesn't help we can dig deeper into those specific servers.
Take care!
ZenMaster Shane William Scott (Hackman238)
CTO
GoVanguard Inc.
sscott@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 Control center won't start anymore because docker is 100% full |
Next Porblem with Zenoss 5 Transform |
> |