You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
if there is a peer in replication.toml with the incorrect key, then we will see a set of log messages like this:
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
The text was updated successfully, but these errors were encountered: