Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unclear Error Message When There Is An Incorrect Peer In replication.toml #102

Open
mhfowler opened this issue Dec 9, 2024 · 0 comments

Comments

@mhfowler
Copy link
Collaborator

mhfowler commented Dec 9, 2024

if there is a peer in replication.toml with the incorrect key, then we will see a set of log messages like this:

[2024-12-10T01:36:54Z DEBUG solar::actors::network::connection_scheduler] <DialRequest @5Pt3dKy2HTJ0mWuS78oIiklIX0gBz6BTfEnXsbvke9c=.ed25519 / 127.0.0.1:8008>
[2024-12-10T01:36:54Z DEBUG solar::actors::network::connection_manager] Attempting secret handshake as client...
[2024-12-10T01:36:54Z ERROR solar::actors::network::connection_manager] Error while handling 'handshaking' event: Secret handshake error: i/o: unexpected end of file

in this case the peer being dialed at this address did not actually have that public key, and this error message results.

not the worst error message, as it kind of makes sense, but also leaving this issue here to document what to expect if replication.toml is misconfigured

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant