não funciona mongodb no ubuntu 16.04

-1

sudo service mongodb status no terminal:

mongodb.service - High-performance, schema-free document-oriented database
   Loaded: loaded (/etc/systemd/system/mongodb.service; enabled; vendor preset: 
   Active: failed (Result: exit-code) since جمعه 2017-08-25 14:47:16 IRDT; 6s ag
  Process: 17268 ExecStart=/usr/bin/mongod --quiet --config /etc/mongod.conf (co
 Main PID: 17268 (code=exited, status=100)

O mongod não inicia e mostra o código:

mongod --help for help and startup options
2017-08-25T14:50:31.406+0430 [initandlisten] MongoDB starting : pid=17322 port=27017 dbpath=/data/db 64-bit host=mahdi-RC512
2017-08-25T14:50:31.406+0430 [initandlisten] db version v2.6.10
2017-08-25T14:50:31.406+0430 [initandlisten] git version: nogitversion
2017-08-25T14:50:31.406+0430 [initandlisten] OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016
2017-08-25T14:50:31.406+0430 [initandlisten] build info: Linux lgw01-12 3.19.0-25-generic #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 BOOST_LIB_VERSION=1_58
2017-08-25T14:50:31.406+0430 [initandlisten] allocator: tcmalloc
2017-08-25T14:50:31.406+0430 [initandlisten] options: {}
2017-08-25T14:50:31.448+0430 [initandlisten] journal dir=/data/db/journal
2017-08-25T14:50:31.448+0430 [initandlisten] recover : no journal files present, no recovery needed
2017-08-25T14:50:31.448+0430 [initandlisten] 
2017-08-25T14:50:31.448+0430 [initandlisten] ERROR: Insufficient free space for journal files
2017-08-25T14:50:31.448+0430 [initandlisten] Please make at least 3379MB available in /data/db/journal or use --smallfiles
2017-08-25T14:50:31.448+0430 [initandlisten] 
2017-08-25T14:50:31.448+0430 [initandlisten] exception in initAndListen: 15926 Insufficient free space for journals, terminating
2017-08-25T14:50:31.448+0430 [initandlisten] dbexit: 
2017-08-25T14:50:31.448+0430 [initandlisten] shutdown: going to close listening sockets...
2017-08-25T14:50:31.448+0430 [initandlisten] shutdown: going to flush diaglog...
2017-08-25T14:50:31.448+0430 [initandlisten] shutdown: going to close sockets...
2017-08-25T14:50:31.448+0430 [initandlisten] shutdown: waiting for fs preallocator...
2017-08-25T14:50:31.448+0430 [initandlisten] shutdown: lock for final commit...
2017-08-25T14:50:31.448+0430 [initandlisten] shutdown: final commit...
2017-08-25T14:50:31.448+0430 [initandlisten] shutdown: closing all files...
2017-08-25T14:50:31.448+0430 [initandlisten] closeAllFiles() finished
2017-08-25T14:50:31.448+0430 [initandlisten] journalCleanup...
2017-08-25T14:50:31.448+0430 [initandlisten] removeJournalFiles
2017-08-25T14:50:31.470+0430 [initandlisten] shutdown: removing fs lock...
2017-08-25T14:50:31.470+0430 [initandlisten] dbexit: really exiting now
    
por Mahdi Bagheri 25.08.2017 / 12:22

1 resposta

3

Os estados de erro

journal dir=/data/db/journal
recover : no journal files present, no recovery needed
Insufficient free space for journal files.
Please make at least 3379MB available in /data/db/journal....

Eu assumo que você não tem espaço suficiente no disco, assim o daemon não pode criar os logs necessários, então ele para. Como a mensagem afirma, você precisa de 3379MB em /data/db/journal .

    
por mazs 25.08.2017 / 12:28