Hayley Campbell

@shaan1337 I'm going to close this given @ylorph's comment above, but let me know if it's still something that needs to be added

Fixed by https://github.com/EventStore/EventStore/pull/2069

We've added a new option, `--allow-unknown-options` which should resolve this. Enabling this option will cause EventStoreDB to simply log out any unrecognised options rather than stopping the server. Check https://github.com/EventStore/EventStore/pull/3652...

Could you try deleting the `epoch.chk` file in your data directory and restarting the node? This should cause Event Store to recreate the checkpoint and catch up to the current...

Thank you for reporting this @mmuller99, those images were pushed by accident instead of bionic and buster-slim The correct images for 21.10.10 should be available on Dockerhub now

Hi @knowitall12, does your certificate file contain empty lines? The error looks similar to the one reported here: https://github.com/EventStore/EventStore/issues/3312

Hi @Keethanjan , could you confirm that the cluster has started correctly? You can do this by ensuring that there is 1 Leader and 2 Followers in the cluster either...

Hi @Zyklop, could you please check the logs for the node that is being shut down for the line: > Leader [{leaderEndPoint},{leaderId:B}] subscribed us at {subscriptionPosition} (0x{subscriptionPosition:X}), which is less...

While I don't think offline truncation should be an error code, having a different exit code for offline truncation vs user shutdown would be helpful We have an issue about...

Part of this should have been fixed by https://github.com/EventStore/EventStore/pull/3584 and https://github.com/EventStore/EventStore/pull/3609. However, there could still be a problem getting 401s while catching up if the $users stream is updated on...