I have two amd64 compilation enviroments which have been capable to compile all the wallets this far but I'm facing connection issues in the wallet. Tried this with another computer and got stuck with same issue :/
~/wallets/granitecoin# ./granited getinfo
error: couldn't connect to server
My config path is
And it looks like this from inside
Is the configuration file kind of correct? Removed the user credentials from the paste.
Tried also adding nodes on run but no success.
Might it be use of BDB5.3 cause that I'm unable to get connections when I compile latest source from dev's github? I've tried to compile with all USE_UPNP= modes 1,0,-.
I'm compiling granited amd64 and it drops some DB related errors, but bypasses them. The daemon itself initializes itself making wallet file and folders to datadir.
Some coins do have autotools so at configuration part before making I could put a --with-incompatible-bdb
-parameter to get rid of BDB related errors in compilation, I tried to do own configure file with autotools but the configurations does not work out of the box and takes some time to finish it as a working one.
Any other solutions than using autotools? I'd like to compile my own wallets. The reason on Linux is because there's BDB and GLIBC library version differences and some wallets which are compiled as static and used in system which have other version of BDB than the wallet is compiled with and because of that the risk of wallet getting corrupt at random point is very high. I've faced it one time on production use and that made me learn. Also, on Windows especially because there is much trojans and similar in those. Third reason is I'd like to choose the version of OpenSSL because some wallets might have bugs.
Thanks in advance
hi bawaler ...
tanx for letting us know ...
the latest build is compiling but failing to run - as i have experienced this currently with a number of coins that ive been 'helping' with - and it seems now granite is affected by it ...
the latest update to boost and openssl and bdb as a combination are causing a database issue with the creation of the peers.dat file ... and even if you get to that level of file creation - the daemon ( or wallet ) crashes and goes no further ...
the debug.log will show exactly that issue ( tail -f ~/<user>/.GraniteCoin/debug.log ) - and we are working on it at the moment ... there seem to be a few changes that have been made to the updates of both boost and bdb in the latest versions which are causing this ... and we are trying to locate the affected areas in the granite code ...
again - this issue has been now seen in a few other coins also - and fixes have been looked at and we are working on getting the fix into the current code of granite at the moment ...
there is only a few blocks left to the last bonus block - where 100krgn will be minted in this one block - so if you are mining and hit the block on any of the pools - they can hold the coins until we can organize a fix ...
what linux are you using? ... maybe i can send you a precompiled wallet or daemon for the time being ... as this issue is a very recent one ( and one we were not expecting ) a workaround / fix will help - but we are already looking at a full rebase ( and have been planning on it for the last two months now ) to advance the codebase for granite for its future growth ...
i cannot see you have done wrong in your setup - in fact its a good setup
the only nodes you require are the three seednodes normally ( if you have the older version of the wallet - the seednodes are now hardcoded into the current codebase ) - they are currently running and fully functional ( and fast ) ...
tanx for bringing this to our attention - and we will come back with a fix soon ...
let me know if i can help you further ... as i do have other versions compiled ( ubuntu daemon - fedora 23 x64 qt5 wallet - centos 7 x64 static daemon ) that ARE functional at the moment ...