Goodwin
Goodwin

Reputation: 183

MongoDB Operation Not Permitted

MongoDB was working perfectly until one day it generated a lock file and stopped starting with the following error:

16-12-28T17:50:14.559+0100 I CONTROL  [initandlisten] build environment:
2016-12-28T17:50:14.559+0100 I CONTROL  [initandlisten]     distmod: debian71
2016-12-28T17:50:14.559+0100 I CONTROL  [initandlisten]     distarch: x86_64
2016-12-28T17:50:14.559+0100 I CONTROL  [initandlisten]     target_arch: x86_64
2016-12-28T17:50:14.559+0100 I CONTROL  [initandlisten] options: {}
2016-12-28T17:50:14.577+0100 I -        [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2016-12-28T17:50:14.577+0100 I STORAGE  [initandlisten]
2016-12-28T17:50:14.577+0100 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
2016-12-28T17:50:14.577+0100 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
2016-12-28T17:50:14.577+0100 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=1024M,session_max=20000,eviction=(threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
2016-12-28T17:50:14.590+0100 E STORAGE  [initandlisten] WiredTiger error (1) [1482943814:590694][32048:0x7f27c7cdcc80], file:WiredTiger.wt, connection: /data/db/WiredTiger.wt: handle-open: open: Operation not permitted
2016-12-28T17:50:14.591+0100 I -        [initandlisten] Assertion: 28595:1: Operation not permitted src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 267
2016-12-28T17:50:14.591+0100 I STORAGE  [initandlisten] exception in initAndListen: 28595 1: Operation not permitted, terminating
2016-12-28T17:50:14.591+0100 I NETWORK  [initandlisten] shutdown: going to close listening sockets...
2016-12-28T17:50:14.591+0100 I NETWORK  [initandlisten] removing socket file: /tmp/mongodb-27017.sock
2016-12-28T17:50:14.591+0100 I NETWORK  [initandlisten] shutdown: going to flush diaglog...
2016-12-28T17:50:14.591+0100 I CONTROL  [initandlisten] now exiting
2016-12-28T17:50:14.591+0100 I CONTROL  [initandlisten] shutting down with code:100

I have removed all packages and reinstalled all of the mongodb services with no luck.

Upvotes: 4

Views: 15800

Answers (3)

Aiman Farhan
Aiman Farhan

Reputation: 216

I faced hours of searching for answers.

I was attempting to run a snapshot on Docker. In my case, after running also the commands to switch the owner to mongodb, what worked was the following command

mongod --repair

Upvotes: 0

Youn Elan
Youn Elan

Reputation: 2452

Assuming permissions are correct. It could be an selinux issue, try:

setenforce 0

then try to start the server. If the server starts, you will have to use semanage to set the proper context to the mongo data folder

Upvotes: 1

Shreya Batra
Shreya Batra

Reputation: 800

Did you try this?

sudo chown -R ⁠⁠⁠⁠id -u⁠⁠⁠⁠ /data/db

Upvotes: 2

Related Questions