I mean, it is a database service and 99% of the times can be, or it is used from the network. In the mongodb configuration mongodb.conf:
... #Net net.bindIp: 127.0.0.1,10.4.78.23 net.port: 27017 ... The db tries to start binding on the 10.4.78.23 ip, that is still not up because there is no hierarchy set up when mongodb starts. The default startup process in systemd is managed by the package and therefore this change is probably to be done by your side. MongoDB is a database server and therefore need to be accessible from the network. In my case, the mongodb database is used on three standalone VMs to support the monitoring of an Openstack installation. Can you please re-open? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1693122 Title: mongodb starts before network on VM and standalone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1693122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
