<html><body><p><font size="2">Hi,</font><br><br><font size="2">are the nodes running on AIX? If so my advice would be to change /var/mmfs/mmsysmon/mmsysmonitor.conf to read</font><br><font size="2">[InterNodeEventing]</font><br><font size="2">usesharedlib = 0</font><br><font size="2"><br>and the do a "mmsysmoncontrol restart".</font><br><br><font size="2">What was the min. release level before the upgrade?</font><br><br><font size="2">For most other cases a "mmsysmoncontrol restart" on the affected nodes + cluster manager node should do.</font><br><br><font size="2" face="Arial">Mit freundlichen Grüßen / Kind regards</font><br><br><b><font face="Arial">Norbert Schuld</font></b><br><br><br><br><img width="16" height="16" src="cid:1__=4EBB0FD1DFD04DEF8f9e8a93df938690918c4EB@" border="0" alt="Inactive hide details for "Caubet Serrabou Marc (PSI)" ---06.04.2020 13:36:28---Hi all, after upgrading one of the clusters to "><font size="2" color="#424282">"Caubet Serrabou Marc (PSI)" ---06.04.2020 13:36:28---Hi all, after upgrading one of the clusters to GPFS v5.0.4-2 and setting "minReleaseLevel 5.0.4.0" I</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">"Caubet Serrabou Marc (PSI)" <marc.caubet@psi.ch></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">"gpfsug-discuss@spectrumscale.org" <gpfsug-discuss@spectrumscale.org></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">06.04.2020 13:36</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">[EXTERNAL] [gpfsug-discuss] "csm_resync_needed" after upgrading to GPFS v5.0.4-2</font><br><font size="2" color="#5F5F5F">Sent by: </font><font size="2">gpfsug-discuss-bounces@spectrumscale.org</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><font face="Calibri">Hi all,</font><br><br><font face="Calibri">after upgrading one of the clusters to GPFS v5.0.4-2 and setting "minReleaseLevel 5.0.4.0" I started to see random "csm_resync_needed" errors on some nodes. This can be easily cleared with "mmhealth node show --resync", however after some minutes the error re-appears.</font><br><font face="Calibri">Apparently, no errors in the log files and no apparent problems other than the "csm_resync_needed" error. </font><br><br><font face="Calibri">Before opening a support case, any hints about what could be the reason of that and whether I should worry about it? I would like to clarify what's going on before upgrading the main cluster.</font><br><br><font face="Calibri">Thanks a lot,</font><br><font face="Calibri">Marc </font><p><font size="2" face="Tahoma">_________________________________________________________<br>Paul Scherrer Institut <br>High Performance Computing & Emerging Technologies<br>Marc Caubet Serrabou<br>Building/Room: OHSA/014</font><br><font size="2" face="Tahoma">Forschungsstrasse, 111</font><br><font size="2" face="Tahoma">5232 Villigen PSI<br>Switzerland<br><br>Telephone: +41 56 310 46 67<br>E-Mail: marc.caubet@psi.ch</font><tt><font size="2">_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></font></tt><tt><font size="2"><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></font></tt><tt><font size="2"> <br></font></tt><br><br><BR>
</body></html>