node icon indicating copy to clipboard operation
node copied to clipboard

Published 20 hours ago • verified publisher icon mysteriumnetwork

Myst node not starting

Open CarryingHim opened this issue 1 year ago • 3 comments

Describe the bug Myst node wont start error message wil be showen

i tried everything i found on the internet sadly i am not native englisch ore particularry well versed with linux ore it in generall

Environment (please complete the following information):

  • Node version: 1.29.2
  • OS: raspbian

Additional context COPYRIGHT: Mysterium Node Copyright (C) 2017 The "MysteriumNetwork/node" Authors. This program comes with ABSOLUTELY NO WARRANTY; for details run command 'license --warranty'. This is free software, and you are welcome to redistribute it under certain conditions; run command 'license --conditions' for details. pelki@earnpie:~ $ myst cli W1227 00:34:56.382477 7184 native_arm64.go:188] Could not read /proc/self/auxv: open /proc/self/auxv: permission denied [ERROR] Failed to connect to node via url: 127.0.0.1:4050 pelki@earnpie:~ $ sudo myst cli [ERROR] Failed to connect to node via url: 127.0.0.1:4050 pelki@earnpie:~ $ sudo myst daemon 2023-12-27T00:36:01.580 DBG ../../config/config.go:81 > Loading user configuration: /root/.mysterium/config-mainnet.toml 2023-12-27T00:36:01.581 INF ../../config/config.go:93 > User configuration loaded: {} 2023-12-27T00:36:01.602 INF ../../logconfig/config.go:74 > Log level: debug 2023-12-27T00:36:01.602 INF ../../logconfig/config.go:76 > Log file path: /root/.mysterium/logs/mysterium-node 2023-12-27T00:36:01.603 DBG ../../logconfig/rollingwriter/rollingwriter.go:80 > Found 0 old log files in log directory, skipping cleanup 2023-12-27T00:36:01.603 INF ../../cmd/di.go:226 > Starting Mysterium Node 1.29.2 2023-12-27T00:36:01.604 INF ../../firewall/outgoing_firewall_noop.go:35 > Rules reset was requested 2023-12-27T00:36:01.605 ERR ../../cmd/mysterium_node/mysterium_node.go:68 > Failed to execute command: error="the port 4050 seems to be taken. Either you're already running a node or it is already used by another application: listen tcp 127.0.0.1:4050: bind: address already in use" pelki@earnpie:~ $ sudo myst daemon 2023-12-27T00:37:59.276 DBG ../../config/config.go:81 > Loading user configuration: /root/.mysterium/config-mainnet.toml 2023-12-27T00:37:59.277 INF ../../config/config.go:93 > User configuration loaded: {} 2023-12-27T00:37:59.298 INF ../../logconfig/config.go:74 > Log level: debug 2023-12-27T00:37:59.298 INF ../../logconfig/config.go:76 > Log file path: /root/.mysterium/logs/mysterium-node 2023-12-27T00:37:59.299 DBG ../../logconfig/rollingwriter/rollingwriter.go:80 > Found 0 old log files in log directory, skipping cleanup 2023-12-27T00:37:59.299 INF ../../cmd/di.go:226 > Starting Mysterium Node 1.29.2 2023-12-27T00:37:59.300 INF ../../firewall/outgoing_firewall_noop.go:35 > Rules reset was requested 2023-12-27T00:37:59.301 ERR ../../cmd/mysterium_node/mysterium_node.go:68 > Failed to execute command: error="the port 4050 seems to be taken. Either you're already running a node or it is already used by another application: listen tcp 127.0.0.1:4050: bind: address already in use" pelki@earnpie:~ $ sudo myst daemon 2023-12-27T00:41:04.550 DBG ../../config/config.go:81 > Loading user configuration: /root/.mysterium/config-mainnet.toml 2023-12-27T00:41:04.550 INF ../../config/config.go:93 > User configuration loaded: {} 2023-12-27T00:41:04.571 INF ../../logconfig/config.go:74 > Log level: debug 2023-12-27T00:41:04.571 INF ../../logconfig/config.go:76 > Log file path: /root/.mysterium/logs/mysterium-node 2023-12-27T00:41:04.572 DBG ../../logconfig/rollingwriter/rollingwriter.go:80 > Found 0 old log files in log directory, skipping cleanup 2023-12-27T00:41:04.572 INF ../../cmd/di.go:226 > Starting Mysterium Node 1.29.2 2023-12-27T00:41:04.573 INF ../../firewall/incoming_firewall_noop.go:32 > Rules bootstrap was requested 2023-12-27T00:41:04.574 INF ../../cmd/di.go:702 > Using local DNS: observer.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:41:04.575 INF ../../cmd/di.go:702 > Using local DNS: trust.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:41:04.575 INF ../../cmd/di.go:702 > Using local DNS: location.mysterium.network -> [51.158.129.204] 2023-12-27T00:41:04.575 INF ../../cmd/di.go:702 > Using local DNS: quality.mysterium.network -> [51.158.129.204] 2023-12-27T00:41:04.576 INF ../../cmd/di.go:702 > Using local DNS: badupnp.benjojo.co.uk -> [104.22.70.70 104.22.71.70 172.67.25.154] 2023-12-27T00:41:04.576 INF ../../cmd/di.go:702 > Using local DNS: affiliator.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:41:04.577 INF ../../cmd/di.go:702 > Using local DNS: pilvytis.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:41:04.577 INF ../../cmd/di.go:702 > Using local DNS: feedback.mysterium.network -> [116.203.17.150] 2023-12-27T00:41:04.577 INF ../../cmd/di.go:702 > Using local DNS: api.ipify.org -> [54.204.14.42 54.225.153.147 54.235.83.248 54.243.161.145 23.21.109.69 23.21.126.66 50.19.252.36 174.129.214.20] 2023-12-27T00:41:04.578 INF ../../cmd/di.go:702 > Using local DNS: discovery.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:41:04.578 INF ../../cmd/di.go:702 > Using local DNS: broker.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:41:04.578 INF ../../cmd/di.go:702 > Using local DNS: transactor.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:41:04.579 DBG ../../communication/nats/connector.go:79 > Connecting to NATS servers: [nats://broker.mysterium.network:4222] 2023-12-27T00:41:04.579 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://broker.mysterium.network:4222 access 2023-12-27T00:41:04.580 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://broker.mysterium.network:4222 access 2023-12-27T00:41:04.580 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://51.158.204.30:4222 access 2023-12-27T00:41:04.580 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://51.158.204.75:4222 access 2023-12-27T00:41:04.581 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://51.158.204.9:4222 access 2023-12-27T00:41:04.581 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://51.158.204.23:4222 access 2023-12-27T00:41:06.127 INF ../../cmd/di.go:731 > Using L1 Eth endpoints: [https://ethereum1.mysterium.network/ https://cloudflare-eth.com/] 2023-12-27T00:41:06.131 INF ../../cmd/di.go:732 > Using L2 Eth endpoints: [https://polygon1.mysterium.network/ https://polygon-rpc.com/] 2023-12-27T00:41:06.136 WRN ../../cmd/di.go:324 > observer hermeses call failed, using fallback known hermeses err="Get "https://observer.mysterium.network/api/v1/observed/hermes?approved=true": dial tcp: lookup observer.mysterium.network on [::1]:53: read udp [::1]:58755->[::1]:53: read: connection refused" 2023-12-27T00:41:06.137 INF ../../cmd/di.go:521 > Node chain id 137 2023-12-27T00:41:06.157 ERR ../../session/pingpong/hermes_url_getter.go:104 > failed to get hermes url from blockchain, using fallback error="Post "https://polygon1.mysterium.network/": dial tcp: lookup polygon1.mysterium.network on [::1]:53: read udp [::1]:49017->[::1]:53: read: connection refused" chain_id=137 hermes_id=0x80Ed28d84792d8b153bf2F25F0C4B7a1381dE4ab 2023-12-27T00:41:06.163 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://broker.mysterium.network:4222 removed 2023-12-27T00:41:06.162 WRN ../../communication/nats/connection_wrap.go:105 > NATS: disconnected 2023-12-27T00:41:06.163 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://broker.mysterium.network:4222 removed 2023-12-27T00:41:06.164 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://51.158.204.30:4222 removed 2023-12-27T00:41:06.165 WRN ../../communication/nats/connection_wrap.go:104 > NATS: connection closed 2023-12-27T00:41:06.165 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://51.158.204.75:4222 removed 2023-12-27T00:41:06.166 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://51.158.204.9:4222 removed 2023-12-27T00:41:06.167 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://51.158.204.23:4222 removed 2023-12-27T00:41:06.167 INF ../../firewall/incoming_firewall_noop.go:38 > Rules reset was requested 2023-12-27T00:41:06.168 INF ../../firewall/outgoing_firewall_noop.go:35 > Rules reset was requested 2023-12-27T00:41:06.169 ERR ../../cmd/mysterium_node/mysterium_node.go:68 > Failed to execute command: error="could not get hermes URL: Get "https://observer.mysterium.network/api/v1/observed/hermes": dial tcp: lookup observer.mysterium.network on [::1]:53: read udp [::1]:38700->[::1]:53: read: connection refused" pelki@earnpie:~ $ sudo myst daemon 2023-12-27T00:41:34.322 DBG ../../config/config.go:81 > Loading user configuration: /root/.mysterium/config-mainnet.toml 2023-12-27T00:41:34.322 INF ../../config/config.go:93 > User configuration loaded: {} 2023-12-27T00:41:34.343 INF ../../logconfig/config.go:74 > Log level: debug 2023-12-27T00:41:34.343 INF ../../logconfig/config.go:76 > Log file path: /root/.mysterium/logs/mysterium-node 2023-12-27T00:41:34.344 DBG ../../logconfig/rollingwriter/rollingwriter.go:80 > Found 0 old log files in log directory, skipping cleanup 2023-12-27T00:41:34.344 INF ../../cmd/di.go:226 > Starting Mysterium Node 1.29.2 2023-12-27T00:41:34.345 INF ../../firewall/incoming_firewall_noop.go:32 > Rules bootstrap was requested 2023-12-27T00:41:34.346 INF ../../cmd/di.go:702 > Using local DNS: badupnp.benjojo.co.uk -> [104.22.70.70 104.22.71.70 172.67.25.154] 2023-12-27T00:41:34.346 INF ../../cmd/di.go:702 > Using local DNS: discovery.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:41:34.346 INF ../../cmd/di.go:702 > Using local DNS: trust.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:41:34.347 INF ../../cmd/di.go:702 > Using local DNS: transactor.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:41:34.347 INF ../../cmd/di.go:702 > Using local DNS: affiliator.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:41:34.347 INF ../../cmd/di.go:702 > Using local DNS: pilvytis.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:41:34.347 INF ../../cmd/di.go:702 > Using local DNS: observer.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:41:34.348 INF ../../cmd/di.go:702 > Using local DNS: location.mysterium.network -> [51.158.129.204] 2023-12-27T00:41:34.348 INF ../../cmd/di.go:702 > Using local DNS: quality.mysterium.network -> [51.158.129.204] 2023-12-27T00:41:34.348 INF ../../cmd/di.go:702 > Using local DNS: feedback.mysterium.network -> [116.203.17.150] 2023-12-27T00:41:34.348 INF ../../cmd/di.go:702 > Using local DNS: api.ipify.org -> [54.204.14.42 54.225.153.147 54.235.83.248 54.243.161.145 23.21.109.69 23.21.126.66 50.19.252.36 174.129.214.20] 2023-12-27T00:41:34.349 INF ../../cmd/di.go:702 > Using local DNS: broker.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:41:34.349 DBG ../../communication/nats/connector.go:79 > Connecting to NATS servers: [nats://broker.mysterium.network:4222] 2023-12-27T00:41:34.349 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://broker.mysterium.network:4222 access 2023-12-27T00:41:34.350 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://broker.mysterium.network:4222 access 2023-12-27T00:41:34.350 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://51.158.204.30:4222 access 2023-12-27T00:41:34.350 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://51.158.204.75:4222 access 2023-12-27T00:41:34.350 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://51.158.204.9:4222 access 2023-12-27T00:41:34.351 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://51.158.204.23:4222 access 2023-12-27T00:41:34.354 WRN ../../requests/dialer_swarm.go:293 > Failed to lookup host: "broker.mysterium.network" error="lookup broker.mysterium.network on [::1]:53: read udp [::1]:53025->[::1]:53: read: connection refused" 2023-12-27T00:41:35.916 INF ../../cmd/di.go:731 > Using L1 Eth endpoints: [https://ethereum1.mysterium.network/ https://cloudflare-eth.com/] 2023-12-27T00:41:35.916 INF ../../cmd/di.go:732 > Using L2 Eth endpoints: [https://polygon1.mysterium.network/ https://polygon-rpc.com/] 2023-12-27T00:41:35.919 WRN ../../cmd/di.go:324 > observer hermeses call failed, using fallback known hermeses err="Get "https://observer.mysterium.network/api/v1/observed/hermes?approved=true": dial tcp: lookup observer.mysterium.network on [::1]:53: read udp [::1]:37624->[::1]:53: read: connection refused" 2023-12-27T00:41:35.920 INF ../../cmd/di.go:521 > Node chain id 137 2023-12-27T00:41:35.925 ERR ../../session/pingpong/hermes_url_getter.go:104 > failed to get hermes url from blockchain, using fallback error="Post "https://polygon1.mysterium.network/": dial tcp: lookup polygon1.mysterium.network on [::1]:53: read udp [::1]:57048->[::1]:53: read: connection refused" chain_id=137 hermes_id=0x80Ed28d84792d8b153bf2F25F0C4B7a1381dE4ab 2023-12-27T00:41:35.928 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://broker.mysterium.network:4222 removed 2023-12-27T00:41:35.928 WRN ../../communication/nats/connection_wrap.go:105 > NATS: disconnected 2023-12-27T00:41:35.928 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://broker.mysterium.network:4222 removed 2023-12-27T00:41:35.928 WRN ../../communication/nats/connection_wrap.go:104 > NATS: connection closed 2023-12-27T00:41:35.928 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://51.158.204.30:4222 removed 2023-12-27T00:41:35.929 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://51.158.204.75:4222 removed 2023-12-27T00:41:35.929 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://51.158.204.9:4222 removed 2023-12-27T00:41:35.929 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://51.158.204.23:4222 removed 2023-12-27T00:41:35.929 INF ../../firewall/incoming_firewall_noop.go:38 > Rules reset was requested 2023-12-27T00:41:35.930 INF ../../firewall/outgoing_firewall_noop.go:35 > Rules reset was requested 2023-12-27T00:41:35.930 ERR ../../cmd/mysterium_node/mysterium_node.go:68 > Failed to execute command: error="could not get hermes URL: Get "https://observer.mysterium.network/api/v1/observed/hermes": dial tcp: lookup observer.mysterium.network on [::1]:53: read udp [::1]:57323->[::1]:53: read: connection refused" pelki@earnpie:~ $ sudo myst cli [ERROR] Failed to connect to node via url: 127.0.0.1:4050 pelki@earnpie:~ $ sudo myst daemon 2023-12-27T00:42:15.991 DBG ../../config/config.go:81 > Loading user configuration: /root/.mysterium/config-mainnet.toml 2023-12-27T00:42:15.991 INF ../../config/config.go:93 > User configuration loaded: {} 2023-12-27T00:42:16.011 INF ../../logconfig/config.go:74 > Log level: debug 2023-12-27T00:42:16.012 INF ../../logconfig/config.go:76 > Log file path: /root/.mysterium/logs/mysterium-node 2023-12-27T00:42:16.012 DBG ../../logconfig/rollingwriter/rollingwriter.go:80 > Found 0 old log files in log directory, skipping cleanup 2023-12-27T00:42:16.013 INF ../../cmd/di.go:226 > Starting Mysterium Node 1.29.2 2023-12-27T00:42:16.013 INF ../../firewall/incoming_firewall_noop.go:32 > Rules bootstrap was requested 2023-12-27T00:42:16.014 INF ../../cmd/di.go:702 > Using local DNS: transactor.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:42:16.015 INF ../../cmd/di.go:702 > Using local DNS: affiliator.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:42:16.015 INF ../../cmd/di.go:702 > Using local DNS: location.mysterium.network -> [51.158.129.204] 2023-12-27T00:42:16.015 INF ../../cmd/di.go:702 > Using local DNS: quality.mysterium.network -> [51.158.129.204] 2023-12-27T00:42:16.015 INF ../../cmd/di.go:702 > Using local DNS: badupnp.benjojo.co.uk -> [104.22.70.70 104.22.71.70 172.67.25.154] 2023-12-27T00:42:16.016 INF ../../cmd/di.go:702 > Using local DNS: observer.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:42:16.016 INF ../../cmd/di.go:702 > Using local DNS: discovery.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:42:16.016 INF ../../cmd/di.go:702 > Using local DNS: trust.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:42:16.016 INF ../../cmd/di.go:702 > Using local DNS: broker.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:42:16.017 INF ../../cmd/di.go:702 > Using local DNS: feedback.mysterium.network -> [116.203.17.150] 2023-12-27T00:42:16.017 INF ../../cmd/di.go:702 > Using local DNS: api.ipify.org -> [54.204.14.42 54.225.153.147 54.235.83.248 54.243.161.145 23.21.109.69 23.21.126.66 50.19.252.36 174.129.214.20] 2023-12-27T00:42:16.017 INF ../../cmd/di.go:702 > Using local DNS: pilvytis.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:42:16.017 DBG ../../communication/nats/connector.go:79 > Connecting to NATS servers: [nats://broker.mysterium.network:4222] 2023-12-27T00:42:16.018 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://broker.mysterium.network:4222 access 2023-12-27T00:42:16.018 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://broker.mysterium.network:4222 access 2023-12-27T00:42:16.018 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://51.158.204.30:4222 access 2023-12-27T00:42:16.018 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://51.158.204.75:4222 access 2023-12-27T00:42:16.019 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://51.158.204.9:4222 access 2023-12-27T00:42:16.019 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://51.158.204.23:4222 access 2023-12-27T00:42:17.556 INF ../../cmd/di.go:731 > Using L1 Eth endpoints: [https://ethereum1.mysterium.network/ https://cloudflare-eth.com/] 2023-12-27T00:42:17.557 INF ../../cmd/di.go:732 > Using L2 Eth endpoints: [https://polygon1.mysterium.network/ https://polygon-rpc.com/] 2023-12-27T00:42:17.560 WRN ../../cmd/di.go:324 > observer hermeses call failed, using fallback known hermeses err="Get "https://observer.mysterium.network/api/v1/observed/hermes?approved=true": dial tcp: lookup observer.mysterium.network on [::1]:53: read udp [::1]:56681->[::1]:53: read: connection refused" 2023-12-27T00:42:17.561 INF ../../cmd/di.go:521 > Node chain id 137 2023-12-27T00:42:17.571 ERR ../../session/pingpong/hermes_url_getter.go:104 > failed to get hermes url from blockchain, using fallback error="Post "https://polygon1.mysterium.network/": dial tcp: lookup polygon1.mysterium.network on [::1]:53: read udp [::1]:34267->[::1]:53: read: connection refused" chain_id=137 hermes_id=0x80Ed28d84792d8b153bf2F25F0C4B7a1381dE4ab 2023-12-27T00:42:17.574 WRN ../../communication/nats/connection_wrap.go:105 > NATS: disconnected 2023-12-27T00:42:17.574 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://broker.mysterium.network:4222 removed 2023-12-27T00:42:17.575 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://broker.mysterium.network:4222 removed 2023-12-27T00:42:17.575 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://51.158.204.30:4222 removed 2023-12-27T00:42:17.575 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://51.158.204.75:4222 removed 2023-12-27T00:42:17.575 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://51.158.204.9:4222 removed 2023-12-27T00:42:17.576 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://51.158.204.23:4222 removed 2023-12-27T00:42:17.576 INF ../../firewall/incoming_firewall_noop.go:38 > Rules reset was requested 2023-12-27T00:42:17.576 INF ../../firewall/outgoing_firewall_noop.go:35 > Rules reset was requested 2023-12-27T00:42:17.576 WRN ../../communication/nats/connection_wrap.go:104 > NATS: connection closed 2023-12-27T00:42:17.576 ERR ../../cmd/mysterium_node/mysterium_node.go:68 > Failed to execute command: error="could not get hermes URL: Get "https://observer.mysterium.network/api/v1/observed/hermes": dial tcp: lookup observer.mysterium.network on [::1]:53: read udp [::1]:47859->[::1]:53: read: connection refused" pelki@earnpie:~ $ sudo myst sevice No help topic for 'sevice' pelki@earnpie:~ $ sudo myst sevices No help topic for 'sevices' pelki@earnpie:~ $ sudo myst service 2023-12-27T00:46:09.915 DBG ../../config/config.go:81 > Loading user configuration: /root/.mysterium/config-mainnet.toml 2023-12-27T00:46:09.916 INF ../../config/config.go:93 > User configuration loaded: {} Mysterium Node Version: 1.29.2 Build info: Branch: 1.29.2. Build id: 1106616633. Commit: 56a93e78

Mysterium Node Copyright (C) 2017 The "MysteriumNetwork/node" Authors. This program comes with ABSOLUTELY NO WARRANTY; for details type 'license --warranty'. This is free software, and you are welcome to redistribute it under certain conditions; type 'license --conditions' for details.

                        MYSTERIUM NETWORK
                           TERMS OF USE
                       FOR MYSTERIUM NODES

SHORT VERSION IN HUMAN LANGUAGE FOR EXIT NODE:

  • You will join our network and act as an exit node for others who will use your hardware and internet traffic to access internet resources.
  • We strive to protect you from any legal liability and believe that you should not be liable for running an exit node, but we cannot guarantee that you might not face it.
  • You cannot use or encourage or assist others to use the network in any way which violates any laws or rights of any party, including intellectual property rights.
  • You can monitor data which passes through your equipment only to whitelist the exit destinations for outgoing traffic.
  • You can use the network with our Mysterium software (https://github.com/mysteriumnetwork) or any other compatible software.
  • Your use of the network is at your own risk. We provide it to you “as is” without any warranties.
  • In no event will we be liable for any damages which you may incur.
  • We recommend that you read the full version below to get acquainted with all of the terms and conditions.

SHORT VERSION IN HUMAN LANGUAGE FOR END USER:

  • You cannot use or encourage or assist others to use the network in any way which violates any laws or rights of any party, including intellectual property rights.
  • Your use of the network is at your own risk. We provide it to you “as is” without any warranties.
  • You are responsible for all the content that you receive, distribute or otherwise transmit through the network.
  • You can use the network with our Mysterium software (https://github.com/mysteriumnetwork) or any other compatible software.
  • In no event will we be liable for any damages which you may incur.
  • We recommend you to read the full version bellow to get acquainted with all of the terms and conditions.

We recommend that you read the full versions below to get acquainted with all of the terms and conditions available here: https://github.com/mysteriumnetwork/terms/blob/master/documents/TERMS_EXIT_NODE.md https://github.com/mysteriumnetwork/terms/blob/master/documents/TERMS_END_USER.md

[ERROR] You must agree with provider terms of use in order to use this command [INFO] If you agree with these Terms & Conditions, run program again with '--agreed-terms-and-conditions' flag pelki@earnpie:~ $ sudo myst service --agreed-terms-and-conditions 2023-12-27T00:46:31.005 DBG ../../config/config.go:81 > Loading user configuration: /root/.mysterium/config-mainnet.toml 2023-12-27T00:46:31.005 INF ../../config/config.go:93 > User configuration loaded: {} 2023-12-27T00:46:31.031 INF ../../logconfig/config.go:74 > Log level: debug 2023-12-27T00:46:31.032 INF ../../logconfig/config.go:76 > Log file path: /root/.mysterium/logs/mysterium-node 2023-12-27T00:46:31.032 DBG ../../logconfig/rollingwriter/rollingwriter.go:80 > Found 0 old log files in log directory, skipping cleanup 2023-12-27T00:46:31.032 INF ../../cmd/di.go:226 > Starting Mysterium Node 1.29.2 2023-12-27T00:46:31.033 INF ../../firewall/incoming_firewall_noop.go:32 > Rules bootstrap was requested 2023-12-27T00:46:31.034 INF ../../cmd/di.go:702 > Using local DNS: pilvytis.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:46:31.034 INF ../../cmd/di.go:702 > Using local DNS: observer.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:46:31.034 INF ../../cmd/di.go:702 > Using local DNS: trust.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:46:31.035 INF ../../cmd/di.go:702 > Using local DNS: api.ipify.org -> [54.204.14.42 54.225.153.147 54.235.83.248 54.243.161.145 23.21.109.69 23.21.126.66 50.19.252.36 174.129.214.20] 2023-12-27T00:46:31.035 INF ../../cmd/di.go:702 > Using local DNS: transactor.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:46:31.035 INF ../../cmd/di.go:702 > Using local DNS: feedback.mysterium.network -> [116.203.17.150] 2023-12-27T00:46:31.035 INF ../../cmd/di.go:702 > Using local DNS: badupnp.benjojo.co.uk -> [104.22.70.70 104.22.71.70 172.67.25.154] 2023-12-27T00:46:31.035 INF ../../cmd/di.go:702 > Using local DNS: affiliator.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:46:31.036 INF ../../cmd/di.go:702 > Using local DNS: discovery.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:46:31.036 INF ../../cmd/di.go:702 > Using local DNS: broker.mysterium.network -> [51.158.204.30 51.158.204.75 51.158.204.9 51.158.204.23] 2023-12-27T00:46:31.036 INF ../../cmd/di.go:702 > Using local DNS: location.mysterium.network -> [51.158.129.204] 2023-12-27T00:46:31.036 INF ../../cmd/di.go:702 > Using local DNS: quality.mysterium.network -> [51.158.129.204] 2023-12-27T00:46:31.037 DBG ../../communication/nats/connector.go:79 > Connecting to NATS servers: [nats://broker.mysterium.network:4222] 2023-12-27T00:46:31.037 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://broker.mysterium.network:4222 access 2023-12-27T00:46:31.037 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://broker.mysterium.network:4222 access 2023-12-27T00:46:31.037 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://51.158.204.30:4222 access 2023-12-27T00:46:31.038 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://51.158.204.75:4222 access 2023-12-27T00:46:31.038 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://51.158.204.9:4222 access 2023-12-27T00:46:31.038 INF ../../firewall/outgoing_firewall_noop.go:57 > Allow URL nats://51.158.204.23:4222 access 2023-12-27T00:46:31.042 WRN ../../requests/dialer_swarm.go:293 > Failed to lookup host: "broker.mysterium.network" error="lookup broker.mysterium.network on [::1]:53: read udp [::1]:49023->[::1]:53: read: connection refused" 2023-12-27T00:46:32.579 INF ../../cmd/di.go:731 > Using L1 Eth endpoints: [https://ethereum1.mysterium.network/ https://cloudflare-eth.com/] 2023-12-27T00:46:32.579 INF ../../cmd/di.go:732 > Using L2 Eth endpoints: [https://polygon1.mysterium.network/ https://polygon-rpc.com/] 2023-12-27T00:46:32.582 WRN ../../cmd/di.go:324 > observer hermeses call failed, using fallback known hermeses err="Get "https://observer.mysterium.network/api/v1/observed/hermes?approved=true": dial tcp: lookup observer.mysterium.network on [::1]:53: read udp [::1]:36059->[::1]:53: read: connection refused" 2023-12-27T00:46:32.583 INF ../../cmd/di.go:521 > Node chain id 137 2023-12-27T00:46:32.588 ERR ../../session/pingpong/hermes_url_getter.go:104 > failed to get hermes url from blockchain, using fallback error="Post "https://polygon1.mysterium.network/": dial tcp: lookup polygon1.mysterium.network on [::1]:53: read udp [::1]:46157->[::1]:53: read: connection refused" chain_id=137 hermes_id=0x80Ed28d84792d8b153bf2F25F0C4B7a1381dE4ab 2023-12-27T00:46:32.592 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://broker.mysterium.network:4222 removed 2023-12-27T00:46:32.593 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://broker.mysterium.network:4222 removed 2023-12-27T00:46:32.593 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://51.158.204.30:4222 removed 2023-12-27T00:46:32.593 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://51.158.204.75:4222 removed 2023-12-27T00:46:32.594 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://51.158.204.9:4222 removed 2023-12-27T00:46:32.594 DBG ../../firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://51.158.204.23:4222 removed 2023-12-27T00:46:32.594 INF ../../firewall/incoming_firewall_noop.go:38 > Rules reset was requested 2023-12-27T00:46:32.594 INF ../../firewall/outgoing_firewall_noop.go:35 > Rules reset was requested 2023-12-27T00:46:32.594 WRN ../../communication/nats/connection_wrap.go:105 > NATS: disconnected 2023-12-27T00:46:32.595 ERR ../../cmd/mysterium_node/mysterium_node.go:68 > Failed to execute command: error="could not get hermes URL: Get "https://observer.mysterium.network/api/v1/observed/hermes": dial tcp: lookup observer.mysterium.network on [::1]:53: read udp [::1]:53819->[::1]:53: read: connection refused" pelki@earnpie:~ $ myst version W1227 00:49:02.243089 8229 native_arm64.go:188] Could not read /proc/self/auxv: open /proc/self/auxv: permission denied Mysterium Node Version: 1.29.2 Build info: Branch: 1.29.2. Build id: 1106616633. Commit: 56a93e78

CarryingHim avatar Dec 26 '23 23:12 CarryingHim

what is the output of running this command? sudo systemctl status mysterium-node.service

jgabriel98 avatar Jan 09 '24 14:01 jgabriel98

pelki@earnpie:~ $ myst cli W1227 00:34:56.382477 7184 native_arm64.go:188] Could not read /proc/self/auxv: open /proc/self/auxv: permission denied

It looks as a privileges issue, elevate your privileges and execute the command with sudo or as root user.

2023-12-27T00:46:32.595 ERR ../../cmd/mysterium_node/mysterium_node.go:68 > Failed to execute command: error="could not get hermes URL: Get "[https://observer.mysterium.network/api/v1/observed/hermes](https://observer.mysterium.network/api/v1/observed/hermes%5C)": dial tcp: lookup observer.mysterium.network on [::1]:53: read udp [::1]:53819->[::1]:53: read: connection refused"

Some networking issues too:

  1. Ensure your correctly connected to the internet (ping 8.8.8.8)
  2. Ensure your DNS configuration is working (ping google.com / dig observer.mysterium.network / curl https://observer.mysterium.network/api/v1/observed/hermes)

Nementon avatar Feb 11 '24 11:02 Nementon

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] avatar May 12 '24 05:05 stale[bot]

This issue has been automatically closed because it has not had activity for a long time. If this issue is still valid, please ping a maintainer and ask them to label it as "pinned". Thank you for your contributions.

stale[bot] avatar Jul 12 '24 23:07 stale[bot]