Zenoss and possible problems

Note at the beggining : if a WIN server is not in AD, WinRM will not work!!!
Link towards error numbers which WinRM gives.

1) When host is „Modelled“, and this appears :
2016-12-26 08:19:08,767 ERROR zen.PythonClient: Error on myserver.mydomain: Server not found in Kerberos database: HTTP@
♥It is most probably this :
A service principal name (SPN) is a unique identifier of a service instance. SPNs are used by Kerberos authentication to associate a service instance with a service logon account. This allows a client application to request that the service authenticate an account even if the client does not have the account name.

What can be done :
Button „Start“/Run/gpedit.msc :
Individual Machine configuration:
Open ports 5985 (http)/5986(https) for WinRM
winrm quickconfig
winrm s winrm/config/service @{MaxConcurrentOperationsPerUser=”4294967295″}
winrm s winrm/config/winrs @{MaxShellsPerUser=”2147483647″}
winrm s winrm/config/winrs @{IdleTimeout=”7200000″}
Basic Authentication (Windows default is Kerberos see note below for more information):
winrm s winrm/config/service/auth @{Basic=”true”}
winrm s winrm/config/service @{AllowUnencrypted=”true”}

Entry in /etc/hosts file on Zenoss server :
[root@zenoss etc]# more hosts localhost localhost.localdomain zenoss.mydomain myserver1.mydomain myserver2.mydomain myserver2 myserver3.mydomain myserver3

2) Error during modelling :
2016-12-26 09:06:36,534 ERROR zen.PythonClient: Connection refused on mojserver.mojdomen: Verify WinRM setup
♥Solution :
a) check if the user used for monitoring is in a local administrators group
b) check from a Zenoss server command line :
[root@zenoss etc]# nc -z -w1 5985;echo $?
(“1” means it is OK)

Check the PowerShell version, using command : $PSVersionTable
If there is no output, it means it is a version 1, and we need 2.0 (at least)!
♥Install the necessary PowerShell version!

3) Modelling error : AttributeError: ‘NoneType’ object has no attribute ‘DomainRole’

4) Modelling error : WARNING zen.ZenModeler: The plugin zenoss.winrm.IIS returned no results.
♥This usually menas that the IIS is not active on server. If that is the case, turn off that module (Modeler Plugins).

5) Modelling error : HTTP Unauthorized received on kerberos initialization. Kerberos error code -1765328343
♥Check the AD entry for this server.

6) Modelling error : ERROR zen.PythonClient: Error on mojserver.mojdomen : Cannot determine realm for numeric host address
♥Solution is to set Configuration Properties/ zWinRMServerName as a FQDN of the server!

7) Error : The following exception was thrown when trying to enumerate the collection : Failed to connect to server myserver.mydomain
♥Solution : add a user for the overseeing of MS SQL (with at least public)

8) Modelling error : ERROR zen.PythonClient: Query error on myserver.mydomain : HTTP status: 500. The system cannot find the file specified.
♥Solution : lookup at event log on server, and if there is a problem with a user profile of the account used for monitoring, do as this text.

9) Modelling error : SQL Server Management Object Assemblies were not found on the server. Please be sure they are installed.
♥Solution : Install a SQL SMO (Server Management Objects) in version adequate for the SQL server. File downloaded from Microsoft site : SharedManagementObjects.msu
Folder for installation : C:\Program Files\Microsoft SQL Server\130\SDK\Assemblies\
Link : https://msdn.microsoft.com/en-us/library/ms162189.aspx

10) Error :
Event Class : /Status/Winrm/Ping
Status : New
Message : Device is DOWN!

But server can be pinged!
♥ Solution 1 : install adequate PoSh version
♥ Solution 2 : do as under No (8)

This entry was posted in Uncategorized and tagged , . Bookmark the permalink.

Comments are closed.