> Source: [sk182235](https://support.checkpoint.com/results/sk/sk182235)

# sk182235 - Updating the NTP Server may cause a temporary outage

| Property | Value |
|----------|-------|
| Solution ID | sk182235 |
| Date Created | 2024-04-22 |
| Last Modified | 2024-04-30 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R81.20, R81.10 (EOS), R81 (EOS) |

## Symptoms

- * Processes such as IKED and VPND fail to restart after the time shift on the NTP Server and cause a temporary outage.
* The `/var/log/messages` file shows:

  DATE TIME Firewall1 ntpd\[40048\]: 0.0.0.0 clock_step **-287.099573** s  
  DATE TIME Firewall1 ntpd\[40048\]: 0.0.0.0 clock_sync  
  DATE TIME Firewall1 monitord\[2313\]: **Time shift detected !!!**   
  DATE TIME Firewall1 ntpd\[40048\]: 0.0.0.0 no_sys_peer
* The `cpwd.elg` file may also show:   
  \[cpWatchDog \] \[ERROR\] vpnd (pid=41468) did not send keep-alive message for 1 number of times   
  \[cpWatchDog \] \[ERROR\] vpnd (pid=41468) did not send keep-alive message for 2 number of times   
  \[cpWatchDog \] \[ERROR\] vpnd (pid=41468) did not send keep-alive message for 3 number of times   
  \[cpWatchDog \] \[ERROR\] vpnd (pid=41468) did not send keep-alive message for 4 number of times   
  \[cpWatchDog \] \[ERROR\] vpnd (pid=41468) did not send keep-alive message for 5 number of times   
  \[cpWatchDog \] \[ERROR\] vpnd (pid=41468) did not send keep-alive message for 6 number of times   
  \[cpWatchDog \] \[INFO\] Signal was sent to process vpnd (pid=41468)   
  \[cpWatchDog \] \[ERROR\] vpnd (pid=41468) did not send keep-alive message for 7 number of times  
  **\[cpWatchDog \] \[SUCCESS\] Killed process vpnd with** pid 41468

## Cause

Manual editing of the NTP Server clock caused a synchronization issue between the NTP Server and the Security Gateway.

## Solution

This problem was fixed. The fix is included in:

* [Jumbo Hotfix Accumulator for R81.20](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.20/Default.htm) starting from Take 54
* [Jumbo Hotfix Accumulator for R80.40](https://sc1.checkpoint.com/documents/Jumbo_HFA/R80.40/Default.htm) starting from Take 211
* [Jumbo Hotfix Accumulator for R81.10](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.10/Default.htm) starting from Take 141

If you choose not to upgrade, Check Point can supply a **Hotfix** . [Contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) to get a Hotfix for this issue.  
A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.  
For faster resolution and verification, please collect [CPinfo files](http://supportcontent.checkpoint.com/solutions?id=sk92739) from the Security Management Server and Security Gateways involved in the case.

**Hotfix installation instructions:**   
Refer to [sk168597 - How to install a Hotfix](https://support.checkpoint.com/results/sk/sk168597).

<br />

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content