lollapalooza1973

lollapalooza1973

Member Since 3 years ago

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

12 contributions in the last year

Pinned
Activity
Oct
17
1 week ago
Activity icon
issue

lollapalooza1973 issue comment mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

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

lollapalooza1973
lollapalooza1973

@etherunit it has just happened again. I have submitted node logs by clicking on the "bug" button on the NodeUI. Here attached you'll find /var/log/daemon.log and /var/log/syslog

Myst.zip

Activity icon
issue

lollapalooza1973 issue comment mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

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

lollapalooza1973
lollapalooza1973

@etherunit Yes, I have passed "--log-level=info" flag into daemon opts. I will submit the node logs the next time that issue happens.

Activity icon
issue

lollapalooza1973 issue comment mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

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

lollapalooza1973
lollapalooza1973

Adding again log files. /var/log/syslog and /var/log/daemon.log have grown about 35 MB each in about 1 hour. Mysterium_logs.zip

Activity icon
issue

lollapalooza1973 issue mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

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 Myst_logs.zip

Oct
15
1 week ago
Activity icon
issue

lollapalooza1973 issue comment mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

Node shown "online" in MMN, but it's not accepting connections.

Describe the bug Quite often the mysterium-node service stops working. At the same time on MMN the node is shown as "online" with "no active services found". When checking the service status with systemctl, it seems to be online. I tried to restart mysterium-node service with systemctl, but the command got stuck (I had to interrupt with CTRL+C). After rebooting the Raspberry, issue was fixed. Today happened two times to me.

To Reproduce Just leave the node online and wait.

Expected behavior I would expect the node to keep working correctly.

Screenshots immagine

Environment (please complete the following information):

  • Node version: 0.67.0
  • OS: Raspberry

Please give me a secure link to share the logs without leaving personal data exposed to public.

lollapalooza1973
lollapalooza1973

Updated to 0.67.2 Issue still persists.

Oct
14
1 week ago
Activity icon
issue

lollapalooza1973 issue mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

Node shown "online" in MMN, but it's not accepting connections.

Describe the bug Quite often the mysterium-node service stops working. At the same time on MMN the node is shown as "online" with "no active services found". When checking the service status with systemctl, it seems to be online. I tried to restart mysterium-node service with systemctl, but the command got stuck (I had to interrupt with CTRL+C). After rebooting the Raspberry, issue was fixed. Today happened two times to me.

To Reproduce Just leave the node online and wait.

Expected behavior I would expect the node to keep working correctly.

Screenshots immagine

Environment (please complete the following information):

  • Node version: 0.67.0
  • OS: Raspberry

Please give me a secure link to share the logs without leaving personal data exposed to public.

Activity icon
issue

lollapalooza1973 issue mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

MMN: adding a button to restart service or entire node

Is your feature request related to a problem? Please describe. Sometimes the node got stuck, and it would be useful to remotely restart the node or reboot the Raspberry.

Describe the solution you'd like I'd like a button on MMN that allows me to restart the mysterium-node service, or reboot the whole Raspberry.

Oct
9
2 weeks ago
Activity icon
issue

lollapalooza1973 issue mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

Node ranked at #11 in the Global Bounty, despite earnings are greater then node 1st position

Describe the bug My node is listed in position #11, despite it has earned more Myst than the node at position #1.

To Reproduce Check the Global Bounty page in Mysterium website, country Italy.

Expected behavior I would expect to be listed at position #1.

Screenshots immagine immagine

Environment (please complete the following information):

  • Node 0.66.4
  • OS: Raspbian
Sep
29
3 weeks ago
Activity icon
issue

lollapalooza1973 issue comment mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

Update from 0.65.1 to 0.66.1 - Node UI does not work

Describe the bug Last night the node automatically updated to 0.66.1. Now I see that the Node UI does not work (I see a blank screen). I tried to reboot the node, but nothing has changed.

Environment (please complete the following information):

  • Node version: 0.66.1
  • OS: Raspbian
lollapalooza1973
lollapalooza1973

Have you tried clearing cache or using incognito to access it? Might be something cached on your side.

You're right... it worked! Thanks

Activity icon
issue

lollapalooza1973 issue comment mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

Update from 0.65.1 to 0.66.1 - Node UI does not work

Describe the bug Last night the node automatically updated to 0.66.1. Now I see that the Node UI does not work (I see a blank screen). I tried to reboot the node, but nothing has changed.

Environment (please complete the following information):

  • Node version: 0.66.1
  • OS: Raspbian
lollapalooza1973
lollapalooza1973

I have updated the node to 0.66.2, nothing has changed.

Activity icon
issue

lollapalooza1973 issue comment mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

Update from 0.65.1 to 0.66.1 - Node UI does not work

Describe the bug Last night the node automatically updated to 0.66.1. Now I see that the Node UI does not work (I see a blank screen). I tried to reboot the node, but nothing has changed.

Environment (please complete the following information):

  • Node version: 0.66.1
  • OS: Raspbian
Sep
20
1 month ago
Activity icon
issue

lollapalooza1973 issue comment mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

Node does not accept any incoming connection - MMN shows status "online"

Describe the bug After a while that the node is running (>30 hours) the node does not accept any incoming connection. On MMN page the status is "online" but when clicking on "check connection", nothing happens:

  • no incoming connections
  • no change in status

I have collected the daemon.log and the syslog just before rebooting the node. Please give a safe place where to upload the logs.

Expected behavior I would expect the node does not stop working.

Environment (please complete the following information):

  • Node version: 0.63.0
  • OS: Raspbian
lollapalooza1973
lollapalooza1973

After a couple of days since last reboot, node stopped working again. Again, the status on MMN was "online".

Sep
18
1 month ago
Activity icon
issue

lollapalooza1973 issue mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

Node does not accept any incoming connection - MMN shows status "online"

Describe the bug After a while that the node is running (>30 hours) the node does not accept any incoming connection. On MMN page the status is "online" but when clicking on "check connection", nothing happens:

  • no incoming connections
  • no change in status

I have collected the daemon.log and the syslog just before rebooting the node. Please give a safe place where to upload the logs.

Expected behavior I would expect the node does not stop working.

Environment (please complete the following information):

  • Node version: 0.63.0
  • OS: Raspbian
Aug
12
2 months ago
Activity icon
issue

lollapalooza1973 issue comment mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

No more connections since update to 0.53.2

My node has updated to 0.53.2 in the night between 9th and 10th Aug. Since then, I get no more connections.

Latest connection is from 10 Augh, 5.32 am.

Node is shown online in MMN. Node ID: 0x641cb8019932b0fc112eeb1c265a4e93811c9086

Environment (please complete the following information):

  • Node version: 0.53.2
  • OS: Raspbian

This is what I in node logs when I trigger the "check connection" button.

Aug 11 08:05:53 raspberry-myst myst[584]: 2021-08-11T08:05:53.070 WRN nat/mapping/port_mapping.go:115          > Couldn't detect router IP address error="goupnp: SOAP request got HTTP 500 Internal Server Error"
Aug 11 08:05:53 raspberry-myst myst[584]: 2021-08-11T08:05:53.071 INF nat/mapping/port_mapping.go:74           > Port mapping is useless, skipping it. error="failed to find router public IP"
Aug 11 08:05:53 raspberry-myst myst[584]: 2021-08-11T08:05:53.072 INF nat/event/tracker.go:53                  > Got NAT event event={"error":{},"id":"0x641cb8019932b0fc112eeb1c265a4e93811c9086","stage":"port_mapping","successful":false}
Aug 11 08:06:23 raspberry-myst myst[584]: 2021-08-11T08:06:23.835 WRN p2p/channel.go:571                       > No initial traffic for 30 sec. Terminating channel.
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.294 INF core/port/pool.go:59                     > Supplying port 16672
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.295 INF core/port/pool.go:59                     > Supplying port 19228
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.299 WRN nat/mapping/port_mapping.go:115          > Couldn't detect router IP address error="goupnp: SOAP request got HTTP 500 Internal Server Error"
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.301 INF nat/mapping/port_mapping.go:74           > Port mapping is useless, skipping it. error="failed to find router public IP"
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.302 INF nat/event/tracker.go:53                  > Got NAT event event={"error":{},"id":"0x641cb8019932b0fc112eeb1c265a4e93811c9086","stage":"port_mapping","successful":false}
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.952 INF core/port/pool.go:59                     > Supplying port 11333
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.953 INF core/port/pool.go:59                     > Supplying port 46882
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.960 WRN nat/mapping/port_mapping.go:115          > Couldn't detect router IP address error="goupnp: SOAP request got HTTP 500 Internal Server Error"
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.961 INF nat/mapping/port_mapping.go:74           > Port mapping is useless, skipping it. error="failed to find router public IP"
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.962 INF nat/event/tracker.go:53                  > Got NAT event event={"error":{},"id":"0x641cb8019932b0fc112eeb1c265a4e93811c9086","stage":"port_mapping","successful":false}
Aug 11 08:07:11 raspberry-myst myst[584]: 2021-08-11T08:07:11.080 WRN p2p/channel.go:571                       > No initial traffic for 30 sec. Terminating channel.
Aug 11 08:07:16 raspberry-myst myst[584]: 2021-08-11T08:07:16.725 WRN p2p/channel.go:571                       > No initial traffic for 30 sec. Terminating channel.

lollapalooza1973
lollapalooza1973

@Snawoot here's the new config file.

# Define additional args for `myst` service (see `myst --help` for full list)
CONF_DIR="--config-dir=/etc/mysterium-node"
SCRIPT_DIR="--script-dir=/etc/mysterium-node"
RUN_DIR="--runtime-dir=/var/run/mysterium-node"
DATA_DIR="--data-dir=/var/lib/mysterium-node"
DAEMON_OPTS="--p2p.listen.ports=51820:52075 --experiment-natpunching=false --keystore.lightweight --log-level=info --stun-servers="
SERVICE_OPTS="--wireguard.listen.ports=52820:53075 wireguard"

I have restarted the service and triggered the test connections, but on the node UI I still do not see any incoming connection.

The following are the last rows of the logs:

Aug 12 15:00:40 raspberry-myst myst[1074]: 2021-08-12T15:00:40.360 WRN p2p/stun.go:102                          > Failed to get ports from STUN servers, falling back to local ports
Aug 12 15:01:05 raspberry-myst myst[1074]: 2021-08-12T15:01:05.752 WRN p2p/channel.go:571                       > No initial traffic for 30 sec. Terminating channel.

Activity icon
issue

lollapalooza1973 issue comment mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

No more connections since update to 0.53.2

My node has updated to 0.53.2 in the night between 9th and 10th Aug. Since then, I get no more connections.

Latest connection is from 10 Augh, 5.32 am.

Node is shown online in MMN. Node ID: 0x641cb8019932b0fc112eeb1c265a4e93811c9086

Environment (please complete the following information):

  • Node version: 0.53.2
  • OS: Raspbian

This is what I in node logs when I trigger the "check connection" button.

Aug 11 08:05:53 raspberry-myst myst[584]: 2021-08-11T08:05:53.070 WRN nat/mapping/port_mapping.go:115          > Couldn't detect router IP address error="goupnp: SOAP request got HTTP 500 Internal Server Error"
Aug 11 08:05:53 raspberry-myst myst[584]: 2021-08-11T08:05:53.071 INF nat/mapping/port_mapping.go:74           > Port mapping is useless, skipping it. error="failed to find router public IP"
Aug 11 08:05:53 raspberry-myst myst[584]: 2021-08-11T08:05:53.072 INF nat/event/tracker.go:53                  > Got NAT event event={"error":{},"id":"0x641cb8019932b0fc112eeb1c265a4e93811c9086","stage":"port_mapping","successful":false}
Aug 11 08:06:23 raspberry-myst myst[584]: 2021-08-11T08:06:23.835 WRN p2p/channel.go:571                       > No initial traffic for 30 sec. Terminating channel.
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.294 INF core/port/pool.go:59                     > Supplying port 16672
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.295 INF core/port/pool.go:59                     > Supplying port 19228
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.299 WRN nat/mapping/port_mapping.go:115          > Couldn't detect router IP address error="goupnp: SOAP request got HTTP 500 Internal Server Error"
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.301 INF nat/mapping/port_mapping.go:74           > Port mapping is useless, skipping it. error="failed to find router public IP"
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.302 INF nat/event/tracker.go:53                  > Got NAT event event={"error":{},"id":"0x641cb8019932b0fc112eeb1c265a4e93811c9086","stage":"port_mapping","successful":false}
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.952 INF core/port/pool.go:59                     > Supplying port 11333
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.953 INF core/port/pool.go:59                     > Supplying port 46882
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.960 WRN nat/mapping/port_mapping.go:115          > Couldn't detect router IP address error="goupnp: SOAP request got HTTP 500 Internal Server Error"
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.961 INF nat/mapping/port_mapping.go:74           > Port mapping is useless, skipping it. error="failed to find router public IP"
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.962 INF nat/event/tracker.go:53                  > Got NAT event event={"error":{},"id":"0x641cb8019932b0fc112eeb1c265a4e93811c9086","stage":"port_mapping","successful":false}
Aug 11 08:07:11 raspberry-myst myst[584]: 2021-08-11T08:07:11.080 WRN p2p/channel.go:571                       > No initial traffic for 30 sec. Terminating channel.
Aug 11 08:07:16 raspberry-myst myst[584]: 2021-08-11T08:07:16.725 WRN p2p/channel.go:571                       > No initial traffic for 30 sec. Terminating channel.

Aug
11
2 months ago
Activity icon
issue

lollapalooza1973 issue comment mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

No more connections since update to 0.53.2

My node has updated to 0.53.2 in the night between 9th and 10th Aug. Since then, I get no more connections.

Latest connection is from 10 Augh, 5.32 am.

Node is shown online in MMN. Node ID: 0x641cb8019932b0fc112eeb1c265a4e93811c9086

Environment (please complete the following information):

  • Node version: 0.53.2
  • OS: Raspbian

This is what I in node logs when I trigger the "check connection" button.

Aug 11 08:05:53 raspberry-myst myst[584]: 2021-08-11T08:05:53.070 WRN nat/mapping/port_mapping.go:115          > Couldn't detect router IP address error="goupnp: SOAP request got HTTP 500 Internal Server Error"
Aug 11 08:05:53 raspberry-myst myst[584]: 2021-08-11T08:05:53.071 INF nat/mapping/port_mapping.go:74           > Port mapping is useless, skipping it. error="failed to find router public IP"
Aug 11 08:05:53 raspberry-myst myst[584]: 2021-08-11T08:05:53.072 INF nat/event/tracker.go:53                  > Got NAT event event={"error":{},"id":"0x641cb8019932b0fc112eeb1c265a4e93811c9086","stage":"port_mapping","successful":false}
Aug 11 08:06:23 raspberry-myst myst[584]: 2021-08-11T08:06:23.835 WRN p2p/channel.go:571                       > No initial traffic for 30 sec. Terminating channel.
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.294 INF core/port/pool.go:59                     > Supplying port 16672
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.295 INF core/port/pool.go:59                     > Supplying port 19228
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.299 WRN nat/mapping/port_mapping.go:115          > Couldn't detect router IP address error="goupnp: SOAP request got HTTP 500 Internal Server Error"
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.301 INF nat/mapping/port_mapping.go:74           > Port mapping is useless, skipping it. error="failed to find router public IP"
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.302 INF nat/event/tracker.go:53                  > Got NAT event event={"error":{},"id":"0x641cb8019932b0fc112eeb1c265a4e93811c9086","stage":"port_mapping","successful":false}
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.952 INF core/port/pool.go:59                     > Supplying port 11333
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.953 INF core/port/pool.go:59                     > Supplying port 46882
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.960 WRN nat/mapping/port_mapping.go:115          > Couldn't detect router IP address error="goupnp: SOAP request got HTTP 500 Internal Server Error"
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.961 INF nat/mapping/port_mapping.go:74           > Port mapping is useless, skipping it. error="failed to find router public IP"
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.962 INF nat/event/tracker.go:53                  > Got NAT event event={"error":{},"id":"0x641cb8019932b0fc112eeb1c265a4e93811c9086","stage":"port_mapping","successful":false}
Aug 11 08:07:11 raspberry-myst myst[584]: 2021-08-11T08:07:11.080 WRN p2p/channel.go:571                       > No initial traffic for 30 sec. Terminating channel.
Aug 11 08:07:16 raspberry-myst myst[584]: 2021-08-11T08:07:16.725 WRN p2p/channel.go:571                       > No initial traffic for 30 sec. Terminating channel.

lollapalooza1973
lollapalooza1973

I don't even get those "test" connections.

Activity icon
issue

lollapalooza1973 issue comment mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

No more connections since update to 0.53.2

My node has updated to 0.53.2 in the night between 9th and 10th Aug. Since then, I get no more connections.

Latest connection is from 10 Augh, 5.32 am.

Node is shown online in MMN. Node ID: 0x641cb8019932b0fc112eeb1c265a4e93811c9086

Environment (please complete the following information):

  • Node version: 0.53.2
  • OS: Raspbian

This is what I in node logs when I trigger the "check connection" button.

Aug 11 08:05:53 raspberry-myst myst[584]: 2021-08-11T08:05:53.070 WRN nat/mapping/port_mapping.go:115          > Couldn't detect router IP address error="goupnp: SOAP request got HTTP 500 Internal Server Error"
Aug 11 08:05:53 raspberry-myst myst[584]: 2021-08-11T08:05:53.071 INF nat/mapping/port_mapping.go:74           > Port mapping is useless, skipping it. error="failed to find router public IP"
Aug 11 08:05:53 raspberry-myst myst[584]: 2021-08-11T08:05:53.072 INF nat/event/tracker.go:53                  > Got NAT event event={"error":{},"id":"0x641cb8019932b0fc112eeb1c265a4e93811c9086","stage":"port_mapping","successful":false}
Aug 11 08:06:23 raspberry-myst myst[584]: 2021-08-11T08:06:23.835 WRN p2p/channel.go:571                       > No initial traffic for 30 sec. Terminating channel.
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.294 INF core/port/pool.go:59                     > Supplying port 16672
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.295 INF core/port/pool.go:59                     > Supplying port 19228
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.299 WRN nat/mapping/port_mapping.go:115          > Couldn't detect router IP address error="goupnp: SOAP request got HTTP 500 Internal Server Error"
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.301 INF nat/mapping/port_mapping.go:74           > Port mapping is useless, skipping it. error="failed to find router public IP"
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.302 INF nat/event/tracker.go:53                  > Got NAT event event={"error":{},"id":"0x641cb8019932b0fc112eeb1c265a4e93811c9086","stage":"port_mapping","successful":false}
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.952 INF core/port/pool.go:59                     > Supplying port 11333
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.953 INF core/port/pool.go:59                     > Supplying port 46882
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.960 WRN nat/mapping/port_mapping.go:115          > Couldn't detect router IP address error="goupnp: SOAP request got HTTP 500 Internal Server Error"
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.961 INF nat/mapping/port_mapping.go:74           > Port mapping is useless, skipping it. error="failed to find router public IP"
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.962 INF nat/event/tracker.go:53                  > Got NAT event event={"error":{},"id":"0x641cb8019932b0fc112eeb1c265a4e93811c9086","stage":"port_mapping","successful":false}
Aug 11 08:07:11 raspberry-myst myst[584]: 2021-08-11T08:07:11.080 WRN p2p/channel.go:571                       > No initial traffic for 30 sec. Terminating channel.
Aug 11 08:07:16 raspberry-myst myst[584]: 2021-08-11T08:07:16.725 WRN p2p/channel.go:571                       > No initial traffic for 30 sec. Terminating channel.

lollapalooza1973
lollapalooza1973

I tried to change the used port range from 41820:42075 / 42820:43075 (that I set up a few weeks ago) to 51820:52075 / 52820:53075, and modified the port-forwarding rule accordingly on the router, but nothing has changed.

Activity icon
issue

lollapalooza1973 issue comment mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

No more connections since update to 0.53.2

My node has updated to 0.53.2 in the night between 9th and 10th Aug. Since then, I get no more connections.

Latest connection is from 10 Augh, 5.32 am.

Node is shown online in MMN.

Environment (please complete the following information):

  • Node version: 0.53.2
  • OS: Raspbian

This is what I in node logs when I trigger the "check connection" button.

Aug 11 08:05:53 raspberry-myst myst[584]: 2021-08-11T08:05:53.070 WRN nat/mapping/port_mapping.go:115          > Couldn't detect router IP address error="goupnp: SOAP request got HTTP 500 Internal Server Error"
Aug 11 08:05:53 raspberry-myst myst[584]: 2021-08-11T08:05:53.071 INF nat/mapping/port_mapping.go:74           > Port mapping is useless, skipping it. error="failed to find router public IP"
Aug 11 08:05:53 raspberry-myst myst[584]: 2021-08-11T08:05:53.072 INF nat/event/tracker.go:53                  > Got NAT event event={"error":{},"id":"0x641cb8019932b0fc112eeb1c265a4e93811c9086","stage":"port_mapping","successful":false}
Aug 11 08:06:23 raspberry-myst myst[584]: 2021-08-11T08:06:23.835 WRN p2p/channel.go:571                       > No initial traffic for 30 sec. Terminating channel.
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.294 INF core/port/pool.go:59                     > Supplying port 16672
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.295 INF core/port/pool.go:59                     > Supplying port 19228
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.299 WRN nat/mapping/port_mapping.go:115          > Couldn't detect router IP address error="goupnp: SOAP request got HTTP 500 Internal Server Error"
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.301 INF nat/mapping/port_mapping.go:74           > Port mapping is useless, skipping it. error="failed to find router public IP"
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.302 INF nat/event/tracker.go:53                  > Got NAT event event={"error":{},"id":"0x641cb8019932b0fc112eeb1c265a4e93811c9086","stage":"port_mapping","successful":false}
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.952 INF core/port/pool.go:59                     > Supplying port 11333
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.953 INF core/port/pool.go:59                     > Supplying port 46882
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.960 WRN nat/mapping/port_mapping.go:115          > Couldn't detect router IP address error="goupnp: SOAP request got HTTP 500 Internal Server Error"
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.961 INF nat/mapping/port_mapping.go:74           > Port mapping is useless, skipping it. error="failed to find router public IP"
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.962 INF nat/event/tracker.go:53                  > Got NAT event event={"error":{},"id":"0x641cb8019932b0fc112eeb1c265a4e93811c9086","stage":"port_mapping","successful":false}
Aug 11 08:07:11 raspberry-myst myst[584]: 2021-08-11T08:07:11.080 WRN p2p/channel.go:571                       > No initial traffic for 30 sec. Terminating channel.
Aug 11 08:07:16 raspberry-myst myst[584]: 2021-08-11T08:07:16.725 WRN p2p/channel.go:571                       > No initial traffic for 30 sec. Terminating channel.

lollapalooza1973
lollapalooza1973
 curl -X POST --data '{"email":"[email protected]"}' localhost:4050/feedback/issue
{"issueId":"3384"}
Activity icon
issue

lollapalooza1973 issue mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

No more connections since update to 0.53.2

My node has updated to 0.53.2 in the night between 9th and 10th Aug. Since then, I get no more connections.

Latest connection is from 10 Augh, 5.32 am.

Node is shown online in MMN.

Environment (please complete the following information):

  • Node version: 0.53.2
  • OS: Raspbian

This is what I in node logs when I trigger the "check connection" button.

Aug 11 08:05:53 raspberry-myst myst[584]: 2021-08-11T08:05:53.070 WRN nat/mapping/port_mapping.go:115          > Couldn't detect router IP address error="goupnp: SOAP request got HTTP 500 Internal Server Error"
Aug 11 08:05:53 raspberry-myst myst[584]: 2021-08-11T08:05:53.071 INF nat/mapping/port_mapping.go:74           > Port mapping is useless, skipping it. error="failed to find router public IP"
Aug 11 08:05:53 raspberry-myst myst[584]: 2021-08-11T08:05:53.072 INF nat/event/tracker.go:53                  > Got NAT event event={"error":{},"id":"0x641cb8019932b0fc112eeb1c265a4e93811c9086","stage":"port_mapping","successful":false}
Aug 11 08:06:23 raspberry-myst myst[584]: 2021-08-11T08:06:23.835 WRN p2p/channel.go:571                       > No initial traffic for 30 sec. Terminating channel.
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.294 INF core/port/pool.go:59                     > Supplying port 16672
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.295 INF core/port/pool.go:59                     > Supplying port 19228
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.299 WRN nat/mapping/port_mapping.go:115          > Couldn't detect router IP address error="goupnp: SOAP request got HTTP 500 Internal Server Error"
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.301 INF nat/mapping/port_mapping.go:74           > Port mapping is useless, skipping it. error="failed to find router public IP"
Aug 11 08:06:40 raspberry-myst myst[584]: 2021-08-11T08:06:40.302 INF nat/event/tracker.go:53                  > Got NAT event event={"error":{},"id":"0x641cb8019932b0fc112eeb1c265a4e93811c9086","stage":"port_mapping","successful":false}
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.952 INF core/port/pool.go:59                     > Supplying port 11333
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.953 INF core/port/pool.go:59                     > Supplying port 46882
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.960 WRN nat/mapping/port_mapping.go:115          > Couldn't detect router IP address error="goupnp: SOAP request got HTTP 500 Internal Server Error"
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.961 INF nat/mapping/port_mapping.go:74           > Port mapping is useless, skipping it. error="failed to find router public IP"
Aug 11 08:06:45 raspberry-myst myst[584]: 2021-08-11T08:06:45.962 INF nat/event/tracker.go:53                  > Got NAT event event={"error":{},"id":"0x641cb8019932b0fc112eeb1c265a4e93811c9086","stage":"port_mapping","successful":false}
Aug 11 08:07:11 raspberry-myst myst[584]: 2021-08-11T08:07:11.080 WRN p2p/channel.go:571                       > No initial traffic for 30 sec. Terminating channel.
Aug 11 08:07:16 raspberry-myst myst[584]: 2021-08-11T08:07:16.725 WRN p2p/channel.go:571                       > No initial traffic for 30 sec. Terminating channel.

Aug
4
2 months ago
Activity icon
issue

lollapalooza1973 issue comment mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

A session >12 hours long gave 0 MYST

Describe the bug I had a session that lasted for more than 12 hours, and it shows 0 MYST earned.

Screenshots image

Environment (please complete the following information):

  • Node version: 0.52.0
  • OS: Raspbian

I have submitted the logs via node CLI: {"issueId":"3287"}

lollapalooza1973
lollapalooza1973
Jul
27
2 months ago
Activity icon
issue

lollapalooza1973 issue comment mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

A session >12 hours long gave 0 MYST

Describe the bug I had a session that lasted for more than 12 hours, and it shows 0 MYST earned.

Screenshots image

Environment (please complete the following information):

  • Node version: 0.52.0
  • OS: Raspbian

I have submitted the logs via node CLI: {"issueId":"3287"}

lollapalooza1973
lollapalooza1973

Same issue with other long sessions. image image image

Activity icon
issue

lollapalooza1973 issue comment mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

Node status online and running fine. Dashboard stating "no services found"

Describe the bug Multiple nodes experiencing an issue where their nodes are working just fine. However, upon checking connection on their nodes they get message that there are no service to be found..

To Reproduce Steps to reproduce the behavior:

  1. Go to Dashboard
  2. Click on 'Check connection'
  3. See error 'No services found'

Expected behavior Check connection should be queued

Screenshots

Environment (please complete the following information): Screenshot 2021-07-27 at 07 34 09 Screenshot 2021-07-27 at 07 34 09

Additional context Add any other context about the problem here.

lollapalooza1973
lollapalooza1973

Same issue here. Node is "online", and I also have incoming connections. Anyway, MMS shows "No services found".

Node ID: 0x641cb8019932b0fc112eeb1c265a4e93811c9086

Activity icon
issue

lollapalooza1973 issue mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

A session >12 hours long gave 0 MYST

Describe the bug I had a session that lasted for more than 12 hours, and it shows 0 MYST earned.

Screenshots image

Environment (please complete the following information):

  • Node version: 0.52.0
  • OS: Raspbian

I have submitted the logs via node CLI: {"issueId":"3287"}

Activity icon
issue

lollapalooza1973 issue comment mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

Huge logs files - /var/log partition gets 100% full in very short time

If there's a small number of connections to the node, the daemon.log and syslog files are just behaving normally. They grow up slowly, and rotate when it's scheduled.

If there are many connection to the node, the logs are growing incredibly fast, and the /var/log partition gets full in just a few hours (my /var/log partition is 80 GB in size), and logrotation will not work, as there's no free space to compress the files.

Environment (please complete the following information):

  • Node version: 0.52.0
  • OS: Raspbian Buster
lollapalooza1973
lollapalooza1973
Activity icon
issue

lollapalooza1973 issue comment mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

Huge logs files - /var/log partition gets 100% full in very short time

If there's a small number of connections to the node, the daemon.log and syslog files are just behaving normally. They grow up slowly, and rotate when it's scheduled.

If there are many connection to the node, the logs are growing incredibly fast, and the /var/log partition gets full in just a few hours (my /var/log partition is 80 GB in size), and logrotation will not work, as there's no free space to compress the files.

Environment (please complete the following information):

  • Node version: 0.52.0
  • OS: Raspbian Buster
lollapalooza1973
lollapalooza1973

Shall I set this in /etc/default/mysterium-node? Something like LOG_LEVEL="--log-level=info"

Activity icon
issue

lollapalooza1973 issue comment mysteriumnetwork/node

lollapalooza1973
lollapalooza1973

Huge logs files - /var/log partition gets 100% full in very short time

If there's a small number of connections to the node, the daemon.log and syslog files are just behaving normally. They grow up slowly, and rotate when it's scheduled.

If there are many connection to the node, the logs are growing incredibly fast, and the /var/log partition gets full in just a few hours (my /var/log partition is 80 GB in size), and logrotation will not work, as there's no free space to compress the files.

Environment (please complete the following information):

  • Node version: 0.52.0
  • OS: Raspbian Buster
lollapalooza1973
lollapalooza1973

How do I change the log verbosity?