osx mavericks - MongoDB : Failed to connect to 127.0.0.1:27017, reason: errno:61 Connection refused -
My problem is similar to other inputs and suggestions on this site, but no one does help me after installing Mongodebi , Has not started because the database is not running.
Try to run the moto first and I answered:
Mac-Pro-D-User: ~ User $ Mongo Mongodi shell version: 2.6.4 Connect Do: Testing 2014-10-28 T 10: 47: 08713-0700 Warning: Failed to connect to 127.0.0.170177, Reason: errno: 61 Connection refused 2014-10-28 T10: 47: 08713-0700 Error: 127.0.0.170177 (127.0.0.1) Could not connect to server. Failed connection failure on Src / mongo / shell / mongo.js: 146 exception: connect failed Then try checking mongod and I answered:
Mac-Pro-Day-User: ~ User $ Mongode Mongode - Options for Help and Startup Options 2014-10-28 T 10: 59: 34,485-0700 [initandlisten] MongoDB Start: PID = 926 port = 27017 dbpath = / data / db host = 64-bit Mac Pro-de-Ernesto.local 2014-10-28T10: 59: 34,485-0700 [initandlisten] 2014-10-28 T 10: 59: 34485-0700 [initandlisten] ** WARNING: Soft vacancies are very low The number of files is 256, should be at least 1000 2014-10-28T10: 59: 34,485-0700 [initandlisten] database version v2.6.4 2014-10-28T10: 59: 34,485-0700 [initandlisten] Git version: 3a830be0eb92d772aa855ebb711ac91d658ee910 2014- 10-28 T10: 59: 34485-0700 [initandlisten] Build information: Darwin BS-OSX 108-4 12.5.0 Darwin Kernel Edition 12.5.0: Sun 29 September 13:33:47 PDT 2013; Root: XNU-2050.48.12 ~ 1 / x86_64 RELEASE_X86_64 BOOST_LIB_VERSION = 1_49 2014-10-28T10: 59: 34,485-0700 [initandlisten] Suppressor: System 2014-10-28T10: 59: 34,485-0700 [initandlisten] Option: {} 2014-10-28 T 10: 59: 34486-0700 [initandlisten] magazine dir = / data / db / journal 2014-10-28 T 10: 59: 34486-0700 [initandlisten] Recover: no magazine exists, no Recovery Needed 2014-10 -28T10: 59: 34500-0700 [FileAllocator] New DataFile Allocation / Data / DB / Local. N, filling with zero ... 2014-10-28 T10: 59: 34500-0700 [FileAllocator ] Directory / Data / DB / _tmp 2014-10-28T10: 59: 34,512-0700 [FileAllocato R] done datafile /data/db/local.ns, size allocation: 16MB, taken 0.011 sec 2014-10-28T10: 59: 34726-0700 [FileAllocator] New allocation datafile /data/db/local.0, of With ... 2014-10-28T10 Filling the vacuum: 59: 35,398-0700 [FileAllocator] datafile /data/db/local.0, allocated size: 64MB, took 0.671 seconds 2014 -10-28 T10: 59 : 35695-0700 [initandlisten] Build Index: Local Startup_log Properties: {v: 1, Key: {_id: 1}, Name: "_id_" ns "local.startup_log"} 2014-10-28 T10: 59: 35695- 0700 [initandlisten] Index added to the empty archive 2014-10 -28 T10: 59: 35695-0700 [initandlisten] Create local command $ cmd command {Create: "startup_log" Size: 10485 760, capped: true} ntoreturn: 1 keyUpdates: 0 numyields: 0 reslen: 37 1194ms 2014-10-28T10: 59: 35,695-0700 [initandlisten] waiting for connection on port 27017 2014- 10-28T11: 00: 34516 -0700 [ClientCarson] Mem (MB) Ridge: 33 RT: 2653 2014-10-28 T 11: 00: 34516-0700 [ClientCarson] Map (see documentary): 160 2014-10-28 T 11: 00: 34516-0700 [ClientCarson] Connection: 0 Then try again to connect and spend some time, and again say the same:
2014 - 10-28T11: 05: 34589-0700 [ClientCurmuman] Mem (MB) Ris: 33 RT: 2653 2014-10-28 T 11: 05: 3458 9 0700 [ClientCarson] Map (see documentary): 160 2014-10-28 T 11: 05: 34589-0700 [Clients] Connection: 0< / Pre>and so on. If you can help, then appreciate it.
PS: Already have data / DB 777 with permissions, and I am using OSX Mavericks 10.9.5
Are you running these commands as separate tasks in the same terminal as your timestamp suggestion? (If not, I expect to see the overlap between the failures and the logs to properly diagnose.)
If so, what are you doing as follows:
- Starting a shell, attempting to connect to a non-running database (connection has been rejected)
- Start the database by looking at the 0 connections in the login
- Stop the database (Ctrl-C or
- Repeat
- Repeat
- P> Data Esse needs to run together with the shell so that you can connect it. So you should start the
mongodprocess in one terminal, leave it running, and then open a new terminal (or tab) ) And still connect to themongocommand to connect to the database, which is the second option, which will allow you to run theMongocommand in the same terminal.NOTE: You do not have a folder with 777 permissions It is not necessary and there is an important security risk.
Comments
Post a Comment