Electroneum Aurora V4.0.0.1 - Daemon not establishing connecting anymore

I can run a remote node fine with:

electroneum-wallet-cli.exe --daemon-host=13.74.171.8:8081

However, I want to remain independent and run my own node. I have been doing so but recently
my daemon has stopped establishing a connection to the blockchain and downloading blocks.

When I run electroneumd.exe, nothing happens initially.

After a while (more than an hour or more) it gives me an error “No Incoming connection - check firewall/routers allow port 26967”

When I run the ‘status’ command, I can see there are no ‘in’ or ‘out’ connections.

I’ve enabled the app in Windows defender and setup an exception in my anti virus, so these are not blocking the connection.

It has always work up until a few days ago.

Any ideas? I am using v4.0.0.1.

Hi User, without some errors or more info, not a lot can be diagnosed. Does it start syncing? What shows in your node when its running? What block has it reached when you use status, is the p2p service starting OK?

Perhaps increase the set_log level for electroneumd.exe to see more of what’s happening. (you can type “help” inside the app to get list of commands)

Nodes are running fine, I have one and there are no problems.

It doesn’t sync. It gets to “Validators list loaded from JSON endpoint! Refresh in 12 hours” and does nothing else for sometime. After a while (a few hours) it produces the error “No Incoming connection - check firewall/routers allow port 26967”. Electroneumd.exe is enabled for in coming connections in Windows defender and anti virus has an exception. Has all worked fine until recently.

When I run the status command, I get:
“Height: 126758/1267580 (100.0%) on mainnet, not mining, net hash 273 H/s, v10, 0(out)+0(in) connections, uptime…”

Tried restarting PC and switching off VPN but still no luck. Have even downloaded the binaries again.

Well according to that you are synced. 100%. (i assume that’s a typo in your post 126758/1267580).

How big is your blockchain file? default is c:/ProgramData/electroneum…its the LMDB file (data.mdb). Currently it should be ~45gb

It is not a typo. It’s not establishing a connection and reading from the last time it fully syn’d at block 1267580. The electroneum IMDb file is 43.9 GB.

Pretty sure you are not at 100% sync with 44gb database when on block 126,758 of 1,267,580. :wink:

…but anyway, I assume you mean the max height doesn’t change when you run the node, i.e. its stuck on 1,267,580?

So what did it say when changed the set_log level to something higher? You can check your electroneum.log file (defaults to same area as lmdb files).

(remember if you post anything, make sure to hide any personal information like IP’s etc)

1 Like

We are waiting for the user’s 1140 log. Everything works perfectly.
I’m also following this thread. From time to time.

Yesterday it started syncing again… but now again today its not establishing a connection despite it stating “you are now synchronizing with the network”. Today it states block 1276990, when yesterday I got to block 1276985. There has been more than 5 blocks since yesterday. Here are the logs:

Log

2022-02-19 02:45:50.676 9548 INFO logging contrib/epee/src/mlog.cpp:273 New log categories: *:WARNING,net:FATAL,net.http:FATAL,net.ssl:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,serialization:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO
2022-02-19 02:45:50.676 9548 INFO global src/daemon/main.cpp:354 Electroneum ‘Aurora’ (v4.0.0.1-6ebe933c2)
2022-02-19 02:45:50.676 9548 INFO global src/daemon/protocol.h:54 Initializing cryptonote protocol…
2022-02-19 02:45:50.676 9548 INFO global src/daemon/protocol.h:59 Cryptonote protocol initialized OK
2022-02-19 02:45:50.692 9548 INFO global src/daemon/p2p.h:64 Initializing p2p server…
2022-02-19 02:45:57.286 9548 INFO global src/daemon/p2p.h:69 p2p server initialized OK
2022-02-19 02:45:57.286 9548 INFO global src/daemon/rpc.h:63 Initializing core RPC server…
2022-02-19 02:45:57.286 9548 INFO global contrib/epee/include/net/http_server_impl_base.h:78 Binding on 127.0.0.1:26968
2022-02-19 02:45:57.286 9548 INFO global contrib/epee/src/net_ssl.cpp:124 Generating SSL certificate
2022-02-19 02:45:58.430 9548 INFO global src/daemon/rpc.h:69 core RPC server initialized OK on port: 26968
2022-02-19 02:45:58.430 9548 INFO global src/daemon/core.h:74 Initializing core…
2022-02-19 02:45:58.430 9548 INFO global src/cryptonote_core/cryptonote_core.cpp:560 Loading blockchain from folder C:\ProgramData\electroneum\lmdb …
2022-02-19 02:46:06.254 9548 INFO global src/cryptonote_core/cryptonote_core.cpp:721 Loading checkpoints
2022-02-19 02:46:06.363 9548 INFO global contrib/epee/src/net_ssl.cpp:124 Generating SSL certificate
2022-02-19 02:46:07.887 9548 INFO global src/daemon/core.h:84 Core initialized OK
2022-02-19 02:46:07.887 9548 INFO global src/daemon/rpc.h:74 Starting core RPC server…
2022-02-19 02:46:07.887 [SRV_MAIN] INFO global src/daemon/rpc.h:79 core RPC server started ok
2022-02-19 02:46:07.934 [SRV_MAIN] INFO global src/daemon/p2p.h:79 Starting p2p net loop…
2022-02-19 02:46:08.941 [P2P7] INFO global src/cryptonote_core/cryptonote_core.cpp:1643 e[1;33m


The daemon will start synchronizing with the network. This may take a long time to complete.

You can set the level of process detailization through “set_log <level|categories>” command,
where is between 0 (no details) and 4 (very verbose), or custom category based levels (eg, *:WARNING).

Use the “help” command to see the list of available commands.
Use "help " to see a command’s documentation.


e[0m
2022-02-19 02:46:09.035 [P2P7] INFO global src/cryptonote_basic/validators.cpp:44 Loading Validator List…
2022-02-19 02:46:09.051 [P2P7] INFO global src/cryptonote_basic/validators.cpp:120 e[1;35mPublic Validators:e[0m
2022-02-19 02:46:09.051 [P2P7] INFO global src/cryptonote_basic/validators.cpp:130 e[1;35mAnon Validators: 24e[0m
2022-02-19 02:46:09.051 [P2P7] INFO global src/cryptonote_basic/validators.h:214 Validators list loaded from JSON endpoint! Refresh in 12 hours
2022-02-19 03:15:45.132 [P2P5] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:389 [67.204.233.176:26967 OUT] Sync data returned a new top block candidate: 1276806 → 1276985 [Your node is 179 blocks (0 days) behind]
SYNCHRONIZATION started
2022-02-19 03:15:49.713 [P2P3] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1522 e[1;33mSynced 1276826/1276985 (99%, 159 left)e[0m
2022-02-19 03:15:53.952 [P2P3] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1522 e[1;33mSynced 1276846/1276985 (99%, 139 left)e[0m
2022-02-19 03:15:57.833 [P2P5] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1522 e[1;33mSynced 1276866/1276985 (99%, 119 left)e[0m
2022-02-19 03:16:01.081 [P2P5] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1522 e[1;33mSynced 1276886/1276985 (99%, 99 left)e[0m
2022-02-19 03:16:04.985 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1522 e[1;33mSynced 1276906/1276985 (99%, 79 left)e[0m
2022-02-19 03:16:08.395 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1522 e[1;33mSynced 1276926/1276985 (99%, 59 left)e[0m
2022-02-19 03:16:12.324 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1522 e[1;33mSynced 1276946/1276985 (99%, 39 left)e[0m
2022-02-19 03:16:17.517 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1522 e[1;33mSynced 1276966/1276985 (99%, 19 left)e[0m
2022-02-19 03:16:20.344 [P2P3] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1522 e[1;33mSynced 1276985/1276985e[0m
2022-02-19 03:16:20.344 [P2P3] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:2180 e[1;32mSYNCHRONIZED OKe[0m
2022-02-19 03:16:20.344 [P2P3] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:2198 e[1;33m


You are now synchronized with the network. You may now start electroneum-wallet-cli.

Use the “help” command to see the list of available commands.
**********************************************************************e[0m
2022-02-19 03:27:47.878 12268 INFO msgwriter src/common/scoped_message_writer.h:103 Blockchain saved
2022-02-19 03:27:53.128 12268 INFO msgwriter src/common/scoped_message_writer.h:103 Height: 1276990/1276990 (100.0%) on mainnet, not mining, net hash 262 H/s, v10, 1(out)+0(in) connections, uptime 0d 0h 41m 55s
2022-02-19 03:27:58.364 12268 INFO msgwriter src/common/scoped_message_writer.h:103 Blockchain saved
2022-02-19 03:28:11.439 12268 INFO msgwriter src/common/scoped_message_writer.h:103 Stop signal sent
2022-02-19 03:28:14.478 [SRV_MAIN] INFO global src/daemon/p2p.h:81 p2p net loop stopped
2022-02-19 03:28:14.509 [SRV_MAIN] INFO global src/daemon/rpc.h:84 Stopping core RPC server…
2022-02-19 03:28:14.509 [SRV_MAIN] INFO global src/daemon/daemon.cpp:217 Node stopped.
2022-02-19 03:28:14.587 [SRV_MAIN] INFO global src/daemon/rpc.h:96 Deinitializing core RPC server…
2022-02-19 03:28:14.592 [SRV_MAIN] INFO global src/daemon/p2p.h:91 Deinitializing p2p…
2022-02-19 03:28:18.623 [SRV_MAIN] INFO global src/daemon/core.h:95 Deinitializing core…
2022-02-19 03:28:18.748 [SRV_MAIN] INFO global src/daemon/protocol.h:76 Stopping cryptonote protocol…
2022-02-19 03:28:18.763 [SRV_MAIN] INFO global src/daemon/protocol.h:80 Cryptonote protocol stopped successfully
2022-02-19 22:02:51.612 10232 INFO logging contrib/epee/src/mlog.cpp:273 New log categories: *:WARNING,net:FATAL,net.http:FATAL,net.ssl:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,serialization:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO
2022-02-19 22:02:51.612 10232 INFO global src/daemon/main.cpp:354 Electroneum ‘Aurora’ (v4.0.0.1-6ebe933c2)
2022-02-19 22:02:51.612 10232 INFO global src/daemon/protocol.h:54 Initializing cryptonote protocol…
2022-02-19 22:02:51.612 10232 INFO global src/daemon/protocol.h:59 Cryptonote protocol initialized OK
2022-02-19 22:02:51.628 10232 INFO global src/daemon/p2p.h:64 Initializing p2p server…
2022-02-19 22:02:56.687 10232 INFO global src/daemon/p2p.h:69 p2p server initialized OK
2022-02-19 22:02:56.687 10232 INFO global src/daemon/rpc.h:63 Initializing core RPC server…
2022-02-19 22:02:56.687 10232 INFO global contrib/epee/include/net/http_server_impl_base.h:78 Binding on 127.0.0.1:26968
2022-02-19 22:02:56.687 10232 INFO global contrib/epee/src/net_ssl.cpp:124 Generating SSL certificate
2022-02-19 22:02:58.159 10232 INFO global src/daemon/rpc.h:69 core RPC server initialized OK on port: 26968
2022-02-19 22:02:58.159 10232 INFO global src/daemon/core.h:74 Initializing core…
2022-02-19 22:02:58.159 10232 INFO global src/cryptonote_core/cryptonote_core.cpp:560 Loading blockchain from folder C:\ProgramData\electroneum\lmdb …
2022-02-19 22:03:05.057 10232 INFO global src/cryptonote_core/cryptonote_core.cpp:721 Loading checkpoints
2022-02-19 22:03:05.167 10232 INFO global contrib/epee/src/net_ssl.cpp:124 Generating SSL certificate
2022-02-19 22:03:07.767 10232 INFO global src/daemon/core.h:84 Core initialized OK
2022-02-19 22:03:07.767 10232 INFO global src/daemon/rpc.h:74 Starting core RPC server…
2022-02-19 22:03:07.767 [SRV_MAIN] INFO global src/daemon/rpc.h:79 core RPC server started ok
2022-02-19 22:03:07.814 [SRV_MAIN] INFO global src/daemon/p2p.h:79 Starting p2p net loop…
2022-02-19 22:03:08.832 [P2P7] INFO global src/cryptonote_core/cryptonote_core.cpp:1643 e[1;33m


The daemon will start synchronizing with the network. This may take a long time to complete.

You can set the level of process detailization through “set_log <level|categories>” command,
where is between 0 (no details) and 4 (very verbose), or custom category based levels (eg, *:WARNING).

Use the “help” command to see the list of available commands.
Use "help " to see a command’s documentation.


e[0m
2022-02-19 22:03:09.004 [P2P7] INFO global src/cryptonote_basic/validators.cpp:44 Loading Validator List…
2022-02-19 22:03:09.004 [P2P7] INFO global src/cryptonote_basic/validators.cpp:120 e[1;35mPublic Validators:e[0m
2022-02-19 22:03:09.004 [P2P7] INFO global src/cryptonote_basic/validators.cpp:130 e[1;35mAnon Validators: 24e[0m
2022-02-19 22:03:09.019 [P2P7] INFO global src/cryptonote_basic/validators.h:214 Validators list loaded from JSON endpoint! Refresh in 12 hours
2022-02-19 22:13:44.312 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:2198 e[1;33m


You are now synchronized with the network. You may now start electroneum-wallet-cli.

Use the “help” command to see the list of available commands.
**********************************************************************e[0m
2022-02-19 22:15:05.909 12368 INFO msgwriter src/common/scoped_message_writer.h:103 Height: 1276990/1276990 (100.0%) on mainnet, not mining, net hash 262 H/s, v10, 0(out)+0(in) connections, uptime 0d 0h 12m 7s

I think the problem is it takes ages to pick up a connection and when it does its only ever has 1 connection in, see below: Is there a way to increase the connections?

Log

2022-02-19 22:02:51.612 I Electroneum ‘Aurora’ (v4.0.0.1-6ebe933c2)
2022-02-19 22:02:51.612 I Initializing cryptonote protocol…
2022-02-19 22:02:51.612 I Cryptonote protocol initialized OK
2022-02-19 22:02:51.628 I Initializing p2p server…
2022-02-19 22:02:56.687 I p2p server initialized OK
2022-02-19 22:02:56.687 I Initializing core RPC server…
2022-02-19 22:02:56.687 I Binding on 127.0.0.1:26968
2022-02-19 22:02:56.687 I Generating SSL certificate
2022-02-19 22:02:58.159 I core RPC server initialized OK on port: 26968
2022-02-19 22:02:58.159 I Initializing core…
2022-02-19 22:02:58.159 I Loading blockchain from folder C:\ProgramData\electroneum\lmdb …
2022-02-19 22:03:05.057 I Loading checkpoints
2022-02-19 22:03:05.167 I Generating SSL certificate
2022-02-19 22:03:07.767 I Core initialized OK
2022-02-19 22:03:07.767 I Starting core RPC server…
2022-02-19 22:03:07.767 I core RPC server started ok
2022-02-19 22:03:07.814 I Starting p2p net loop…
2022-02-19 22:03:08.832 I


The daemon will start synchronizing with the network. This may take a long time to complete.

You can set the level of process detailization through “set_log <level|categories>” command,
where is between 0 (no details) and 4 (very verbose), or custom category based levels (eg, *:WARNING).

Use the “help” command to see the list of available commands.
Use "help " to see a command’s documentation.


2022-02-19 22:03:09.004 I Loading Validator List…
2022-02-19 22:03:09.004 I Public Validators:
2022-02-19 22:03:09.004 I Anon Validators: 24
2022-02-19 22:03:09.019 I Validators list loaded from JSON endpoint! Refresh in 12 hours
2022-02-19 22:13:44.312 I


You are now synchronized with the network. You may now start electroneum-wallet-cli.

Use the “help” command to see the list of available commands.


status
Height: 1276990/1276990 (100.0%) on mainnet, not mining, net hash 262 H/s, v10, 0(out)+0(in) connections, uptime 0d 0h 12m 7s
status
Height: 1276990/1276990 (100.0%) on mainnet, not mining, net hash 262 H/s, v10, 0(out)+0(in) connections, uptime 0d 0h 15m 10s
status
Height: 1276990/1276990 (100.0%) on mainnet, not mining, net hash 262 H/s, v10, 0(out)+0(in) connections, uptime 0d 0h 18m 3s
2022-02-19 22:27:06.537 I [-- OUT] Sync data returned a new top block candidate: 1276990 → 1277553 [Your node is 563 blocks (0 days) behind]
SYNCHRONIZATION started
2022-02-19 22:27:10.307 I Synced 1277010/1277553 (99%, 543 left)
2022-02-19 22:27:12.199 I Synced 1277030/1277553 (99%, 523 left)
2022-02-19 22:27:14.663 I Synced 1277050/1277553 (99%, 503 left)
2022-02-19 22:27:17.152 I Synced 1277070/1277553 (99%, 483 left)
2022-02-19 22:27:21.120 I Synced 1277090/1277553 (99%, 463 left)
2022-02-19 22:27:23.148 I Synced 1277110/1277553 (99%, 443 left)
2022-02-19 22:27:25.900 I Synced 1277130/1277553 (99%, 423 left)
2022-02-19 22:27:31.010 I Synced 1277150/1277553 (99%, 403 left)
2022-02-19 22:27:33.550 I Synced 1277170/1277553 (99%, 383 left)
2022-02-19 22:27:37.266 I Synced 1277190/1277553 (99%, 363 left)
2022-02-19 22:27:49.722 I Synced 1277210/1277553 (99%, 343 left)
2022-02-19 22:27:54.259 I Synced 1277230/1277553 (99%, 323 left)
2022-02-19 22:28:06.526 I Synced 1277250/1277553 (99%, 303 left)
2022-02-19 22:28:09.951 I Synced 1277270/1277553 (99%, 283 left)
2022-02-19 22:28:13.289 I Synced 1277290/1277553 (99%, 263 left)
2022-02-19 22:28:18.443 I Synced 1277310/1277553 (99%, 243 left)
2022-02-19 22:28:27.677 I Synced 1277330/1277554 (99%, 224 left)
2022-02-19 22:28:31.123 I Synced 1277350/1277554 (99%, 204 left)
2022-02-19 22:28:34.188 I Synced 1277370/1277554 (99%, 184 left)
2022-02-19 22:28:37.880 I Synced 1277390/1277554 (99%, 164 left)
2022-02-19 22:28:41.792 I Synced 1277410/1277554 (99%, 144 left)
2022-02-19 22:28:50.343 I Synced 1277430/1277554 (99%, 124 left)
2022-02-19 22:28:53.757 I Synced 1277450/1277554 (99%, 104 left)
2022-02-19 22:28:58.698 I Synced 1277470/1277554 (99%, 84 left)
2022-02-19 22:29:01.985 I Synced 1277490/1277554 (99%, 64 left)
2022-02-19 22:29:05.309 I Synced 1277510/1277554 (99%, 44 left)
2022-02-19 22:29:09.086 I Synced 1277530/1277554 (99%, 24 left)
2022-02-19 22:29:12.563 I Synced 1277550/1277554 (99%, 4 left)
2022-02-19 22:29:14.160 I Synced 1277553/1277554 (99%, 1 left)
2022-02-19 22:29:16.543 I Synced 1277554/1277554
2022-02-19 22:29:16.544 I SYNCHRONIZED OK
status
Height: 1277555/1277555 (100.0%) on mainnet, not mining, net hash 275 H/s, v10, 1(out)+0(in) connections, uptime 0d 0h 26m 51s

If memory serves me right, it gets a list of peers when you start. Not sure why you would not be able to connect, as its very unlikely the peers will have banned your node. Usually this is firewall type issues but you seem confident its not.

Try stopping your node and deleting the p2pstate.bin file (this has your known peers). Then restart.

See if that helps.

I think there is a --add-peer command to start electroneumd with a trusted peer. That might also help if you have an IP you know works.

I had issues with connectivity as well if I didn’t use it for a while it would take several attempts to connect and had to mess around with it many times. The blockchain is a huge size now as well so I actually stopped using it. Its easier to keep the coins on the exchange or on a few exchanges plus the mobile app. Even paper is better I think. That way the process isn’t always hogging resources on the computer.

I just tested my node and it is syncing ok. If you are running MS Windows then the CPU & I/O usage is high now. Just watch your local resources as high page faults can cause other issues.

I just spent some time analysing the resource usage and it’s quite interesting. There is a high number of page faults on the daemon at circa 500 Hard Faults/sec. I then asked MS Windows to analyse the wait chain and is stated three threads were waiting to finish network I/O. I also noticed that when the daemon is synced the memory usage grows quite considerably and we are talking in GB numbers. Once the daemon is synced, as expected, the page faults drop to 0.

The most concerning finding, is the memory is not released after the sync. If I close the daemon the memory is released. If I then start the daemon it does not consume memory as it does not have to sync.

Therefore, based on this analysis I have come to the conclusion there is a memory leak/flush-issue in the sync process.

This should be fixed.

In the meantime I would keep any eye on the memory and restart the daemon when you start running of memory. To be clear this problem will only occur when do a large sync.

1 Like

Yeah thanks for that. Very good advice. I have an old machine so it is really struggling . What u describe makes perfect sense.

Its easier to keep the coins on the exchange or on a few exchanges plus the mobile app.

The entire crypto community is scattered with the financial corpses of people who thought it was better/easier to leave coins on centralised platforms like exchanges.

Only keep coins on exchanges when you are exchanging them. Even top ones, who have insurance or say they keep the majority in cold storage… dont use them as storage.

Like you said, paper wallet is the best option. Anyone can make a paper wallet in a few clicks whilst the computer is offline, use something like 7zip to encrypt the PDF with a password and put on a few memory sticks and put in several safe places. Then send your coins to the public address and know it can never be hacked, lost, blocked due to regulation or have someone exit sca m with them.

If someone does want to keep their coins on CLI or Desktop, they can run a node, or just use a public node so they dont need to have the whole blockchain running.

CLI/GUI is not as safe as paper but with a few precautions a much better option than leaving on exchange. Fingers crossed we finally get hardware wallet integration for CLI/GUI this year to make it much much more secure.

Be safe people. :+1:

2 Likes

I deleted the p2pstate.bin file, restarted my system and now haven’t been able to sync / download blocks since.

Would be handy to have the commands to establish connections.

1 Like

electroneumd.exe --help
from command line (whilst in the directory of the executable obviously) will give you all the commands you can use to start the node.

(grab the bin file from recycle bin and replace the new one if you wish to keep that, but shoudlnt make any difference :+1: )

1 Like

What would you recommend setting as the total number of peers for in and out with these commands?:

electroneumd.exe --in-peers=?

electroneumd.exe --out-peers=?

Defaults fine. No need to hardcode a max number unless you wanted to limit how many.

1 Like