hi do any one knows how much server space i need to host live bitcoin wallet i have
MEMORY - 8gb
vCPUs - 4cpu
SSD DISK -160
is it good or i need more ?
Topic: bitcoin core slow sync today? (Read 499 times)
-reindex-chainstate should work in most of cases
-reindex-chainstate does wipe the chainstate + rebuilds it.
This is helpful if your chainstate got somehow corrupted.
But if the block index is corrupted, this command won't help you. You'll need to use -reindex instead.
-reindex does wipe the chainstate and the blockindex and rebuilds both of them (Chainstate is being built by validating blocks in the block index).
Both are unrelated to the time it takes for core to synch.
This is mostly dependend on the hardware (especially hard drive and CPU) and the network rate.
-reindex-chainstate should work in most of cases
Hey,
where do I find the most recent blk*.dat and rev*.dat files??
I run Bitcoind (wallet only through terminal)
Thanks.
where do I find the most recent blk*.dat and rev*.dat files??
I run Bitcoind (wallet only through terminal)
Thanks.
they are in the /blocks folder if you are running bitcoin core. not sure whether or not Bitcoind is part of bitcoin core though.
It is. It's just BTC-core without the graphic user interface. Anyways, I just corrupted the SD-card, so I'm running a recent backup. So I never got to try the proposed solution.
Hey,
where do I find the most recent blk*.dat and rev*.dat files??
I run Bitcoind (wallet only through terminal)
Thanks.
where do I find the most recent blk*.dat and rev*.dat files??
I run Bitcoind (wallet only through terminal)
Thanks.
they are in the /blocks folder if you are running bitcoin core. not sure whether or not Bitcoind is part of bitcoin core though.
Hey,
where do I find the most recent blk*.dat and rev*.dat files??
I run Bitcoind (wallet only through terminal)
Thanks.
where do I find the most recent blk*.dat and rev*.dat files??
I run Bitcoind (wallet only through terminal)
Thanks.
Hi
You might try what worked for me... bear in mind it will reindex the chain which took about 2 days in total. First pass goes fast then the next one takes longer.
I did the "deleting the most recent blk*.dat and rev*.dat files"
You might try what worked for me... bear in mind it will reindex the chain which took about 2 days in total. First pass goes fast then the next one takes longer.
I did the "deleting the most recent blk*.dat and rev*.dat files"
Ok. I two days isn't that long compared to the time it takes to first sync with the network.
I read through the whole post and can find the information I'll need there. Otherwise I'll return for help.
Thanks
Hi
You might try what worked for me... bear in mind it will reindex the chain which took about 2 days in total. First pass goes fast then the next one takes longer.
I did the "deleting the most recent blk*.dat and rev*.dat files"
You might try what worked for me... bear in mind it will reindex the chain which took about 2 days in total. First pass goes fast then the next one takes longer.
I did the "deleting the most recent blk*.dat and rev*.dat files"
Hey.
I have a problem, that I found fit to post here.
Since yesterday my note only shows headers to be 508757. Before it got "synced" it showed the correct headers 536424 as of writing this post
Your help will be much appreciated.
best regards!
I have a problem, that I found fit to post here.
Since yesterday my note only shows headers to be 508757. Before it got "synced" it showed the correct headers 536424 as of writing this post
Your help will be much appreciated.
Code:
pi@btccore:~ $ bitcoin-cli getblockchaininfo
{
"chain": "main",
"blocks": 508757,
"headers": 508757,
"bestblockhash": "00000000000000000021b78e0d404649b4b91e3104e4ef2310e38563c7347722",
"difficulty": 2874674234415.941,
"mediantime": 1518400210,
"verificationprogress": 0.8450131626940209,
"initialblockdownload": true,
"chainwork": "00000000000000000000000000000000000000000112b04f78f51cecbb145970",
"size_on_disk": 890825462,
"pruned": true,
"pruneheight": 508092,
"automatic_pruning": true,
"prune_target_size": 1048576000,
"softforks": [
{
"id": "bip34",
"version": 2,
"reject": {
"status": true
}
},
{
"id": "bip66",
"version": 3,
"reject": {
"status": true
}
},
{
"id": "bip65",
"version": 4,
"reject": {
"status": true
}
}
],
"bip9_softforks": {
"csv": {
"status": "active",
"startTime": 1462060800,
"timeout": 1493596800,
"since": 419328
},
"segwit": {
"status": "active",
"startTime": 1479168000,
"timeout": 1510704000,
"since": 481824
}
},
"warnings": ""
}
best regards!
hi guys
it seems to have worked, it was syncing all day, now left at 25 weeks behind, so far so good... hopefully also the newest transactions will work OK
it seems to have worked, it was syncing all day, now left at 25 weeks behind, so far so good... hopefully also the newest transactions will work OK
Great to hear! Let us know when you get up to 100%.
it's complete now, finished and all back to normal.
hi guys
it seems to have worked, it was syncing all day, now left at 25 weeks behind, so far so good... hopefully also the newest transactions will work OK
it seems to have worked, it was syncing all day, now left at 25 weeks behind, so far so good... hopefully also the newest transactions will work OK
Great to hear! Let us know when you get up to 100%.
hi guys
it seems to have worked, it was syncing all day, now left at 25 weeks behind, so far so good... hopefully also the newest transactions will work OK
it seems to have worked, it was syncing all day, now left at 25 weeks behind, so far so good... hopefully also the newest transactions will work OK
The problem is that your node is rejecting block 533816 which means that any node which attempts to give it that block or any of its descendants will be disconnected from immediately.
Open the Debug Console (Help > Debug Window > Console) and then enter this command: reconsiderblock 0000000000000000001f642d24d3968eeef81460531346adbfb9882dd711ed45. If it returns with null, then the block was accepted and you should be able to connect to nodes and sync the rest of the blockchain.
Otherwise, start Bitcoin Core with the -reindex-chainstate option. That will reindex the chainstate (not quite as bad as a full reindex) and that should also fix the problem.
If all else fails, deleting the most recent blk*.dat and rev*.dat files and then starting Bitcoin Core should work too. That will trigger a full reindex as well as redownload the most recent blocks.
Open the Debug Console (Help > Debug Window > Console) and then enter this command: reconsiderblock 0000000000000000001f642d24d3968eeef81460531346adbfb9882dd711ed45. If it returns with null, then the block was accepted and you should be able to connect to nodes and sync the rest of the blockchain.
Otherwise, start Bitcoin Core with the -reindex-chainstate option. That will reindex the chainstate (not quite as bad as a full reindex) and that should also fix the problem.
If all else fails, deleting the most recent blk*.dat and rev*.dat files and then starting Bitcoin Core should work too. That will trigger a full reindex as well as redownload the most recent blocks.
thanks a lot, actually I did the "deleting the most recent blk*.dat and rev*.dat files", it took 2 hours and 30 minutes for the database, now doing the "processing blocks on disk" and seems to work......I reckon other few hours for this round and let's see...thanks!
The problem is that your node is rejecting block 533816 which means that any node which attempts to give it that block or any of its descendants will be disconnected from immediately.
Open the Debug Console (Help > Debug Window > Console) and then enter this command: reconsiderblock 0000000000000000001f642d24d3968eeef81460531346adbfb9882dd711ed45. If it returns with null, then the block was accepted and you should be able to connect to nodes and sync the rest of the blockchain.
Otherwise, start Bitcoin Core with the -reindex-chainstate option. That will reindex the chainstate (not quite as bad as a full reindex) and that should also fix the problem.
If all else fails, deleting the most recent blk*.dat and rev*.dat files and then starting Bitcoin Core should work too. That will trigger a full reindex as well as redownload the most recent blocks.
Open the Debug Console (Help > Debug Window > Console) and then enter this command: reconsiderblock 0000000000000000001f642d24d3968eeef81460531346adbfb9882dd711ed45. If it returns with null, then the block was accepted and you should be able to connect to nodes and sync the rest of the blockchain.
Otherwise, start Bitcoin Core with the -reindex-chainstate option. That will reindex the chainstate (not quite as bad as a full reindex) and that should also fix the problem.
If all else fails, deleting the most recent blk*.dat and rev*.dat files and then starting Bitcoin Core should work too. That will trigger a full reindex as well as redownload the most recent blocks.
In safe mode now and it seems exactly the same... teued to get connections for a bit then blinks then off again.
The whole chain? Well im on a 17mbit connection.. that will be long.
Any other ideas? Oh actually the pc went to standby when i was home without shutting down the core client .. laptop ... altho that happened before.
Thank you
The whole chain? Well im on a 17mbit connection.. that will be long.
Any other ideas? Oh actually the pc went to standby when i was home without shutting down the core client .. laptop ... altho that happened before.
Thank you
It won't redownload the chain it will run back through it but it will still take quite a long time to do that.
If by standby you mean hybernate then that shouldn't be the cause of the issue.
I'd suggest waiting between a few hours a day for someone who can work out the exact error in the debug.logs that you have provided as they should be indepth enough for someone who knows more about the source code of bitcoin core.
Right that makes sense.....now deciding whether doing that re-download thing (if that is at all a viable option) or doing something else... in that case.. ANY EXPERT around???
thanks for all your help jackg anyway!
Give them 24 hours to come here and then try reindexing (deleting the last blk file).
It won't download everything again unless it finds an issue but it will have to scan through it all and reindex everything.
In safe mode now and it seems exactly the same... teued to get connections for a bit then blinks then off again.
The whole chain? Well im on a 17mbit connection.. that will be long.
Any other ideas? Oh actually the pc went to standby when i was home without shutting down the core client .. laptop ... altho that happened before.
Thank you
The whole chain? Well im on a 17mbit connection.. that will be long.
Any other ideas? Oh actually the pc went to standby when i was home without shutting down the core client .. laptop ... altho that happened before.
Thank you
It won't redownload the chain it will run back through it but it will still take quite a long time to do that.
If by standby you mean hybernate then that shouldn't be the cause of the issue.
I'd suggest waiting between a few hours a day for someone who can work out the exact error in the debug.logs that you have provided as they should be indepth enough for someone who knows more about the source code of bitcoin core.
Right that makes sense.....now deciding whether doing that re-download thing (if that is at all a viable option) or doing something else... in that case.. ANY EXPERT around???
thanks for all your help jackg anyway!
In safe mode now and it seems exactly the same... teued to get connections for a bit then blinks then off again.
The whole chain? Well im on a 17mbit connection.. that will be long.
Any other ideas? Oh actually the pc went to standby when i was home without shutting down the core client .. laptop ... altho that happened before.
Thank you
The whole chain? Well im on a 17mbit connection.. that will be long.
Any other ideas? Oh actually the pc went to standby when i was home without shutting down the core client .. laptop ... altho that happened before.
Thank you
It won't redownload the chain it will run back through it but it will still take quite a long time to do that.
If by standby you mean hybernate then that shouldn't be the cause of the issue.
I'd suggest waiting between a few hours a day for someone who can work out the exact error in the debug.logs that you have provided as they should be indepth enough for someone who knows more about the source code of bitcoin core.
What does it say at the bottom of the screen next to the loading bar?
Is is saying that it is syncronising with blocks or "no block source avaliable" etc...
Is is saying that it is syncronising with blocks or "no block source avaliable" etc...
it seems as "normal" although I see 0 connections, sometimes it goes to 8 then goes away....
So it's sticking on connecting to peers according to that, do you have any new firewalls that could be blocking it (or your ISP) although it's not even loading up the list of peers that they normally have...
nothing new really... I tried to use a proxy just earlier but no difference, I can see that there is network traffic, like 3MB... this is very odd.. on another forum someone suggested to delete the latest blk and rev file.. what u think of that? thank you
If you do that it'll reindex your entire blockchain.
How long did it take to sync, as it'll do all of that again?
I'd sooner suggest booting your computer in "safe mode with networking" and run your bitcoin core to see that it definitely isn't a firewall issue.
In safe mode now and it seems exactly the same... teued to get connections for a bit then blinks then off again.
The whole chain? Well im on a 17mbit connection.. that will be long.
Any other ideas? Oh actually the pc went to standby when i was home without shutting down the core client .. laptop ... altho that happened before.
Thank you
What does it say at the bottom of the screen next to the loading bar?
Is is saying that it is syncronising with blocks or "no block source avaliable" etc...
Is is saying that it is syncronising with blocks or "no block source avaliable" etc...
it seems as "normal" although I see 0 connections, sometimes it goes to 8 then goes away....
So it's sticking on connecting to peers according to that, do you have any new firewalls that could be blocking it (or your ISP) although it's not even loading up the list of peers that they normally have...
nothing new really... I tried to use a proxy just earlier but no difference, I can see that there is network traffic, like 3MB... this is very odd.. on another forum someone suggested to delete the latest blk and rev file.. what u think of that? thank you
If you do that it'll reindex your entire blockchain.
How long did it take to sync, as it'll do all of that again?
I'd sooner suggest booting your computer in "safe mode with networking" and run your bitcoin core to see that it definitely isn't a firewall issue.
What does it say at the bottom of the screen next to the loading bar?
Is is saying that it is syncronising with blocks or "no block source avaliable" etc...
Is is saying that it is syncronising with blocks or "no block source avaliable" etc...
it seems as "normal" although I see 0 connections, sometimes it goes to 8 then goes away....
So it's sticking on connecting to peers according to that, do you have any new firewalls that could be blocking it (or your ISP) although it's not even loading up the list of peers that they normally have...
nothing new really... I tried to use a proxy just earlier but no difference, I can see that there is network traffic, like 3MB... this is very odd.. on another forum someone suggested to delete the latest blk and rev file.. what u think of that? thank you
What does it say at the bottom of the screen next to the loading bar?
Is is saying that it is syncronising with blocks or "no block source avaliable" etc...
Is is saying that it is syncronising with blocks or "no block source avaliable" etc...
it seems as "normal" although I see 0 connections, sometimes it goes to 8 then goes away....
So it's sticking on connecting to peers according to that, do you have any new firewalls that could be blocking it (or your ISP) although it's not even loading up the list of peers that they normally have...
What does it say at the bottom of the screen next to the loading bar?
Is is saying that it is syncronising with blocks or "no block source avaliable" etc...
Is is saying that it is syncronising with blocks or "no block source avaliable" etc...
it seems as "normal" although I see 0 connections, sometimes it goes to 8 then goes away....
https://snag.gy/ATcaCy.jpg
https://snag.gy/1vwMWN.jpg
What does it say at the bottom of the screen next to the loading bar?
Is is saying that it is syncronising with blocks or "no block source avaliable" etc...
Is is saying that it is syncronising with blocks or "no block source avaliable" etc...
Can you find the session log where the error originally started to occur and the previous session log before it.
ok here's 3
https://pastebin.com/RLEJKUNQ
thanks
Can you find the session log where the error originally started to occur and the previous session log before it.
Can you post your debug.log there looks like there probably is an issue.
It'll be in the data folder for bitcoin core, either C:\users\username\appdata\roaming\bitcoin, C:\users\username\appdata\local\bitcoin or ~/.bitcoin depending on your operating system (if you didn't set a custom difrectory).
It'll be in the data folder for bitcoin core, either C:\users\username\appdata\roaming\bitcoin, C:\users\username\appdata\local\bitcoin or ~/.bitcoin depending on your operating system (if you didn't set a custom difrectory).
the whole thing? is like 10mb
Unless you can post today's stuff then yes.
you can use pastebin https://pastebin.com/ to put it up.
this is from the last session, there's some ERROR if u go down... thanks
2018-07-29 17:42:24 Bitcoin Core version v0.16.1 (release build)
2018-07-29 17:42:24 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-07-29 17:42:24 Assuming ancestors of block 0000000000000000005214481d2d96f898e3d5416e43359c145944a909d242e0 have valid signatures.
2018-07-29 17:42:24 Setting nMinimumChainWork=000000000000000000000000000000000000000000f91c579d57cad4bc5278cc
2018-07-29 17:42:24 Using the 'sse4' SHA256 implementation
2018-07-29 17:42:24 Using RdRand as an additional entropy source
2018-07-29 17:42:26 Default data directory XXXXXXXXXXXXXXXXXXXXXXXXX
2018-07-29 17:42:26 Using data directory XXXXXXXXXXXXXXXXXXXXXXXXX
2018-07-29 17:42:26 Using config file XXXXXXXXXXXXXXXXXXXXXXXXX
2018-07-29 17:42:26 Using at most 125 automatic connections (2048 file descriptors available)
2018-07-29 17:42:26 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2018-07-29 17:42:26 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2018-07-29 17:42:26 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2018-07-29 17:42:26 Using 4 threads for script verification
2018-07-29 17:42:26 Using wallet directory XXXXXXXXXXXXXXXXXXXXXXXXX
2018-07-29 17:42:26 init message: Verifying wallet(s)...
2018-07-29 17:42:26 scheduler thread start
2018-07-29 17:42:26 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2018-07-29 17:42:26 Using wallet XXXXXXXXXXXXXXXXXXXXXXXXX
2018-07-29 17:42:26 CDBEnv::Open: LogDir=XXXXXXXXXXXXXXXXXXXXXXXXX
2018-07-29 17:42:26 Cache configuration:
2018-07-29 17:42:26 * Using 2.0MiB for block index database
2018-07-29 17:42:26 * Using 8.0MiB for chain state database
2018-07-29 17:42:26 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2018-07-29 17:42:26 init message: Loading block index...
2018-07-29 17:42:26 Opening LevelDB in XXXXXXXXXXXXXXXXXXXXXXXXX\blocks\index
2018-07-29 17:42:27 Opened LevelDB successfully
2018-07-29 17:42:27 Using obfuscation key for XXXXXXXXXXXXXXXXXXXXXXXXX\blocks\index: 0000000000000000
2018-07-29 17:42:34 LoadBlockIndexDB: last block file = 1326
2018-07-29 17:42:34 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=102, size=93814955, heights=533642...533816, time=2018-07-25...2018-07-26)
2018-07-29 17:42:34 Checking all blk files are present...
2018-07-29 17:42:34 LoadBlockIndexDB: transaction index disabled
2018-07-29 17:42:34 Opening LevelDB in D:\Bitcoin\chainstate
2018-07-29 17:42:35 Opened LevelDB successfully
2018-07-29 17:42:35 Using obfuscation key for XXXXXXXXXXXXXXXXXXXXXXXXX\chainstate: b545d44daeb98bc2
2018-07-29 17:42:36 Loaded best chain: hashBestChain=000000000000000000159398b609db2cf004c969873665c47a646c6518d4a1f0 height=533815 date=2018-07-26 19:42:46 progress=0.997340
2018-07-29 17:42:36 init message: Rewinding blocks...
2018-07-29 17:42:42 init message: Verifying blocks...
2018-07-29 17:42:42 Verifying last 6 blocks at level 3
2018-07-29 17:42:42 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2018-07-29 17:42:52 No coin database inconsistencies in last 7 blocks (14060 transactions)
2018-07-29 17:42:52 block index 25246ms
2018-07-29 17:42:52 init message: Loading wallet...
2018-07-29 17:42:52 nFileVersion = 160100
2018-07-29 17:42:52 Keys: 0 plaintext, 1160 encrypted, 1160 w/ metadata, 1160 total
2018-07-29 17:42:52 wallet 177ms
2018-07-29 17:42:52 setKeyPool.size() = 999
2018-07-29 17:42:52 mapWallet.size() = 44
2018-07-29 17:42:52 mapAddressBook.size() = 44
2018-07-29 17:42:52 mapBlockIndex.size() = 533836
2018-07-29 17:42:52 nBestHeight = 533815
2018-07-29 17:42:52 torcontrol thread start
2018-07-29 17:42:52 AddLocal([2001:0:4137:9e76:3860:1d02:26d8:9640]:8333,1)
2018-07-29 17:42:52 Discover: gabrio-asus - 2001:0:4137:9e76:3860:1d02:26d8:9640
2018-07-29 17:42:52 Bound to [::]:8333
2018-07-29 17:42:52 Bound to 0.0.0.0:8333
2018-07-29 17:42:52 init message: Loading P2P addresses...
2018-07-29 17:42:52 AddToWallet dbfd412566946c77e732b73730c22a7bb10a55318b952de9b194136e361c7c7a
2018-07-29 17:42:52 Imported mempool transactions from disk: 15 succeeded, 0 failed, 0 expired, 0 already there
2018-07-29 17:42:52 Loaded 62950 addresses from peers.dat 635ms
2018-07-29 17:42:52 init message: Loading banlist...
2018-07-29 17:42:52 init message: Starting network threads...
2018-07-29 17:42:52 init message: Done loading
2018-07-29 17:42:52 dnsseed thread start
2018-07-29 17:42:52 addcon thread start
2018-07-29 17:42:52 net thread start
2018-07-29 17:42:52 msghand thread start
2018-07-29 17:42:52 opencon thread start
2018-07-29 17:42:52 GUI: Platform customization: "windows"
2018-07-29 17:42:52 GUI: PaymentServer::LoadRootCAs: Loaded 59 root certificates
2018-07-29 17:42:53 New outbound peer connected: version: 70015, blocks=534294, peer=0
2018-07-29 17:42:53 ERROR: AcceptBlockHeader: block 0000000000000000001f642d24d3968eeef81460531346adbfb9882dd711ed45 is marked invalid
2018-07-29 17:42:53 ERROR: invalid header received
2018-07-29 17:42:59 New outbound peer connected: version: 70015, blocks=534294, peer=1
2018-07-29 17:43:00 ERROR: AcceptBlockHeader: block 0000000000000000001f642d24d3968eeef81460531346adbfb9882dd711ed45 is marked invalid
2018-07-29 17:43:00 ERROR: invalid header received
2018-07-29 17:43:03 Loading addresses from DNS seeds (could take a while)
2018-07-29 17:43:05 141 addresses found from DNS seeds
2018-07-29 17:43:05 dnsseed thread exit
2018-07-29 17:43:06 New outbound peer connected: version: 70015, blocks=534294, peer=2
2018-07-29 17:43:07 New outbound peer connected: version: 70015, blocks=534294, peer=3
2018-07-29 17:43:07 ERROR: AcceptBlockHeader: block 0000000000000000001f642d24d3968eeef81460531346adbfb9882dd711ed45 is marked invalid
2018-07-29 17:43:07 ERROR: invalid header received
2018-07-29 17:43:07 ERROR: AcceptBlockHeader: block 0000000000000000001f642d24d3968eeef81460531346adbfb9882dd711ed45 is marked invalid
2018-07-29 17:43:07 ERROR: invalid header received
2018-07-29 17:43:30 New outbound peer connected: version: 70015, blocks=534294, peer=5
2018-07-29 17:43:31 ERROR: AcceptBlockHeader: block 0000000000000000001f642d24d3968eeef81460531346adbfb9882dd711ed45 is marked invalid
2018-07-29 17:43:31 ERROR: invalid header received
2018-07-29 17:43:41 New outbound peer connected: version: 70015, blocks=534294, peer=6
2018-07-29 17:43:42 ERROR: AcceptBlockHeader: block 0000000000000000001f642d24d3968eeef81460531346adbfb9882dd711ed45 is marked invalid
2018-07-29 17:43:42 ERROR: invalid header received
2018-07-29 17:43:42 New outbound peer connected: version: 70015, blocks=534294, peer=7
2018-07-29 17:43:54 New outbound peer connected: version: 70015, blocks=534294, peer=8
2018-07-29 17:43:54 ERROR: AcceptBlockHeader: block 0000000000000000001f642d24d3968eeef81460531346adbfb9882dd711ed45 is marked invalid
2018-07-29 17:43:54 ERROR: invalid header received
2018-07-29 17:43:54 New outbound peer connected: version: 70015, blocks=534294, peer=9
2018-07-29 17:43:55 ERROR: AcceptBlockHeader: block 0000000000000000001f642d24d3968eeef81460531346adbfb9882dd711ed45 is marked invalid
2018-07-29 17:43:55 ERROR: invalid header received
2018-07-29 17:43:55 New outbound peer connected: version: 70015, blocks=534294, peer=10
2018-07-29 17:43:55 ERROR: AcceptBlockHeader: block 0000000000000000001f642d24d3968eeef81460531346adbfb9882dd711ed45 is marked invalid
2018-07-29 17:43:55 ERROR: invalid header received
2018-07-29 17:43:56 New outbound peer connected: version: 70015, blocks=534294, peer=11
2018-07-29 17:43:57 New outbound peer connected: version: 70015, blocks=534294, peer=12
2018-07-29 17:43:57 ERROR: AcceptBlockHeader: block 0000000000000000001f642d24d3968eeef81460531346adbfb9882dd711ed45 is marked invalid
2018-07-29 17:43:57 ERROR: invalid header received
2018-07-29 17:43:57 ERROR: AcceptBlockHeader: block 0000000000000000001f642d24d3968eeef81460531346adbfb9882dd711ed45 is marked invalid
2018-07-29 17:43:57 ERROR: invalid header received
2018-07-29 17:44:25 New outbound peer connected: version: 70015, blocks=534294, peer=13
2018-07-29 17:44:25 tor: Thread interrupt
2018-07-29 17:44:25 torcontrol thread exit
2018-07-29 17:44:25 Shutdown: In progress...
2018-07-29 17:44:25 addcon thread exit
2018-07-29 17:44:25 net thread exit
2018-07-29 17:44:25 msghand thread exit
2018-07-29 17:44:30 opencon thread exit
2018-07-29 17:44:31 scheduler thread interrupt
2018-07-29 17:44:31 Dumped mempool: 0s to copy, 0.058844s to dump
2018-07-29 17:44:31 Shutdown: done
Can you post your debug.log there looks like there probably is an issue.
It'll be in the data folder for bitcoin core, either C:\users\username\appdata\roaming\bitcoin, C:\users\username\appdata\local\bitcoin or ~/.bitcoin depending on your operating system (if you didn't set a custom difrectory).
It'll be in the data folder for bitcoin core, either C:\users\username\appdata\roaming\bitcoin, C:\users\username\appdata\local\bitcoin or ~/.bitcoin depending on your operating system (if you didn't set a custom difrectory).
the whole thing? is like 10mb
Unless you can post today's stuff then yes.
you can use pastebin https://pastebin.com/ to put it up.
Can you post your debug.log there looks like there probably is an issue.
It'll be in the data folder for bitcoin core, either C:\users\username\appdata\roaming\bitcoin, C:\users\username\appdata\local\bitcoin or ~/.bitcoin depending on your operating system (if you didn't set a custom difrectory).
It'll be in the data folder for bitcoin core, either C:\users\username\appdata\roaming\bitcoin, C:\users\username\appdata\local\bitcoin or ~/.bitcoin depending on your operating system (if you didn't set a custom difrectory).
the whole thing? is like 10mb
Can you post your debug.log there looks like there probably is an issue.
It'll be in the data folder for bitcoin core, either C:\users\username\appdata\roaming\bitcoin, C:\users\username\appdata\local\bitcoin or ~/.bitcoin depending on your operating system (if you didn't set a custom difrectory).
It'll be in the data folder for bitcoin core, either C:\users\username\appdata\roaming\bitcoin, C:\users\username\appdata\local\bitcoin or ~/.bitcoin depending on your operating system (if you didn't set a custom difrectory).
hi guys,
I've launched core this morning on 99.74% and it's still there after all day, are there some issues? I see 0 active connections to bitcoin network...
thanks,
gab
I've launched core this morning on 99.74% and it's still there after all day, are there some issues? I see 0 active connections to bitcoin network...
thanks,
gab
Jump to: