Hallo,
ich habe/hatte MongoDB installiert (inkl. angelegten Usern)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 | db version v3.4.20 less /etc/mongod.conf storage: dbPath: /var/lib/mongodb journal: enabled: true systemLog: destination: file logAppend: true path: /var/log/mongodb/mongod.log net: port: 27717 bindIp: 127.0.0.1 tail -20 /var/log/mongodb/mongod.log 2019-05-19T09:39:27.760-0400 I CONTROL [initandlisten] target_arch: x86_64 2019-05-19T09:39:27.760-0400 I CONTROL [initandlisten] options: { config: "/etc/mongod.conf", net: { bindIp: "127.0.0.1", port: 27717 }, storage: { dbPath: "/var/lib/mongodb", journal: { enabled: true } }, systemLog: { destination: "file", logAppend: true, path: "/var/log/mongodb/mongod.log" } } 2019-05-19T09:39:27.786-0400 I - [initandlisten] Detected data files in /var/lib/mongodb created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'. 2019-05-19T09:39:27.786-0400 I STORAGE [initandlisten] 2019-05-19T09:39:27.786-0400 I STORAGE [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine 2019-05-19T09:39:27.786-0400 I STORAGE [initandlisten] ** See http://dochub.mongodb.org/core/prodnotes-filesystem 2019-05-19T09:39:27.786-0400 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=1536M,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),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),verbose=(recovery_progress), 2019-05-19T09:39:28.002-0400 I STORAGE [initandlisten] WiredTiger message [1558273168:2842][1412:0x7ff243b8dd40], txn-recover: Main recovery loop: starting at 57/5888 2019-05-19T09:39:28.139-0400 I STORAGE [initandlisten] WiredTiger message [1558273168:139724][1412:0x7ff243b8dd40], txn-recover: Recovering log 57 through 58 2019-05-19T09:39:28.239-0400 I STORAGE [initandlisten] WiredTiger message [1558273168:239854][1412:0x7ff243b8dd40], txn-recover: Recovering log 58 through 58 2019-05-19T09:39:28.328-0400 I CONTROL [initandlisten] 2019-05-19T09:39:28.328-0400 I CONTROL [initandlisten] ** WARNING: Access control is not enabled for the database. 2019-05-19T09:39:28.328-0400 I CONTROL [initandlisten] ** Read and write access to data and configuration is unrestricted. 2019-05-19T09:39:28.328-0400 I CONTROL [initandlisten] 2019-05-19T09:39:28.328-0400 I CONTROL [initandlisten] 2019-05-19T09:39:28.328-0400 I CONTROL [initandlisten] ** WARNING: You are running in OpenVZ which can cause issues on versions of RHEL older than RHEL6. 2019-05-19T09:39:28.329-0400 I CONTROL [initandlisten] 2019-05-19T09:39:28.333-0400 W FTDC [initandlisten] Error checking directory '/sys/block': No such file or directory 2019-05-19T09:39:28.333-0400 I FTDC [initandlisten] Initializing full-time diagnostic data capture with directory '/var/lib/mongodb/diagnostic.data' 2019-05-19T09:39:28.334-0400 I NETWORK [thread1] waiting for connections on port 27717 mongo -u mngadmin -p pw --authenticationDatabase admin MongoDB shell version v3.4.20 connecting to: mongodb://127.0.0.1:27017 2019-05-19T09:58:27.260-0400 W NETWORK [thread1] Failed to connect to 127.0.0.1:27017, in(checking socket for error after poll), reason: Connection refused 2019-05-19T09:58:27.261-0400 E QUERY [thread1] Error: couldn't connect to server 127.0.0.1:27017, connection attempt failed : connect@src/mongo/shell/mongo.js:240:13 @(connect):1:6 exception: connect failed ls -lah /var/lib/mongodb/mongod.lock -rw-r--r-- 1 mongodb mongodb 5 May 19 09:39 mongod.lock |
Die WiredTiger Warnung war schon da, als noch alles funktioniert. Wenn ich mich jetzt verbinde, sehe ich nichts weiter in der log Datei. Ich habe per strg + r gesehen, dass ich den connection string verwendet habe und soweit ich mich erinnern kann, klappte das auch bis vor ca. 1 Monat problemlos.
Woran könnte es denn liegen, dass es nicht funktioniert?