etherunit

etherunit

Member Since 1 year ago

Experience Points
2
follower
Lessons Completed
0
follow
Best Reply Awards
2
repos

310 contributions in the last year

Pinned
Activity
Oct
22
2 days ago
Activity icon
issue

etherunit issue mysteriumnetwork/node

etherunit
etherunit

Bounty payout history show payment made but no payment received

Describe the bug as per record , i suppose to receive payout before 10th Oct but i dont see any deposit to my account. my node id 0x498a5ad56204b339cf5a38e938c62dcc75a0482b

Steps to reproduce the behavior: see screenshot for the dates and trx but the amount was not deposited.

Expected behavior The reward should get deposited.

Environment (please complete the following information): version : 0.62.1

Activity icon
issue

etherunit issue mysteriumnetwork/node

etherunit
etherunit

MetaMask wallet still 0 since day one

Describe the bug My MetaMask wallet still shows 0 ever since the first day of running the node. I have collected around 6 MYST token as of now. I followed node-runner documentation on how to setup the MetaMask wallet.

To Reproduce n/a

Expected behavior MetaMask to display the the current amount of MYST token I have

Screenshots gnome-shell-screenshot-794WB1 gnome-shell-screenshot-5A2XB1

Environment:

  • Node version: 0.67.3
  • OS: Raspbian GNU/Linux 10 (buster)

Additional context n/a

Activity icon
issue

etherunit issue comment mysteriumnetwork/node

etherunit
etherunit

MetaMask wallet still 0 since day one

Describe the bug My MetaMask wallet still shows 0 ever since the first day of running the node. I have collected around 6 MYST token as of now. I followed node-runner documentation on how to setup the MetaMask wallet.

To Reproduce n/a

Expected behavior MetaMask to display the the current amount of MYST token I have

Screenshots gnome-shell-screenshot-794WB1 gnome-shell-screenshot-5A2XB1

Environment:

  • Node version: 0.67.3
  • OS: Raspbian GNU/Linux 10 (buster)

Additional context n/a

etherunit
etherunit

Thanks for providing it. Please note that you still haven't hit the min threshold of 10 (5) MYST. At the time of payment distribution, the total amount of MYST was 4.6304 MYST. According to the stats, your could potentially get your payment during the next payout cycle. More information:https://docs.mysterium.network/token/bounty/

Activity icon
issue

etherunit issue mysteriumnetwork/node

etherunit
etherunit

Missing bounty payment

Describe the bug MMN still reports as pending the payments of August and September for 0xf281d61f1d056b42323ad72b3cd75339eb1ebf7e

2021, September | 584.9226 MYST | - / - | #76 | #4 | Payment in progress. It should reach you before 2021-10-07.
-- | -- | -- | -- | -- | --
2021, August | 502.9860 MYST | - / - | #211 | #8 | Payment in progress. It should reach you before 2021-09-07.

Min 10 MYST threshold was hit.

Screenshots Screenshot 2021-10-22 at 12 24 16

Environment (please complete the following information):

  • Node version: 0.64
  • OS: Alpine Linux v3.12(docker)
Activity icon
issue

etherunit issue comment mysteriumnetwork/node

etherunit
etherunit

Infinite Time

Describe the bug This bug makes it so that a person who connected to your node, stays there forever, he has currently been on my node for 6 hours but he isn't even connected to it, no data is being sent and there is nothing about it in the live sessions.

To Reproduce Steps to reproduce the behavior: Basically how this started was my power tripped for a split second, came back on and this started happening

Expected behavior I expected it to just go away once the user has logged off of this node, but he stayed and the session time is just building up

Screenshots

prof1

prof2

Environment (please complete the following information):

  • Node version: [0.67.3-alpine]
  • OS: [Windows 10]
  • Desktop app version (if applicable): [1.0.17]
  • Docker (if applicable): Docker Desktop 4.1.1 (69879)
etherunit
etherunit

@LPZStephan Thanks for reporting! Can you please submit your node logs so we can have a closer look? Login to your Node UI and click the "Bug" button on the left side panel.

Oct
21
3 days ago
Activity icon
issue

etherunit issue comment mysteriumnetwork/node

etherunit
etherunit

MetaMask wallet still 0 since day one

Describe the bug My MetaMask wallet still shows 0 ever since the first day of running the node. I have collected around 6 MYST token as of now. I followed node-runner documentation on how to setup the MetaMask wallet.

To Reproduce n/a

Expected behavior MetaMask to display the the current amount of MYST token I have

Screenshots gnome-shell-screenshot-794WB1 gnome-shell-screenshot-5A2XB1

Environment:

  • Node version: 0.67.3
  • OS: Raspbian GNU/Linux 10 (buster)

Additional context n/a

Activity icon
issue

etherunit issue comment mysteriumnetwork/node

etherunit
etherunit

Bounty payout history show payment made but no payment received

Describe the bug as per record , i suppose to receive payout before 10th Oct but i dont see any deposit to my account. my node id 0x498a5ad56204b339cf5a38e938c62dcc75a0482b

Steps to reproduce the behavior: see screenshot for the dates and trx but the amount was not deposited.

Expected behavior The reward should get deposited.

Environment (please complete the following information): version : 0.62.1

Activity icon
issue

etherunit issue comment mysteriumnetwork/node

etherunit
etherunit

Test token withdrawal flow in NodeUI

In MainNet node runners will be able to settle collected funds into blockchain wallet (on Polygon or Ethereum).

  • Check withdrawal widget in NodeUI dashboard present and working
Dashboard - withdrawal
  • Check token withdrawal

Withdrawal popup Group 2862348

  • Check withdrawal for both networks: Polygon and Ethereum (Default should be "L2: Polygon-Matic (smaller fees, faster transactions)", secondary option is "L1: Ethereum (bigger fees, slower transactions))
etherunit
etherunit

No chains except Goerli and fee way to high. Screenshot 2021-10-21 at 11 15 42

Activity icon
issue

etherunit issue comment mysteriumnetwork/node

etherunit
etherunit

Test fresh mainnet node installation on Ubuntu Linux

Scenario to test

  1. Add the repo: sudo add-apt-repository ppa:mysteriumnetwork/node-mainnet

  2. Update after repo change: sudo apt-get update

  3. Update the cache policy: sudo apt-cache policy myst

  4. Install Mysterium node: sudo apt install myst

  5. Open NodeUI in your browser (http://[node_ip]:4449) and finish onboarding process. You should see WireGuard service be up and running.

    For those who are running mysterium node in data centers you can use our CLI to setup the node:

    • $ myst cli
    • » identities list # this will show your identity
    • » identities unlock [your identity] # you need to unlock identity before using it
    • » identities register [your identity] # you need register your identity, must be done only once
    • » service start [your identity] wireguard # this will start wireguard service
    • » service list # if you see ID of your running service then congrats, you're mysterium node runner
  6. Download dVPN desktop or mobile app from our nightly builds (look for .apk, .exe or .dmg): https://github.com/mysteriumnetwork/nightly/releases/latest and try establishing connection to your own node.

DON'T FORGET: you have to be in separate networks (e.g. node on local WIFI and mobile phone using 4G) for successful connection.


NOTE: After finishing this scenario please post a comment above (if all was ok, please also give us know about that).

etherunit
etherunit

Added http://ppa.launchpad.net/mysteriumnetwork/node-mainnet/ubuntu focal/main to apt lists to fix it.

$ myst cli

  • » identities list # this will shiow your identity
  • » identities unlock [your identity] # you need to unlock identity before using it
  • » identities register [your identity] # you need register your identity, must be done only once
  • » service start [your identity] wireguard #0xf646c6a0804e2ef8bff9da738a6b328e5c9f0578 wireguard [ERROR] Failed to start service: server response invalid: 409 Conflict (http://127.0.0.1:4050/services). Possible error: Service already running. Step is not needed as service is being started automatically.
  • » service list # if you see ID of your running service then congrats, you're mysterium node runner
Activity icon
issue

etherunit issue comment mysteriumnetwork/node

etherunit
etherunit

Test fresh mainnet node installation on Ubuntu Linux

Scenario to test

  1. Add the repo: sudo add-apt-repository ppa:mysteriumnetwork/node-mainnet

  2. Update after repo change: sudo apt-get update

  3. Update the cache policy: sudo apt-cache policy myst

  4. Install Mysterium node: sudo apt install myst

  5. Open NodeUI in your browser (http://[node_ip]:4449) and finish onboarding process. You should see WireGuard service be up and running.

    For those who are running mysterium node in data centers you can use our CLI to setup the node:

    • $ myst cli
    • » identities list # this will show your identity
    • » identities unlock [your identity] # you need to unlock identity before using it
    • » identities register [your identity] # you need register your identity, must be done only once
    • » service start [your identity] wireguard # this will start wireguard service
    • » service list # if you see ID of your running service then congrats, you're mysterium node runner
  6. Download dVPN desktop or mobile app from our nightly builds (look for .apk, .exe or .dmg): https://github.com/mysteriumnetwork/nightly/releases/latest and try establishing connection to your own node.

DON'T FORGET: you have to be in separate networks (e.g. node on local WIFI and mobile phone using 4G) for successful connection.


NOTE: After finishing this scenario please post a comment above (if all was ok, please also give us know about that).

etherunit
etherunit
[email protected]:~# sudo add-apt-repository ppa:mysteriumnetwork/node-mainnet

Repository: 'deb http://ppa.launchpad.net/mysteriumnetwork/node-mainnet/ubuntu/ groovy main'
More info: https://launchpad.net/~mysteriumnetwork/+archive/ubuntu/node-mainnet
Adding repository.
Press [ENTER] to continue or Ctrl-c to cancel.Adding deb entry to /etc/apt/sources.list.d/mysteriumnetwork-ubuntu-node-mainnet-groovy.list
Adding disabled deb-src entry to /etc/apt/sources.list.d/mysteriumnetwork-ubuntu-node-mainnet-groovy.list
Adding key to /etc/apt/trusted.gpg.d/mysteriumnetwork-ubuntu-node-mainnet.gpg with fingerprint B2233C1C4E92F82FBAA44BCCECCB6A56B22C536D
Hit:1 http://ppa.launchpad.net/mysteriumnetwork/node/ubuntu focal InRelease
Hit:2 http://ppa.launchpad.net/mysteriumnetwork/node-mainnet/ubuntu focal InRelease
Hit:3 https://repos-droplet.digitalocean.com/apt/droplet-agent main InRelease
Ign:4 http://ppa.launchpad.net/mysteriumnetwork/node-mainnet/ubuntu groovy InRelease
Hit:5 http://ppa.launchpad.net/mysteriumnetwork/node-pre/ubuntu groovy InRelease
Hit:6 http://mirrors.digitalocean.com/ubuntu groovy InRelease
Err:7 http://ppa.launchpad.net/mysteriumnetwork/node-mainnet/ubuntu groovy Release
  404  Not Found [IP: 2001:67c:1560:8008::19 80]
Hit:8 http://mirrors.digitalocean.com/ubuntu groovy-updates InRelease
Hit:9 http://mirrors.digitalocean.com/ubuntu groovy-backports InRelease
Hit:10 http://security.ubuntu.com/ubuntu groovy-security InRelease
Reading package lists... Done
E: The repository 'http://ppa.launchpad.net/mysteriumnetwork/node-mainnet/ubuntu groovy Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Activity icon
issue

etherunit issue comment mysteriumnetwork/node

etherunit
etherunit

Test exit node migration into mainnet

Scenario to test

  1. Migrate your node into mainnet (look at instructions provided below)
  2. Open NodeUI in your browser (http://[your_ip]:4449 and finish onboarding (your node identity will be registered in on Matic Mumbai chain).
  3. Ensure that you node identity didn't change. It should remain the same as in testnet3.
  4. Recheck service price (e.g. for WireGuard). It should be set automatically (you should be not able to change it).
  5. Recheck beneficiary (a.k.a. payout address) address in NodeUI and in MMN. It should remain the same as you had before upgrade (in testnet3).
  6. In NodeUI try changing payout address into new one. This should be done instantly (even when your node balance is zero).
  7. Recheck MMN to ensure that new address is changed there as well.

Migration instructions

How to update your Docker node:

  1. Pull the testnet3 node image: docker pull mysteriumnetwork/myst:mainnet

  2. Delete the container that is already being used for running node: docker rm -f myst

  3. Follow the running a docker node guide (https://docs.mysterium.network/node-runners/setup/docker/) to start a new container using :mainnet tag.

How to update your Linux node:

  1. Add the repo: sudo add-apt-repository ppa:mysteriumnetwork/node-mainnet

  2. Update after repo change: sudo apt-get update

  3. Update the cache policy: sudo apt-cache policy myst

  4. Upgrade Mysterium node: sudo apt upgrade myst

How to update your RPi node:

In /etc/apt/sources.list add source deb http://ppa.launchpad.net/mysteriumnetwork/node-mainnet/ubuntu focal

cat /etc/apt/sources.list

Uncomment line below then apt-get update to enable apt-get source

#deb-src http://raspbian.raspberrypi.org/raspbian/ buster main contrib non-free rpi
#deb http://raspbian.raspberrypi.org/raspbian/ buster main contrib non-free rpi
deb http://ppa.launchpad.net/mysteriumnetwork/node-mainnet/ubuntu focal main

Remove unattended-upgrades: sudo apt-get -y remove unattended-upgrades sudo apt-get update sudo apt-cache policy myst sudo apt install myst=<Myst candidate version>


NOTE: After finishing this scenario please post a comment above (if all was ok, please also give us know about that).

etherunit
etherunit

Updated myst container and ubuntu node (needed to adjust release files (groovy > focal) as part of version is absent) to Node version: 0.67.3-1branch-mainnet-bu-1 WebUI version: 0.5.0-mainnet

  • - Migrate your node into mainnet (look at instructions provided below)
  • - Open NodeUI in your browser (http://[your_ip]:4449 and finish onboarding (your node identity will be registered in on Matic Mumbai chain).
  • - Ensure that you node identity didn't change. It should remain the same as in testnet3.
  • - Recheck service price (e.g. for WireGuard). It should be set automatically (you should be not able to change it).
  • - Recheck beneficiary (a.k.a. payout address) address in NodeUI and in MMN. It should remain the same as you had before upgrade (in testnet3).
  • - In NodeUI try changing payout address into new one. This should be done instantly (even when your node balance is zero).
  • - Recheck MMN to ensure that new address is changed there as well.
Activity icon
issue

etherunit issue comment mysteriumnetwork/node

etherunit
etherunit

Test exit node migration into mainnet

Scenario to test

  1. Migrate your node into mainnet (look at instructions provided below)
  2. Open NodeUI in your browser (http://[your_ip]:4449 and finish onboarding (your node identity will be registered in on Matic Mumbai chain).
  3. Ensure that you node identity didn't change. It should remain the same as in testnet3.
  4. Recheck service price (e.g. for WireGuard). It should be set automatically (you should be not able to change it).
  5. Recheck beneficiary (a.k.a. payout address) address in NodeUI and in MMN. It should remain the same as you had before upgrade (in testnet3).
  6. In NodeUI try changing payout address into new one. This should be done instantly (even when your node balance is zero).
  7. Recheck MMN to ensure that new address is changed there as well.

Migration instructions

How to update your Docker node:

  1. Pull the testnet3 node image: docker pull mysteriumnetwork/myst:mainnet

  2. Delete the container that is already being used for running node: docker rm -f myst

  3. Follow the running a docker node guide (https://docs.mysterium.network/node-runners/setup/docker/) to start a new container using :mainnet tag.

How to update your Linux node:

  1. Add the repo: sudo add-apt-repository ppa:mysteriumnetwork/node-mainnet

  2. Update after repo change: sudo apt-get update

  3. Update the cache policy: sudo apt-cache policy myst

  4. Upgrade Mysterium node: sudo apt upgrade myst

How to update your RPi node:

In /etc/apt/sources.list add source deb http://ppa.launchpad.net/mysteriumnetwork/node-mainnet/ubuntu focal

cat /etc/apt/sources.list

Uncomment line below then apt-get update to enable apt-get source

#deb-src http://raspbian.raspberrypi.org/raspbian/ buster main contrib non-free rpi
#deb http://raspbian.raspberrypi.org/raspbian/ buster main contrib non-free rpi
deb http://ppa.launchpad.net/mysteriumnetwork/node-mainnet/ubuntu focal main

Remove unattended-upgrades: sudo apt-get -y remove unattended-upgrades sudo apt-get update sudo apt-cache policy myst sudo apt install myst=<Myst candidate version>


NOTE: After finishing this scenario please post a comment above (if all was ok, please also give us know about that).

etherunit
etherunit

sudo apt upgrade myst - this would not update to Mainnet beta on Linux (0.67.3+1branch+mainnet+bu+1+build392356647+focal). It's required to specify version with apt install myst=0.67.3+1branch+mainnet+bu+1+build392356647+focal

Activity icon
issue

etherunit issue mysteriumnetwork/node

etherunit
etherunit

Long session not reflected into earnings

Describe the bug

ID: 0x7525249fd4ad940829eb538fa3855a9c2f890376

Few days ago i had someone connected to my network for a long time (3 days as you can see). I've seen Live earning as higher than 0 MYSTT. but once connection ended, in Sessions history i see it gave my nothing. Live data was also bigger than 0, bigger than 500mb for sure. Both session time and data transferred are worth something. What happened there? Here are details:

LU 3d 21:31:42 10/7/2021, 6:15:44 PM 0.0000000 MYSTT 0 Bytes d8381320

*Logs can be found on Additional context section

Expected behavior Earnings should be updating.

Environment (please complete the following information): OS: Debian GNU/Linux 10 (buster) Architecture: linux/arm64 Node version: 0.63.0

Additional context mysterium-node.log

Oct
18
6 days ago
Activity icon
issue

etherunit issue mysteriumnetwork/node

etherunit
etherunit

Nodes going offline randomly

It happens periodically and requires a node restart.

Affected providers:

0xa62070eb5dfabb7521ee20119ae55f18b872985b 0x11d1384674c434cee4919dbac400049c6678649f 0x105d710ee16350b63ce4216f16b6aaab1d480031 0x308f1be6ac3ea1b7cbc8ae8d3c3c8503b849b9fd

2021-10-14T16:07:20.746 DBG session/pingpong/price_calculator.go:52  > Calculated price 7642074342445. Time component: 5.3204355207856789403e+12, data component: 2.3216388216604240575e+12. Transferred: 23636, duration: 363.211118735. Price 52733980010130/h, 105467960020260384/GiB 
2021-10-14T16:07:20.747 ERR core/service/session_manager.go:316      > Payment engine error error="sending of invoice failed: did not sent a new exchange message"
2021-10-14T16:07:20.749 INF services/wireguard/service/service_unix.go:170 > Cleaning up session 532b734a-60f6-481f-abaa-b28c1f4e8695
2021-10-14T16:07:20.750 INF services/wireguard/service/stats_publisher.go:64 > Stopped publishing statistics for session 532b734a-60f6-481f-abaa-b28c1f4e8695
Oct 14 15:47:44 raspberry-myst myst[463]: 2021-10-14T15:47:44.504 INF session/pingpong/invoice_tracker.go:503  > did not get paid for invoice with hashlock ee09cd69a3081e2b9af53fb3af80cbbdfc77d6c9f3e5ad40bb419d40e9d05297, invoice is critical. Aborting.
Oct 14 15:47:44 raspberry-myst myst[463]: 2021-10-14T15:47:44.505 ERR core/service/session_manager.go:316      > Payment engine error error="did not get paid for critical invoice with hashlock ee09cd69a3081e2b9af53fb3af80cbbdfc77d6c9f3e5ad40bb419d40e9d05297"
Oct 14 15:47:44 raspberry-myst myst[463]: 2021-10-14T15:47:44.506 INF services/wireguard/service/service_unix.go:170 > Cleaning up session 5b372d86-7513-4dd2-9352-6feaa22112d2

Logs: 0x11d1384674c434cee4919dbac400049c6678649f_issue_nr_3969.zip 0x105d710ee16350b63ce4216f16b6aaab1d480031_issue_nr_3968.zip 0x308f1be6ac3ea1b7cbc8ae8d3c3c8503b849b9fd_issue_nr_3967.zip 0xa62070eb5dfabb7521ee20119ae55f18b872985b_issue_nr_3970.zip

Activity icon
issue

etherunit issue comment mysteriumnetwork/node

etherunit
etherunit

Huge logs files - daemon.log and syslog are flooded with logs from mysterium-node service

Describe the bug Sometimes, the /var/log/daemon.log and /var/log/syslog files are flooded with messages coming from mysterium-node service. In such cases, the two files are growing quickly, and they fill up the log partition, causing the mysterium service to stop.

To Reproduce I don't know. It happens randomly.

Environment (please complete the following information):

  • Node version: 0.67.2
  • OS: Raspbian Buster

Additional context Adding the logs files here. Myst_logs.zip

etherunit
etherunit

I would be very useful if you could run sudo lsof -nP next time it happens. Thanks!

Activity icon
issue

etherunit issue comment mysteriumnetwork/node

etherunit
etherunit

"Test Connection" gets the message "Unauthenticated"

Describe the bug Node's status is marked as test failed. Even after node reboot and update.

0xb0858ca5931a1a1310399dd1ab58f849b00260c1

[email protected]:~#0.67.0 Build info: Branch: 0.67.0. Build id: 386192775. Commit: 8aeb9998

Expected behavior Node should complete a test connection with the node.

Environment (please complete the following information): OS: Ubuntu 20.04.3 LTS Architecture: linux/amd64 Node version: 0.66.3

Additional context

$ sudo systemctl daemon-reload $ sudo systemctl restart mysterium-node $ systemctl status mysterium-node ● mysterium-node.service - Server for Mysterium - decentralised VPN Network Loaded: loaded (/lib/systemd/system/mysterium-node.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2021-10-09 01:03:24 CEST; 564ms ago Docs: https://mysterium.network/ Main PID: 1805054 (myst) Tasks: 10 (limit: 9485) Memory: 10.2M CGroup: /system.slice/mysterium-node.service └─1805054 /usr/bin/myst --config-dir=/etc/mysterium-node --script-dir=/etc/mysterium-node --data-dir=/var/lib/mysterium-node --runtime-dir=/var/run/mysterium-no> Oct 09 01:03:25 vmi683860.contaboserver.net myst[1805054]: 2021-10-09T01:03:25.081 INF cmd/di.go:645 > Using local DNS: testnet3-location.mysteriu> Oct 09 01:03:25 vmi683860.contaboserver.net myst[1805054]: 2021-10-09T01:03:25.082 INF cmd/di.go:645 > Using local DNS: api.ipify.org -> [54.204.1> Oct 09 01:03:25 vmi683860.contaboserver.net myst[1805054]: 2021-10-09T01:03:25.082 INF cmd/di.go:645 > Using local DNS: badupnp.benjojo.co.uk -> [> Oct 09 01:03:25 vmi683860.contaboserver.net myst[1805054]: 2021-10-09T01:03:25.082 INF cmd/di.go:645 > Using local DNS: testnet3-trust.mysterium.n> Oct 09 01:03:25 vmi683860.contaboserver.net myst[1805054]: 2021-10-09T01:03:25.082 INF cmd/di.go:645 > Using local DNS: testnet3-quality.mysterium> Oct 09 01:03:25 vmi683860.contaboserver.net myst[1805054]: 2021-10-09T01:03:25.082 INF cmd/di.go:645 > Using local DNS: feedback.mysterium.network> Oct 09 01:03:25 vmi683860.contaboserver.net myst[1805054]: 2021-10-09T01:03:25.082 DBG communication/nats/connector.go:78 > Connecting to NATS servers: [nats://testnet> Oct 09 01:03:25 vmi683860.contaboserver.net myst[1805054]: 2021-10-09T01:03:25.082 INF firewall/outgoing_firewall_noop.go:57 > Allow URL nats://testnet3-broker.mysterium.> Oct 09 01:03:25 vmi683860.contaboserver.net myst[1805054]: 2021-10-09T01:03:25.083 INF firewall/outgoing_firewall_noop.go:57 > Allow URL nats://testnet3-broker.mysterium.> Oct 09 01:03:25 vmi683860.contaboserver.net myst[1805054]: 2021-10-09T01:03:25.083 INF firewall/outgoing_firewall_noop.go:57 > Allow URL nats://167.233.11.60:4222 access $ systemctl status mysterium-node ● mysterium-node.service - Server for Mysterium - decentralised VPN Network Loaded: loaded (/lib/systemd/system/mysterium-node.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Sat 2021-10-09 01:03:32 CEST; 288ms ago Docs: https://mysterium.network/ Process: 1805054 ExecStart=/usr/bin/myst $CONF_DIR $SCRIPT_DIR $DATA_DIR $RUN_DIR $DAEMON_OPTS service --agreed-terms-and-conditions $SERVICE_OPTS (code=exited, status=1> Main PID: 1805054 (code=exited, status=1/FAILURE) Oct 09 01:03:32 vmi683860.contaboserver.net systemd[1]: mysterium-node.service: Main process exited, code=exited, status=1/FAILURE Oct 09 01:03:32 vmi683860.contaboserver.net systemd[1]: mysterium-node.service: Failed with result 'exit-code'.

etherunit
etherunit
Oct
17
1 week ago
Activity icon
issue

etherunit issue comment mysteriumnetwork/node

etherunit
etherunit

Huge logs files - daemon.log and syslog are flooded with logs from mysterium-node service

Describe the bug Sometimes, the /var/log/daemon.log and /var/log/syslog files are flooded with messages coming from mysterium-node service. In such cases, the two files are growing quickly, and they fill up the log partition, causing the mysterium service to stop.

To Reproduce I don't know. It happens randomly.

Environment (please complete the following information):

  • Node version: 0.67.2
  • OS: Raspbian Buster

Additional context Adding the logs files here. Myst_logs.zip

etherunit
etherunit

@lollapalooza1973 Can you please also submit node logs?

Oct
15
1 week ago
Activity icon
issue

etherunit issue comment mysteriumnetwork/node

etherunit
etherunit

Node test failed even after restarting. "Permissive NAT"

Describe the bug

Hello, My node respond with "Test Failed" for two days. I have no idea what to do. The node runs on Oracle arm64 VPS, Ubuntu 20.04. The identity is: 0xcdeb451f572a6f77491086bda2ec15f63667b6e0 The DH2i NAT Test responds with "Permissive NAT". Thanks in advance!

Expected behavior If node is receiving both test and normal sessions, transfer of data and earnings should be increasing.

Environment (please complete the following information): OS: Ubuntu 20.04.3 LTS Architecture: linux/arm64 Node version: 0.66.4

Additional context mysterium-node-13.log

etherunit
etherunit

@isaackielma Could you request the output of sudo iptables-save?

Activity icon
issue

etherunit issue mysteriumnetwork/node

etherunit
etherunit

Long session not reflected into earnings

Describe the bug

ID: 0x7525249fd4ad940829eb538fa3855a9c2f890376

Few days ago i had someone connected to my network for a long time (3 days as you can see). I've seen Live earning as higher than 0 MYSTT. but once connection ended, in Sessions history i see it gave my nothing. Live data was also bigger than 0, bigger than 500mb for sure. Both session time and data transferred are worth something. What happened there? Here are details:

LU 3d 21:31:42 10/7/2021, 6:15:44 PM 0.0000000 MYSTT 0 Bytes d8381320

*Logs can be found on Additional context section

Expected behavior Earnings should be updating.

Environment (please complete the following information): OS: Debian GNU/Linux 10 (buster) Architecture: linux/arm64 Node version: 0.63.0

Additional context mysterium-node.log

Oct
14
1 week ago
Activity icon
issue

etherunit issue mysteriumnetwork/node

etherunit
etherunit

Nodes going offline randomly

0xa62070eb5dfabb7521ee20119ae55f18b872985b_issue_nr_3970.zip It happens periodically and requires a node restart.

Affected providers:

0xa62070eb5dfabb7521ee20119ae55f18b872985b 0x11d1384674c434cee4919dbac400049c6678649f 0x105d710ee16350b63ce4216f16b6aaab1d480031 0x308f1be6ac3ea1b7cbc8ae8d3c3c8503b849b9fd

2021-10-14T16:07:20.746 DBG session/pingpong/price_calculator.go:52  > Calculated price 7642074342445. Time component: 5.3204355207856789403e+12, data component: 2.3216388216604240575e+12. Transferred: 23636, duration: 363.211118735. Price 52733980010130/h, 105467960020260384/GiB 
2021-10-14T16:07:20.747 ERR core/service/session_manager.go:316      > Payment engine error error="sending of invoice failed: did not sent a new exchange message"
2021-10-14T16:07:20.749 INF services/wireguard/service/service_unix.go:170 > Cleaning up session 532b734a-60f6-481f-abaa-b28c1f4e8695
2021-10-14T16:07:20.750 INF services/wireguard/service/stats_publisher.go:64 > Stopped publishing statistics for session 532b734a-60f6-481f-abaa-b28c1f4e8695

Logs: 0x11d1384674c434cee4919dbac400049c6678649f_issue_nr_3969.zip 0x105d710ee16350b63ce4216f16b6aaab1d480031_issue_nr_3968.zip 0x308f1be6ac3ea1b7cbc8ae8d3c3c8503b849b9fd_issue_nr_3967.zip

Activity icon
issue

etherunit issue mysteriumnetwork/node

etherunit
etherunit

email is not optional anymore

Starting from 0.67 email input is required to send a bug report. I guess we forgot to remove 'optional'. Uploading Screenshot 2021-10-14 at 18.28.38.png…

Oct
13
1 week ago
Activity icon
issue

etherunit issue comment mysteriumnetwork/node

etherunit
etherunit

Node not working properly

Describe the bug All sessions ended at around 10 minutes and all are from Germany. Sessions from countries other than Germany do not seem to connect. These are the warnings that showed up. Error 1: One of the pings has error error="ping receiver error: context deadline exceeded" Which led to error 2: Could not ping peer error="too few connections were built"

To Reproduce Connecting the node from countries other than Germany

Expected behavior The above-mentioned errors

Environment (please complete the following information):

  • Node version: [0.66.4]
  • OS: [e.g. mac OS, 10.15.7]
  • Docker (if applicable): 4.1.0
Activity icon
issue

etherunit issue comment mysteriumnetwork/node

etherunit
etherunit

Long session not reflected into earnings

Describe the bug

ID: 0x7525249fd4ad940829eb538fa3855a9c2f890376

Few days ago i had someone connected to my network for a long time (3 days as you can see). I've seen Live earning as higher than 0 MYSTT. but once connection ended, in Sessions history i see it gave my nothing. Live data was also bigger than 0, bigger than 500mb for sure. Both session time and data transferred are worth something. What happened there? Here are details:

LU 3d 21:31:42 10/7/2021, 6:15:44 PM 0.0000000 MYSTT 0 Bytes d8381320

*Logs can be found on Additional context section

Expected behavior Earnings should be updating.

Environment (please complete the following information): OS: Debian GNU/Linux 10 (buster) Architecture: linux/arm64 Node version: 0.63.0

Additional context mysterium-node.log

etherunit
etherunit

@isaackielma You can find this session on my.mysterium.network with details. I suspect it's related to another bug where NodeUI fails to visually display earnings. Advice him to update his node version and check if issue remains after restart.

d8381320-069a-435f-9781-7ea33b1e6aba Luxembourg 5 days ago Completed 12h 155.37 MB 0.04698525 Normal
https://testnet3-grafana.mysterium.network/d/eC1DulgGz/session?orgId=1&var-service_type=All&var-session=d8381320-069a-435f-9781-7ea33b1e6aba
Activity icon
issue

etherunit issue comment mysteriumnetwork/node

etherunit
etherunit

Bounty pilot displays 0 MYST

Describe the bug Provider_id: 0x91cbdf5594d8c75a92cc44e39cfc61863f591874 Bounty pilot displays 0 MYST earned despite many successful sessions in historical view.

Expected behavior Bounty amount is calculated respectively.

Screenshots Screenshot 2021-10-12 at 19 59 19 Screenshot 2021-10-12 at 19 59 25 Screenshot 2021-10-12 at 19 59 31

Environment (please complete the following information):

  • Node version: 0.67.0
  • OS: Debian GNU/Linux 10 (buster)

Additional context Logs: https://my.mysterium.network/admin/issues/download/3937

etherunit
etherunit

Update: Earnings moved from deadpoint but still too low.

Oct
12
1 week ago
Activity icon
issue

etherunit issue mysteriumnetwork/node

etherunit
etherunit

Bounty pilot displays 0 MYST

Describe the bug Provider_id: 0x91cbdf5594d8c75a92cc44e39cfc61863f591874 Bounty pilot displays 0 MYST earned despite many successful sessions in historical view.

Expected behavior Bounty amount is calculated respectively.

Screenshots Screenshot 2021-10-12 at 19 59 19 Screenshot 2021-10-12 at 19 59 25 Screenshot 2021-10-12 at 19 59 31

Environment (please complete the following information):

  • Node version: 0.66.3
  • OS: Debian GNU/Linux 10 (buster)

Additional context Logs: https://my.mysterium.network/admin/issues/download/3937

Activity icon
issue

etherunit issue comment mysteriumnetwork/node

etherunit
etherunit

Lots of 0 byte connections from Germany. No normal sessions

Describe the bug

I keep getting lots of 0 byte connections, please can you check my node is functioning properly? thanks.

Test sessions seem to be successful but no normal incoming sessions

The specifications of my node are these 👇🏻 Node: 0x9ba274ab7c... Status: Online Last seen: 1 minute ago Node version: 0.66.4

Expected behavior Normal sessions should be happening

Environment (please complete the following information): OS: Ubuntu 20.04.3 LTS Architecture: linux/amd64 Node version: 0.66.4

Additional context mysterium-node-15.log

etherunit
etherunit
Previous