Running startnodecore from the CLI, nodecore kept unexpectedly crashing and disappearing after updating from nodecore-0.2.0 r3 to r4 on Ubuntu. This was the error log: veriblock.nodecore-error.log
When trying to launch the new version of the software: a new wallet address and a new BTC Testnet address were "created", which was odd, and nodecore kept crashing after a few seconds to a few minutes.
Restarting the PC fixed the problem though (probably another nodecore instance running or hung in the background causing the problem), and the new wallet addresses disappeared (probably the 2nd nodecore instance couldn't write to the locked files).
You might want to add some detection for other instances running and display a warning or error message of the bad state, or to prevent it. That would make it easier to figure out what might be wrong. Thanks!
Running startnodecore from the CLI, nodecore kept unexpectedly crashing and disappearing after updating from nodecore-0.2.0 r3 to r4 on Ubuntu. This was the error log: veriblock.nodecore-error.log When trying to launch the new version of the software: a new wallet address and a new BTC Testnet address were "created", which was odd, and nodecore kept crashing after a few seconds to a few minutes.
Restarting the PC fixed the problem though (probably another nodecore instance running or hung in the background causing the problem), and the new wallet addresses disappeared (probably the 2nd nodecore instance couldn't write to the locked files).
You might want to add some detection for other instances running and display a warning or error message of the bad state, or to prevent it. That would make it easier to figure out what might be wrong. Thanks!