Не могу запустить MongoDB на Ubuntu 16. Как быть?

Question

[vk22]

Друзья, помогите!
Никак не могу запустить MongoDB на Ubuntu 16. Все утро бьюсь((( Пробовал разные версии монги. В итоге сейчас стоит так:

mongo -version
MongoDB shell version v4.0.5
git version: 3739429dd92b92d1b0ab120911a23d50bf03c412
OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016
allocator: tcmalloc
modules: none
build environment:
    distmod: ubuntu1604
    distarch: x86_64
    target_arch: x86_64

/etc/systemd/system/mongodb.service

[Unit]
Description=High-performance, schema-free document-oriented database
After=network.target

[Service]
User=mongodb
ExecStart=/usr/bin/mongod --quiet --config /etc/mongod.conf

[Install]
WantedBy=multi-user.target

но sudo service mongod status
выдает:

mongod.service - MongoDB Database Server
   Loaded: loaded (/lib/systemd/system/mongod.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2019-01-22 11:43:31 UTC; 12min ago
     Docs: https://docs.mongodb.org/manual
  Process: 24207 ExecStart=/usr/bin/mongod --config /etc/mongod.conf (code=exited, status=1/FAILURE)
 Main PID: 24207 (code=exited, status=1/FAILURE)

Jan 22 11:43:31 mahumach systemd[1]: Started MongoDB Database Server.
Jan 22 11:43:31 mahumach systemd[1]: mongod.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:43:31 mahumach systemd[1]: mongod.service: Unit entered failed state.
Jan 22 11:43:31 mahumach systemd[1]: mongod.service: Failed with result 'exit-code'.

Подскажите что делать! Заранее спасибо!

Comments

[Hanneman]

Конфигурационный файл MongoDB никому не показывайте.

[vk22]

Hanneman, а вот и покажу:

# mongod.conf

# for documentation of all options, see:
#   http://docs.mongodb.org/manual/reference/configuration-options/

# Where and how to store data.
storage:
  dbPath: /var/lib/mongodb
  journal:
    enabled: true
#  engine:
#  mmapv1:
#  wiredTiger:

# where to write logging data.
systemLog:
  destination: file
  logAppend: true
  path: /var/log/mongodb/mongod.log

# network interfaces
net:
  port: 27017
  bindIp: 127.0.0.1


#processManagement:

#security:

#operationProfiling:

#replication:

#sharding:

## Enterprise-Only Options:

#auditLog:

#snmp:

Но тут вроде все стандартно. Блин где-то я запутался. Устаналивал по разным туториалам((

[vk22]

В логи ничего не пишется /var/log/mongodb/mongod.log

[Hanneman]

vk22, а путь /var/lib/mongodb вообще существует?

[vk22]

Hanneman, да. В общем у менять так получилось запустить:
sudo /usr/bin/mongod --config /etc/mongod.conf
далее получилось запустить mongo и вроде заработало. Странно, почему так?

[Hanneman]

Я подозреваю, что вас просто тупо права не выставлены на директории. Т.е. User=mongodb, от имени которого у вас запускается MongoDB (как указано в /etc/systemd/system/mongodb.service), банально не имеет прав на эти директории.

В документации указано:

If you installed via the package manager, the data directory /var/lib/mongodb and the log directory /var/log/mongodb are created during the installation.

By default, MongoDB runs using the mongodb user account. If you change the user that runs the MongoDB process, you must also modify the permission to the data and log directories to give this user access to these directories.

Даже если вы не меняли пользователя, все же проверьте права сначала и запустите команды, приведенные ниже.

chown -R mongodb:mongodb /var/lib/mongodb
chown -R mongodb:mongodb /var/log/mongodb
chown mongodb:mongodb /tmp/mongodb-27017.sock

[vk22]

Hanneman, не помогает(( После смены прав. и даже после еще одной переустановки:

sudo apt purge mongodb-org mongodb-org-mongos mongodb-org-server mongodb-org-shell mongodb-org-tools
sudo rm -rfv /etc/mongod.conf /var/log/mongodb /var/lib/mongodb
sudo apt install mongodb-org

Затем sudo systemctl start mongod

Failed to start mongod.service: Unit mongod.service not found.

sudo mongod

2019-01-22T19:01:57.647+0000 I CONTROL  [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'
2019-01-22T19:01:57.650+0000 I CONTROL  [initandlisten] MongoDB starting : pid=31858 port=27017 dbpath=/data/db 64-bit host=mahumachinen
2019-01-22T19:01:57.650+0000 I CONTROL  [initandlisten] db version v4.0.5
2019-01-22T19:01:57.650+0000 I CONTROL  [initandlisten] git version: 3739429dd92b92d1b0ab120911a23d50bf03c412
2019-01-22T19:01:57.650+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016
2019-01-22T19:01:57.650+0000 I CONTROL  [initandlisten] allocator: tcmalloc
2019-01-22T19:01:57.650+0000 I CONTROL  [initandlisten] modules: none
2019-01-22T19:01:57.650+0000 I CONTROL  [initandlisten] build environment:
2019-01-22T19:01:57.650+0000 I CONTROL  [initandlisten]     distmod: ubuntu1604
2019-01-22T19:01:57.650+0000 I CONTROL  [initandlisten]     distarch: x86_64
2019-01-22T19:01:57.650+0000 I CONTROL  [initandlisten]     target_arch: x86_64
2019-01-22T19:01:57.650+0000 I CONTROL  [initandlisten] options: {}
2019-01-22T19:01:57.651+0000 F STORAGE  [initandlisten] An incomplete repair has been detected! This is likely because a repair operation unexpectedly failed before completing. MongoDB will not start up again without --repair.
2019-01-22T19:01:57.651+0000 F -        [initandlisten] Fatal Assertion 50922 at src/mongo/db/storage/storage_engine_init.cpp 86
2019-01-22T19:01:57.651+0000 F -        [initandlisten]

***aborting after fassert() failure

[vk22]

mongod --repair

2019-01-22T19:12:50.019+0000 I CONTROL  [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'
2019-01-22T19:12:50.021+0000 I CONTROL  [initandlisten] MongoDB starting : pid=32104 port=27017 dbpath=/data/db 64-bit host=mahumachinen
2019-01-22T19:12:50.022+0000 I CONTROL  [initandlisten] db version v4.0.5
2019-01-22T19:12:50.022+0000 I CONTROL  [initandlisten] git version: 3739429dd92b92d1b0ab120911a23d50bf03c412
2019-01-22T19:12:50.022+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016
2019-01-22T19:12:50.022+0000 I CONTROL  [initandlisten] allocator: tcmalloc
2019-01-22T19:12:50.022+0000 I CONTROL  [initandlisten] modules: none
2019-01-22T19:12:50.022+0000 I CONTROL  [initandlisten] build environment:
2019-01-22T19:12:50.022+0000 I CONTROL  [initandlisten]     distmod: ubuntu1604
2019-01-22T19:12:50.022+0000 I CONTROL  [initandlisten]     distarch: x86_64
2019-01-22T19:12:50.022+0000 I CONTROL  [initandlisten]     target_arch: x86_64
2019-01-22T19:12:50.022+0000 I CONTROL  [initandlisten] options: { repair: true }
2019-01-22T19:12:50.022+0000 I STORAGE  [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2019-01-22T19:12:50.022+0000 I STORAGE  [initandlisten]
2019-01-22T19:12:50.022+0000 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
2019-01-22T19:12:50.022+0000 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
2019-01-22T19:12:50.022+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=3468M,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-01-22T19:12:50.539+0000 E STORAGE  [initandlisten] WiredTiger error (13) [1548184370:539889][32104:0x7f7b9edd2a40], wiredtiger_open: __posix_open_file, 715: /data/db/WiredTiger.lock: handle-open: open: Permission denied Raw: [1548184370:539889][32104:0x7f7b9edd2a40], wiredtiger_open: __posix_open_file, 715: /data/db/WiredTiger.lock: handle-open: open: Permission denied
2019-01-22T19:12:50.540+0000 E STORAGE  [initandlisten] WiredTiger error (13) [1548184370:540005][32104:0x7f7b9edd2a40], wiredtiger_open: __posix_open_file, 715: /data/db/WiredTiger.lock: handle-open: open: Permission denied Raw: [1548184370:540005][32104:0x7f7b9edd2a40], wiredtiger_open: __posix_open_file, 715: /data/db/WiredTiger.lock: handle-open: open: Permission denied
2019-01-22T19:12:50.540+0000 E STORAGE  [initandlisten] WiredTiger error (13) [1548184370:540073][32104:0x7f7b9edd2a40], wiredtiger_open: __posix_open_file, 715: /data/db/WiredTiger.lock: handle-open: open: Permission denied Raw: [1548184370:540073][32104:0x7f7b9edd2a40], wiredtiger_open: __posix_open_file, 715: /data/db/WiredTiger.lock: handle-open: open: Permission denied
2019-01-22T19:12:50.540+0000 W STORAGE  [initandlisten] Failed to start up WiredTiger under any compatibility version.
2019-01-22T19:12:50.540+0000 F STORAGE  [initandlisten] Reason: 13: Permission denied
2019-01-22T19:12:50.540+0000 W STORAGE  [initandlisten] Attempting to salvage WiredTiger metadata
2019-01-22T19:12:50.540+0000 E STORAGE  [initandlisten] WiredTiger error (13) [1548184370:540161][32104:0x7f7b9edd2a40], wiredtiger_open: __posix_open_file, 715: /data/db/WiredTiger.lock: handle-open: open: Permission denied Raw: [1548184370:540161][32104:0x7f7b9edd2a40], wiredtiger_open: __posix_open_file, 715: /data/db/WiredTiger.lock: handle-open: open: Permission denied
2019-01-22T19:12:50.540+0000 F STORAGE  [initandlisten] Failed to salvage WiredTiger metadata: 13: Permission denied
2019-01-22T19:12:50.540+0000 F -        [initandlisten] Fatal Assertion 50947 at src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 653
2019-01-22T19:12:50.540+0000 F -        [initandlisten]

***aborting after fassert() failure

[vk22]

Hanneman добрый день, очень нужна помощь. Я никак не могу запустить монгу. У меня сейчас один в один ситуация как описано тут - https://stackoverflow.com/questions/45691032/mongo...
Не могу добавить монгу в сервисы((

[vk22]

Решилось! Всем спасибо))