<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.MsoHyperlink
{color:#0563C1;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:#954F72;
text-decoration:underline}
p.msonormal0, li.msonormal0, div.msonormal0
{margin-right:0in;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
span.EmailStyle18
{font-family:"Calibri",sans-serif;
color:windowtext}
span.EmailStyle19
{font-family:"Calibri",sans-serif;
color:windowtext}
.MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.WordSection1
{}
ol
{margin-bottom:0in}
ul
{margin-bottom:0in}
-->
</style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black; background-color:white">
Ah. I'm running 4.2.3 but haven't changed the release level. I'll get that sorted out.
<br>
<br>
</div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black; background-color:white">
Thanks for the replies! <br>
<br>
</div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black; background-color:white">
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black; background-color:white">
Get <a href="https://aka.ms/ghei36">Outlook for Android</a></div>
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> gpfsug-discuss-bounces@spectrumscale.org <gpfsug-discuss-bounces@spectrumscale.org> on behalf of John Hearns <john.hearns@asml.com><br>
<b>Sent:</b> Monday, September 4, 2017 8:43:59 AM<br>
<b>To:</b> gpfsug main discussion list<br>
<b>Subject:</b> Re: [gpfsug-discuss] Date formats inconsistent mmfs.log</font>
<div> </div>
</div>
<div>
<div class="WordSection1">
<p class="MsoNormal">Richard,</p>
<p class="MsoNormal">The date format changed at an update level.</p>
<p class="MsoNormal">We recently updated to 4.2.3 and when you run mmchconfig release=LATEST you are prompted to confirm that the new log format can be used.</p>
<p class="MsoNormal">I guess you might not have cut all nodes over yet on your update over the weekend?</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Cut and paste from the documentation:</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr>
<td valign="top" style="border:solid #DDDDDD 1.0pt; padding:5.25pt 7.5pt 5.25pt 7.5pt">
<p class="MsoNormal" style="margin-top:7.5pt"><span style="font-size:10.5pt; font-family:"Arial",sans-serif; color:#333333">mmfsLogTimeStampISO8601={yes | no}</span></p>
</td>
<td valign="top" style="border:solid #DDDDDD 1.0pt; border-left:none; padding:5.25pt 7.5pt 5.25pt 7.5pt">
<p class="MsoNormal" style="margin-top:7.5pt"><span style="font-size:10.5pt; font-family:"Arial",sans-serif; color:#333333">Setting this parameter to no allows the cluster to continue running with the earlier log time stamp format.</span></p>
<p class="MsoNormal" style="margin-top:7.5pt"><span style="font-size:10.5pt; font-family:"Arial",sans-serif; color:#333333">For more information, see
<a href="https://www.ibm.com/support/knowledgecenter/STXKQY_4.2.3/com.ibm.spectrum.scale.v4r23.doc/bl1adm_securitymode.htm?view=kc#bl1adm_securitymode" target="_blank" title="The security mode of a cluster determines the level of security that the cluster provides for communications between nodes in the cluster and also for communications between clusters.">
<span style="color:#3572B0; text-decoration:none">Security mode</span></a>.</span></p>
</td>
<td valign="top" style="border:solid #DDDDDD 1.0pt; border-left:none; padding:5.25pt 7.5pt 5.25pt 7.5pt">
<p class="MsoNormal" style="margin-left:0in; text-indent:-.25in"><span style="font-size:10.0pt; font-family:Symbol; color:#333333"><span style="">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:10.5pt; font-family:"Arial",sans-serif; color:#333333">Set mmfsLogTimeStampISO8061 to no if you save log information and you are not yet ready to switch to the new log time stamp format.</span></p>
<p class="MsoNormal" style="margin-top:7.5pt"><span style="font-size:10.5pt; font-family:"Arial",sans-serif; color:#333333">After you complete the migration, you can change the log time stamp format at any time with the mmchconfig command.</span></p>
<p class="MsoNormal" style="margin-left:0in; text-indent:-.25in"><span style="font-size:10.0pt; font-family:Symbol; color:#333333"><span style="">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:10.5pt; font-family:"Arial",sans-serif; color:#333333">Omit this parameter if you are ready to switch to the new format. The default value is yes</span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal" style="margin-top:7.5pt"><span style="font-size:10.5pt; font-family:"Arial",sans-serif; color:#333333"> </span></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> gpfsug-discuss-bounces@spectrumscale.org [mailto:gpfsug-discuss-bounces@spectrumscale.org]
<b>On Behalf Of </b>Sobey, Richard A<br>
<b>Sent:</b> Saturday, September 02, 2017 11:36 AM<br>
<b>To:</b> 'gpfsug-discuss@spectrumscale.org' <gpfsug-discuss@spectrumscale.org><br>
<b>Subject:</b> [gpfsug-discuss] Date formats inconsistent mmfs.log</p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span lang="EN-GB">Is there a good reason for the date formats in mmfs.log to be inconsistent? Apart from my OCD getting the better of me, it makes log analysis a bit difficult.</span></p>
<p class="MsoNormal"><span lang="EN-GB"> </span></p>
<p class="MsoNormal"><span lang="EN-GB">Sat Sep 2 10:33:42.145 2017: [I] Command: successful mount gpfs</span></p>
<p class="MsoNormal"><span lang="EN-GB">Sat 2 Sep 10:33:42 BST 2017: finished mounting /dev/gpfs</span></p>
<p class="MsoNormal"><span lang="EN-GB">Sat Sep 2 10:33:42.168 2017: [I] Calling user exit script mmSysMonGpfsStartup: event startup, Async command /usr/lpp/mmfs/bin/mmsysmoncontrol.</span></p>
<p class="MsoNormal"><span lang="EN-GB">Sat Sep 2 10:33:42.190 2017: [I] Calling user exit script mmSinceShutdownRoleChange: event startup, Async command /usr/lpp/mmfs/bin/mmsysmonc.</span></p>
<p class="MsoNormal"><span lang="EN-GB">Sat 2 Sep 10:33:42 BST 2017: [I] sendRasEventToMonitor: Successfully send a filesystem event to monitor</span></p>
<p class="MsoNormal"><span lang="EN-GB">Sat 2 Sep 10:33:42 BST 2017: [I] The Spectrum Scale monitoring service is already running. Pid=5134</span></p>
<p class="MsoNormal"><span lang="EN-GB"> </span></p>
<p class="MsoNormal"><span lang="EN-GB">Cheers</span></p>
<p class="MsoNormal"><span lang="EN-GB">Richard</span></p>
</div>
-- The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. Unless explicitly stated
otherwise in the body of this communication or the attachment thereto (if any), the information is provided on an AS-IS basis without any express or implied warranties or liabilities. To the extent you are relying on this information, you are doing so at your
own risk. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. Neither the sender nor the company/group of companies he or she represents shall be
liable for the proper and complete transmission of the information contained in this communication, or for any delay in its receipt.
</div>
</body>
</html>