Hi @Joe_Swanson
As far as I understand it, the following dependencies in the unit file should be fine:
After=network-online.target
Wants=network-online.target
Obviously you’ll want to fix the startup order problem, if that’s what’s happening, but what happens if you manually start mongod with systemct start mongod? Once your machine has finished booting, the IP should be available, so that command should work fine when you run it manually. Does it?
If it doesn’t that implies that something has already bound to port 27017, which would explain why mongod is failing to bind to it.
MongoDB maintains a working systemd configuration.