After performing a withdraw there is currently very limited settlement tracking capabilities. From Node runner perspective - broken UX.

Cases:

• withdrawal initiated, node shuts down, settlement history has a record of pending settlement.

• node crashes during withdrawal, transaction is sent to block-chain but not recorded in DB (big stretch but maybe doing whole sync would be an option?)

i.e. array of ["x", null] would throw error, array of ["x", "b"] would be stored

On MacOS: connect to provider -> put computer to sleep.

The app says it's connected to VPN, but there's no internet connection. Need to disconnect / connect to regain internet connection.

Logs:

2020-07-15T15:30:58.455 DBG source/core/discovery/repository.go:61 > Retrieving proposals from 2 repositories 2020-07-15T15:31:08.030 DBG source/core/discovery/repository.go:61 > Retrieving proposals from 2 repositories 2020-07-15T15:31:08.934 WRN source/core/quality/mysterium_morqa.go:201 > Failed to request or parse proposals metrics error="net/http: request canceled (Client.Timeout exceeded while reading body)" 2020-07-15T15:31:09.388 ERR source/core/connection/manager.go:783 > Failed to send p2p keepalive ping. SessionID=3e4c5b97-9eb6-439d-bb6e-fb261b3e2797 error="timeout waiting for reply to "p2p-keepalive": p2p send timeout" 2020-07-15T15:31:11.004 WRN source/communication/nats/connection_wrap.go:86 > NATS: disconnected 2020-07-15T15:31:18.028 DBG source/core/discovery/repository.go:61 > Retrieving proposals from 2 repositories 2020-07-15T15:31:18.455 ERR source/core/discovery/repository.go:91 > Returning 410 unique proposals error="ErrorCollection: could not query proposals: cannot fetch proposals: Get https://testnet-api.mysterium.network/v1/proposals?service_type=wireguard: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" 2020-07-15T15:31:28.029 ERR source/core/discovery/repository.go:91 > Returning 410 unique proposals error="ErrorCollection: could not query proposals: cannot fetch proposals: Get https://testnet-api.mysterium.network/v1/proposals?service_type=wireguard: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" 2020-07-15T15:31:28.030 DBG source/core/discovery/repository.go:61 > Retrieving proposals from 2 repositories 2020-07-15T15:31:31.156 ERR source/core/quality/mysterium_morqa.go:112 > Failed to sent batch metrics request error="Post https://quality.mysterium.network/api/v1/batch: net/http: request canceled (Client.Timeout exceeded while awaiting headers)" 2020-07-15T15:31:34.394 ERR source/core/connection/manager.go:783 > Failed to send p2p keepalive ping. SessionID=3e4c5b97-9eb6-439d-bb6e-fb261b3e2797 error="timeout waiting for reply to "p2p-keepalive": p2p send timeout" 2020-07-15T15:31:38.029 ERR source/core/discovery/repository.go:91 > Returning 391 unique proposals error="ErrorCollection: could not query proposals: cannot fetch proposals: Get https://testnet-api.mysterium.network/v1/proposals?service_type=wireguard: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" 2020-07-15T15:31:38.032 DBG source/core/discovery/repository.go:61 > Retrieving proposals from 2 repositories 2020-07-15T15:31:44.130 DBG source/consumer/statistics/reporter.go:116 > Stats sent 2020-07-15T15:31:48.031 ERR source/core/discovery/repository.go:91 > Returning 369 unique proposals error="ErrorCollection: could not query proposals: cannot fetch proposals: Get https://testnet-api.mysterium.network/v1/proposals?service_type=wireguard: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" 2020-07-15T15:31:48.033 DBG source/core/discovery/repository.go:61 > Retrieving proposals from 2 repositories 2020-07-15T15:31:58.032 DBG source/core/discovery/repository.go:61 > Retrieving proposals from 2 repositories 2020-07-15T15:31:58.038 ERR source/core/discovery/repository.go:91 > Returning 369 unique proposals error="ErrorCollection: could not query proposals: cannot fetch proposals: Get https://testnet-api.mysterium.network/v1/proposals?service_type=wireguard: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" 2020-07-15T15:31:59.402 ERR source/core/connection/manager.go:783 > Failed to send p2p keepalive ping. SessionID=3e4c5b97-9eb6-439d-bb6e-fb261b3e2797 error="timeout waiting for reply to "p2p-keepalive": p2p send timeout" 2020-07-15T15:32:08.032 DBG source/core/discovery/repository.go:61 > Retrieving proposals from 2 repositories 2020-07-15T15:32:08.034 ERR source/core/discovery/repository.go:91 > Returning 369 unique proposals error="ErrorCollection: could not query proposals: cannot fetch proposals: Get https://testnet-api.mysterium.network/v1/proposals?service_type=wireguard: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" 2020-07-15T15:32:18.034 DBG source/core/discovery/repository.go:61 > Retrieving proposals from 2 repositories 2020-07-15T15:32:18.035 ERR source/core/discovery/repository.go:91 > Returning 357 unique proposals error="ErrorCollection: could not query proposals: cannot fetch proposals: Get https://testnet-api.mysterium.network/v1/proposals?service_type=wireguard: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" 2020-07-15T15:32:21.164 ERR source/core/quality/mysterium_morqa.go:112 > Failed to sent batch metrics request error="Post https://quality.mysterium.network/api/v1/batch: net/http: request canceled (Client.Timeout exceeded while awaiting headers)" 2020-07-15T15:32:24.410 ERR source/core/connection/manager.go:783 > Failed to send p2p keepalive ping. SessionID=3e4c5b97-9eb6-439d-bb6e-fb261b3e2797 error="timeout waiting for reply to "p2p-keepalive": p2p send timeout" 2020-07-15T15:32:28.032 DBG source/core/discovery/repository.go:61 > Retrieving proposals from 2 repositories 2020-07-15T15:32:28.033 ERR source/core/discovery/repository.go:91 > Returning 324 unique proposals error="ErrorCollection: could not query proposals: cannot fetch proposals: Get https://testnet-api.mysterium.network/v1/proposals?service_type=wireguard: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" 2020-07-15T15:32:38.028 DBG source/core/discovery/repository.go:61 > Retrieving proposals from 2 repositories 2020-07-15T15:32:38.039 ERR source/core/discovery/repository.go:91 > Returning 297 unique proposals error="ErrorCollection: could not query proposals: cannot fetch proposals: Get https://testnet-api.mysterium.network/v1/proposals?service_type=wireguard: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" 2020-07-15T15:32:41.356 ERR source/core/quality/mysterium_morqa.go:112 > Failed to sent batch metrics request error="Post https://quality.mysterium.network/api/v1/batch: net/http: request canceled (Client.Timeout exceeded while awaiting headers)"

I'm trying to make sure the user is notified in case connection is dropped.

Yet, in case computer enters sleep mode, it seems connection is dropped no matter what (I assume on purpose?). When entering sleep mode, connection goes through the following phases -> Connected -> Disconnecting -> Not connected. Then when entering out of sleep -> Connecting -> Connected.

• Does this reconnect to the same proposal as previously? What happens, if a) node is not longer available b) proposal is outdated (e.g. computer can be in sleep mode for weeks), would it connect to old proposal with outdated prices? Suggestion here: add some kind of hook where developer can decide what to do when app comes back from sleep.
• How can I know exactly, that we're dealing with getting out of sleep case, but not simple connection drop problem? Suggestion here: add separate connection statuses for specific use cases.

Describe the bug Node v0.66.3 0xa56879b4c1eeb6d4f5a06e421ad7b72858aa28cf running Raspbian GNU/Linux 10 (buster) seems to be partially offline.

It keeps sending proposals to the broker, so it's visible in discovery. But nothing else seems working on the provider side. It does not send metrics, it does not accept connections, even does not respond to messages via the broker.

There might be more nodes affected by this. This could cause multiple problems with connections if this happening a lot.

The monitoring agent will mark such node as test failed eventually, but it will take 24h before we do this.

About Bug: Node runners can waste Myst tokens and bandwidth of client connected. Basically node runner can setup a script to ping large amount to connected device.

How to perform: 1.If node is running in Linux/ Raspberry Pi, Run below command in terminal

Example: ping 10.182.0.2 -s 64000

Here 10.182.0.2 is the IP address of client connected to node. Most of the cases it will be 10.182.0.2 or 10.182.1.2.

By running above command the client will be charged for the bandwidth which is actually not used by client it self. The problem is that ping requests are being charged.

Bad Node Runners can use this method to increase their earnings and this will abuse network usage. I have added link to watch demo video https://youtu.be/YZ-H0gqjqfU

There is no information about our payments system at dev documentation page. We should add information about general principles of our payment system and functions in payments package. https://docs.mysterium.network/en/latest/architecture/payments/

Provider: 0x641cb8019932b0fc112eeb1c265a4e93811c9086 SessionID: 3e345f6c-538c-443d-9924-5193626d7740

In NodeUI it's still showing as active: Country: DE Duration: 17:21:18 Started: 7/20/2021, 3:08:09 PM Earnings: 0.0000000 MYSTT Transferred: 0 Bytes

Consumer: https://testnet2-grafana.mysterium.network/d/Pp9tMURGz/consumer?orgId=1&var-consumer=0x9f215ef0b681b6d587d00468d0bb3e1ee6b4a51f

On MMN it's shows as completed.

The last record about this SessionID in node logs:

2021-07-20T22:56:29.389 DBG eventbus/event_bus.go:81                 > Published topic="provider_ping_p2p" event={SessionID:3e345f6c-538c-443d-9924-5193626d7740 Duration:38.86992ms}
2021-07-20T22:56:31.145 DBG session/pingpong/price_calculator.go:51  > Calculated price 212047942991486529. Time component: 1.4050769462499500583e+15, data component: 2.106428660452365791e+17 
2021-07-20T22:56:31.645 DBG core/service/session_manager.go:330      > Received p2p keepalive ping with SessionID=3e345f6c-538c-443d-9924-5193626d7740

Logs: https://my.mysterium.network/admin/issues/download/3244

Issue #5110 was closed but is still open.

Latest updated:

All data was migrated from one node to the other, as per instructions on https://docs.mysterium.network/for-node-runners/migrating-your-node