 Show Posts
|
|
Pages: « 1 2 [3] 4 5 »
|
Ok, i took the plunge, panic mode ON and launched the command.... it worked!  thanks guys! guess it happens when you sync sometimes, right? always learn something new! It shouldn't usually happen. Did you modify your bitcoin.conf or anything? Is there anything about this hash in the earlier parts of your debug.log? nah it started with 2020-08-02T11:08:20Z InvalidChainFound: invalid block=00000000000000000007b86426ffa671d5f52a0cf22eb1a03a73c114695983c8 then all the further errors, that's all i can see. |
|
|
|
Ok, i took the plunge, panic mode ON and launched the command.... it worked! thanks guys! guess it happens when you sync sometimes, right? always learn something new! |
|
|
|
|
so shall i do
reconsiderblock 00000000000000000007b86426ffa671d5f52a0cf22eb1a03a73c114695983c8
worst case nothing happens?
|
|
|
|
AFAIK there's no fork and my Bitcoin Core are able to sync without any problem. Did you run any command that might break Bitcoin Core such as : invalidateblock 00000000000000000007b86426ffa671d5f52a0cf22eb1a03a73c114695983c8
Edit : if you do, try to run command shown by @ranochigo hi both, no i haven't ran any command line command at all, just launched usual sync, went to do some emails and wait in background. i tried to check the network state with a couple of commands but i haven't invalidated anything. so, which would be the best course of action? wallet seems fine, i have backup, but i rather Not RE sync 300Gigs if i possible  thanks guys |
|
|
|
|
hi guys,
I just launched my "usual" blockchain catch-up and core 0.20.0 is stuck from a while, he was crunching some data, CPU active, disk, network traffic, etc,. then all of a sudden all quiet, 0% network activity, etc. the disk is fine and PC as well, no hooks etc.
Sync is stuck at 2 days ago, Last Block time Fri Jul 31 09:50:27 2020 (99.89%)
Network is connected, i see all 4 dots connected, i have 10-12 connections active, though that then drops to 2 dots only, back to 4, very irregular. seems something is def up!
Can someone help me out please? i just had a peek at the debug log and here's what we have there:
2020-08-02T11:43:16Z ERROR: AcceptBlockHeader: block 00000000000000000007b86426ffa671d5f52a0cf22eb1a03a73c114695983c8 is marked invalid
2020-08-02T11:43:16Z ERROR: AcceptBlockHeader: block 00000000000000000007b86426ffa671d5f52a0cf22eb1a03a73c114695983c8 is marked invalid
2020-08-02T11:43:16Z ERROR: AcceptBlockHeader: block 00000000000000000007b86426ffa671d5f52a0cf22eb1a03a73c114695983c8 is marked invalid
2020-08-02T11:43:16Z ERROR: AcceptBlockHeader: block 00000000000000000007b86426ffa671d5f52a0cf22eb1a03a73c114695983c8 is marked invalid
2020-08-02T11:43:16Z ERROR: AcceptBlockHeader: block 00000000000000000007b86426ffa671d5f52a0cf22eb1a03a73c114695983c8 is marked invalid
2020-08-02T11:43:17Z ERROR: AcceptBlockHeader: block 00000000000000000007b86426ffa671d5f52a0cf22eb1a03a73c114695983c8 is marked invalid
2020-08-02T11:43:17Z ERROR: AcceptBlockHeader: block 00000000000000000007b86426ffa671d5f52a0cf22eb1a03a73c114695983c8 is marked invalid
2020-08-02T11:43:17Z New outbound peer connected: version: 70015, blocks=641879, peer=87 (full-relay)
2020-08-02T11:43:22Z ERROR: AcceptBlockHeader: block 00000000000000000007b86426ffa671d5f52a0cf22eb1a03a73c114695983c8 is marked invalid
2020-08-02T11:43:29Z ERROR: AcceptBlockHeader: block 00000000000000000007b86426ffa671d5f52a0cf22eb1a03a73c114695983c8 is marked invalid
2020-08-02T11:43:40Z New outbound peer connected: version: 70015, blocks=641879, peer=88 (full-relay)
2020-08-02T11:43:41Z New outbound peer connected: version: 70015, blocks=641879, peer=89 (full-relay)
2020-08-02T11:43:47Z New outbound peer connected: version: 70015, blocks=641879, peer=90 (full-relay)
2020-08-02T11:44:04Z New outbound peer connected: version: 70015, blocks=641879, peer=93 (full-relay)
2020-08-02T11:44:05Z New outbound peer connected: version: 70015, blocks=641879, peer=94 (full-relay)
2020-08-02T11:44:06Z New outbound peer connected: version: 70015, blocks=641879, peer=95 (full-relay)
2020-08-02T11:44:07Z New outbound peer connected: version: 70015, blocks=641879, peer=96 (block-relay)
2020-08-02T11:44:24Z New outbound peer connected: version: 70015, blocks=641879, peer=97 (block-relay)
2020-08-02T11:44:30Z New outbound peer connected: version: 70015, blocks=641879, peer=98 (block-relay)
2020-08-02T11:46:03Z ERROR: AcceptBlockHeader: block 00000000000000000007b86426ffa671d5f52a0cf22eb1a03a73c114695983c8 is marked invalid
2020-08-02T11:46:03Z ERROR: AcceptBlockHeader: block 00000000000000000007b86426ffa671d5f52a0cf22eb1a03a73c114695983c8 is marked invalid
2020-08-02T11:46:04Z ERROR: AcceptBlockHeader: block 00000000000000000007b86426ffa671d5f52a0cf22eb1a03a73c114695983c8 is marked invalid
2020-08-02T11:46:04Z ERROR: AcceptBlockHeader: block 00000000000000000007b86426ffa671d5f52a0cf22eb1a03a73c114695983c8 is marked invalid
2020-08-02T11:46:04Z ERROR: AcceptBlockHeader: block 00000000000000000007b86426ffa671d5f52a0cf22eb1a03a73c114695983c8 is marked invalid
2020-08-02T11:46:04Z ERROR: AcceptBlockHeader: block 00000000000000000007b86426ffa671d5f52a0cf22eb1a03a73c114695983c8 is marked invalid
2020-08-02T11:46:04Z ERROR: AcceptBlockHeader: block 00000000000000000007b86426ffa671d5f52a0cf22eb1a03a73c114695983c8 is marked invalid
2020-08-02T11:46:07Z ERROR: AcceptBlockHeader: block 00000000000000000007b86426ffa671d5f52a0cf22eb1a03a73c114695983c8 is marked invalid
2020-08-02T11:46:15Z ERROR: AcceptBlockHeader: block 00000000000000000007b86426ffa671d5f52a0cf22eb1a03a73c114695983c8 is marked invalid
2020-08-02T11:46:16Z New outbound peer connected: version: 70015, blocks=641880, peer=104 (full-relay)
2020-08-02T11:46:33Z New outbound peer connected: version: 70015, blocks=641880, peer=105 (full-relay)
2020-08-02T11:46:34Z New outbound peer connected: version: 70015, blocks=641880, peer=106 (full-relay)
2020-08-02T11:46:38Z New outbound peer connected: version: 70015, blocks=641879, peer=103 (full-relay)
many thanks,
Gab
|
|
|
|
|
thank you, I just added a bug there - @HCP if you could confirm that bug perhaps they will take care of it sooner ;-)
Best,
Gabrio
|
|
|
|
|
hello all, does anyone have any news about this issue? is it reported to the DEVs? if not how can I do it?
thank you
Gabrio
|
|
|
|
Great you got it "working"... For the record, I did a little test while I was away, and left my node to fall behind by a hundred blocks or so to test what it would do while syncing a larger number of blocks. I too then got the intermittent "not responding" issue (and associated 100% disk usage on the disk with the blocks folder)!  I had not noticed this issue on previous versions (granted I don't remember the last time my node was out of sync by any more than 3 or 4 blocks following a reset/temp shutdown)... and had not noticed it on 0.19.0.1 until I let it get to 100+ blocks behind. So, I'm wondering if there is indeed some new "performance tweak(s)" in 0.19.0.1 that are driving up the HDD usage and causing the 'not responding' issues on Windows?  Also, one small gripe, please avoid multiple consecutive posts like that... if you need to post an "update", then just use the "EDIT" button on your previous post and add/update it as required.  Ok so it's something to do with 0.19.0.1, glad that you replicated the "problem" 😀 |
|
|
|
|
nope. happening again, now he's deep into syncing and same hanging happening.
oh well, not great but if in the end it works, fine with me
|
|
|
|
|
so far so good, syncing and no hanging issues... let's see when it completes.
HDD flat out 100% and 1-2 mb/sec as usual
|
|
|
|
it's a usb 3.0 max transfer rate is 100 mb/sec, tested. when it's on 100% usage with core, it barely uses 1-2 mb/sec so that's NOT the bottleneck.
It can't be the RAM, CPU and BitcoinCore 0.19.0.1 because most of the users doesn't experience that freezing issue. See, it's at 100% but it it's only at 1-2 MBps ( that's the max performance). How about the USB port where it is connected? If you plug it in a USB2.0 port, it wont use the USB3.0 bandwidth. well, with the previous release this was never an issue, so I rule out my hardware in the first place, don't you think? if I transfer a movie the hdd goes to 100 mb/sec no problem and my internal ssd can do I think 300-400 mb/sec, is quite fast. I will try to plug it back now so it has one day to sync again, let's see what happens. thanks anyway |
|
|
|
hi,
as I just mentioned in the previous msg, I cannot find any bitcoin.conf anywhere. should I be worried? however it fully works 😀
If you don't have you can generate bitcoin.conf from this link https://jlopp.github.io/bitcoin-core-config-generator/Just look for dbcache and max mempool then edit after you edit it will show on the right side as a result of bitcoin.conf now you can download it and paste it in this path %APPDATA%\Bitcoin\ or C:\Users\username\AppData\Roaming\Bitcoin\bitcoin.conf thanks, i will check, but i will try it again today, yesterday worked flawlessly in the end (after this odd thing). |
|
|
|
Task Manager only had the HDD (where the chain is) to 100% at all times until synced. the CPU and ram are all looking good.
That might be the issue, any 100% process usually causes those 'freezing' that still running in the background because it's on its limits and the process is demanding " more''. Based from the spec, your Rig can handle BitcoinCore even with higher dbcache. however Core runs the blockchain on an external hdd, which i think is a 7200rpm Maxtor External or 5400 rpm (cant remember)
The External HDD must be the bottleneck, specially if it's connected to a USB2.0 port instead of USB3.0, the HDD speed won't matter much for the former. Check the External HDD's ( or enclosure/adapter) specs if it's USB3.0 ( usually blue) and the port where it is plugged. it's a usb 3.0 max transfer rate is 100 mb/sec, tested. when it's on 100% usage with core, it barely uses 1-2 mb/sec so that's NOT the bottleneck. |
|
|
|
Can you check your bitcoin.conf and maybe you put a wrong config with "dbcache=" under bitcoin.conf or try to add the code below. dbcache=100
maxmempool=100 Copy that and paste it on bitcoin.conf then test the wallet again. If it still freezing try to reduce the dbcache and maxmempool to 50 then let's see if still freezing or hang. Note: if you already have this config try to remove those code both dbcache and maxmempool then test it again. hi, as I just mentioned in the previous msg, I cannot find any bitcoin.conf anywhere. should I be worried? however it fully works 😀 |
|
|
|
I have been running 0.19.0.1 on Win10 x64 since it was advertised in the "news" bar at the top of BitcoinTalk... I have not seen any "Not Responding" errors with this release since I have been using it. And that's running on a crappy old i5-3570k, with 8 gigs of RAM and the blocks folder on an HDD... that is also running an Electrum server and an LND server and a shitton of other services and background apps. Is there anything in your debug.log that might give an indication as to why it is "not responding"? The next few times that it freezes... open/refresh your debug.log in a text editor and see what the last few lines say. See if it is outputting the same things each time it freezes. I just had a log in the debug.log and didn't see any strange things but maybe missed smthg, one thing that I noticed is this one: 2020-01-08T06:35:55Z Config file: X:\XYZ\bitcoin.conf (not found, skipping)cannot find it anywhere, not even in the user appdata folder. odd. |
|
|
|
What is your previous version before upgrading and can you post your W10 PC's specs?
You may also check your 'Task Manager' if your CPU, Memory and Disk process is at 100% during BitcoinCore's operation.
I haven't updated to 0.19.01 and still using 0.18.1, I will upgrade right now to see if it's a problem with the version.
-edit-
Mine isn't freezing, is yours random or all the time?
Task Manager only had the HDD (where the chain is) to 100% at all times until synced. the CPU and ram are all looking good. |
|
|
|
What is your previous version before upgrading and can you post your W10 PC's specs?
You may also check your 'Task Manager' if your CPU, Memory and Disk process is at 100% during BitcoinCore's operation.
I haven't updated to 0.19.01 and still using 0.18.1, I will upgrade right now to see if it's a problem with the version.
-edit-
Mine isn't freezing, is yours random or all the time?
thanks for your reply, well i had 0.18.1 i believe - not in front of the pc right now .... that was fine laptop is a i5 core 3.38ghz quite fast actually 8 gb ram 256 Fast Sandisk however Core runs the blockchain on an external hdd, which i think is a 7200rpm Maxtor External or 5400 rpm (cant remember) it actually happened earlier today when syncing and it was off by 3-4 days. CPU usage was decent like 24% however external HDD (where the blockchain is) is flat-out at 100% during syncing. This happened also with the 0.18 version and didnt show the not responding all the time, maybe just once upon loading then fine. this one was like 15 seconds Not responding, then responding... then same, until it finally synced all, and then worked fine actually. |
|
|
|
|
hi guys,
recently upgraded and I noticed that latest release keep hanging while syncing coins goes to Not Responding for like up to 30 seconds, then works, please check it out
that is on win10 64 bit
this happened in the past but not all the time like with this release, it seems to proceed though
other users might kill the app and thus make a big mess!
thanks,
Gabrio
|
|
|
|
I didn't know that Skype and WhatsApp are banned in Dubai. It's frustrating because a client of mine if interacting with me through those apps.
This is old news. Skype and Whatsapp have been banned completely since the beginning of 2018 which is a shame for a country which has been embracing technological developments seriously in recent times. On the other hand, I don't really see the problem with running Bitcoin core in Dubai since I have not heard anything against it in this regard. Completely agree, and with the risk of going off topic, I will just leave any further comments as in "what's wrong with text and free calls?" - we got Skype for decades.. but let's leave it there. thanks everyone for feedback! |
|
|
|
|
ok good stuff thanks guys
|
|
|
|
|
