TECHZEN Zenoss User Community ARCHIVE  

Unable to pull any metrics at all

Subject: Unable to pull any metrics at all
Author: Jason Olson
Posted: 2018-08-13 12:33

I decided to give Zenoss another try with a fresh install of Core 6.2.0. Brand new system, fresh install of RHEL 7.4, clean install of Control Center, clean deployment of Zenoss 6.2.0. Added three servers to this new deployment. Worked for about 15 minutes, then all I get in the logs are:

ERROR zen.PythonClient: Error on <server name>: 'NoneType' object has no attribute '__getitem__'

Doesn't matter if it's event logs, performance metrics, whatever it might be. Tore down Zenoss, deleted the instance. Deployed fresh again. No change.....works once then I get the above message in the event console. Can't find anything relevant in Kibana, although I admit I haven't looked through all 31 logs. Has anyone seen anything like this before? 


------------------------------
Jason Olson
------------------------------


Subject: RE: Unable to pull any metrics at all
Author: Jared Maurina
Posted: 2018-08-13 14:25

We had a fresh install of Control Center and also Zenoss Core. We are unable to view an metrics on any devices. We followed every support forum we could and had no luck. Still not working.

------------------------------
Jared
------------------------------


Subject: RE: Unable to pull any metrics at all
Author: Jason Olson
Posted: 2018-11-02 10:18

@Jared So we solved our metrics gathering problem here; we had created a GPO to enable WinRM monitoring on Windows servers that had gone corrupt and while WinRM was enabled, the service was blocking all requests from any remote system. We deleted and recreated the GPO, ensured that the network that Zenoss was on *and * the subnet local to the servers was defined in the GPO, and now we're able to pull metrics from the affected servers.

Might be worth checking your systems for a similar situation with a dodgy WinRM config. TXWINRM's util.py is where the exception was thrown and while it's able to handle many error conditions, WinRM being enabled but rejecting a connection from Zenoss due to network restrictions isn't one of them, hence the generic and oh-so-unhelpful error message.​

------------------------------
Jason Olson
------------------------------


< Previous
heartbeat failure
  Next
not able to add devices using zendisc command
>