SMS didn't restart after reboot in a SafeCity project

Publication Date:  2016-06-29 Views:  452 Downloads:  0
Issue Description
In a SafeCity project, after power off and power on, the SMS module didn't start.
Handling Process
According to the logs below, password expired already. 

Jun  2 11:05:33 SMS1 su: pam_unix(su-l:chauthtok): password - (old) token not obtained

Jun  2 11:05:33 SMS1 su: FAILED SU (to sms) root on none

 

2016/05/27 04:54:35 SMS2 reboot

2016/05/27 04:54:35 VCS NOTICE V-16-1-11022 VCS engine (had) started

2016/05/27 04:54:35 VCS INFO V-16-1-10196 Cluster logger started

 

 VCS cannot start the resource due to password expire

2016/05/27 04:54:52 VCS NOTICE V-16-1-10435 Group VCShmg will not start automatically on System SMS1 as the system is not a part of AutoStartList attribute of the group.

2016/05/27 04:54:52 VCS NOTICE V-16-1-10438 Group VCShmg has been probed on system SMS2

2016/05/27 04:54:52 VCS NOTICE V-16-1-10435 Group VCShmg will not start automatically on System SMS2 as the system is not a part of AutoStartList attribute of the group.

 

 2016/06/02 Reset the password

Jun  2 11:07:27 SMS1 sshd[208206]: pam_unix(sshd:chauthtok): password changed for sms

 

Jun  2 11:11:07 SMS2 sshd[212969]: pam_unix(sshd:chauthtok): password changed for sms

 

2016/06/02 11:07:34 tomcat start

2016/06/02 11:07:34 VCS INFO V-16-1-10304 Resource tomcat (Owner: Unspecified, Group: ClusterService) is offline on SMS1 (First probe)

2016/06/02 11:07:34 VCS NOTICE V-16-1-10438 Group ClusterService has been probed on system SMS1

 

Root Cause

Password of SMS module expired.

Solution
Reset the password of SMS.
Suggestions
Modify the password routinely.

END