[SERVER-42208] Permission Denied Error, cannot start DB Created: 12/Jul/19 Updated: 01/Oct/19 Resolved: 01/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Minor - P4 |
| Reporter: | Tobias Eichinger | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Machine: NVIDIA DGX-1 |
||
| Participants: |
| Description |
|
Dear MongoDB community,
I have the following error messages after running my usual startup command:
numactl --interleave=all mongod ############################### 2019-07-12T17:15:42.293+0200 I CONTROL [initandlisten] MongoDB starting : pid=12762 port=27017 dbpath=/data/db 64-bit host=dgx-server
Since this is a Permission Denied error, I tried sudoing sudo numactl --interleave=all mongod #############################################
2019-07-12T17:23:23.845+0200 I CONTROL [initandlisten] MongoDB starting : pid=12772 port=27017 dbpath=/data/db 64-bit host=dgx-server
I am sorry but I have no clue what causes this issue since it has been starting up perfectly fine in the past. Perhaps there was a crash on the server that I am co-working with others. Do you know what I can do to resolve this? Kind regards
|
| Comments |
| Comment by Danny Hatcher (Inactive) [ 04/Sep/19 ] | ||
|
Have you had a chance to follow my instructions? | ||
| Comment by Danny Hatcher (Inactive) [ 06/Aug/19 ] | ||
|
In general, I recommend using our official documentation located at docs.mongodb.com but the site you linked does appear to be accurate for the download step. The error you see is related to dpkg not liking that another version exists. You should be able to run
then try to run the install again. The admin command you mentioned uses the mongo shell that comes with the binaries you download. After downloading the package, use the mongo command. Then enter the following into the new prompt:
| ||
| Comment by Tobias Eichinger [ 06/Aug/19 ] | ||
|
Hey, sorry for the late response, summer break... I tried installing (additionally to the 3.6.3 binaries) the 4.0.1 binaries for testing. I followed the instructions in https://tecadmin.net/install-mongodb-on-ubuntu/ until I reached another dead end. When I try to install the binaries via sudo apt install mongodb-org=4.0.1 mongodb-org-server=4.0.1 mongodb-org-shell=4.0.1 mongodb-org-mongos=4.0.1 mongodb-org-tools=4.0.1
It seems as if it finds the download locations, downloads them, yet cannot process the archives via dpkg... It also seems that upgrading my verison 3.6.3 to 4.0.1 is an option, yet I cannot follow the instructions in your docs.. I do not understand where to enter for example:
It does not seem to be my bash shell. Perhaps I can also add it to the config file? [I wanted to follow the instructions here:https://docs.mongodb.com/manual/release-notes/4.0-upgrade-standalone/ ] Sorry again for my ignorance on the matter.
| ||
| Comment by Danny Hatcher (Inactive) [ 30/Jul/19 ] | ||
|
Have you had a chance to try the 4.0 binaries? | ||
| Comment by Danny Hatcher (Inactive) [ 19/Jul/19 ] | ||
|
I'm not sure what happened but the only situation this error should occur is when a database has Feature Compatibility Version 4.0 and that can only happen if the node was started as 4.0.x at one point. Regardless of how it occurred, could you please try install 4.0.10 binaries and start the node with them? That will at least confirm the problem. | ||
| Comment by Tobias Eichinger [ 16/Jul/19 ] | ||
|
I started another method, since I was not sure whether to use numactl or sysctl. since I am using a NUMA machine I went back to numactl, yet I did not find any mongod version 4.x, the version that I have installed (/usr/bin/mongod) is version 3.6.3... I do not grasp this problem, where could the version 4.x binary be? I have not installed another version. I have asked my colleagues, they did not touch it either. /usr/bin/mongod --version :: db version v3.6.3 | ||
| Comment by Danny Hatcher (Inactive) [ 15/Jul/19 ] | ||
|
You need to set the parameter on a currently running version of the database. In the first example you provided you were starting mongod with numactl but the most recent example you are using systemctl. Which do you use to normally start the server? You should use the same command you normally do but with the 4.0.10 binaries instead of 3.6.3. | ||
| Comment by Tobias Eichinger [ 15/Jul/19 ] | ||
|
Thank you Mr. Hatcher for your timely reply. I did the following
I am puzzled what the help page for the compatibility version tells me. I tried having a look at the config option, but I did not find anything there. Could you please provide a line of code that starts the 4.0 binaries with feature compatibility version 4.0? I am sure that there is a command line option, but I did not find anything on the docu page.. mongod --setParameter featureCompatibilityVersion=4.0 [did not work]
| ||
| Comment by Danny Hatcher (Inactive) [ 12/Jul/19 ] | ||
|
There are two different errors here; a permission denied error and an indication that you are using a different version of MongoDB than the data expects.
The above error will only appear if the server was once started with 4.0 binaries and has the feature compatibility version set to 4.0. If you start up the server using 4.0 binaries, you should be able to change the feature compatibility version to 3.6, cleanly shutdown, then successfully start up as a 3.6 server. Could you please do the above and see if it resolves both issues or at least the second? |