Problem with upgrade to 6.2.15 from 6.1.x version

As the title suggests, after installing the 6.2.15.pkg, fdbcli is now complaining

Could not communicate with a quorum of coordination servers: (unreachable)
I noticed that on activity monitor that I do not see fdbserver running, only 2 fdbmonitor processes. I have tried restarting the fdbserver with launchctl multiple times, but to no avail. I’ve also checked with lsof to see if 4689 is occupied, and don’t find any entry.

What else could be the issue?

Oh, well, apparently fdbmonitor isn’t piped or saved anywhere, which makes this a little more troublesome.

In /usr/local/foundationdb/logs/ there are log files. Does the most recent one happen to have any Severity="40" lines in it?

Assuming you haven’t changed anything, fdbmonitor should be equivalent to manually running:
sudo /usr/local/libexec/fdbserver --public_address=auto:4689 --listen_address=public --datadir=/usr/local/foundationdb/data/4689 --logdir=/usr/local/foundationdb/logs

Could you try doing that locally to see what the error is?

Did a cat trace.* | grep "Severity=\"40" and did not get anything.

sudo /usr/local/libexec/fdbserver --public_address=auto:4689 --listen_address=public --datadir=/usr/local/foundationdb/data/4689 --logdir=/usr/local/foundationdb/logs
starts the server normally. No error. Cluster quickly becomes healthy after a quick reinitialization.

I guess something is borked with start up?

sudo launchctl load /Library/LaunchDaemons/com.foundationdb.fdbmonitor.plist is what i used to start the service following

So turns out, launchctl is not happy when there are foundationsdb.conf and foundationsdb.conf.bak in /usr/local/etc/foundationdb directory. After removing one of them and restarts fdb, the server is now launched successfully. In activity monitor, there is now one fdbmonitor and one fdbserver process as opposed to two fdbmonitor processes before. This seems like a bug to me, but nevertheless, the issue is resolved now.