We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda NextGen Firewall X

"Unresolvable clock skew detected" error in dstatm logfile

  • Type: Knowledgebase
  • Date changed: 6 months ago
Solution #00005106
 
Scope:
This solution replies to:
- NG Firewall firmware versions 4.2.x, 5.0.x, 5.2.x
- netfence firmware versions 4.2.x

 
Symptoms:

After system reboot, a time inconsistency occurs. The following error messages are recorded in the dstatm log file:

 

Error *** Unresolvable clock skew detected *** (last run 1066262400, today 1280707200)
Error Main stopped

 


Solution:

System time on the Management Centre does not match with the time of the last statistics collection. Reset the timestamp in the header of the dstatm.db file.

Check actual value, key and filename.

    showdb /phion0/dstatm/dstatm.db
    [...]
    _header_ 2611 100 1053043200 1066262400 manc
    shofw.... box F range clean idle 0 1066276850 10.1.1.1 data collect
    [...]

 

Set the new parameter to the database.
    setbdb _header_ "2611 100 0 0 manc" ./dstatm.db 2611 100 = key
    0 0 manc = value
    ./dstatm.db = filename

Check the new parameter in the database

    showdb /phion0/dstatm/dstatm.db
    _header_ 2611 100 0 0 manc
    fw.... box F range clean idle 0 1066276850 10.1.1.1 data collect

 

 

Link to This Page:
https://campus.barracuda.com/solution/50160000000IKYNAA4