[SERVER-42252] aborting after fassert() on command mongod Created: 16/Jul/19  Updated: 30/Jul/19  Resolved: 30/Jul/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Prashant Brahmbhatt Assignee: Danny Hatcher (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 18.04


Participants:

 Description   

I was facing a series of different errors on input of command mongod so I uninstalled mongodb and have freshly installed again and facing this issue now, none of the existing solutions are working for me:

 

(base) prashant@arkhamPC:~$ sudo service mongod start && mongod
2019-07-17T00:24:10.353+0530 I CONTROL  [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'
2019-07-17T00:24:10.356+0530 I CONTROL  [initandlisten] MongoDB starting : pid=32120 port=27017 dbpath=/data/db 64-bit host=arkhamPC
2019-07-17T00:24:10.356+0530 I CONTROL  [initandlisten] db version v4.0.10
2019-07-17T00:24:10.356+0530 I CONTROL  [initandlisten] git version: c389e7f69f637f7a1ac3cc9fae843b635f20b766
2019-07-17T00:24:10.356+0530 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.1.1  11 Sep 2018
2019-07-17T00:24:10.356+0530 I CONTROL  [initandlisten] allocator: tcmalloc
2019-07-17T00:24:10.356+0530 I CONTROL  [initandlisten] modules: none
2019-07-17T00:24:10.356+0530 I CONTROL  [initandlisten] build environment:
2019-07-17T00:24:10.356+0530 I CONTROL  [initandlisten]     distmod: ubuntu1804
2019-07-17T00:24:10.356+0530 I CONTROL  [initandlisten]     distarch: x86_64
2019-07-17T00:24:10.356+0530 I CONTROL  [initandlisten]     target_arch: x86_64
2019-07-17T00:24:10.356+0530 I CONTROL  [initandlisten] options: {}
2019-07-17T00:24:10.357+0530 I STORAGE  [initandlisten] 
2019-07-17T00:24:10.357+0530 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
2019-07-17T00:24:10.357+0530 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
2019-07-17T00:24:10.357+0530 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=5429M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),
2019-07-17T00:24:11.127+0530 E STORAGE  [initandlisten] WiredTiger error (13) [1563303251:127038][32120:0x7f29de1e3a40], wiredtiger_open: __posix_open_file, 715: /data/db/WiredTiger.turtle: handle-open: open: Permission denied Raw: [1563303251:127038][32120:0x7f29de1e3a40], wiredtiger_open: __posix_open_file, 715: /data/db/WiredTiger.turtle: handle-open: open: Permission denied
2019-07-17T00:24:11.127+0530 E STORAGE  [initandlisten] WiredTiger error (13) [1563303251:127278][32120:0x7f29de1e3a40], wiredtiger_open: __posix_open_file, 715: /data/db/WiredTiger.turtle: handle-open: open: Permission denied Raw: [1563303251:127278][32120:0x7f29de1e3a40], wiredtiger_open: __posix_open_file, 715: /data/db/WiredTiger.turtle: handle-open: open: Permission denied
2019-07-17T00:24:11.127+0530 E STORAGE  [initandlisten] WiredTiger error (13) [1563303251:127464][32120:0x7f29de1e3a40], wiredtiger_open: __posix_open_file, 715: /data/db/WiredTiger.turtle: handle-open: open: Permission denied Raw: [1563303251:127464][32120:0x7f29de1e3a40], wiredtiger_open: __posix_open_file, 715: /data/db/WiredTiger.turtle: handle-open: open: Permission denied
2019-07-17T00:24:11.127+0530 W STORAGE  [initandlisten] Failed to start up WiredTiger under any compatibility version.
2019-07-17T00:24:11.127+0530 F STORAGE  [initandlisten] Reason: 13: Permission denied
2019-07-17T00:24:11.127+0530 F -        [initandlisten] Fatal Assertion 28595 at src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 704
2019-07-17T00:24:11.127+0530 F -        [initandlisten] ***aborting after fassert() failure

 



 Comments   
Comment by Danny Hatcher (Inactive) [ 30/Jul/19 ]

Closing due to lack of response.

Comment by Danny Hatcher (Inactive) [ 17/Jul/19 ]

The most likely cause of the issue is that the service user does not have appropriate file permissions on the data path of "/data/db". I recommend starting the mongod manually via the binary using the same config to see if there is an existing user account that does successfully start the server. You may also wish to try specifying a new directory that you create with full rights to see if that works.

Generated at Thu Feb 08 04:59:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.