How to check if NTP is working on your RSA SecurID Access Identity Router
Originally Published: 2017-04-19
Last Modified: 2022-06-20
Article Number
Applies To
RSA Product/Service Type: Identity Router
Issue
Having accurate time is important for authentication session management and other purposes.
This article explains how to check if an IDR has been successfully connecting to an NTP server and adjusting its time accordingly.
Tasks
Runtime events for ntpd are logged in the /var/log/messages file.
To check if ntpd has been able to connect to the NTP server and adjust time successfully each day, check /var/log/messages and search for any events containing ntpd. This must be done for every IDR, as follows:
- Generate and Download an Identity Router Log Bundle.
- Unzip the downloaded log bundle, and edit the file var\log\messages. This is a text file so any text editor can be used, such as Microsoft Notepad.
- Look for daily events that contain ntpdate and ntpd.
Resolution
Jan 28 16:15:02 portal ntpdate: Force synchronizing time Jan 28 16:15:02 portal ntpd[27058]: ntpd exiting on signal 15 Jan 28 16:15:02 portal ntpd[27058]: can't open /var/lib/ntp/drift.TEMP: Permission denied Jan 28 16:15:02 portal ntpdate: Shutting down network time protocol daemon (NTPD)..done Jan 28 16:15:02 portal ntpd[13802]: ntpd 4.2.4p8@1.1612-o Mon Feb 9 13:31:58 UTC 2015 (1) Jan 28 16:15:02 portal ntpd[13802]: precision = 1.000 usec Jan 28 16:15:02 portal ntpd[13802]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Jan 28 16:15:02 portal ntpd[13802]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled Jan 28 16:15:02 portal ntpd[13802]: Listening on interface #1 wildcard, ::#123 Disabled Jan 28 16:15:02 portal ntpd[13802]: Listening on interface #2 eth0, fe80::250:56ff:fe9a:6435#123 Enabled Jan 28 16:15:02 portal ntpd[13802]: Listening on interface #3 eth1, fe80::250:56ff:fe9a:7a90#123 Enabled Jan 28 16:15:02 portal ntpd[13802]: Listening on interface #4 lo, ::1#123 Enabled Jan 28 16:15:02 portal ntpd[13802]: Listening on interface #5 lo, 127.0.0.1#123 Enabled Jan 28 16:15:02 portal ntpd[13802]: Listening on interface #6 lo, 127.0.0.2#123 Enabled Jan 28 16:15:02 portal ntpd[13802]: Listening on interface #7 eth0, 10.156.194.12#123 Enabled Jan 28 16:15:02 portal ntpd[13802]: Listening on interface #8 eth1, 10.156.194.11#123 Enabled Jan 28 16:15:02 portal ntpd[13802]: Listening on interface #9 tun0, 10.250.242.26#123 Enabled Jan 28 16:15:02 portal ntpd[13802]: kernel time sync status 2040 Jan 28 16:15:02 portal ntpd[13802]: Frequency format error in /var/lib/ntp/drift Jan 28 16:15:11 portal ntpd[13802]: synchronized to 10.0.10.133, stratum 4 Jan 28 16:15:11 portal ntpd[13802]: time slew +0.000267 s Jan 28 16:15:11 portal ntpdate: ntpd: time slew +0.000267s Jan 28 16:15:11 portal ntpd[13874]: ntpd 4.2.4p8@1.1612-o Mon Feb 9 13:31:58 UTC 2015 (1) Jan 28 16:15:11 portal ntpd[13875]: precision = 1.000 usec Jan 28 16:15:11 portal ntpd[13875]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Jan 28 16:15:11 portal ntpd[13875]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled Jan 28 16:15:11 portal ntpd[13875]: Listening on interface #1 wildcard, ::#123 Disabled Jan 28 16:15:11 portal ntpd[13875]: Listening on interface #2 eth0, fe80::250:56ff:fe9a:6435#123 Enabled Jan 28 16:15:11 portal ntpd[13875]: Listening on interface #3 eth1, fe80::250:56ff:fe9a:7a90#123 Enabled Jan 28 16:15:11 portal ntpd[13875]: Listening on interface #4 lo, ::1#123 Enabled Jan 28 16:15:11 portal ntpd[13875]: Listening on interface #5 lo, 127.0.0.1#123 Enabled Jan 28 16:15:11 portal ntpd[13875]: Listening on interface #6 lo, 127.0.0.2#123 Enabled Jan 28 16:15:11 portal ntpd[13875]: Listening on interface #7 eth0, 10.156.194.12#123 Enabled Jan 28 16:15:11 portal ntpd[13875]: Listening on interface #8 eth1, 10.156.194.11#123 Enabled Jan 28 16:15:11 portal ntpd[13875]: Listening on interface #9 tun0, 10.250.242.26#123 Enabled Jan 28 16:15:11 portal ntpd[13875]: kernel time sync status 2040 Jan 28 16:15:11 portal ntpd[13875]: Frequency format error in /var/lib/ntp/drift Jan 28 16:15:11 portal ntpdate: Starting network time protocol daemon (NTPD)..done Jan 28 16:15:11 portal ntpdate: Time synchronizedIf the NTP server time is incorrect or unstable you may see messages like the one below, rather than a valid non-zero "time slew" message:
Apr 30 18:45:14 portal ntpd[6049]: ntpd: no servers found
If the IDR has not been able to connect to the configured NTP server because the NTP server was not listed in the configured DNS, you will get something like the following example instead of the lines above. Note that here, instead of a server IP address in the synchronized event, it shows that it synchronized with LOCAL(0) and time slew is always 0:
Jan 28 16:15:11 portal ntpd[13802]: synchronized to LOCAL(0), stratum 10
Jan 28 16:15:11 portal ntpd[13802]: time slew +0.000000 s
Notes
The stratum number reported by the NTP server in the synchronized event is an indication of how many NTP server hops there are between it and the reference clock. A lower number means it is closer, and so the time the NTP server delivers is more accurate.
Related Articles
How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x 662Number of Views RSA ID Plus Cloud Administration Console Forgot Password link is not working 397Number of Views Can you enforce DN uniqueness on KCA 14Number of Views SNMP queries and traps not working after configuring Authentication/Privacy passwords on RSA Authentication Manager 8.x 378Number of Views RSA SecurID Access Automatic Integrated Windows Authentication (IWA) not working 308Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?