# Errors: Database is unavailable and unable to reach coordination servers on Mac **URL:** \ **Category:** Using FoundationDB\ **Created:** [May 16, 2023, 6:22am UTC](https://forums.foundationdb.org/t/errors-database-is-unavailable-and-unable-to-reach-coordination-servers-on-mac/3967 "2023-05-16T06:22:43Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![joannak-vmware](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@joannak-vmware](https://forums.foundationdb.org/u/joannak-vmware)\ **Post date:** [May 16, 2023, 6:22am UTC](https://forums.foundationdb.org/t/errors-database-is-unavailable-and-unable-to-reach-coordination-servers-on-mac/3967/1 "2023-05-16T06:22:43Z")
I am encountering the following errors in fdbcli after updating my fdb version to 7.1.28 with pkg, [https://github.com/apple/foundationdb/releases/download/7.1.28/FoundationDB-7.1.28\_x86\_64.pkg](https://github.com/apple/foundationdb/releases/download/7.1.28/FoundationDB-7.1.28_x86_64.pkg). > fdbcli > Using cluster file `/usr/local/etc/foundationdb/fdb.cluster’. The database is unavailable; type `status’ for more information. Welcome to the fdbcli. For help, type `help’. fdb\> status Using cluster file `/usr/local/etc/foundationdb/fdb.cluster’. Could not communicate with a quorum of coordination servers: 127.0.0.1:4689 (unreachable) I have tried completely uninstalling and reinstalling with different pkg versions, and also running the following; fdb\> configure ssd single WARNING: Long delay (Ctrl-C to interrupt) The database is unavailable; type `status’ for more information. ERROR: The database is unavailable Type `configure FORCE \’ to configure without this check ---
**Author:** ![jzhou](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/jzhou/32/445_2.png) [@jzhou](https://forums.foundationdb.org/u/jzhou)\ **Post date:** [May 18, 2023, 9:17pm UTC](https://forums.foundationdb.org/t/errors-database-is-unavailable-and-unable-to-reach-coordination-servers-on-mac/3967/2 "2023-05-18T21:17:46Z")
is this an empty database? If so, try the command: `configure new single ssd` to create one. ---
**Author:** ![joannak-vmware](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@joannak-vmware](https://forums.foundationdb.org/u/joannak-vmware)\ **Post date:** [May 18, 2023, 10:12pm UTC](https://forums.foundationdb.org/t/errors-database-is-unavailable-and-unable-to-reach-coordination-servers-on-mac/3967/3 "2023-05-18T22:12:33Z")
> [@jzhou](#): > > `configure new single ssd` Yes, since I completely uninstalled and reinstalled database, this should be empty. Running `configure new single ssd ` remains stuck at the following: fdb\> configure new single ssd WARNING: Long delay (Ctrl-C to interrupt) The database is unavailable; type `status’ for more information. ---
**Author:** ![jzhou](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/jzhou/32/445_2.png) [@jzhou](https://forums.foundationdb.org/u/jzhou)\ **Post date:** [May 18, 2023, 10:19pm UTC](https://forums.foundationdb.org/t/errors-database-is-unavailable-and-unable-to-reach-coordination-servers-on-mac/3967/4 "2023-05-18T22:19:58Z")
> [@joannak-vmware](#): > > 127.0.0.1:4689 do you have a `fdbserver` process listening on this port? ---
**Author:** ![joannak-vmware](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@joannak-vmware](https://forums.foundationdb.org/u/joannak-vmware)\ **Post date:** [May 18, 2023, 10:23pm UTC](https://forums.foundationdb.org/t/errors-database-is-unavailable-and-unable-to-reach-coordination-servers-on-mac/3967/5 "2023-05-18T22:23:04Z")
I don’t see any `fdbserver` processes running on this port, `lsof -i :4689` returns no processes ---
**Author:** ![jzhou](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/jzhou/32/445_2.png) [@jzhou](https://forums.foundationdb.org/u/jzhou)\ **Post date:** [May 18, 2023, 10:42pm UTC](https://forums.foundationdb.org/t/errors-database-is-unavailable-and-unable-to-reach-coordination-servers-on-mac/3967/6 "2023-05-18T22:42:02Z")
that’s the problem. you need to run one with that port. ---
**Author:** ![joannak-vmware](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@joannak-vmware](https://forums.foundationdb.org/u/joannak-vmware)\ **Post date:** [May 18, 2023, 11:32pm UTC](https://forums.foundationdb.org/t/errors-database-is-unavailable-and-unable-to-reach-coordination-servers-on-mac/3967/7 "2023-05-18T23:32:21Z")
I tried setting the port with the following (per [documentation](https://apple.github.io/foundationdb/configuration.html#changing-coordination-servers)), but fdbcli still remains stuck – fdb\> coordinators 127.0.0.1:4689 WARNING: Long delay (Ctrl-C to interrupt) The database is unavailable; type `status’ for more information. ---
**Author:** ![joannak-vmware](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@joannak-vmware](https://forums.foundationdb.org/u/joannak-vmware)\ **Post date:** [May 19, 2023, 7:42pm UTC](https://forums.foundationdb.org/t/errors-database-is-unavailable-and-unable-to-reach-coordination-servers-on-mac/3967/8 "2023-05-19T19:42:46Z")
Also verified `/etc/foundationdb/foundationdb.conf` contains: `#An individual fdbserver process with id 4689` `##Parameters set here override defaults from the [fdbserver] section` `[fdbserver.4689]`