If you’ve installed the package, then it should both install and start
fdbserver for you, unless you subsequently disabled it.
Can you grep your running processes for anything with
fdb in it? The main thing we’d be looking for is
fdbmonitor, which is the process that manages
fdbserver and other processes. You could also look to see if there exists a running
backup_agent process, which would normally be there by default.
If you don’t see
fdbmonitor running at all, then we should try to fix that. You could verify that it exists on your system (I believe it should be located at
/usr/local/libexec/fdbmonitor) and that it is configured to run in macOS.
If you see two instances of
fdbmonitor running, then that would be an indication that
fdbserver is failing to start properly (
fdbserver by forking and execing, and errors can result in delays before the exec). Unfortunately on macOS we have an issue where the output from
fdbmonitor doesn’t go anywhere, so if this is happening we won’t have a log for why. However, if this ends up being the problem we can manually set it up to get the logs.
One other thing you could do if you discover that you do have a running
fdbserver process is to look in the
fdbcli output for a warning message that the version of your
fdbcli is incompatible with the cluster. Alternatively, you could run
fdbcli -v and
/path/to/running/fdbserver -v and confirm that the major and minor version numbers match (e.g. both are 6.2.x).