[gpfsug-discuss] Pmsensors and gui

[Sobey, Richard A]

I can help with the first one as I had the issue a few weeks ago. The answer from support is below, verbatim.

---------------------------------------------------------------------------------------------------------------------------------------------

When trying to resolve the IP-Address in the JAVA code the first entry entry in the list is returned.
Just localhost was expected for this. If the order is other way around and the list starts with
localhost.localdomain, the GUI unfortunately cannot resolve the real node name and will fail with
the message seen in the log files.
Thus I assume that this is the case for your customer.

it seems that our code it not as tolerant as it should be for the localhost definitions in
the /etc/hosts file on the GUI node.
We need to change this in our code to handle accordingly.

Please let the customer adjust this entry and place localhost at the top of the list.
After this the task should run successful and the state should be OK again for the pm_collector.
---------------------------------------------------------------------------------------------------------------------------------------------

checking the GUI nodes /etc/hosts it shows actually

127.0.0.1   localhost.localdomain localhost4 localhost4.localdomain4 localhost

From: gpfsug-discuss-bounces at spectrumscale.org <gpfsug-discuss-bounces at spectrumscale.org> On Behalf Of Simon Thompson
Sent: 09 October 2018 14:38
To: gpfsug-discuss at spectrumscale.org
Subject: [gpfsug-discuss] Pmsensors and gui

Hi,

I have a couple of a problems with the GUI and the stats data in there …

First, on the gui node, I am getting “The following GUI refresh task(s) failed: PM_MONITOR”, looking at the log for this:

PM_MONITOR *      2018-10-09 14:35:31 15ms    failed RefreshTaskScheduler$1.run           com.ibm.fscc.common.exceptions.FsccException: No entity found for NODE: null/localhost.localdomain

Suggestions?

Second, a bunch of my hosts have multiple NICs on different networks, they are joined to the cluster with the name hostname1-data, however the “primary” hostname of the host is “hostname”. I see summary stats information in the GUI which references the shortname of the host, but when I click the host in the GUI, it claims no data – I assume because the GPFS hostname is the -data nama and pmsensors is using the primary hostname.

Simon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20181009/ff215428/attachment.htm>