Richard,
The date format changed at an update level.
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.
I guess you might not have cut all nodes over yet on your update over the
weekend?
Cut and paste from the documentation:
mmfsLogTimeStampISO8601={yes | no}
Setting this parameter to no allows the cluster to continue running with the
earlier log time stamp format.
For more information, see Security
mode<https://www.ibm.com/support/knowledgecenter/STXKQY_4.2.3/com.ibm.spectrum.scale.v4r23.doc/bl1adm_securitymode.htm?view=kc#bl1adm_securitymode>.
* Set mmfsLogTimeStampISO8061 to no if you save log information and you
are not yet ready to switch to the new log time stamp format.
After you complete the migration, you can change the log time stamp format at
any time with the mmchconfig command.
* Omit this parameter if you are ready to switch to the new format. The
default value is yes
From: [email protected]
[mailto:[email protected]] On Behalf Of Sobey, Richard A
Sent: Saturday, September 02, 2017 11:36 AM
To: '[email protected]' <[email protected]>
Subject: [gpfsug-discuss] Date formats inconsistent mmfs.log
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.
Sat Sep 2 10:33:42.145 2017: [I] Command: successful mount gpfs
Sat 2 Sep 10:33:42 BST 2017: finished mounting /dev/gpfs
Sat Sep 2 10:33:42.168 2017: [I] Calling user exit script mmSysMonGpfsStartup:
event startup, Async command /usr/lpp/mmfs/bin/mmsysmoncontrol.
Sat Sep 2 10:33:42.190 2017: [I] Calling user exit script
mmSinceShutdownRoleChange: event startup, Async command
/usr/lpp/mmfs/bin/mmsysmonc.
Sat 2 Sep 10:33:42 BST 2017: [I] sendRasEventToMonitor: Successfully send a
filesystem event to monitor
Sat 2 Sep 10:33:42 BST 2017: [I] The Spectrum Scale monitoring service is
already running. Pid=5134
Cheers
Richard
-- 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.
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss
