# Cwmp service failed with "Database clock skew too great" log

**URL:** <https://forum.genieacs.com/t/cwmp-service-failed-with-database-clock-skew-too-great-log/4635>\
**Category:** Uncategorized\
**Created:** [October 25, 2023, 6:44am UTC](https://forum.genieacs.com/t/cwmp-service-failed-with-database-clock-skew-too-great-log/4635 "2023-10-25T06:44:17Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![harilam](https://avatars.discourse-cdn.com/v4/letter/h/8dc957/32.png) [@harilam](https://forum.genieacs.com/u/harilam)\
**Post date:** [November 30, 2023, 9:02am UTC](https://forum.genieacs.com/t/cwmp-service-failed-with-database-clock-skew-too-great-log/4635/5 "2023-11-30T09:02:56Z")

</div>

Hi Felipe,  
I think I already figured out the problem with my production environment.  
My production run a cron job to get all devices’ information periodically via NBI and this is the main cause of the _exceptionName=“Error” exceptionMessage=“Database clock skew too great”_ and _exceptionName=“MongoNotConnectedError” exceptionMessage=“MongoClient must be connected to perform this operation”_. **So, mongoDB high load is the main cause of this problem.**  
I just add some delay and reduce the number of devices / each request from my cron job and now problem disappeared.

For others: please check the mongoDB read/write statistics (using Studio3T) when problem happen and identify the source of problem in your environment.

---

_[View the full topic](https://forum.genieacs.com/t/cwmp-service-failed-with-database-clock-skew-too-great-log/4635)._