cimserver: PGS17200: Authentication failed for user root

[kenny chia]

Hi
I have this recurring log that occurs in my server /var/adm/syslog/syslog.log file everyday at the same time

Oct 8 16:06:08 svr cimserver[1504]: PGS17200: Authentication failed for user root.
Oct 8 16:06:25 svr sshd[242]: Did not receive identification string from 192.168.23.108
Oct 8 16:06:24 svr cimserver[1504]: PGS17200: Authentication failed for user root.


This server is a HPUX11.23 server.
There is a HPSIM installation at IP 192.168.23.108.

my guess is that HPSIM is trying to login to the server but there seems to be some authentication issues here. What could be wrong?

[corinne haesaerts]

well, when you initialize SIM there is a page with global protocol settings. On that page you can define users/passwords that have to be authenticated for wbem. Usually you would enter the wbem user, but for linux systems you would probably have a pegasus user too.
my guess is that you entered multiple user/passwd combinations & that these are not present in your /etc/passwd file, or that the root password for that particular server does not match.

[Charles Slivkoff]

Anyone have any more info on this?

I'm getting the exact same error, daily:

Apr 2 16:05:40 hostname cimserver[PID]: PGS17200: Authentication failed for user .

[David Claypool]

If you have WBEM globally enabled, there are up to 5 username/password combinations that can be specified. During Daily System Identification, HP SIM will attempt to use all populated authentication pairs to establish whether HP SIM can communicate with the device using WBEM (Common Information Model data encoded in XML and transported over secure HTTP).

[Turgay Cavdar]

Hi,
Can you check the following article?!!



Submitted Date: Tue Apr 29 20:30:45 GMT 2008
Title: HP-UX Operating Systems - Authentication CIM Error Message in Syslog.log
Document ID: emr_na-c01446676-1
Last Modified Date: Wed May 07 18:23:35 GMT 2008



You may provide feedback on this document

HP-UX Operating Systems - Authentication CIM Error Message in Syslog.log
ISSUE:
The following error message is being seen in the /var/adm/syslog/syslog.log file:

CIM :PGS17200: Authentication failed for user root.

SOLUTION:
The system that was getting the message in syslog.log is a Central Management Server (CMS) which runs System Insight Manager (SIM). It is running SIM v C.05.01.

Test the communication between the server and node that was being identified from the error message.

Run the following from the server:

# mxnode -ld


...
Protocols: HTTP: WBEM:1.0 SMH:2.0 SNMP:1.0 SSH:SSH-2.0-OpenSSH_4.4p1-hpn12v11
...



The Protocol line shows that WBEM is being one of the available protocols, meaning the WBEM communication is working (The CIM error is a WBEM issue).

The next step is to remove the node from the server. This can be done from the GUI of the SIM through the browser, or from the command line.

From the Command line:

# mxnode â r

And then re-added it

# mxnode â a or

After re-adding the node, the messages stopped.

[cemperor]

I had suffered this problem for a month, either.

I didn't apply the approach exactly posted here ,which is using mxnode in command line of SIM server. Instead, I tried to manually remove the node from SIM GUI and re-added. By removing and re-adding the I think it serves as the same way the command line 'mxnode -d ' does.

But what I get is that it still not working.
The PGS17200 message still troubles me over and over.

Is there anyone can help me solve this?
Many thanks in advance.

[catastro]

Hi all. I am having the same problems as you all and solved this issue.
In the SIM server, you should select your server from the System collection, and go from ther to the "Tools & Links" tab.
Go to System Credentials and select all or the WBEM / WMI / Sign in / SSH ones. Push the "Edit System Credentials..." button, and in the "Sign in" tab, enter the right user and password.
Hope this helps. This helped me as this was affecteing several servers and now it's not happening.

Note, that if you change the user's password, all this issue will appear again. I use the root user and it's password as it's only collecting information from the server.