Help us test Nubits v2.1.0

That branch doesn’t seem to be updated for some time… That’s why I was asking.

The changes I mentioned were added a while ago but new builds haven’t been produced till today.

Ah, got it!
That leaves the question for the version of LevelDB open.

I just pushed the changes to the 2.1.0-RC branch (I pushed the tag but forgot to push the branch).

LevelDB is included in the source tree, so it’s not a new dependency.

That means if you compile the Nu wallet, the included LevelDB code is used?

@CoinGame, are you speaking of when the client hangs for a little bit and says not responding when switching between the NuBits and NuShares screens, or is there more to it than that? This at least would happen to me when I was still using Windows.

Yes.

1 Like

Great! That will prevent a lot of BD related problems. Thank you!

While the client is syncing it will usually hang for a few moments when switching units. When it’s fully synced it shouldn’t be as bad. That is expected and not the current issue.

This issue that I and few other have reported is the client hanging for upwards up 30 seconds (meaning the user interface freezes and is unusable). During this time memory usage of the client will usually jump to around 1GB, then sharply return to around 400Mb when the client becomes usable again. The trigger event appears to be when the client is not the currently focused application for a period of time. This has been mostly a Windows issue, but i’d like to hear others experiences from using the Linux build as well.

1 Like

Just installed Nu 2.1 RC7 binary as published on my Ubuntu 15.04 desktop instance to monitor LiquidBits payments. Will do some testing every now and then and report when encountering ‘hangs’ or other bugs.
It took more than a few minutes to convert a synchronised database with 2.1, one will need to be patient.

Upgrade of the database apparently failed. I couldn’t get Nu start, it was just stuck on the splash screen showing ‘Done’. Had to delete the blk*.dat files and sync again from start. Will try again later with another instance. Is there anyone been able to have a smooth conversion of a fully synchronised chain?

Did you check the debug file before you scrapped everything? That’s kind of a big deal. It would be great to know why it failed.

I have a 92Mb debug.log but I can’t find anything unusual other than many block cleanup messages. Or maybe that is already the debug.log from the new sync? Hmm… Ok, useless, Trying again…

Right, converting another wallet also on Linux-64-bit. Splash screen is showing ‘Done loading’ and frozen. Same problem.

Logs show this:

2016-01-10 01:40:46 Nu version v2.1.0-RC7-beta (2016-01-08 09:21:03 +0100)
2016-01-10 01:40:46 Using OpenSSL version OpenSSL 1.0.1g 7 Apr 2014
2016-01-10 01:40:46 Default data directory /home/user/.nu
2016-01-10 01:40:46 Using data directory /home/user/.nu
2016-01-10 01:40:46 Using at most 12 connections (1024 file descriptors available)
2016-01-10 01:40:46 Using 12 threads for script verification
2016-01-10 01:40:46 init message: Verifying wallet…
2016-01-10 01:40:46 dbenv.open LogDir=/home/user/.nu/database ErrorFile=/home/user/.nu/db.log
2016-01-10 01:40:46 Bound to [::]:7890
2016-01-10 01:40:46 Bound to 0.0.0.0:7890
2016-01-10 01:40:46 Hardlinked /home/user/.nu/blk0001.dat -> /home/user/.nu/blocks/blk00000.dat
2016-01-10 01:40:46 init message: Loading block index…
2016-01-10 01:40:46 Wiping LevelDB in /home/user/.nu/blocks/index
2016-01-10 01:40:46 Opening LevelDB in /home/user/.nu/blocks/index
2016-01-10 01:40:46 Opened LevelDB successfully
2016-01-10 01:40:46 Wiping LevelDB in /home/user/.nu/chainstate
2016-01-10 01:40:46 Opening LevelDB in /home/user/.nu/chainstate
2016-01-10 01:40:46 Opened LevelDB successfully
2016-01-10 01:40:46 Nu Network: genesis=0x000003cc2da5a0a289ad nBitsLimit=0x1e0fffff nBitsInitial=0x1e00ffff nStakeMinAge=604800 nCoinbaseMaturity=100 nCoinstakeMaturity=5000 nModifierInterval=14400
2016-01-10 01:40:46 Initializing databases…
2016-01-10 01:40:46 ResetSyncCheckpoint: pending for sync-checkpoint 11b331cb1e5ba525fdcd5915aa47ee9dc0ca79337e634beabc7be21b1e23b5b4
2016-01-10 01:40:46 ResetSyncCheckpoint: sync-checkpoint reset to 000003cc2da5a0a289ad0a590c20a8b975219ddc1204efd169e947dd4cbad73f
2016-01-10 01:40:46 init message: Verifying blocks…
2016-01-10 01:40:46 block index 21ms
2016-01-10 01:40:46 init message: Loading wallets…
2016-01-10 01:40:46 Loading wallet for unit S…
2016-01-10 01:40:46 nFileVersion = 2000100
2016-01-10 01:40:46 wallet 199ms
2016-01-10 01:40:46 Loading wallet for unit B…
2016-01-10 01:40:46 nFileVersion = 2000100
2016-01-10 01:40:46 wallet 9ms
2016-01-10 01:40:46 Reindexing block file blk00000.dat…
2016-01-10 01:40:46 init message: Loading addresses…
2016-01-10 01:40:46 ERROR: CAddrman::Read() : open failed
2016-01-10 01:40:46 Invalid or missing peers.dat; recreating
2016-01-10 01:40:46 Loaded 0 addresses from peers.dat 0ms
2016-01-10 01:40:46 mapBlockIndex.size() = 0
2016-01-10 01:40:46 nBestHeight = 0
2016-01-10 01:40:46 wallet S:
2016-01-10 01:40:46 setKeyPool.size() = 501
2016-01-10 01:40:46 mapWallet.size() = 8593
2016-01-10 01:40:46 mapAddressBook.size() = 18
2016-01-10 01:40:46 wallet B:
2016-01-10 01:40:46 setKeyPool.size() = 500
2016-01-10 01:40:46 mapWallet.size() = 64
2016-01-10 01:40:46 mapAddressBook.size() = 41
2016-01-10 01:40:46 AddLocal([2402:8200:754:1600:24b6:7501:c416:864b]:7890,1)
2016-01-10 01:40:46 IPv6 eth1: 2402:8200:754:1600:24b6:7501:c416:864b
2016-01-10 01:40:46 AddLocal([2402:8200:754:1600:a62:66ff:fe81:5b5a]:7890,1)
2016-01-10 01:40:46 IPv6 eth1: 2402:8200:754:1600:a62:66ff:fe81:5b5a
2016-01-10 01:40:46 dnsseed thread start
2016-01-10 01:40:46 Loading addresses from DNS seeds (could take a while)
2016-01-10 01:40:46 0 addresses found from DNS seeds
2016-01-10 01:40:46 dnsseed thread exit
2016-01-10 01:40:46 net thread start
2016-01-10 01:40:46 addcon thread start
2016-01-10 01:40:46 opencon thread start
2016-01-10 01:40:46 msghand thread start
2016-01-10 01:40:46 dumpaddr thread start
2016-01-10 01:40:46 trying connection 198.52.160.71:7890 lastseen=375663.9hrs
2016-01-10 01:40:46 ERROR: GetSyncCheckpoint: block index missing for current sync-checkpoint 000003cc2da5a0a289ad0a590c20a8b975219ddc1204efd169e947dd4cbad73f
2016-01-10 01:40:46 SetBestChain: new best=000003cc2da5a0a289ad0a590c20a8b975219ddc1204efd169e947dd4cbad73f height=0 log2_trust=0 moneysupply(S)=0.00 moneysupply(B)=0.00 tx=1 date=2014-08-02 23:50:35 progress=0.000000
2016-01-10 01:40:46 ProcessBlock: ACCEPTED
2016-01-10 01:40:46 ThreadUpdateFromDataFeed started
2016-01-10 01:40:46 ThreadStakeMinter started
2016-01-10 01:40:46 PeerMiner started for proof-of-stake
2016-01-10 01:40:46 Pre-allocating up to position 0x100000 in rev00000.dat
2016-01-10 01:40:46 init message: Done loading
2016-01-10 01:40:46 AddToWallet 13b76b8a435e75810799293c563abedbaabe1f678ff4042a459b64b87021d6b5
2016-01-10 01:40:47 Added 10 addresses from 127.0.0.1: 0 tried, 10 new
2016-01-10 01:40:47 trying connection 128.199.96.127:7890 lastseen=259.0hrs
2016-01-10 01:40:47 connect() failed after select(): Connection refused
2016-01-10 01:40:47 trying connection 188.226.223.94:7890 lastseen=207.6hrs
2016-01-10 01:40:48 connected 188.226.223.94:7890
2016-01-10 01:40:48 send version message: version 2000000, blocks=0, us=[2402:8200:754:1600:a62:66ff:fe81:5b5a]:7890, them=188.226.223.94:7890, peer=188.226.223.94:7890
2016-01-10 01:40:48 trying connection 128.199.96.127:7890 lastseen=259.0hrs
2016-01-10 01:40:48 GetMyExternalIP() received [121.98.165.144] 121.98.165.144:0
2016-01-10 01:40:48 GetMyExternalIP() returned 121.98.165.144

Continues with this for a long time (waited 24h the last time to no avail).

2016-01-10 01:42:20 trying connection 119.9.104.119:7890 lastseen=327.1hrs
2016-01-10 01:42:25 connection timeout
2016-01-10 01:42:26 trying connection 128.199.96.127:7890 lastseen=259.0hrs
2016-01-10 01:42:26 connect() failed after select(): Connection refused
2016-01-10 01:42:27 trying connection 192.237.200.146:7890 lastseen=185.6hrs
2016-01-10 01:42:32 connection timeout
2016-01-10 01:42:32 trying connection 192.237.200.146:7890 lastseen=185.6hrs
2016-01-10 01:42:37 connection timeout
2016-01-10 01:42:38 trying connection 128.199.96.127:7890 lastseen=259.0hrs
2016-01-10 01:42:38 connect() failed after select(): Connection refused
2016-01-10 01:42:38 trying connection 192.237.200.146:7890 lastseen=185.6hrs
2016-01-10 01:42:43 connection timeout
2016-01-10 01:42:44 trying connection 192.237.200.146:7890 lastseen=185.6hrs
2016-01-10 01:42:49 connection timeout
2016-01-10 01:42:49 trying connection 192.237.200.146:7890 lastseen=185.6hrs
2016-01-10 01:42:52 trying connection 198.52.160.71:7890 lastseen=375663.9hrs
2016-01-10 01:42:54 connection timeout
2016-01-10 01:42:55 trying connection 192.237.200.146:7890 lastseen=185.6hrs
2016-01-10 01:42:57 connection timeout
2016-01-10 01:42:58 trying connection 128.199.159.68:7890 lastseen=375663.9hrs
2016-01-10 01:42:58 connected 128.199.159.68:7890
2016-01-10 01:42:58 send version message: version 2000000, blocks=0, us=121.98.165.144:7890, them=128.199.159.68:7890, peer=128.199.159.68:7890
2016-01-10 01:43:00 connection timeout
2016-01-10 01:43:01 trying connection 192.237.200.146:7890 lastseen=185.6hrs
2016-01-10 01:43:06 connection timeout
2016-01-10 01:43:06 trying connection 119.9.104.119:7890 lastseen=327.1hrs
2016-01-10 01:43:11 connection timeout
2016-01-10 01:43:13 trying connection 192.237.200.146:7890 lastseen=185.6hrs
2016-01-10 01:43:18 connection timeout
2016-01-10 01:43:19 trying connection 192.237.200.146:7890 lastseen=185.6hrs
2016-01-10 01:43:24 connection timeout
2016-01-10 01:43:25 trying connection 192.237.200.146:7890 lastseen=185.6hrs
2016-01-10 01:43:30 connection timeout
2016-01-10 01:43:31 trying connection 192.237.200.146:7890 lastseen=185.6hrs
2016-01-10 01:43:36 connection timeout
2016-01-10 01:43:36 trying connection 192.237.200.146:7890 lastseen=185.6hrs
2016-01-10 01:43:41 connection timeout
2016-01-10 01:43:42 trying connection 119.9.104.119:7890 lastseen=327.2hrs
2016-01-10 01:43:47 connection timeout
2016-01-10 01:43:47 trying connection 192.237.200.146:7890 lastseen=185.7hrs
2016-01-10 01:43:52 connection timeout
2016-01-10 01:43:53 trying connection 192.237.200.146:7890 lastseen=185.7hrs
2016-01-10 01:43:58 connection timeout
2016-01-10 01:43:58 trying connection 192.237.200.146:7890 lastseen=185.7hrs
2016-01-10 01:43:59 socket no message in first 60 seconds, 0 1
2016-01-10 01:43:59 disconnecting node 128.199.159.68:7890
2016-01-10 01:44:03 connection timeout
2016-01-10 01:44:04 trying connection 128.199.96.127:7890 lastseen=259.1hrs
2016-01-10 01:44:04 connect() failed after select(): Connection refused
2016-01-10 01:44:05 trying connection 192.237.200.146:7890 lastseen=185.7hrs
2016-01-10 01:44:10 connection timeout
2016-01-10 01:44:10 trying connection 192.237.200.146:7890 lastseen=185.7hrs

does it just lock up again when you kill the process and restart?

Just tried, killed the process and restarted and seeing same behaviour in GUI, frozen splash screen with ‘Done loading’ and similar entries in debug.log.

I wonder if it’s an Ubuntu 15 issue. I’ve done all my testing on 14 without issue. I don’t know if i’ll be able to spin up at 15 anytime soon though.

Could be, I also don’t have another Linux instance at hand. The workaround, re downloading the blockchain on the same machine at the same time but in another folder appears to work even with killing and restarting it while synchronising. So it may just not like the conversion part.

Alright. In the mean time I’m going to try some more conversions on my linux VM’s to see if I can get it to break. Interested to hear if anyone else has these results on Linux.

@Cybnate try removing the peers.dat file.