Closed cvl closed 2 years ago
From what I see in logs, connection state changed from Connected to OnHold multiple times due to the reasons below:
2021-12-09T06:23:38.000 ERR app/core/connection/manager.go:927 > Max p2p keepalive err count reached, disconnecting. SessionID=88272deb-c023-4ac6-b870-9c39e3030663
2021-12-09T06:23:38.000 INF app/core/connection/manager.go:706 > Connection state: Connected -> OnHold
2021-12-09T09:50:57.000 WRN app/session/pingpong/invoice_payer.go:194 > Provider trying to overcharge
2021-12-09T09:50:57.000 ERR app/core/connection/manager.go:482 > Payment error error="invoice not valid: provider is overcharging"
2021-12-09T09:50:57.000 INF app/core/connection/manager.go:706 > Connection state: Connected -> OnHold
After failing to maintain a p2p keepalive pings, connection is placed on hold and then it fails to reconnect active sessions which lead to disconnect:
2021-12-09T09:53:00.000 ERR app/core/connection/manager.go:889 > Failed to reconnect active session, will try again error="could not create p2p channel during connect: p2p dialer failed: timeout while performing configuration exchange"
Several providers in charge: 0xe1e42a2f258fe8961261d85327343a216089543b - holepunching 0x249592fd5cc6bfe40391d3215f14bc8f5b2f4217 - manual
Both providers are accessible and have a decent amount of connections.
Describe the bug Node goes to OnHold state constantly. Logs: mysterium-node.log
Environment (please complete the following information):