# Mongo Error: ExceptionName " MongoNotConnectedError"

**URL:** <https://forum.genieacs.com/t/mongo-error-exceptionname-mongonotconnectederror/4488>\
**Category:** Uncategorized\
**Created:** [September 12, 2023, 2:44am UTC](https://forum.genieacs.com/t/mongo-error-exceptionname-mongonotconnectederror/4488 "2023-09-12T02:44:23Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:08am UTC](https://forum.genieacs.com/t/mongo-error-exceptionname-mongonotconnectederror/4488/3 "2023-11-30T09:08:35Z")

</div>

> [@Cwmp service failed with "Database clock skew too great" log](https://forum.genieacs.com/t/cwmp-service-failed-with-database-clock-skew-too-great-log/4635/5):
>
> 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 every 2 hours 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”. I just add some delay and reduce the number of devices / each request from my cron job and now problem di…

---

_[View the full topic](https://forum.genieacs.com/t/mongo-error-exceptionname-mongonotconnectederror/4488)._