btcpayserver icon indicating copy to clipboard operation
btcpayserver copied to clipboard
verified publisher icon btcpayserver

Your nodes are synching... LTC and DASH

Open darkban opened this issue 6 years ago • 46 comments

it happened again this time it happened with ltc ... initially after a dash update it did not synchronize anymore now after the last update happened also with ltc now the ltc node does not work, I reported already 3 months ago or maybe again plus the problem with dash but it has never been solved now the same problem has occurred with ltc ... how can I solve? the only thing I did was update the server

darkban avatar Jul 02 '19 12:07 darkban

+1 with Dash

andres-pinilla avatar Jul 03 '19 17:07 andres-pinilla

Stuck here several days after update: Captura de Pantalla 2019-07-03 a la(s) 12 02 50 p m

andres-pinilla avatar Jul 03 '19 17:07 andres-pinilla

Did a btcpay-restart.sh solve the situation? I noticed this happen only with altcoins.

NicolasDorier avatar Jul 14 '19 13:07 NicolasDorier

Hello, I deleted the data folder and rebuilt the index.

Thanks.

andres-pinilla avatar Jul 14 '19 22:07 andres-pinilla

Hello, I deleted the data folder and rebuilt the index.

Thanks.

Could you tell me exactly which folder you deleted please? Thanks.

guiguy2018 avatar Jul 24 '19 12:07 guiguy2018

Delete all files within this directory: /var/lib/docker/volumes/generated_dash_datadir/_data

Then run this command again and voila:

sudo su -
. ./btcpay-setup.sh -i

andres-pinilla avatar Jul 24 '19 12:07 andres-pinilla

Delete all files within this directory: /var/lib/docker/volumes/generated_dash_datadir/_data

Then run this command again and voila:

sudo su -
. ./btcpay-setup.sh -i

ok thanks very much

guiguy2018 avatar Jul 25 '19 00:07 guiguy2018

Hi @guiguy2018, works for you?

andres-pinilla avatar Jul 25 '19 03:07 andres-pinilla

Hi @guiguy2018, works for you?

nope. working with ltc by the way. Deleted the folder and it still stuck at 99%, ltc sync but nbxplorer stuck. Tried it again and now getting errors when I do . ./btcpay-setup.sh -i

Starting btcpayserver_litecoind ... error

ERROR: for btcpayserver_litecoind Cannot start service litecoind: network a0c41Recreating 7c15a0a9489e_7c15a0a9489e_7c15a0a9489e_7c15a0a9489e_generated_nbxplorer_1 ... error ERROR: for 7c15a0a9489e_7c15a0a9489e_7c15a0a9489e_7c15a0a9489e_generated_nbxplorer_1 Cannot start service nbxplorer: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused "rootfs_linux.go:58: mounting \"/var/lib/docker/volumes/generated_litecoin_datadir/_data\" to rootfs \"/var/lib/docker/overlay2/1c284f4b6c3833a04b93b4f7061f4e4ec668befcfec6db577ab82c9b34cb4139/merged\" at \"/root/.litecoin\" caused \"stat /var/lib/docker/volumes/generated_litecoin_datadir/_data: no such file or directory\""": unknown

guiguy2018 avatar Jul 25 '19 11:07 guiguy2018

mkdir -p /var/lib/docker/volumes/generated_litecoin_datadir/_data

NicolasDorier avatar Jul 26 '19 04:07 NicolasDorier

Same problem with sync 1.6.3.0 LTC stuck at 99, DOGE takes forever after 30%, never syncs. Screen Shot 2022-07-27 at 7 26 53 AM

2022-07-27T22:57:52.599857670Z 2022-07-27T22:57:52Z ERROR: AcceptBlockHeader: block 163f5d4af9e77e7250c9448d17c44726fca346b6aa404108fba9f42203d45dd2 is marked invalid
2022-07-27T22:57:52.599895363Z 2022-07-27T22:57:52Z Disconnecting and discouraging peer 120!
2022-07-27T22:57:52.947973516Z 2022-07-27T22:57:52Z ERROR: AcceptBlockHeader: block 163f5d4af9e77e7250c9448d17c44726fca346b6aa404108fba9f42203d45dd2 is marked invalid
2022-07-27T22:57:52.948008549Z 2022-07-27T22:57:52Z Disconnecting and discouraging peer 121!
2022-07-27T22:57:53.920049991Z 2022-07-27T22:57:53Z ERROR: AcceptBlockHeader: block 163f5d4af9e77e7250c9448d17c44726fca346b6aa404108fba9f42203d45dd2 is marked invalid
2022-07-27T22:57:53.920078661Z 2022-07-27T22:57:53Z Disconnecting and discouraging peer 122!
2022-07-27T22:58:00.886710850Z 2022-07-27T22:58:00Z New outbound peer connected: version: 70016, blocks=2305273, peer=125 (full-relay)
2022-07-27T22:58:01.966586176Z 2022-07-27T22:58:01Z New outbound peer connected: version: 70016, blocks=2305273, peer=126 (full-relay)
2022-07-27T22:58:02.387366440Z 2022-07-27T22:58:02Z New outbound peer connected: version: 70016, blocks=2305273, peer=127 (block-relay)
2022-07-27T22:58:16.716367221Z 2022-07-27T22:58:16Z New outbound peer connected: version: 70016, blocks=2305273, peer=129 (full-relay)
2022-07-27T22:59:03.253001175Z 2022-07-27T22:59:03Z Potential stale tip detected, will try using extra outbound peer (last tip update: 1982 seconds ago)
2022-07-27T22:59:15.514249723Z 2022-07-27T22:59:15Z New outbound peer connected: version: 70016, blocks=2305273, peer=130 (full-relay)
2022-07-27T23:00:22.325449417Z 2022-07-27T23:00:22Z ERROR: AcceptBlockHeader: block 163f5d4af9e77e7250c9448d17c44726fca346b6aa404108fba9f42203d45dd2 is marked invalid
2022-07-27T23:00:22.357817752Z 2022-07-27T23:00:22Z Disconnecting and discouraging peer 129!
2022-07-27T23:00:22.533089628Z 2022-07-27T23:00:22Z ERROR: AcceptBlockHeader: block 163f5d4af9e77e7250c9448d17c44726fca346b6aa404108fba9f42203d45dd2 is marked invalid
2022-07-27T23:00:22.533120320Z 2022-07-27T23:00:22Z Disconnecting and discouraging peer 127!
2022-07-27T23:00:22.672799309Z 2022-07-27T23:00:22Z ERROR: AcceptBlockHeader: block 163f5d4af9e77e7250c9448d17c44726fca346b6aa404108fba9f42203d45dd2 is marked invalid
2022-07-27T23:00:22.672822309Z 2022-07-27T23:00:22Z Disconnecting and discouraging peer 126!
2022-07-27T23:00:23.155326579Z 2022-07-27T23:00:23Z New outbound peer connected: version: 70016, blocks=2305274, peer=131 (full-relay)
2022-07-27T23:00:24.591840656Z 2022-07-27T23:00:24Z New outbound peer connected: version: 70016, blocks=2305274, peer=132 (full-relay)
2022-07-27T23:00:25.074860811Z 2022-07-27T23:00:25Z New outbound peer connected: version: 70016, blocks=2305274, peer=133 (block-relay)
2022-07-27T23:00:27.988684098Z 2022-07-27T23:00:27Z New outbound peer connected: version: 70016, blocks=2305274, peer=134 (block-relay)
2022-07-27T23:00:44.639295953Z 2022-07-27T23:00:44Z New outbound peer connected: version: 70016, blocks=2305274, peer=135 (block-relay)
2022-07-27T23:00:51.168889532Z 2022-07-27T23:00:51Z New outbound peer connected: version: 70016, blocks=2305274, peer=136 (block-relay)
2022-07-27T23:02:03.442132847Z 2022-07-27T23:02:03Z Potential stale tip detected, will try using extra outbound peer (last tip update: 2162 seconds ago)
2022-07-27T23:02:11.913998354Z 2022-07-27T23:02:11Z New outbound peer connected: version: 70016, blocks=2278963, peer=137 (full-relay)
2022-07-27T23:04:46.260800935Z 2022-07-27T23:04:46Z ERROR: AcceptBlockHeader: block 163f5d4af9e77e7250c9448d17c44726fca346b6aa404108fba9f42203d45dd2 is marked invalid
2022-07-27T23:04:46.273135147Z 2022-07-27T23:04:46Z Disconnecting and discouraging peer 131!
2022-07-27T23:04:46.606778765Z 2022-07-27T23:04:46Z ERROR: AcceptBlockHeader: block 163f5d4af9e77e7250c9448d17c44726fca346b6aa404108fba9f42203d45dd2 is marked invalid
2022-07-27T23:04:46.606836525Z 2022-07-27T23:04:46Z Disconnecting and discouraging peer 136!
2022-07-27T23:04:46.894975975Z 2022-07-27T23:04:46Z ERROR: AcceptBlockHeader: block 163f5d4af9e77e7250c9448d17c44726fca346b6aa404108fba9f42203d45dd2 is marked invalid
2022-07-27T23:04:46.895150243Z 2022-07-27T23:04:46Z Disconnecting and discouraging peer 132!
2022-07-27T23:04:49.007310693Z 2022-07-27T23:04:49Z New outbound peer connected: version: 70016, blocks=2305275, peer=138 (full-relay)
2022-07-27T23:04:56.482888830Z 2022-07-27T23:04:56Z New outbound peer connected: version: 70016, blocks=2305275, peer=139 (full-relay)
2022-07-27T23:04:57.218504044Z 2022-07-27T23:04:57Z New outbound peer connected: version: 70016, blocks=2305275, peer=140 (block-relay)
2022-07-27T23:05:03.546737548Z 2022-07-27T23:05:03Z Potential stale tip detected, will try using extra outbound peer (last tip update: 2342 seconds ago)
2022-07-27T23:05:04.159960076Z 2022-07-27T23:05:04Z New outbound peer connected: version: 70016, blocks=2305275, peer=141 (full-relay)
2022-07-27T23:08:03.652790811Z 2022-07-27T23:08:03Z Potential stale tip detected, will try using extra outbound peer (last tip update: 2522 seconds ago)
2022-07-27T23:08:04.101409573Z 2022-07-27T23:08:04Z New outbound peer connected: version: 70016, blocks=2305275, peer=142 (full-relay)

Delitants avatar Jul 27 '22 17:07 Delitants

@Neolo you tried recently? I updated DOGE a few days ago. Did you try to run btcpay-update.sh ?

NicolasDorier avatar Jul 28 '22 00:07 NicolasDorier

@Neolo you tried recently? I updated DOGE a few days ago. Did you try to run btcpay-update.sh ?

Yes, it’s latest version already. It’s flapping, shows 35% (stuck at it) and after page refresh shows starting node again. LTC stuck at block as on screenshot and not moving. Space and ram are sufficient. Reboot didn’t help? more over reboot broke ltc.

Delitants avatar Jul 28 '22 00:07 Delitants

yes I believe that's a RAM issue. DOGE is very greedy in RAM. Checking now.

NicolasDorier avatar Jul 28 '22 00:07 NicolasDorier

you can check dmesg -T | egrep -i 'killed process' if the processes get killed by RAM issue.

I am synching nodes, so will let you know once it is done, it may take a while...

NicolasDorier avatar Jul 28 '22 00:07 NicolasDorier

@darkban for LTC can you tyr to run litecoin-cli.sh getblockchaininfo ?

NicolasDorier avatar Jul 28 '22 01:07 NicolasDorier

you can check dmesg -T | egrep -i 'killed process' if the processes get killed by RAM issue.

No output, there is 8GB of ram, plenty and half of it free, I watch over htop.

for LTC can you tyr to run litecoin-cli.sh getblockchaininfo ?

I had LTC synced, after server reboot it went to 99% and stuck. Future reboots don't help.

litecoin-cli.sh getblockchaininfo { "chain": "main", "blocks": 2304093, "headers": 2304093, "bestblockhash": "6c423f7481a59670e9f067e91b2225ee6649307ba85229db159f905e6bb9bcf9", "difficulty": 14020592.33052793, "mediantime": 1658785905, "verificationprogress": 0.9982360053107212, "initialblockdownload": true, "chainwork": "000000000000000000000000000000000000000000000897ad2b5fde0eac0764", "size_on_disk": 26001220633, "pruned": true, "pruneheight": 2138979, "automatic_pruning": true, "prune_target_size": 26214400000, "softforks": { "bip34": { "type": "buried", "active": true, "height": 710000 }, "bip66": { "type": "buried", "active": true, "height": 811879 }, "bip65": { "type": "buried", "active": true, "height": 918684 }, "csv": { "type": "buried", "active": true, "height": 1201536 }, "segwit": { "type": "buried", "active": true, "height": 1201536 }, "taproot": { "type": "bip8", "bip8": { "status": "active", "start_height": 2161152, "timeout_height": 2370816, "since": 2257920 }, "height": 2257920, "active": true }, "mweb": { "type": "bip8", "bip8": { "status": "active", "start_height": 2217600, "timeout_height": 2427264, "since": 2265984 }, "height": 2265984, "active": true } }, "warnings": "" }

Delitants avatar Jul 28 '22 01:07 Delitants

@Neolo it seems that "initialblockdownload": true, is stuck on LTC, I don't know why, probably a bug from the litecoin node.

Try docker restart btcpayserver_litecoind

NicolasDorier avatar Jul 28 '22 01:07 NicolasDorier

Try docker restart btcpayserver_litecoind

I did that already, and rebooted the whole server 4 times, no changes

Delitants avatar Jul 28 '22 01:07 Delitants

@Neolo I will try to check if there is an outstanding bug in litecoin and if yes, find a workaround

NicolasDorier avatar Jul 28 '22 06:07 NicolasDorier

@Neolo is it a new instance or did you upgraded? if upgrade, https://github.com/litecoin-project/litecoin/issues/829 seems to say it needs to rescan. Is it upgraded or just new instance?

If it is upgraded and not new instance, I think you need to rescan from scratch. For that btcpay-down.sh then rm -rf /var/lib/docker/volumes/generated_litecoin_datadir/_data/* then btcpay-up.sh.

Else can you report the bug on litecoin repository?

NicolasDorier avatar Jul 28 '22 06:07 NicolasDorier

New instance but because it's syncing like that for weeks, version was upgraded several times. As mentioned LTC was fully synced and was ready for payments, I rebooted the server and it fell back to 99% and stuck. So how that sync from scratch may help?

Delitants avatar Jul 28 '22 07:07 Delitants

@Neolo that's a good question your logs says the block 163f5d4af9e77e7250c9448d17c44726fca346b6aa404108fba9f42203d45dd2 is invalid.

But it isn't https://litecoinblockexplorer.net/block/163f5d4af9e77e7250c9448d17c44726fca346b6aa404108fba9f42203d45dd2 so my guess is that your node is stuck for some reason, which may be a bug of litecoin or a corruption of the UTXO set, which a rescan would solve.

I advise you to ask for advise on https://github.com/litecoin-project/litecoin/ and link the discussion here. I am starting a new node to see how it goes.

NicolasDorier avatar Jul 28 '22 07:07 NicolasDorier

@Neolo that's a good question your logs says the block 163f5d4af9e77e7250c9448d17c44726fca346b6aa404108fba9f42203d45dd2 is invalid.

But it isn't https://litecoinblockexplorer.net/block/163f5d4af9e77e7250c9448d17c44726fca346b6aa404108fba9f42203d45dd2 so my guess is that your node is stuck for some reason, which may be a bug of litecoin or a corruption of the UTXO set, which a rescan would solve.

I advise you to ask for advise on https://github.com/litecoin-project/litecoin/ and link the discussion here. I am starting a new node to see how it goes.

ok I will rescan it. What about doge?

Delitants avatar Jul 28 '22 07:07 Delitants

@Neolo I think DOGE is fine, the UI flicker probably because the CPU is busy synching. If the container is still synching and you sometimes see the progress then it is fine.

NicolasDorier avatar Jul 28 '22 07:07 NicolasDorier

@Neolo I think DOGE is fine, the UI flicker probably because the CPU is busy synching. If the container is still synching and you sometimes see the progress then it is fine.

CPU is barely 45% loaded and it's been weeks, I don't understand why so slow.

Delitants avatar Jul 28 '22 17:07 Delitants

@Neolo which VPS are you using? some VPS throttle CPU if you use it too much for too long.

Weeks to sync DOGE doesn't seem normal indeed.

My node already synched LTC, now DGE 88% and BTC 40% (using lunanode)

NicolasDorier avatar Jul 29 '22 02:07 NicolasDorier

@Neolo which VPS are you using? some VPS throttle CPU if you use it too much for too long.

Weeks to sync DOGE doesn't seem normal indeed.

My node already synched LTC, now DGE 88% and BTC 40% (using lunanode)

I own that VPS, I set 16 cores with no limit, it does not use them all. While BTC sync did use all cores and synced in 2 days. Monero also synced well. LTC is slow and buggy, DOGE takes forever.

Delitants avatar Jul 29 '22 03:07 Delitants

@Neolo you use SSD? right now I have been using an M4 instance on https://www.lunanode.com/pricing and it seems to be synching nicely.

Maybe your RAM is swapping?

NicolasDorier avatar Jul 29 '22 03:07 NicolasDorier

@Neolo you use SSD? right now I have been using an M4 instance on https://www.lunanode.com/pricing and it seems to be synching nicely.

Maybe your RAM is swapping?

No, regular 7200 RPM. top %WA parameter is staying near zero, means there is no I/O clogging. Again, BTC synced just fine. Are these Alt coins even have pruning?

Delitants avatar Jul 29 '22 03:07 Delitants