Working on seeing what's going on with 2.0.0.5 because some people have issues, and some don't.
Hang on tight with us, in the meantime you can use 3 and 4 just fine.
Hang on tight with us, in the meantime you can use 3 and 4 just fine.
Working on seeing what's going on with 2.0.0.5 because some people have issues, and some don't.
Hang on tight with us, in the meantime you can use 3 and 4 just fine.
Hang on tight with us, in the meantime you can use 3 and 4 just fine.
It seems to be only people running linux for the masternode have problems.
Windows masternodes and windows controller wallets seem to be fine, judging from the replies on this thread
I can confirm 2.0.0.5 is crashing within 24 hours of starting it up on Windows 10 server VPS. It results in a C++ runtime error and crashes after about 24 hours of startup. I am using 2.0.0.5 as a controller as well, but I only run it for a few minutes a day to sync up and see any payouts, it's not running 24/7.
I wasnt sure what was going on, as something was causing my entire VPS to hang several times for the past week or so, forcing me to reboot it from the host's account website...not something I like to do as it risks corrupting blockchain databases, but i had no choice...suspecting the cause to be my newly installed Bitcloud wallet, i moved it to another Windows 10 VPS a couple of days ago...about 24 hours later i logged on and found it to have crashed with a C++ runtime error again., confirming my suspicions..this time it just crashed the Bitcloud wallet, instead of hanging the entire VPS, thank God.
I did notice that before the wallet crashed, its memory usage was steadily increasing, surpassing 1GB of RAM and continued rising until it crashed. Maybe some sort of memory leak.
Are those able to tun MN 2.0.0.5 using a cold/controller wallet combination, or just using a hotwallet? Maybe the bug lies in the cold/controller combination?
I'm new to Bitcloud MN, so i thought i was being smart starting out with 2.0.0.5
im glad to read in this thread that I'm not the only one (ie im not screwing something up ) and that v2003 and 4 have no such issues, so I will be installing the older version when i get the chance. To that end, can someone please post the link to windows version 2.0.0.4? On Github I can only see the 2.0.0.5 for windows. v4 and 3 have only the source code and linux versions, nothing for windows.
looking forward to the fix. Thanks
Hello,
Thank you for your feedback.
I have uploaded version 2.0.0.4 under release tag 2.0.0.3.
Please try the version 2.0.0.6. from github.
Kind Regards Christian
I tried 2.0.0.7 but it seems to be crashing as well.
I downloaded 2.0.0.4 under the 2.0.0.3 tag, but it is giving me the error below on startup
Assertion failed!
File: main.cpp, Line 2077
Expression: hashPrevBlock == view.GetBestBlock()
I clicked 'Ignore' and then it said i have a corrupted database and is now reindexing the blocks. Will update post with results when i get the chance.
also it shows v2.0.0.0-gcbcb549 on the splash screen, rather than 2.0.0.4, is this ok?
Update: the MN wallet (v2004) synced and running, and controller indicates MN is active. However, the v2004 MN wallet is only connecting to 1 and sometimes 2 peers and is
NOT seeing any other masternodes on the network, whereas v2007 is connecting to 16...same addnodes are in both .conf files. it seems old wallet is NOT compatible with connections to the new one...is this an issue possibly putting me on a fork off the main blockchain or is it ok?
The wallet 2.0.0.0 isn't compatible with the main-net. I recommend to use the version 2.0.0.7. It is possible to delete the folder "chainstate" and "blocks" if you have any problems.
Kind Regards Christian
my wallet still since 2 days ago... hope my upgrade to 2.0.0.7 can finished my problems 
