thelindaprojectinc / metrix Goto Github PK

there is an error loading block database on the linda qt wallet

I've downloaded the latest master branch.
Compilation fails here:
In file included from ./qtum/qtumstate.h:10,
from ./validation.h:41,
from bench/block_assemble.cpp:11:
./qtum/qtumtransaction.h: In static member function ‘static VersionVM VersionVM::fromRaw(uint32_t)’:
./qtum/qtumtransaction.h:24:24: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
24 | VersionVM x = (VersionVM)&val;
| ^~~~~~~~~~~~~~~~
./qtum/qtumtransaction.h:24:24: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
In file included from ./qtum/qtumstate.h:10,
from ./validation.h:41,
from bench/checkblock.cpp:9:
./qtum/qtumtransaction.h: In static member function ‘static VersionVM VersionVM::fromRaw(uint32_t)’:
./qtum/qtumtransaction.h:24:24: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
24 | VersionVM x = (VersionVM)&val;
| ^~~~~~~~~~~~~~~~
./qtum/qtumtransaction.h:24:24: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
In file included from /usr/include/c++/9/tuple:39,
from /usr/include/c++/9/functional:54,
from ./bench/bench.h:8,
from bench/block_assemble.cpp:5:
/usr/include/c++/9/array: In instantiation of ‘struct std::__array_traits<std::shared_ptr, 18446744073709551257>’:
/usr/include/c++/9/array:110:56: required from ‘struct std::array<std::shared_ptr, 18446744073709551257>’
bench/block_assemble.cpp:30:69: required from here
/usr/include/c++/9/array:50:19: error: size ‘18446744073709551257’ of array exceeds maximum object size ‘9223372036854775807’
50 | typedef _Tp _Type[_Nm];
| ^~~~~

You are unable to leave the calldata empty when using the sendtocontract RPC method.

Daemon option blocknotify does not execute when receiving a new block.

Exemplary tested on 18.04. ubuntu VPS
"version" : "v3.1.0.0-g",
"protocolversion" : 70000,

Lindad getinfo shows these THREE typical errors:

1. Lindad getinfo shows errors: "EXCEPTION... "
   short after it shows beahaviour below or crashes completly and need to start again.

2. Lindad hangs / crashes but is still visible htop with SHRvalue of ZERO [0] and TIME+ up to 12h
   
   Can only be solved by killing the deamon before restarting it.

3. Lindad block sync hangs and only stopping of deamon, bootsrapping and restart helps to get it in sync again

During all the three errors CPU consumption is often around 100% all the time!

If different rootscauses are investigated by the DEV's plz split this issues into 3 single ones...

Next time you have a commit you should update the readme file to clean up the team section. This is obviously not a priority but it's a little out of date. Should be able to do it with the next actual commit.

I just thought I would share this as it might be a bug in the coding. Please run a fresh wallet sync to see if you can reenact the issue.

I have found a full sync with a fresh wallet hangs time to time on a block. You have to restart the daemon to get it working through the blocks again.

connect() to #.#.#.#:33820 failed after select(): Connection refused (111)
socket recv error Connection reset by peer (104)

Also this fatal error came up after leaving it stuck for hours...

************************
EXCEPTION: St13runtime_error
tinyformat: Not enough conversion specifiers in format string
Metrix in ProcessMessages()

Again, restarting the daemon got it working.

Both errors have occurred on two separate wallet setups.

Linux x64 CLI wallet v3.4.0.0

Is there any reason why the MacOSX qt wallet syncs slowly and hangs multiples times, compared to the Win64 qt wallet? It can never keep up with the latest block, unless the bootstrap file happens to be super fresh off the cooker.

I have witnessed this on previous versions of the wallet as well, so it's not a recent issue.

OpenSSL version: 1.0.2g 1 Mar 2016

Does that come packaged with the qt wallet? As my OpenSSL version is higher than that!

In the Altitude wallet you have the option to change language. This works for the current session in the wallet. But when you close down the wallet and open it up again it's in my native language again (Dutch).

I've currently installed the latest version of metrix core, 4.0.6, on Linux and started staking as follows:

On one shell: metrixd
On another shell: metrix-cli walletpassphrase "$1" 99999999 true

Where $1 is the password.

Console output:
2021-04-13T04:23:33Z No coin database inconsistencies in last 6 blocks (18 transactions)
2021-04-13T04:23:33Z block index 13887ms
2021-04-13T04:23:33Z init message: Loading wallet...
2021-04-13T04:23:33Z BerkeleyEnvironment::Open: LogDir=/home/martin/.metrixcoin/wallets/database ErrorFile=/home/martin/.metrixcoin/wallets/db.log
2021-04-13T04:23:33Z [default wallet] Wallet File Version = 169900
2021-04-13T04:23:33Z [default wallet] Keys: 0 plaintext, 4008 encrypted, 4008 w/ metadata, 4008 total. Unknown wallet records: 0
2021-04-13T04:23:33Z [default wallet] Wallet completed loading in 496ms
2021-04-13T04:23:33Z [default wallet] setKeyPool.size() = 2000
2021-04-13T04:23:33Z [default wallet] mapWallet.size() = 417
2021-04-13T04:23:33Z [default wallet] mapAddressBook.size() = 2
2021-04-13T04:23:33Z block tree size = 199796
2021-04-13T04:23:33Z nBestHeight = 196690
2021-04-13T04:23:33Z torcontrol thread start
2021-04-13T04:23:33Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there
2021-04-13T04:23:33Z Bound to [::]:33830
2021-04-13T04:23:33Z Bound to 0.0.0.0:33830
2021-04-13T04:23:33Z init message: Loading P2P addresses...
2021-04-13T04:23:34Z Loaded 12687 addresses from peers.dat 332ms
2021-04-13T04:23:34Z init message: Starting network threads...
2021-04-13T04:23:34Z net thread start
2021-04-13T04:23:34Z addcon thread start
2021-04-13T04:23:34Z dnsseed thread start
2021-04-13T04:23:34Z init message: Done loading
2021-04-13T04:23:34Z opencon thread start
2021-04-13T04:23:34Z msghand thread start
2021-04-13T04:23:45Z Loading addresses from DNS seed mainnet.metrixcoin.com
2021-04-13T04:23:45Z 0 addresses found from DNS seeds
2021-04-13T04:23:45Z dnsseed thread exit
2021-04-13T04:23:46Z Leaving InitialBlockDownload (latching to false)
Speicherzugriffsfehler (Speicherabzug geschrieben)

After starting it a second time it works.

In version 3.1.0.1 wallet # 476204th block is not synchronized.

So I have to sync with a lower version wallet and have to reload the version again.