opsmgr adddb/mongod startup connection refused

[vap0rtranz]

New deploy from simple-test-opsmgr succeeds, one Pod is started & up with 2 containers running (appdb/mongod and opsmgr/mms container hosts) but Pod logs show error on localhost for MongoDB port.

Test via curl on local container host running appdb/mongod confirms port rejection:

oc exec mongodb-opsmgr-6976d9b55d-jqv6f --container mongodb-opsmgr-appdb curl localhost:12831
curl: (7) Failed to connect to localhost port 12831: Connection refused

Pod logs repeat following:

2018-06-21 19:54:39,900 CRIT Supervisor running as root (no user in config file)
2018-06-21 19:54:39,905 INFO supervisord started with pid 1
2018-06-21 19:54:40,907 INFO spawned: 'mongodb-opsmgr-appdb' with pid 8
MongoDB shell version v3.7.9
connecting to: mongodb://127.0.0.1:12831/admin
2018-06-21T19:54:41.134+0000 E QUERY    [js] Error: couldn't connect to server 127.0.0.1:12831, connection attempt failed: SocketException: Connection refused :
connect@src/mongo/shell/mongo.js:251:13
@(connect):1:6
2018-06-21 19:54:42,150 INFO success: mongodb-opsmgr-appdb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-06-21T19:54:43.192+0000 I CONTROL  [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'
about to fork child process, waiting until server is ready for connections.
forked process: 18
ERROR: child process failed, exited with error number 1
To see additional information in this output, start without the "--fork" option.
2018-06-21 19:54:43,213 INFO exited: mongodb-opsmgr-appdb (exit status 1; not expected)

[jasonmimick]

Could you post the content of /mongodb-opsmgr-server/runtime/startup-mongod.log? Not sure what's going on since --fork is explicitly set in the startup script.