-
Title
MongoDB service not starting correctly -
Description
MongoDB service starting and then immediately stopping by itself -
Cause
- Check C:\ProgramData\AppRecovery\EventsDatabase\db.log for the reason why MongoDB service is not starting correctly.
- One possible reason is that C drive do not have sufficient free disk space and MongoDB service is unable to start correctly.
- Rapid Recovery uses MongoDB version 7 as of Rapid Recovery 6.9 which requires a processor from the Sandy Bridge family (2011) or newer as per MongoDB requirements.
-
Resolution
To resolve the issue, please make sure that there's at least 4-5GB of free disk space on drive C, where MongoDB datafiles usually reside.
Additionally, the issue can be caused by immense amount of historical db.log files in C:\ProgramData\AppRecovery\EventsDatabase folder. Please delete all db.log files in that folder and try starting the service again.
As per the CPU requirements Here are Intel processor families in order of release date:
NOTE: Rapid Recovery 6.9 or newer supports processor family Sandy Bridge or newer.
Nehalem (2008) - This architecture introduced the concept of Turbo Boost.
Westmere (2009) - An update to Nehalem with minor architectural improvements and higher clock speeds.
Sandy Bridge (2011) - A major architecture leap, introducing improved graphics processing (Intel HD Graphics) and integrated memory controller.
Ivy Bridge (2012) - Updated version of Sandy Bridge with enhanced performance and further improvements to the integrated graphics.
Haswell (2013) - Continued refinements of the Sandy Bridge architecture, focusing on power efficiency and battery life for mobile devices.
Broadwell (2014) - Introduced a new transistor design, aiming for even greater energy efficiency but faced production issues initially.
Skylake (2015) - A significant architectural change, bringing updated security features, improved integrated graphics, and support for DDR4 memory.