|Applies To||SecurID Appliance 3.0|
|Issue||How to start NTP service automatically after a reboot|
The time on the Appliance drifts, eventually causing tokens to go into next tokencode mode.
The NTP service was configured and running, but after a reboot it was no longer running.
|Cause||When the Appliance was initially configured via quick setup the NTP service was not configured, instead it was done by editing the ntp.conf file and then starting NTP with the ?/sbin/service ntpd start' or similar command. Under these circumstances the Appliance is not configured to auto-start the NTP service.|
Log onto the Appliance as emcsrv (either at the console or via SSH) sudo to root and run the '/sbin/chkconfig --levels 2345 ntpd on' command. This configures NTP as a service, to be started automatically when the Appliance is started.
login as: emcsrv
|Legacy Article ID||a49766|