The mongodb service starts with a Permission error: "/ sys / devices / system / node / node1"

Question

I had a problem with mongo on the ubuntu server exact 12.04, after apt-get install mongodb-10gen, when I try to "mongo", I got this error:

terminate called after throwing an instance of 'boost::filesystem3::filesystem_error' what(): boost::filesystem::status: Permission denied: "/sys/devices/system/node/node1" Aborted 

I tried looking at the permissions of "/ sys / devices / system / node / node1", but it doesn't seem to exist.

Anyone got an idea?

Answer 1

Have you installed OVH on the server?

I had the same problem today and it turned out to be a kernel problem (I chose "kernel approved OVH"). Installing the original Ubuntu kernel solved the problem.

Answer 2

I had the same problem on the OVH server, but I did not want to reinstall with a different kernel ...

My workaround was to create the sysfs group and add the mongodb user to this group.

Then I did a few “chgrp sysfs ...” and “chmod g + rx ...” so that the sysfs group can read the directories needed by mongodb:

• / Sys / devices / systems / node
• / Sys / dev / block /
• / Sys / device / virtual / block / MD1 / queue

Indeed, / sys / devices / system / node / node1 does not exist, but read access to / sys / devices / system / node was sufficient.

Note that the mongo client has the same restriction, so all users who need it must be added to the sysfs group.

Answer 3

I had the same problem with OVH debian and solving the problem in a surprisingly simple way: chmod 755 on / sys / devices / system / node / node1 and parent directories.

Answer 4

Here's the corresponding bug report in mongodb: https://jira.mongodb.org/browse/SERVER-10623

He notes that this has been fixed in 2.5.3

Answer 5

Same issue with OVH / kimsufi.

I installed the kernel by default, and everything works at least at the time of writing, although the system has become noticeably slower and less responsive.

You will need

• Install a new kernel
• Make bootable. I banged my head against the wall for several hours before I realized that I had not created a new boot kernel.

Back up /etc/default/grub , and then follow the instructions, for example https://askubuntu.com/questions/156700/how-to-set-default-boot-kernel-in-ubuntu-grub or https: / /askubuntu.com/questions/309874/how-to-install-linux-kernel-3-9-in-ubuntu or https://askubuntu.com/questions/100232/how-do-i-change-the-grub -boot-order