New answers tagged

0

It turns out this was caused by a version mismatch between the mongodump executable and the mongod server. (I was running mongod within a docker container, and I was trying to do backups from the host outside the container which had a different version of the tools installed.) When I switched to the mongodump version that shipped with the server version, it ...


-1

TL;DR: I recently troubleshoot a node server that was trying to resolve names on IPv6 before falling back to IPv4, and this was the solution to my problem (YMMV): Try the following: Open Terminal Edit /etc/sysctl.conf and open the configuration file and add the following lines at the end net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default....


0

You set Type=forking but mongos is not configured to fork. You should reset this to its default, Type=simple. Alternatively you can add --fork to the mongos command line, but you will also need to specify --pidfile. The PID file is not required with Type=simple. Since you're using systemd it's best to just not fork and let systemd handle managing the process....


Top 50 recent answers are included