search

letheanVPN / blockchain-iz

Lethean/IntenseCoin(ITNS) fork of the original CryptonoteFoundation project.
Other
109 stars 33 forks source link

Daemon stuck after x hours #96

Closed uekdyr closed 6 years ago

uekdyr commented 6 years ago

Anyone else having issues that the daemon syncs with the blockchain on startup but after a while (maybe 3h) it for some reason stays on the same height and won't sync to the new height. If I restart the daemon it syncs successfully and then after a couple of hours it gets stuck once again.

On "set_log 3" I have one error "Failed to check ringct signatures"

Any ideas?

valiant1x commented 6 years ago

Please try using PR #98:

git fetch origin
git checkout -b 202-stage origin/202-stage
segredor commented 6 years ago

I'm stuck.

Height: 169334/179109 (94.5%) on mainnet, not mining, net hash 2.29 MH/s, v4, up to date, 3(out)+0(in) connections, uptime 0d 0h 33m 53s

Network status is Synchronizing with Blocks remaining: 9775 since yesterday. I just upgraded from 1.4.1 to the newer client I think is 2.0 but i don't see where to find the version #.

Also see this: 2018-05-05 15:16:28.954 [P2P8] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [13.81.124.112:48772 OUT] Sync data returned a new top block candidate: 169334 -> 179109 [Your node is 9775 blocks (13 days) behind] SYNCHRONIZATION started

11:50am: I just deleted the db and tried to let it sync again. Stuck:

2018-05-05 15:48:59.402 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1154 [203.162.53.156:48772 OUT] Synced 159191/179109 2018-05-05 15:49:00.185 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1154 [203.162.53.156:48772 OUT] Synced 159291/179109 2018-05-05 15:49:00.936 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1154 [203.162.53.156:48772 OUT] Synced 159391/179109 2018-05-05 15:49:01.700 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1154 [203.162.53.156:48772 OUT] Synced 159491/179109 2018-05-05 15:49:02.388 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1154 [203.162.53.156:48772 OUT] Synced 159591/179109 2018-05-05 15:49:03.319 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1154 [203.162.53.156:48772 OUT] Synced 159691/179109 2018-05-05 15:49:04.015 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1154 [203.162.53.156:48772 OUT] Synced 159791/179109 2018-05-05 15:49:04.857 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1154 [203.162.53.156:48772 OUT] Synced 159891/179109 2018-05-05 15:49:05.518 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1154 [203.162.53.156:48772 OUT] Synced 159991/179109

uekdyr commented 6 years ago

@segredor Run your daemon with "--add-exclusive-node 140.82.9.90:48772 --add-exclusive-node 62.48.164.60:48772 --add-exclusive-node 5.249.27.162:48772"

Since your daemon is trying to sync the old V3.

Currently, the blockchain height is "177164" and not "179109" as in your case.

valiant1x commented 6 years ago

@segredor Version number of the daemon is the first log line displayed when you run the program. Use the params suggested by uekdyr.

valiant1x commented 6 years ago

@uekdyr if your original issue was resolved please indicate how/why and close the issue

uekdyr commented 6 years ago

@valiant1x Still waiting, since it happened randomly I'll run the daemon for 24h, if it syncs the whole time without restart I'll close the issue.

Cheers!

segredor commented 6 years ago

So after deleting the db at 11:50am, the sync got a little further, then got stuck at 167915 -> 177203.

2018-05-05 16:45:05.111 [P2P8] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [13.81.124.112:48772 OUT] Sync data returned a new top block candidate: 167915 -> 179109 [Your node is 11194 blocks (15 days) behind] SYNCHRONIZATION started 2018-05-05 16:46:18.312 [P2P6] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [5.66.19.197:48772 OUT] Sync data returned a new top block candidate: 167915 -> 179109 [Your node is 11194 blocks (15 days) behind] SYNCHRONIZATION started 2018-05-05 16:47:45.033 [P2P6] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [51.7.32.175:48772 OUT] Sync data returned a new top block candidate: 167915 -> 177190 [Your node is 9275 blocks (12 days) behind] SYNCHRONIZATION started 2018-05-05 16:52:52.018 [P2P2] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [13.81.124.112:48772 OUT] Sync data returned a new top block candidate: 167915 -> 179109 [Your node is 11194 blocks (15 days) behind] SYNCHRONIZATION started 2018-05-05 17:06:35.153 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [121.134.79.90:48772 OUT] Sync data returned a new top block candidate: 167915 -> 177197 [Your node is 9282 blocks (12 days) behind] SYNCHRONIZATION started 2018-05-05 17:13:58.124 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [208.115.99.177:48772 OUT] Sync data returned a new top block candidate: 167915 -> 177203 [Your node is 9288 blocks (12 days) behind]

segredor commented 6 years ago

@uekdyr Ok just did it and I think it is progressing. I'll report back when it is done.

segredor commented 6 years ago

@uekdyr stuck again.

I was out for a few hours and found it stuck upon returning.

2018-05-05 17:43:35.899 [P2P3] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1154 [140.82.9.90:48772 OUT] Synced 168715/177213 2018-05-05 17:43:58.800 [P2P4] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1154 [140.82.9.90:48772 OUT] Synced 168815/177213 2018-05-05 17:44:22.892 [P2P8] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1154 [140.82.9.90:48772 OUT] Synced 168915/177213 2018-05-05 17:44:41.426 [P2P2] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1154 [140.82.9.90:48772 OUT] Synced 169015/177213 2018-05-05 17:45:15.983 [P2P4] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [62.48.164.60:48772 OUT] Sync data returned a new top block candidate: 169015 -> 177214 [Your node is 8199 blocks (11 days) behind]

This is about where is stopped sync'ing and started doing the following:

SYNCHRONIZATION started 2018-05-05 17:46:01.366 [P2P4] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1154 [140.82.9.90:48772 OUT] Synced 169115/177214 2018-05-05 17:46:30.646 [P2P4] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1154 [140.82.9.90:48772 OUT] Synced 169215/177214 2018-05-05 17:46:58.801 [P2P4] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1154 [140.82.9.90:48772 OUT] Synced 169315/177214 2018-05-05 17:47:19.020 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [62.48.164.60:48772 OUT] Sync data returned a new top block candidate: 169334 -> 177216 [Your node is 7882 blocks (10 days) behind] SYNCHRONIZATION started 2018-05-05 17:48:06.676 [P2P2] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [140.82.9.90:48772 OUT] Sync data returned a new top block candidate: 169334 -> 177217 [Your node is 7883 blocks (10 days) behind] SYNCHRONIZATION started 2018-05-05 17:48:41.821 [P2P6] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [140.82.9.90:48772 OUT] Sync data returned a new top block candidate: 169334 -> 177217 [Your node is 7883 blocks (10 days) behind] SYNCHRONIZATION started 2018-05-05 17:49:14.528 [P2P2] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [140.82.9.90:48772 OUT] Sync data returned a new top block candidate: 169334 -> 177219 [Your node is 7885 blocks (10 days) behind] SYNCHRONIZATION started 2018-05-05 17:49:49.982 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [140.82.9.90:48772 OUT] Sync data returned a new top block candidate: 169334 -> 177219 [Your node is 7885 blocks (10 days) behind]

segredor commented 6 years ago

@uekdyr maybe I didn't put this - --add-exclusive-node 140.82.9.90:48772 --add-exclusive-node 62.48.164.60:48772 --add-exclusive-node 5.249.27.162:48772

in the correct place. Where should I add that?

segredor commented 6 years ago

I just restarted the daemon. It has continued synching...the numbers are increasing again. I'll keep massaging it until it doesn't update anymore or finishes and update this here.

uekdyr commented 6 years ago

@segredor you should use something like this:

If running Linux: ./intensecoind --add-exclusive-node 140.82.9.90:48772 --add-exclusive-node 62.48.164.60:48772 --add-exclusive-node 5.249.27.162:48772

On Windows you open up CMD, go to the path of your intensecoin folder. Then putting "start intensecoind --add-exclusive-node 140.82.9.90:48772 --add-exclusive-node 62.48.164.60:48772 --add-exclusive-node 5.249.27.162:48772"

segredor commented 6 years ago

@uekdyr I have Windows and have that command working correctly.

I'm down to 6 days which is progress but now I get this:

2018-05-05 22:55:08.270 [P2P6] ERROR blockchain src/cryptonote_core/blockchain.cpp:3209 !!!!!!!!! difficulty overhead !!!!!!!!!

segredor commented 6 years ago

@uekdyr I closed the cmd window then launched the daemon from the wallet and it continued sync'ing. Almost done. Your cmd was what got it going...plus massaging it in. Synced 175097/177392

segredor commented 6 years ago

@uekdyr you can close the ticket. Thank you for your help.

You are now synchronized with the network.

uekdyr commented 6 years ago

@segredor Awesome, cheers mate!

@valiant1x Daemon seems to be working fine so far, been running for 12+ hours. Closing the topic now. Thanks for your help!

uekdyr commented 6 years ago

Reopen the issue, it got stuck again after running for about 16 hours :/

Now, with "set_log 3" there's some errors:

1: Output does not exist! Amount = 0 2: Failed to get output keys for tx with amount = 0.0000000 and count indexes 5 3: Failed to check ring signature for tx vin key with k_image: Sig_index: 0 4: pmax_used_block_height: 0 5: Transaction verification failed:

6: Failed to check rinct signatures!

Don't know if these errors are relevant to the issue but posting them either way.

After restarting the daemon it successfully syncs the blockchain again.

valiant1x commented 6 years ago

@uekdyr at this time you seem alone on getting stuck so we will get some info from you next time it becomes stuck again. Please provide the output of the following commands in the daemon: sync_info, print_cn, status

uekdyr commented 6 years ago

@valiant1x Yes, I'll wait for it to get stuck again and then I'll provide the info from the commands you suggested.

valiant1x commented 6 years ago

@uekdyr can you also type help and confirm you're running 2.0.2? if it doesn't show 2.0.2 it's probably just due to a cached version file; you could either a) rebuild from scratch by running make clean first, or b) remove the build/release/version folder and rebuild. if you still don't see 2.0.2 after performing those steps, you aren't in the correct branch (202-stage).

uekdyr commented 6 years ago

@valiant1x Ah shit, yup it said 2.0.1, thought I updated it. Updating now, closing the issue since it probably was the version.

Cheers, thanks for your help!

segredor commented 6 years ago

This is what I see:

help Intensecoin 'Belaya' (v2.0.0.0-06259ac)

From: valiant1x notifications@github.com Sent: Sunday, May 6, 2018 2:47 PM To: valiant1x/intensecoin intensecoin@noreply.github.com Cc: Robert Segredo robert@segredo.us; Mention mention@noreply.github.com Subject: Re: [valiant1x/intensecoin] Daemon stuck after x hours (#96)

@uekdyrhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fuekdyr&data=02%7C01%7C%7Cabf0199585614ea863f508d5b381bc53%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636612292145841278&sdata=TMptAmKoxN9xTm8Textgio4YIFoQfa%2FOIgLcDKWjTIM%3D&reserved=0 can you also type help and confirm you're running 2.0.2? if it doesn't show 2.0.2 it's probably just due to a cached version file; you could either a) rebuild from scratch by running make clean first, or b) remove the build/release/version folder and rebuild. if you still don't see 2.0.2 after performing those steps, you aren't in the correct branch (202-stage).

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fvaliant1x%2Fintensecoin%2Fissues%2F96%23issuecomment-386903149&data=02%7C01%7C%7Cabf0199585614ea863f508d5b381bc53%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636612292145841278&sdata=glkbmn8JGvNYt%2Fzfn1D9ZEsjIpj6%2BkmwBPRmFSf5t8k%3D&reserved=0, or mute the threadhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAhUnl_PVrO_U3B8a48P4UMotL-RnBeBuks5tv0UbgaJpZM4TwiRl&data=02%7C01%7C%7Cabf0199585614ea863f508d5b381bc53%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636612292145841278&sdata=7sTv3tAOWMSLyYDpswd8MxwMYSnYnGgYDwJPLeBMCd4%3D&reserved=0.

valiant1x commented 6 years ago

@segredor either build from source using branch 202-stage (#98) or download the latest release binary. There is a binary available for Windows only at the moment: https://github.com/valiant1x/intensecoin/releases