MongoDB: Exception In InitAndListen: 20 Attempted To Create A Lock File On A Read-Only Directory: /Data/Db, Terminating
I created /data/db in root directory and ran ./mongodb:
[initandlisten] exception in initAndListen: 20 Attempted to create a lock file on a read-only directory: /data/db, terminating
[initandlisten] shutdown: going to close listening sockets... [initandlisten] shutdown: going to flush dialog... [initandlisten] now exiting [initandlisten] shutting down with code:100
If you received the error - MongoDB: Exception In InitAndListen: 20 Attempted To Create A Lock File On A Read-Only Directory: /Data/Db, Terminating The problem is that the directory you created, /data/db is owned by and only writable by the root user, but you are running mongodb as yourself. There are several ways to resolve this, but ultimately, you must give the directory in question the right permissions. If this is for production, I would advise you to check the docs and think this over carefully -- you probably want to take special care.
However, if this is just for testing and you just need this to work and get on with it, you could try this, which will make the directory writable by everyone:
> sudo chmod -R go+w /data/db
or this, which will make the directory owned by you:
> sudo chown -R $USER /data/db
Answer (1)
The error message Exception in initAndListen: 20 Attempted to create a lock file on a read-only directory: /data/db, terminating in MongoDB indicates that MongoDB is trying to create a lock file in the /data/db directory, but it does not have the necessary write permissions to do so. This typically happens due to permission issues or incorrect directory ownership.
To resolve this issue, follow these steps:
1. Check the Directory Permissions
Ensure that the MongoDB process has the correct permissions to write to the /data/db directory.