Zenoss mogući problemi

Napomena na početku : ako WIN server nije u domenu WinRM NEĆE raditi!!!
Link ka brojevima grešaka koje izbacuje WinRM program!.

1) Kada se ponovo „Modeluje“ host, i javi se ovo :
2016-12-26 08:19:08,767 ERROR zen.PythonClient: Error on mojserver.mojdomen: Server not found in Kerberos database: HTTP@10.10.10.27
*****
♥To je najverovatnije ovo :
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.

Šta može da se uradi :
Dugme „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”}

Unos u /etc/hosts tabelu Zenoss servera :
[root@zenoss etc]# more hosts
127.0.0.1 localhost localhost.localdomain zenoss.mojdomen
10.10.10.19 mojserver1.mojdomen
10.10.10.42 mojserver2.mojdomen mojserver2
10.10.10.27 mojserver3.mojdomen mojserver3

2) Pri modelovanju se javi greška :
2016-12-26 09:06:36,534 ERROR zen.PythonClient: Connection refused on mojserver.mojdomen: Verify WinRM setup
♥Rešenje :
a) proveriti da li je user za monitoring u grupi Administratori za dati server
b) Proveriti iz komandne linije Zenoss servera :
[root@zenoss etc]# nc -z -w1 10.10.10.30 5985;echo $?
1
(“1” znači da je sve OK)

Proveriti Verziju PowerShell-a komandom : $PSVersionTable
Ako se ne dobilja ništa : To znači da je u pitanju PowerShell 1.0, a nama treba 2.0 (najmanje)!
♥Instalirati novu verziju PowerShell-a, najmanje 2.0!

3) Greška pri modelovanju : AttributeError: ‘NoneType’ object has no attribute ‘DomainRole’

4) Greška pri modelovanju : WARNING zen.ZenModeler: The plugin zenoss.winrm.IIS returned no results.
♥Ovo obično znači da IIS nije aktivan na serveru. Ako je to – isključiti taj modul pod Zenoss-om (Modeler Plugins).

5) Greška pri modelovanju : HTTP Unauthorized received on kerberos initialization. Kerberos error code -1765328343
♥Proveriti da li je unos za ovaj server u AD-u dobar (dva imena za istu IP adresu npr).

6) Greška pri modelovanju : ERROR zen.PythonClient: Error on mojserver.mojdomen : Cannot determine realm for numeric host address
♥Rešenje je da se podesi Configuration Properties/ zWinRMServerName i uneti puno ime servera sa domenom!

7) Greška : The following exception was thrown when trying to enumerate the collection : Failed to connect to server mojserver.mojdomen
♥Rešenje : dodati user-a za nadzor u MS SQL user-e (sa najmanje public pravima)

8) Greška pri modelovanju : ERROR zen.PythonClient: Query error on mojserver.mojdomen : HTTP status: 500. The system cannot find the file specified.
♥Rešenje : pogledati event log na serveru, i ako javlja probleme sa profilom naloga koji se koristi za nadzor servera uraditi po ovom uputstvu.

9) Greška pri modelovanju : SQL Server Management Object Assemblies were not found on the server. Please be sure they are installed.
♥Rešenje : Instalirati SQL SMO (Server Management Objects) u verziji koja odgovara SQL serveru. Fajl koji se spušta sa Microsoft sajta se zove : SharedManagementObjects.msu
Folder gde se instalira : C:\Program Files\Microsoft SQL Server\130\SDK\Assemblies\
Link : https://msdn.microsoft.com/en-us/library/ms162189.aspx

10) Greška generalno :
Event Class: /Status/Winrm/Ping
Status: New
Message: Device is DOWN!

Ali server je pingabilan!
♥ Rešenje 1 je instalacija PoSh najmanje v 2.0
♥ Rešenje 2 (ako 1 ne deluje) je uraditi kao pod stavkom (8)

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

Comments are closed.