electroneumd not syncing with network about electroneum

[electroneumRepo]

@electroneumRepo Does starting this way limit us to only a single peer? Is there a better way to start the service as I never saw more than one peer when running sync_info

By using --add-exclusive-node this does limit to a single peer.

Using --add-peer would possibly be the better option. We are currently looking into why some people are unable to sync to the Blockchain.

[tlangdon123]

~/SourceCode/electroneum/electroneumd --add-exclusive-node 76.91.14.76:26967

Mine is ~/Downloads/electroneum/electroneumd --add-exclusive-node 76.91.14.76:26967 SourceCode is just a folder that hosts the folder that you have your electroneumd file in. I hope this helps. Sincerely, Terry Langdon

…

On Nov 26, 2017, at 3:26 PM, ryczo ***@***.***> wrote: When I ann this ~/SourceCode/electroneum/electroneumd --add-exclusive-node 76.91.14.76:26967 commant there is info unknown command in console — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[truth3]

@tmloc I am also having the same trouble. It looks like this was also reported on #1 so I am going to try and understand the steps taken to see if it resolves for me as well.

[truth3]

@tmloc So the suggestion from CryptoSiD worked for me as well (running Mac OS). I ran the following command from my terminal and it immediately moves past the sticking point.

~/SourceCode/electroneum/electroneumd --add-exclusive-node 76.91.14.76:26967

Log output

2017-11-25 15:40:42.046	[P2P9]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:302	[76.91.14.76:26967 OUT] Sync data returned a new top block candidate: 1 -> 40108 [Your node is 40107 blocks (27 days) behind] 
SYNCHRONIZATION started

Make sure to also quit the sync and restart it without that option so you pick up more than one peer.

[tmloc]

Thank you a lot for the advise!

[tmloc]

It works now!

[truth3]

@electroneumRepo Does starting this way limit us to only a single peer? Is there a better way to start the service as I never saw more than one peer when running sync_info

[truth3]

@tmloc Make sure to quit and restart without that additional parameter defined so you pick up more peers.

[tlangdon123]

that worked for me too... taking forever to snyc... thank you

[ryczo]

When I andd this ~/SourceCode/electroneum/electroneumd --add-exclusive-node 76.91.14.76:26967 to console there is error unknown command

[visualarttech01]

---

Error: wallet failed to connect to daemon: http://localhost:26968. Daemon either is not started or wrong port was passed. Please make sure daemon is running or restart the wallet with the correct daemon address.
Error: wallet failed to connect to daemon: http://localhost:26968. Daemon either is not started or wrong port was passed. Please make sure daemon is running or restart the wallet with the correct daemon address.

[electroneumRepo]

@visualarttech01 You need to run the daemon and ensure that it is synced with the blockchain before attempting to run the wallet.

[Vande0889]

I've tried going into powershell and entering in what I believe to be a good peer from my laptop which does sync with the node (I'm a noob at this stuff) and this is what I get. I can't for the life of me get electroneumd to sync with the node on my desktop. I have tried both "--add-peer" and "--add-exclusive-node". Same result. Please help.

PS C:\Users\wildw\Desktop\MINER> ./electroneumd.exe --add-peer 24.35.246.174:26967
2017-12-08 00:58:42.375 13152 INFO global src/daemon/main.cpp:279 Electroneum 'Helium Hydra' (v0.11.0.0-53f8b3fa)
2017-12-08 00:58:42.375 13152 INFO global src/daemon/protocol.h:55 Initializing cryptonote protocol...
2017-12-08 00:58:42.375 13152 INFO global src/daemon/protocol.h:60 Cryptonote protocol initialized OK
2017-12-08 00:58:42.376 13152 INFO global src/daemon/p2p.h:63 Initializing p2p server...
2017-12-08 00:58:46.467 13152 INFO global src/daemon/p2p.h:68 P2p server initialized OK
2017-12-08 00:58:46.468 13152 INFO global src/daemon/rpc.h:58 Initializing core rpc server...
2017-12-08 00:58:46.472 13152 INFO global contrib/epee/include/net/http_server_impl_base.h:70 Binding on 127.0.0.1:26968
2017-12-08 00:58:46.473 13152 INFO global src/daemon/rpc.h:63 Core rpc server initialized OK on port: 26968
2017-12-08 00:58:46.474 13152 INFO global src/daemon/core.h:73 Initializing core...
2017-12-08 00:58:46.476 13152 INFO global src/cryptonote_core/cryptonote_core.cpp:323 Loading blockchain from folder C:\ProgramData\electroneum\lmdb ...
2017-12-08 00:58:46.604 13152 INFO global src/cryptonote_core/cryptonote_core.cpp:421 Loading checkpoints
2017-12-08 00:58:46.610 13152 WARN net.dns src/common/dns_utils.cpp:487 WARNING: no two valid ElectroneumPulse DNS checkpoint records were received
2017-12-08 00:58:46.611 13152 INFO global src/daemon/core.h:78 Core initialized OK
2017-12-08 00:58:46.611 13152 INFO global src/daemon/rpc.h:68 Starting core rpc server...
2017-12-08 00:58:46.611 [SRV_MAIN] INFO global src/daemon/rpc.h:73 Core rpc server started ok
2017-12-08 00:58:46.612 [SRV_MAIN] INFO global src/daemon/p2p.h:78 Starting p2p net loop...
2017-12-08 00:58:46.613 [P2P0] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:302 [37.110.66.43:57600 INC] Sync data returned a new top block candidate: 10449 -> 57721 [Your node is 47272 blocks (32 days) behind]
SYNCHRONIZATION started
2017-12-08 00:58:47.612 [P2P0] INFO global src/cryptonote_core/cryptonote_core.cpp:1247

---

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.

---

2017-12-08 00:58:47.620 [P2P0] WARN net.dns src/common/dns_utils.cpp:487 WARNING: no two valid ElectroneumPulse DNS checkpoint records were received
2017-12-08 00:59:18.616 [P2P4] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:302 [164.132.202.168:26967 OUT] Sync data returned a new top block candidate: 10449 -> 57723 [Your node is 47274 blocks (32 days) behind]
SYNCHRONIZATION started
sync_info
Height: 10449, target: 57723 (18.102%)
Downloading at 394 kB/s
2 peers
164.132.202.168:26967 58881eca3ed6db3c 57723 394 kB/s, 0 blocks / 0 MB queued
50.93.46.138:26967 0000000000000000 0 0 kB/s, 0 blocks / 0 MB queued
0 spans, 0 MB
sync_i2017-12-08 01:00:00.540 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:302 [37.110.66.43:26967 OUT] Sync data returned a new top block candidate: 10449 -> 57724 [Your node is 47275 blocks (32 days) behind]
SYNCHRONIZATION started
nfo
Height: 10449, target: 57724 (18.1017%)
Downloading at 296 kB/s
4 peers
37.110.66.43:26967 0dcd4a5d0c6b172f 57724 38 kB/s, 0 blocks / 0 MB queued
110.146.152.207:26967 0000000000000000 0 0 kB/s, 0 blocks / 0 MB queued
110.146.152.207:51699 7975e5a7687871bf 57723 0 kB/s, 0 blocks / 0 MB queued
188.234.82.49:26967 adc0a56d8ce0fee8 57723 258 kB/s, 0 blocks / 0 MB queued
1 spans, 0 MB
37.110.66.43:26967 100 (10450 - 10549) -
sync_info
Height: 10449, target: 57724 (18.1017%)
Downloading at 1138 kB/s
7 peers
80.209.235.232:26967 ee9176d4b62a99ec 57724 213 kB/s, 0 blocks / 0 MB queued
213.248.40.9:26967 378813852e38ba94 57724 10 kB/s, 0 blocks / 0 MB queued
164.132.202.168:26967 58881eca3ed6db3c 57724 87 kB/s, 0 blocks / 0 MB queued
178.148.213.170:65154 0000000000000000 0 0 kB/s, 0 blocks / 0 MB queued
37.110.66.43:26967 0dcd4a5d0c6b172f 57724 397 kB/s, 0 blocks / 0 MB queued
110.146.152.207:51699 7975e5a7687871bf 57724 34 kB/s, 0 blocks / 0 MB queued
50.93.46.138:26967 bf43599e717596be 57724 397 kB/s, 0 blocks / 0 MB queued
4 spans, 0 MB
80.209.235.232:26967 100 (750 - 849) -
110.146.152.207:51699 100 (10450 - 10549) -
164.132.202.168:26967 100 (10550 - 10649) -
80.209.235.232:26967 100 (10650 - 10749) -
2017-12-08 01:01:31.941 [P2P4] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:302 [67.1.197.30:56768 INC] Sync data returned a new top block candidate: 10449 -> 57724 [Your node is 47275 blocks (32 days) behind]
SYNCHRONIZATION started
sync_info
Height: 10449, target: 10449 (100%)
Downloading at 0 kB/s
0 peers
0 spans, 0 MB
2017-12-08 01:01:55.170 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:302 [176.112.8.13:26967 OUT] Sync data returned a new top block candidate: 10449 -> 57725 [Your node is 47276 blocks (32 days) behind]

[Vande0889]

So what does that mean? In laymen’s terms as I’m a noob and this is a foreign language to me. I would assume the nodes shouldn’t be dead? How could they be if they are apart of the Blockchain?

…

On Sun, Dec 17, 2017 at 2:41 AM RealAwkwardPig ***@***.***> wrote: I'm also unable to sync, 3 days and still nothing. Built 2769728 <2769728> from source. Had a look into it... https://github.com/electroneum/electroneum/blob/master/src/p2p/net_node.inl#L407 All these seed nodes are dead. Don't respond to ping or on that port. https://github.com/electroneum/electroneum/blob/master/src/p2p/net_node.h#L133 Are also dead, nonexistent hostnames. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgxBhp_0sUcAy-MGT8yKcVoZuANSt9YXks5tBNOcgaJpZM4QqcO_> .

[RealAwkwardPig]

My issue was a router bug with upnp causing it to block everything (those IPs are still valid, at least some of them. The hostnames are still nonexistent though). You could try one of these nodes:

128.71.100.93:26967
13.125.37.208:26967
13.125.50.165:26967
13.124.43.88:26967
34.240.247.44:26967
34.197.74.127:26967
34.250.126.109:26967

[Vande0889]

No kidding? I would have never thought of a router issue. My laptop syncs just fine. It’s on WiFi. My desktop with the issue is on wired connection. Would turning upnp off solve the issue? I’ve tried using a node from my laptop and it’s like my desktop tries to sync and then it fails moments later. What’s the best way to enter these nodes?

…

On Thu, Dec 21, 2017 at 11:40 AM RealAwkwardPig ***@***.***> wrote: My issue was a router bug with upnp causing it to block everything (those IPs are still valid, at least some of them. The hostnames are still nonexistent though). You could try one of these nodes: 128.71.100.93:2696713.125.37.208:2696713.125.50.165:2696713.124.43.88:2696734.240.247.44:2696734.197.74.127:2696734.250.126.109:26967 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgxBhgLsjR9pfvGbNWfA9qsORWQ-WMnwks5tCpgcgaJpZM4QqcO_> .

[Vande0889]

I had to go into C:\ProgramData\electroneum and deleted that whole file. Then I started up electroneumd app and it finally synced to the node. Being 50 days behind, it took awhile, but it worked lol. That's been driving me bonkers for weeks.

[browolf]

Resetting my router fixed the problem I had with this. I guess upnp had temporarily broken. I have a Zyxel VMG1312 router, periodically it does need resetting.

[jpmoriarty]

I have the same issue - I deleted the MDB file in the electroneum folder and let it sync up again (which took a few days), but it's got to a point that it can't get past again. I leave it running and all I get are entries indicating a new top block has been found. Have reset the router and that's not the issue either. Currently stuck about 1,600 blocks behind. Any suggestions?

2018-03-30 12:30:56.195 3356    INFO    global  src/daemon/main.cpp:279 Electroneum 'Helium Hydra' (v0.11.0.0-53f8b3fa)
2018-03-30 12:30:56.195 3356    INFO    global  src/daemon/protocol.h:55        Initializing cryptonote protocol...
2018-03-30 12:30:56.195 3356    INFO    global  src/daemon/protocol.h:60        Cryptonote protocol initialized OK
2018-03-30 12:30:56.195 3356    INFO    global  src/daemon/p2p.h:63     Initializing p2p server...
2018-03-30 12:30:57.555 3356    INFO    global  src/daemon/p2p.h:68     P2p server initialized OK
2018-03-30 12:30:57.555 3356    INFO    global  src/daemon/rpc.h:58     Initializing core rpc server...
2018-03-30 12:30:57.555 3356    INFO    global  contrib/epee/include/net/http_server_impl_base.h:70  Binding on 127.0.0.1:26968
2018-03-30 12:30:57.555 3356    INFO    global  src/daemon/rpc.h:63     Core rpc server initialized OK on port: 26968
2018-03-30 12:30:57.555 3356    INFO    global  src/daemon/core.h:73    Initializing core...
2018-03-30 12:30:57.555 3356    INFO    global  src/cryptonote_core/cryptonote_core.cpp:323     Loading blockchain from folder C:\ProgramData\electroneum\lmdb ...
2018-03-30 12:30:57.570 3356    WARN    blockchain.db.lmdb      src/blockchain_db/lmdb/db_lmdb.cpp:1155 LMDB memory map needs to be resized, doing that now.
2018-03-30 12:30:57.570 3356    INFO    global  src/blockchain_db/lmdb/db_lmdb.cpp:494  LMDB Mapsize increased.  Old: 17246MiB, New: 18270MiB
2018-03-30 12:30:57.633 3356    INFO    global  src/cryptonote_core/cryptonote_core.cpp:421     Loading checkpoints
2018-03-30 12:30:57.680 3356    WARN    net.dns src/common/dns_utils.cpp:487    WARNING: no two valid ElectroneumPulse DNS checkpoint records were received
2018-03-30 12:30:57.680 3356    INFO    global  src/daemon/core.h:78    Core initialized OK
2018-03-30 12:30:57.680 3356    INFO    global  src/daemon/rpc.h:68     Starting core rpc server...
2018-03-30 12:30:57.680 [SRV_MAIN]      INFO    global  src/daemon/rpc.h:73     Core rpc server started ok
2018-03-30 12:30:57.680 [SRV_MAIN]      INFO    global  src/daemon/p2p.h:78     Starting p2p net loop...
2018-03-30 12:30:58.680 [P2P7]  INFO    global  src/cryptonote_core/cryptonote_core.cpp:1247    �[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 <level> 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.
**********************************************************************
�[0m
2018-03-30 12:30:58.680 [P2P7]  WARN    net.dns src/common/dns_utils.cpp:487    WARNING: no two valid ElectroneumPulse DNS checkpoint records were received
2018-03-30 12:30:59.367 [P2P6]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:1540    �[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.
**********************************************************************�[0m
2018-03-30 12:31:00.820 [P2P9]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:302     [182.239.131.19:26967 OUT] Sync data returned a new top block candidate: 202612 -> 219408 [Your node is 16796 blocks (11 days) behind]
SYNCHRONIZATION started
2018-03-30 12:31:33.789 [P2P4]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:302     [94.130.175.0:40206 INC] Sync data returned a new top block candidate: 202612 -> 219409 [Your node is 16797 blocks (11 days) behind]
SYNCHRONIZATION started
2018-03-30 12:32:48.118 [P2P8]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:302     [91.139.128.190:26967 OUT] Sync data returned a new top block candidate: 202612 -> 219409 [Your node is 16797 blocks (11 days) behind]
SYNCHRONIZATION started
2018-03-30 12:33:49.040 [P2P7]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:302     [91.139.128.190:26967 OUT] Sync data returned a new top block candidate: 202612 -> 219411 [Your node is 16799 blocks (11 days) behind]
SYNCHRONIZATION started
2018-03-30 12:34:58.166 [P2P7]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:302     [54.37.70.137:26967 OUT] Sync data returned a new top block candidate: 202612 -> 219412 [Your node is 16800 blocks (11 days) behind]
SYNCHRONIZATION started
2018-03-30 12:36:53.823 [P2P0]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:302     [91.197.188.117:64911 INC] Sync data returned a new top block candidate: 202612 -> 219415 [Your node is 16803 blocks (11 days) behind]
SYNCHRONIZATION started
2018-03-30 12:38:07.558 [P2P5]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:302     [54.37.70.135:26967 OUT] Sync data returned a new top block candidate: 202612 -> 219415 [Your node is 16803 blocks (11 days) behind]
SYNCHRONIZATION started
2018-03-30 12:38:16.527 [P2P8]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:302     [178.206.201.76:26967 OUT] Sync data returned a new top block candidate: 202612 -> 219416 [Your node is 16804 blocks (11 days) behind]
SYNCHRONIZATION started
2018-03-30 12:39:30.434 [P2P3]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:302     [178.206.201.76:26967 OUT] Sync data returned a new top block candidate: 202612 -> 219416 [Your node is 16804 blocks (11 days) behind]
SYNCHRONIZATION started
2018-03-30 12:40:43.888 [P2P5]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:302     [34.200.213.65:52768 INC] Sync data returned a new top block candidate: 202612 -> 219418 [Your node is 16806 blocks (11 days) behind]
SYNCHRONIZATION started
2018-03-30 12:41:00.950 [P2P2]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:302     [174.114.96.232:26967 OUT] Sync data returned a new top block candidate: 202612 -> 219418 [Your node is 16806 blocks (11 days) behind]
SYNCHRONIZATION started
2018-03-30 12:41:17.497 [P2P1]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:302     [72.251.232.164:54549 INC] Sync data returned a new top block candidate: 202612 -> 219419 [Your node is 16807 blocks (11 days) behind]
SYNCHRONIZATION started
2018-03-30 12:42:15.006 [P2P5]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:302     [45.79.210.48:54310 OUT] Sync data returned a new top block candidate: 202612 -> 219420 [Your node is 16808 blocks (11 days) behind]
SYNCHRONIZATION started

[TheNaterz]

@jpmoriarty I'm seeing the exact same thing on my end as well, stuck on the same block too.

[TheNaterz]

Ah I totally forgot about this.

https://electroneum101.com/the-electroneum-block-202612-bug-what-you-should-know/

Fix is get the latest release: https://github.com/electroneum/electroneum/releases/tag/v0.11.0.0-revert

[jpmoriarty]

Ah I'd read about that but didn't think it would just bung up my daemon. That article is theoretical about a fix - is there not one yet? Is there a new daemon I can get that will get me past that block? Thanks John

…

On Sun, 1 Apr 2018, 06:04 Nate Caroe, ***@***.***> wrote: Ah I totally forgot about this. https://electroneum101.com/the-electroneum-block-202612-bug-what-you-should-know/ — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AkLLgzk-EFLt54RiVL7xHU5QanEDA1UPks5tkF_0gaJpZM4QqcO_> .

[TheNaterz]

Fix is get the latest release: https://github.com/electroneum/electroneum/releases/tag/v0.11.0.0-revert

[jpmoriarty]

Humm; have downloaded that and run the new daemon, but still not making any progress. Do I need to delete and restart the blockchain sync from scratch? Would rather not have to, as it takes forever to sync and then am not entirely confident it won't get stuck again!

…

On 1 April 2018 at 08:41, Nate Caroe ***@***.***> wrote: Fix is get the latest release: https://github.com/electroneum/electroneum/ releases/tag/v0.11.0.0-revert — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AkLLgxY8NW_Q4TRIJ2vtTZmjMrzaTFXkks5tkISegaJpZM4QqcO_> .

-- *John* 0779 271 4045 | [email protected]

[TheNaterz]

Maybe? I did just in case and it synced past the problem block. Try a full system restart. If it doesn't push past, then try from scratch.

[Unyxos]

If I’m right you can delete X past blocks to re-download them and then sync without any problem, don’t remember the command but, explore other issues or search for “pop” in the issues search bar ;) Le 1 avr. 2018 à 10:05 +0200, Nate Caroe <[email protected]>, a écrit :

…

Maybe? I did just in case and it synced past the problem block. Try a full system restart. If it doesn't push past, then try from scratch. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[jpmoriarty]

am deleting the DB and starting again, will see if that helps. is there no way to download a blockchain so I can start a little closer to now than day 0??! If there's a way to roll back blocks, as described above, that would also be handy...

…

On 1 April 2018 at 09:32, Corentin Closs ***@***.***> wrote: If I’m right you can delete X past blocks to re-download them and then sync without any problem, don’t remember the command but, explore other issues or search for “pop” in the issues search bar ;) Le 1 avr. 2018 à 10:05 +0200, Nate Caroe ***@***.***>, a écrit : > Maybe? I did just in case and it synced past the problem block. Try a full system restart. If it doesn't push past, then try from scratch. > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub, or mute the thread. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AkLLg2YQcMPLr31_I904PduWTQXnM5zkks5tkJCtgaJpZM4QqcO_> .

-- *John* 0779 271 4045 | [email protected]

[brankoko]

Hi guys!

Can someone please help me with my issue; about half of month ago I sent my ETN from Kucoin to my local address. Transaction may be seen on a blockchain explorer with Tx hash: 08f440ab66477b808577c22e54a70cb6591c08450503f5ba068dfc16db4eef5a and Tx public key: 09dfa09cb793667fc2d94095335a4c09823cc08d452d616d5eb637a85dcb13b9.

Problem is that I can not synchronize daemon - instead coming closer to the end of a process it actually goes further away. I've tried many thing; first I left my computer for a few day in a row, then I issued command ectroneumd --db-sync-mode =fastest:sync:100 with the same result. I was looking all over the Internet with no answer. I've tried to contact support - maybe they'll help, who knows...
Right now I'm trying to salvage a database with command: electroneumd --db-salvage, but looks to me that this will give a same results.
Now I decided to try again, erased a database and lock and start all over again. But - if someone has some useful idea - please do tell me - I'll pay you a coffee :)

[Unyxos]

Hey Brankoko, have you tried to download the latest software release? (v0.11.0.0 revert v3)? Le 2 avr. 2018 à 18:48 +0200, brankoko <[email protected]>, a écrit :

…

Hi guys! Can someone please help me with my issue; about half of month ago I sent my ETN from Kucoin to my local address. Transaction may be seen on a blockchain explorer with Tx hash: 08f440ab66477b808577c22e54a70cb6591c08450503f5ba068dfc16db4eef5a and Tx public key: 09dfa09cb793667fc2d94095335a4c09823cc08d452d616d5eb637a85dcb13b9. Problem is that I can not synchronize daemon - instead coming closer to the end of a process it actually goes further away. I've tried many thing; first I left my computer for a few day in a row, then I issued command ectroneumd --db-sync-mode =fastest:sync:100 with the same result. I was looking all over the Internet with no answer. I've tried to contact support - maybe they'll help, who knows... Right now I'm trying to salvage a database with command: electroneumd --db-salvage, but looks to me that this will give a same results. Now I decided to try again, erased a database and lock and start all over again. But - if someone has some useful idea - please do tell me - I'll pay you a coffee :) — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[brankoko]

Hello Corentin! Yes, I did. Last night (around 22 UTC+2) I deleted the database and started all over again. This morning, around 7 o'clock a process was above 80000. So it is possible that this time everything's going to be fine.I'll give it a few days... Best regards, Branislav Konjevic 2018-04-02 20:31 GMT+02:00 Corentin Closs <[email protected]>:

…

Hey Brankoko, have you tried to download the latest software release? (v0.11.0.0 revert v3)? Le 2 avr. 2018 à 18:48 +0200, brankoko ***@***.***>, a écrit : > Hi guys! > Can someone please help me with my issue; about half of month ago I sent my ETN from Kucoin to my local address. Transaction may be seen on a blockchain explorer with Tx hash: 08f440ab66477b808577c22e54a70c b6591c08450503f5ba068dfc16db4eef5a and Tx public key: 09dfa09cb793667fc2d94095335a4c09823cc08d452d616d5eb637a85dcb13b9. > Problem is that I can not synchronize daemon - instead coming closer to the end of a process it actually goes further away. I've tried many thing; first I left my computer for a few day in a row, then I issued command ectroneumd --db-sync-mode =fastest:sync:100 with the same result. I was looking all over the Internet with no answer. I've tried to contact support - maybe they'll help, who knows... > Right now I'm trying to salvage a database with command: electroneumd --db-salvage, but looks to me that this will give a same results. > Now I decided to try again, erased a database and lock and start all over again. But - if someone has some useful idea - please do tell me - I'll pay you a coffee :) > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub, or mute the thread. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/APPXMQ_LeiDGfriD8Gdz423z6mZH4x5Qks5tkm5rgaJpZM4QqcO_> .

[amarendar-musham]

Is there anyway that electroneum deamon can sync faster with blockchain.

2018-06-02 04:19:16.707 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1152 [79.184.205.240:26967 OUT] Synced 14801/307511
2018-06-02 04:19:23.502 [P2P7] WARN global src/cryptonote_protocol/cryptonote_protocol_handler.inl:273 [159.89.130.89:44080 OUT] peer claims higher version that we think - we may be forked from the network and a software upgrade may be needed

some getting these type of errors. can anyone suggest me what i can do to get better performance

[brankoko]

I've finally succeeded to receive this … then sent it to the exchange and sell it. I don't want to hear about it anymore. Wish you all the luck. sub, 2. lip 2018. 06:19 Amarendar M <[email protected]> je napisao:

…

Is there anyway that electroneum deamon can sync faster with blockchain. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/APPXMRW2QZ4c63Fj9kgr5mdK1qZBmKKvks5t4hJMgaJpZM4QqcO_> .