| Summary: | dev-db/mongodb-4.2.6 seems to ignore configuration file content | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Ralph Seichter <gentoo> |
| Component: | Current packages | Assignee: | Ultrabug <ultrabug> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | sam |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | /etc/mongodb.conf | ||
Created attachment 645184 [details]
/etc/mongodb.conf
Thanks for this. I have a horrible feeling it's bug 706252 which has come bug to bite us. *** This bug has been marked as a duplicate of bug 706252 *** |
MongoDB no longer starts after updating to ebuild version 4.2.6, neither via the OpenRC init script nor manually: root@wedjat # sudo -u mongodb -- /usr/bin/mongod --config /etc/mongodb.conf CONTROL [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none' ASIO [main] No TransportLayer configured during NetworkInterface startup CONTROL [initandlisten] MongoDB starting : pid=5754 port=27017 dbpath=/data/db 64-bit host=wedjat CONTROL [initandlisten] db version v4.2.6 CONTROL [initandlisten] git version: 20364840b8f1af16917e4c23c1b5f5efd8b352f8 CONTROL [initandlisten] OpenSSL version: OpenSSL 1.1.1g 21 Apr 2020 CONTROL [initandlisten] allocator: tcmalloc CONTROL [initandlisten] modules: none CONTROL [initandlisten] build environment: CONTROL [initandlisten] distarch: x86_64 CONTROL [initandlisten] target_arch: x86_64 CONTROL [initandlisten] options: { config: "/etc/mongodb.conf" } STORAGE [initandlisten] exception in initAndListen: NonExistentPath: Data directory /data/db not found., terminating NETWORK [initandlisten] shutdown: going to close listening sockets... - [initandlisten] Stopping further Flow Control ticket acquisitions. CONTROL [initandlisten] now exiting CONTROL [initandlisten] shutting down with code:100 The odd part is that options: { config: "/etc/mongodb.conf" } indicates that mongod is aware of a config file (world-readable in my case) is being passed, but that the contents like "dbPath" et al are apparently ignored.