Quote from: LADAcoin on October 19, 2017, 02:44:40 PM

Quote from: m1rk0z on October 19, 2017, 11:09:04 AM

Quote from: popcoins on October 19, 2017, 09:55:46 AM

Quote from: m1rk0z on October 17, 2017, 04:32:28 PM

Quote from: LADAcoin on October 17, 2017, 04:00:08 PM

Quote from: m1rk0z on October 17, 2017, 02:23:15 PM

Quote from: popcoins on October 17, 2017, 07:59:24 AM

Quote from: m1rk0z on October 16, 2017, 09:58:19 PM

Hi,
I've download the latest wallet and it segfaults when it reaches current block downloading. How can I solve?

Have you managed to get it worked out syn to the current block?
By the way what is "segfaults"?
Please let me know your progress if you can, I am just about to test the new wallet.
Cheers

It just arrives at the last block or few blocks before and the daemon crashes with a segmentation fault error (a common error given when a program tries to access illegal area in the RAM).
If I use the old wallet all works flawlessly but it syncs to an height above the one reported by the explorer/Cryptopia (a separate blockchains for the new wallet?)

Let me know if you encounter the same problem, too.

Please resynchronize the wallet from the very beginning, delete the folders
blocks
chainstate
and delete file peers.dat
and restart ladacoin wallet

Done right now.
Deleted old ladacoin datadir, started the already compiled wallet, it synced till block 261543 and then crashed. When I restarted it went on from block ~160000 (about 100000 blocks less).

This has happened before back to the last version of the Ladacoin wallet. It was casused because a few nodes was connected to my wallet and their blocks was stucked and not being syned correctly. I think we have to search the right nodes and have them edited in the .conf file so when the wallet first executed it will connect to tbe right nodes at start. Hope this will work out. ;-)

Have you been able to sync correctly? Or do you have the same problem?
I tried connecting to a "good" node, but I get an error regarding wrong header and I don't know what to do.
By the way, I think I'm able to download till the last block (reporter by the explorer) and as soon as I have it in my blockchain I get the segfault (and it stops debug.log from recording all the info, cause I see from strace a "Done loading" which isn't in debug file).
If it is a bug already seen developers should address it...

Please quote here last entered debug.log. I want see this error in to debug.log

And what do you connect to the wallet after synchronization?

The log is normal, nothing strange, just block syncing and suddenly it stops (when I get the segmentation fault from the daemon). I will post the (last part of) debug.log as soon as I resync the daemon

What does the second question mean? I just start the daemon, I wait for it to sync and, just when it approaches last blocks... crash!

Quote from: popcoins on October 19, 2017, 03:06:51 PM

Quote from: m1rk0z on October 19, 2017, 11:09:04 AM

Quote from: popcoins on October 19, 2017, 09:55:46 AM

Quote from: m1rk0z on October 17, 2017, 04:32:28 PM

Quote from: LADAcoin on October 17, 2017, 04:00:08 PM

Quote from: m1rk0z on October 17, 2017, 02:23:15 PM

Quote from: popcoins on October 17, 2017, 07:59:24 AM

Quote from: m1rk0z on October 16, 2017, 09:58:19 PM

Hi,
I've download the latest wallet and it segfaults when it reaches current block downloading. How can I solve?

Have you managed to get it worked out syn to the current block?
By the way what is "segfaults"?
Please let me know your progress if you can, I am just about to test the new wallet.
Cheers

It just arrives at the last block or few blocks before and the daemon crashes with a segmentation fault error (a common error given when a program tries to access illegal area in the RAM).
If I use the old wallet all works flawlessly but it syncs to an height above the one reported by the explorer/Cryptopia (a separate blockchains for the new wallet?)

Let me know if you encounter the same problem, too.

Please resynchronize the wallet from the very beginning, delete the folders
blocks
chainstate
and delete file peers.dat
and restart ladacoin wallet

Done right now.
Deleted old ladacoin datadir, started the already compiled wallet, it synced till block 261543 and then crashed. When I restarted it went on from block ~160000 (about 100000 blocks less).

This has happened before back to the last version of the Ladacoin wallet. It was casused because a few nodes was connected to my wallet and their blocks was stucked and not being syned correctly. I think we have to search the right nodes and have them edited in the .conf file so when the wallet first executed it will connect to tbe right nodes at start. Hope this will work out. ;-)

Have you been able to sync correctly? Or do you have the same problem?
I tried connecting to a "good" node, but I get an error regarding wrong header and I don't know what to do.
By the way, I think I'm able to download till the last block (reporter by the explorer) and as soon as I have it in my blockchain I get the segfault (and it stops debug.log from recording all the info, cause I see from strace a "Done loading" which isn't in debug file).
If it is a bug already seen developers should address it...

Try to limit your node connections to max of 4, so only the good nodes that you found from the explorer, those that are fully syned, then add the good ones to the .conf file.
So when the wallet first executed should connect straight to those working ones. This should bypass the troubling nodes.

How to set max connections to 4? Btw, thanks for your help