NuBits client 2.1 RC2 is out! Be patient - official 2.1 release still in testing!

[masterOfDisaster]

Is this the release that aims at solving the issues with huge RAM consumption?

I guess it’s not necessary to say that this is still a release candidate - so handle with care!

https://bitbucket.org/JordanLeePeershares/nubit/downloads

@hyena, you might want to compile from the source code on your RaspberryPi!

[mhps]

Doesn’t start. needs libgcc_s_sjij-1.dll
win32

@sigmike

[zoro]

in win64 the same. that dll is missing.

[masterOfDisaster]

dunno - still compiling it on my RaPI2
I was close to proposing one of you might create an issue for it, but it appears that bug is already known:

Fix 2.1 issues

Sorry for crying wolf…
…but like I said: it’s a release candidate and not the release!

edit: impressive - nud starts very fast on the RaspberryPi and consumes only little RAM (as little as 38 MB):

  PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND
27552 pi        20   0  223m  37m 8028 S   1.3  3.8   0:03.88 nud

Unfortunately nud doesn’t connect to peers. I killed nud, deleted addr.dat and peers.dat hoping that would solve the problem and started nud again without avail in terms of getting connected to other nodes:

2015-10-20 12:16:59 trying connection 198.52.199.46:7890 lastseen=201.3hrs
2015-10-20 12:17:04 connection timeout
2015-10-20 12:17:04 trying connection 128.199.96.127:7890 lastseen=212.4hrs
2015-10-20 12:17:05 connect() failed after select(): Connection refused
2015-10-20 12:17:05 trying connection 128.199.96.127:7890 lastseen=212.4hrs
2015-10-20 12:17:05 connect() failed after select(): Connection refused
2015-10-20 12:17:06 trying connection 104.239.228.107:7890 lastseen=177.3hrs
2015-10-20 12:17:06 connect() failed after select(): Connection refused
2015-10-20 12:17:07 trying connection 198.52.199.75:7890 lastseen=226.0hrs
2015-10-20 12:17:12 connection timeout
2015-10-20 12:17:12 trying connection 198.52.199.46:7890 lastseen=201.3hrs
2015-10-20 12:17:17 connection timeout
2015-10-20 12:17:18 trying connection 128.199.96.127:7890 lastseen=212.4hrs
2015-10-20 12:17:18 connect() failed after select(): Connection refused
2015-10-20 12:17:18 trying connection 198.52.199.46:7890 lastseen=201.3hrs
2015-10-20 12:17:23 connection timeout
2015-10-20 12:17:24 trying connection 192.237.200.146:7890 lastseen=250.9hrs
2015-10-20 12:17:29 connection timeout
2015-10-20 12:17:32 trying connection 104.239.228.107:7890 lastseen=177.3hrs
2015-10-20 12:17:32 connect() failed after select(): Connection refused
2015-10-20 12:17:32 trying connection 198.52.199.75:7890 lastseen=226.0hrs
2015-10-20 12:17:37 connection timeout
2015-10-20 12:17:38 trying connection 119.9.104.119:7890 lastseen=267.3hrs
2015-10-20 12:17:38 connect() failed after select(): Connection refused
2015-10-20 12:17:39 trying connection 119.9.104.119:7890 lastseen=267.3hrs
2015-10-20 12:17:39 connect() failed after select(): Connection refused
2015-10-20 12:17:40 trying connection 104.239.228.107:7890 lastseen=177.3hrs
2015-10-20 12:17:40 connect() failed after select(): Connection refused
2015-10-20 12:17:41 trying connection 119.9.104.119:7890 lastseen=267.3hrs
2015-10-20 12:17:41 connect() failed after select(): Connection refused
2015-10-20 12:17:42 trying connection 192.237.200.146:7890 lastseen=250.9hrs
2015-10-20 12:17:47 connection timeout
2015-10-20 12:17:47 trying connection 188.226.223.94:7890 lastseen=177.4hrs
2015-10-20 12:17:47 connected 188.226.223.94:7890
2015-10-20 12:17:47 send version message: version 2000000, blocks=1, us=85.212.80.144:7890, them=188.226.223.94:7890, peer=188.226.223.94:7890
2015-10-20 12:17:48 trying connection 128.199.96.127:7890 lastseen=212.4hrs
2015-10-20 12:17:48 connect() failed after select(): Connection refused
2015-10-20 12:17:49 trying connection 104.239.228.107:7890 lastseen=177.3hrs
2015-10-20 12:17:49 connect() failed after select(): Connection refused
2015-10-20 12:17:49 trying connection 128.199.96.127:7890 lastseen=212.4hrs
2015-10-20 12:17:49 connect() failed after select(): Connection refused
2015-10-20 12:17:50 trying connection 119.9.104.119:7890 lastseen=267.3hrs
2015-10-20 12:17:50 connect() failed after select(): Connection refused

[JordanLee]

It is true that the latest 2.1 build is accessible in the public code repository. However, it is not yet of the quality needed for even a limited beta release. There are a number of significant problems that need to be resolved at this point. I recommend it not be used yet, except for testing.

On one machine, the latest 2.1 build showed a 65% reduction in RAM utilisation and a 94% decrease in the time required to start the client. Your results may vary, but 2.1 certainly includes major performance enhancements.

[Hyena]

Excellent news. I can try this on my Pi2 next week.

[sigmike]

Doesn’t start. needs libgcc_s_sjij-1.dll

That should be fixed in the new RC3.

Note that there are major internal changes in this release and you should backup your datadir before upgrading. The whole block index will be rewritten during the first startup and this may take some time. I’m not sure you can run the 2.0 client on the rewritten index.

[dysconnect]

Downloading the blockchain is very slow. I’m not under very ideal networking conditions, but it was much faster before on the same network.

[zoro]

i just realized that the 64b version is installed in the Program Files (x86) folder of win7

edit: zero active connections after 1 hour!

[willy]

Maybe DNS is malfunctioning?

try adding some of these

A name:nuseed.coinerella.comaddress:46.101.49.165 ttl:300
A name:nuseed.coinerella.comaddress:5.135.184.184 ttl:300
A name:nuseed.coinerella.comaddress:96.46.29.134 ttl:300
A name:nuseed.coinerella.comaddress:79.165.45.95 ttl:300
A name:nuseed.coinerella.comaddress:94.23.252.118 ttl:300
A name:nuseed.coinerella.comaddress:74.71.28.67 ttl:300
A name:nuseed.coinerella.comaddress:91.220.43.146 ttl:300
A name:nuseed.coinerella.comaddress:81.169.207.53 ttl:300
A name:nuseed.coinerella.comaddress:85.214.145.24 ttl:300
A name:nuseed.coinerella.comaddress:62.75.163.12 ttl:300

to your nu.conf with

addnode=1.2.3.4

[Sentinelrv]

Any update on this? I’ve been encountering some issues with my 2.0 client (long loading times, lots of orphans, blockchain download freezing, etc…) It may be because I’m running everything on an older and slower computer. I figured maybe the new version might fix my problems, since it’s supposed to use less resources.

[jooize]

I’m hoping the same. Firefox with a gazillion tabs and Nu are competing over resources.

[sportscliche]

It’s been 27 days and counting since I stopped minting (and voting).

[CoinGame]

There are many changes going into 2.1 so it’s taking extra time to make sure things are squared away. It’s not just the memory improvements.

[luxiang7890]

我的2.1不能在2.0上更新，全部从新下载区块，并且卡在了598316这里，一天不会更新。请给予帮助，谢谢了。

[Nagalim]

我的2.1不能在2.0上更新，全部从新下载区块，并且卡在了598316这里，一天不会更新。请给予帮助，谢谢了

Nu 2.1 is still in testing. @luxiang7890 is stuck on block 598,316.

[luxiang7890]

另一台电脑又卡在了605695，现在要重新下载2.0版本，不知道安装有啥技巧，希望得到指导，谢谢了。

[Nagalim]

怒江2.1還處於測試

你試試這個？

try adding some of these

A name:nuseed.coinerella.comaddress:46.101.49.165 ttl:300 A name:nuseed.coinerella.comaddress:5.135.184.184 ttl:300 A name:nuseed.coinerella.comaddress:96.46.29.134 ttl:300 A name:nuseed.coinerella.comaddress:79.165.45.95 ttl:300 A name:nuseed.coinerella.comaddress:94.23.252.118 ttl:300 A name:nuseed.coinerella.comaddress:74.71.28.67 ttl:300 A name:nuseed.coinerella.comaddress:91.220.43.146 ttl:300 A name:nuseed.coinerella.comaddress:81.169.207.53 ttl:300 A name:nuseed.coinerella.comaddress:85.214.145.24 ttl:300 A name:nuseed.coinerella.comaddress:62.75.163.12 ttl:300

to your nu.conf with

addnode=1.2.3.4

[Yurizhai]

Is Nu 2.1 testing still progressing?

[Sentinelrv]

CoinGame posted this yesterday in another thread…

I cant download the blockchain, getting 3kb/s and getting slower

https://bitbucket.org/JordanLeePeershares/nubit/pull-requests/255/210-rc/diff

Here is a list of the changes in 2.1. They are extensive changes. It is not a simple feature update like previous releases. The blocker right now is performance related. Once we identify the source of the performance issues and fix them it should be ready for release.