That’s worked, thanks Andreas. Question: when I upgrade to the new PTF when it’s available, can I install it first on just the GUI node (which happens to be the Quorum server for the cluster) and the fixes will go in, or do I need to deploy the new pmsensors packages?
From: [email protected] [mailto:[email protected]] On Behalf Of Andreas Koeninger Sent: 08 November 2016 16:50 To: [email protected] Subject: Re: [gpfsug-discuss] How to clear stale entries in GUI log Hello Richard, without the PTF (which is not yet available) you will have to manually clear the GUI database as well by running the following command on the GUI node: psql postgres postgres -c "delete from fscc.gss_state where sensor like 'H\_%';" This will remove all events from the GUI database coming from mmhealth. To repopulate this table with all the currently reported events from mmhealth please run: /usr/lpp/mmfs/gui/cli/runtask HEALTH_STATES Let me know if that helps, Andreas Koeninger Spectrum Scale GUI Development ----- Original message ----- From: "Sobey, Richard A" <[email protected]> Sent by: [email protected] To: gpfsug main discussion list <[email protected]> Cc: Subject: Re: [gpfsug-discuss] How to clear stale entries in GUI log Date: Tue, Nov 8, 2016 4:10 PM Thanks. I’ve run that on, I assume, our quorum server where this disk is mounted, but the error is still showing up. The event itself doesn’t say which node is affected. ICSAN_GPFS_FSD_QUORUM nsd 512 103 no no ready up system That looks ok to me. Maybe I misunderstood your line “This is a per node database, so you need to run this on all the nodes which have stale entries.”. Should I just run it on all the nodes in the cluster instead… there’s not many so won’t take long but wondering if that’s really necessary? Thanks Richard From: [email protected] [mailto:[email protected]] On Behalf Of Markus Rohwedder Sent: 08 November 2016 14:51 To: [email protected] Subject: [gpfsug-discuss] How to clear stale entries in GUI log Hello, you ran into a defect which is fixed with the upcoming 4.2.1.2 PTF Here is a workaround: You can clear the eventlog of the system health component using mmsysmonc clearDB This is a per node database, so you need to run this on all the nodes which have stale entries. It will clear all the events on this node, if you want to save them run: mmhealth node eventlog > log.save On the GUI node, run systemctl restart gpfsgui afterwards. The mmhealth command suppresses events during startup. So in case a bad condition turns OK during a restart phase, the bad event will remain stale. Regards, Markus Rohwedder IBM Spectrum Scale GUI development _______________________________________________ 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
