Commit errors observed on dual REs, indicating the file /var/run/db/juniper.db is unavailable

The below errors is observed during the commit:

user@host# commit

re1:

re0:

error: could not get initial lock on database: Resource temporarily unavailable

error: Database lock failed for file '/var/run/db/juniper.db': Resource temporarily unavailable

error: Could not initialize database

Database was created by software version: MGD release 20210209.032601_builder.r1169532 built by builder on 2021-02-09 03:45:03 UTCCurrent software version: MGD release 20210209.032601_builder.r1169532 built by builder on 2021-02-09 03:45:03 UTC

The database can be re-created with the current software version and reloaded with the currently committed configuration (using rollback).

The error observed indicates a problem at the time of accessing the database files, this can often be seen when there is a memory problem on the RE, in this specific case, the RE was rebooted which cleared the memory error and the subsequent commits were successful