Troubleshooting Tip: How to troubleshoot NTP issues on FortiWeb

Description

This article describes how to troubleshoot NTP-related issues on FortiWeb.

Scope

FortiWeb.

Solution

For NTP-related issues, such as NTP not syncing correctly with NTP servers (internal or external) or reachability issues, there are some troubleshooting steps to perform to speed up resolution.

1. Check if the NTPD daemon is working.
   
   

FortiWeb-VM-01 # diagnose sys ps | grep ntp
3244 root 88708 S /bin/ntpd < ------ntpd is working with S status
5452 root 2920 S /bin/cli_grep ntp

If the daemon is not working, refer to this link to restart the NTPD daemon: Technical Tip: How to restart process or daemon on FortiWeb using CLI.

2. Check the available NTP servers:
    

FortiWeb-VM-01 # get sys ntp
ntpsync : enable
syncinterval : 1
== [ 1 ]
server: pool.ntp.org1
authentication: disable
ip-type: v4

== [ 2 ]
server: time.google.com
authentication: disable

3. Debugs: Start by taking debugs and packet captures. Open FortiWeb via SSH (putty or secure CRT).

Run the commands below:

diagnose debug application ntpd
diagnose debug enable

Run for a few minutes, depending on the NTP sync interval time.

To disable, run the commands below:

diagnose debug disable

For more information on how to collect packet capture: packet capture.

4. Check event logs for any events related to NTP-related issues.

5. One more workaround to try: toggle the Set time setting from NTP to Manual settings and save it. Then, in 1 minute, put it back to NTP again and save it. This will restart the NTP process on FortiWeb.

Related document:

Setting the system time & date