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

# sk170233 - Time and date in dmesg and /var/log/messages are not correlated 

| Property | Value |
|----------|-------|
| Solution ID | sk170233 |
| Date Created | 2020-10-28 |
| Last Modified | 2020-11-01 |
| Technical Level | Advanced |
| Products | Security Gateway, Security Management Server |
| Versions | R81 (EOS), R81 (EOS) |
| OS | Gaia |

## Symptoms

- Time prints in `dmesg` and `/var/log/messages` are not correlated.  
For example:  

`[Expert@GW:0]# dmesg | grep eth3-01`  
`[Thu `**Oct 22 04:03:43**` 2020] mlx5_core 0000:3c:00.0 eth3-01: Link down`  
`[Thu `**Oct 22 04:03:43**` 2020] mlx5_core 0000:3c:00.0 eth3-01: speed changed to 0 for port eth3-01`  
`[Thu Oct 22 04:03:43 2020] mlx5_core 0000:3c:00.1 eth3-02: Link down`  
`[Thu Oct 22 04:03:43 2020] bond0: link status down for interface eth3-01, disabling it in 200 ms`  

`[Expert@GW:0]# cat /var/log/messages | grep eth3-01`  
**Oct 22 05:07:09**` 2020 GW kernel: mlx5_core 0000:3c:00.0 eth3-01: Link down`  
**Oct 22 05:07:09**` 2020 GW kernel: mlx5_core 0000:3c:00.0 eth3-01: speed changed to 0 for port eth3-01`

## Cause

The *dmesg* prints messages based on the Hardware clock, while the */var/log/messages* content is based on the System clock and they are not synchronized.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# 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