Hi Andreas,
Output of the debug log – no clue, but maybe you can interpret it better 😊
[root@icgpfsq1 ~]# /usr/lpp/mmfs/gui/cli/runtask pm_monitor --debug
debug: locale=en_US
debug: Raising event: gui_pmcollector_connection_ok, for node:
localhost.localdomain
err: com.ibm.fscc.common.exceptions.FsccException:
com.ibm.fscc.common.exceptions.FsccException: No entity found for NODE:
null/localhost.localdomain
at
com.ibm.fscc.db.object.health.HealthEventRaiser.raiseEvent(HealthEventRaiser.java:280)
at
com.ibm.fscc.common.tasks.ZiMONMonitorTask.run(ZiMONMonitorTask.java:144)
at
com.ibm.fscc.common.newscheduler.RefreshTaskExecutor.executeRefreshTask(RefreshTaskExecutor.java:221)
at
com.ibm.fscc.common.newscheduler.RefreshTaskExecutor.executeRefreshTask(RefreshTaskExecutor.java:193)
at
com.ibm.fscc.common.newscheduler.RefreshTaskIds.execute(RefreshTaskIds.java:369)
at
com.ibm.fscc.newcli.commands.task.CmdRunTask.doExecute(CmdRunTask.java:65)
at
com.ibm.fscc.newcli.internal.AbstractCliCommand.execute(AbstractCliCommand.java:156)
at
com.ibm.fscc.cli.CliProtocol.processNewStyleCommand(CliProtocol.java:426)
at com.ibm.fscc.cli.CliProtocol.processRequest(CliProtocol.java:412)
at com.ibm.fscc.cli.CliServer$CliClientServer.run(CliServer.java:93)
Caused by: com.ibm.fscc.common.exceptions.FsccException: No entity found for
NODE: null/localhost.localdomain
at
com.ibm.fscc.db.object.health.HealthEventRaiser.raiseEvent(HealthEventRaiser.java:328)
at
com.ibm.fscc.db.object.health.HealthEventRaiser.raiseEvent(HealthEventRaiser.java:278)
... 9 more
err: com.ibm.fscc.common.exceptions.FsccException:
com.ibm.fscc.common.exceptions.FsccException: No entity found for NODE:
null/localhost.localdomain
at
com.ibm.fscc.db.object.health.HealthEventRaiser.raiseEvent(HealthEventRaiser.java:280)
at
com.ibm.fscc.common.tasks.ZiMONMonitorTask.run(ZiMONMonitorTask.java:144)
at
com.ibm.fscc.common.newscheduler.RefreshTaskExecutor.executeRefreshTask(RefreshTaskExecutor.java:221)
at
com.ibm.fscc.common.newscheduler.RefreshTaskExecutor.executeRefreshTask(RefreshTaskExecutor.java:193)
at
com.ibm.fscc.common.newscheduler.RefreshTaskIds.execute(RefreshTaskIds.java:369)
at
com.ibm.fscc.newcli.commands.task.CmdRunTask.doExecute(CmdRunTask.java:65)
at
com.ibm.fscc.newcli.internal.AbstractCliCommand.execute(AbstractCliCommand.java:156)
at
com.ibm.fscc.cli.CliProtocol.processNewStyleCommand(CliProtocol.java:426)
at com.ibm.fscc.cli.CliProtocol.processRequest(CliProtocol.java:412)
at com.ibm.fscc.cli.CliServer$CliClientServer.run(CliServer.java:93)
Caused by: com.ibm.fscc.common.exceptions.FsccException: No entity found for
NODE: null/localhost.localdomain
at
com.ibm.fscc.db.object.health.HealthEventRaiser.raiseEvent(HealthEventRaiser.java:328)
at
com.ibm.fscc.db.object.health.HealthEventRaiser.raiseEvent(HealthEventRaiser.java:278)
... 9 more
debug: Will not raise the following event using 'mmsysmonc' since it already
exists in the database: reportingNode = 'icgpfsq1', eventName =
'gui_refresh_task_failed', entityId = '11', arguments = 'PM_MONITOR',
identifier = 'null'
err: com.ibm.fscc.common.exceptions.FsccException: No entity found for NODE:
null/localhost.localdomain
err: com.ibm.fscc.cli.CommandException: EFSSG1150C Running specified task was
unsuccessful.
at
com.ibm.fscc.cli.CommandException.createCommandException(CommandException.java:117)
at
com.ibm.fscc.newcli.commands.task.CmdRunTask.doExecute(CmdRunTask.java:69)
at
com.ibm.fscc.newcli.internal.AbstractCliCommand.execute(AbstractCliCommand.java:156)
at
com.ibm.fscc.cli.CliProtocol.processNewStyleCommand(CliProtocol.java:426)
at com.ibm.fscc.cli.CliProtocol.processRequest(CliProtocol.java:412)
at com.ibm.fscc.cli.CliServer$CliClientServer.run(CliServer.java:93)
EFSSG1150C Running specified task was unsuccessful.
Thanks
Richard
From: Andreas Koeninger [mailto:[email protected]]
Sent: 27 June 2018 13:50
To: Sobey, Richard A <[email protected]>
Cc: [email protected]
Subject: Re: [gpfsug-discuss] PM_MONITOR refresh task failed
Hi Richard,
if you double-click the event there should be some additional help available.
The steps under "User Action" will hopefully help to identify the root cause:
1.) Check if there is additional information available by executing
'/usr/lpp/mmfs/gui/cli/lstasklog [taskname]'.
2.) Run the specified task manually on the CLI by executing
'/usr/lpp/mmfs/gui/cli/runtask [taskname] --debug'.
...
Mit freundlichen Grüßen / Kind regards
Andreas Koeninger
Scrum Master and Software Developer / Spectrum Scale GUI and REST API
IBM Systems &Technology Group, Integrated Systems Development / M069
-------------------------------------------------------------------------------------------------------------------------------------------
IBM Deutschland
Am Weiher 24
65451 Kelsterbach
Phone: +49-7034-643-0867
Mobile: +49-7034-643-0867
E-Mail: [email protected]<mailto:[email protected]>
-------------------------------------------------------------------------------------------------------------------------------------------
IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats:
Martina Koederitz
Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen /
Registergericht: Amtsgericht Stuttgart, HRB 243294
----- Original message -----
From: "Sobey, Richard A" <[email protected]<mailto:[email protected]>>
Sent by:
[email protected]<mailto:[email protected]>
To: gpfsug main discussion list
<[email protected]<mailto:[email protected]>>
Cc:
Subject: Re: [gpfsug-discuss] PM_MONITOR refresh task failed
Date: Wed, Jun 27, 2018 2:29 PM
Hi Renar,
No, it all runs over the same network.
Thanks,
Richard
From:
[email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Grunenberg,
Renar
Sent: 27 June 2018 12:29
To: 'gpfsug main discussion list'
<[email protected]<mailto:[email protected]>>
Subject: Re: [gpfsug-discuss] PM_MONITOR refresh task failed
Hallo Richard,
do have a private admin-interface-lan in your cluster if yes than the logic of
query the collector-node, and the representing ccr value are wrong. Can you
‘mmperfmon query cpu’? If not then you hit a problem that I had yesterday.
Renar Grunenberg
Abteilung Informatik – Betrieb
HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon:
09561 96-44110
Telefax:
09561 96-44104
E-Mail:
[email protected]<mailto:[email protected]>
Internet:
www.huk.de<http://www.huk.de>
________________________________
HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands
a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav
Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas.
________________________________
Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte
Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich
erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist
nicht gestattet.
This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information in
error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in this
information is strictly forbidden.
________________________________
Von:
[email protected]<mailto:[email protected]>
[mailto:[email protected]] Im Auftrag von Sobey,
Richard A
Gesendet: Mittwoch, 27. Juni 2018 12:47
An: '[email protected]'
<[email protected]<mailto:[email protected]>>
Betreff: [gpfsug-discuss] PM_MONITOR refresh task failed
Hi all,
I’m getting the following error in the GUI, running 5.0.1:
“The following GUI refresh task(s) failed: PM_MONITOR”.
As yet, this is the only node I’ve upgraded to 5.0.1 – the rest are running
(healthily, according to the GUI) 4.2.3.7. I’m not sure if this version
mismatch is relevant to reporting this particular error.
All the usual steps of restarting gpfsgui / pmcollector / pmsensors have been
done.
Will the error go away when I’ve completed the cluster upgrade, or is there
some other foul play at work here?
Cheers
Richard
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss
