Giving myself the answer ;-):

It seems that the heavy loading of so many blockheaders just consumed a lot 
o CPU and that caused that bas user experience to have the startup getting 
stalled.
With a newly created up to date checkpoint file the initial download is not 
super fast. 

There are probably a few minor issues like the disconnection from the local 
node, the orphan (seems an block processing ordering issue) and the logs 
not being clear... 


Am Donnerstag, 6. Dezember 2018 00:27:24 UTC+1 schrieb Manfred Karrer:
>
> After further testing I could isolate the issue to be between v14.4. and 
> v.14.5. Bisq is based on 14.4. After comparing and I found that the 
> checkpoint files was causing the issue. After updating it from 14.5. it 
> works. Any idea why?
>
> I got those logs in the "broken" version:
> 00:09:44 26 AbstractBlockChain.add: Block does not connect: 
> 000000000001c7ea71d37675ab53ee77851d46bcd2688077343eeccda4d50570 prev 
> 000000000000ff74c2f0973e6b9eb0fa6f9033ee093dc38e7cbec52b7cc5ef41
> 00:09:45 26 AbstractBlockChain.tryConnectingOrphans: Connected orphan 
> 000000000001c7ea71d37675ab53ee77851d46bcd2688077343eeccda4d50570
> 00:09:45 26 AbstractBlockChain.tryConnectingOrphans: Connected 1 orphan 
> blocks.
>
> maybe thats related...
>
> Am Dienstag, 4. Dezember 2018 17:18:35 UTC+1 schrieb Andreas Schildbach:
>>
>> The stall messages are just a symptom. For finding the cause have a look 
>> at the logfile of both bitcoinj and Bitcoin Core. 
>>
>>
>> On 04/12/2018 00.12, Manfred Karrer wrote: 
>> > I use whitelist=127.0.0.1 in the bitcoin.conf file. There was another 
>> > property but that does require the port as well and we use random local 
>> > ports. 
>> > 
>> > Am Montag, 3. Dezember 2018 23:12:33 UTC+1 schrieb Jameson Lopp: 
>> > 
>> >     Hmmmm I believe I ran into similar issues a while back - have you 
>> >     tried whitelisting the IP of your bitcoinj client in the Bitcoin 
>> >     Core conf? 
>> > 
>> >     I also vaguely recall getting stalled connections from time to time 
>> >     and adding logic in my app to hack around it by disconnecting and 
>> >     reconnecting. 
>> > 
>> >     On Sun, Dec 2, 2018 at 4:51 PM Manfred Karrer <manfred...@gmail.com> 
>>
>> >     wrote: 
>> > 
>> >         Here is a bug report form a user as 
>> >         well: https://github.com/bisq-network/bisq/issues/1823 
>> >         <https://github.com/bisq-network/bisq/issues/1823> 
>> > 
>> >         Here is the fork we are using: 
>> >         https://github.com/bisq-network/bitcoinj/commits/bisq_0.14.4.1 
>> >         <https://github.com/bisq-network/bitcoinj/commits/bisq_0.14.4.1> 
>>
>> > 
>> > 
>> >         Am Sonntag, 2. Dezember 2018 18:53:49 UTC+1 schrieb Manfred 
>> Karrer: 
>> > 
>> >             When having latest Bitcoin Core running in testnet and 
>> >             starting a new BitcoinJ instance (Bisq, using latest 
>> >             BitcoinJ release) I get download stalled at 91MB (as seen 
>> in 
>> >             Bictoin Core debug window) then gets disconnected from 
>> >             Bitcoin Core and then reconnects but gets very low 
>> >             bandwidth. Seems Bitcoin Core added some ddos protection. I 
>> >             never observed that in earlier versions. Does anyone know 
>> >             how to avoid that issue? 
>> > 
>> >             With mainet it seems even lower, about 7,8 MB. 
>> > 
>> >             I can reproduce that with each fresh start (deleting Bisq 
>> >             app directory so it starts as new node again). 
>> > 
>> >             Br, 
>> >             Manfred 
>> > 
>> >         -- 
>> >         You received this message because you are subscribed to the 
>> >         Google Groups "bitcoinj" group. 
>> >         To unsubscribe from this group and stop receiving emails from 
>> >         it, send an email to bitcoinj+u...@googlegroups.com. 
>> >         For more options, visit https://groups.google.com/d/optout 
>> >         <https://groups.google.com/d/optout>. 
>> > 
>> > -- 
>> > You received this message because you are subscribed to the Google 
>> > Groups "bitcoinj" group. 
>> > To unsubscribe from this group and stop receiving emails from it, send 
>> > an email to bitcoinj+u...@googlegroups.com 
>> > <mailto:bitcoinj+u...@googlegroups.com>. 
>> > For more options, visit https://groups.google.com/d/optout. 
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"bitcoinj" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bitcoinj+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to