NuBox testing

erkan 2016-05-19 16:31:34 UTC #16

Installed it on a fresh OS.

First, this made me smile: (1).

I tried the “nubox -public” since it looked nice from you, but it gave me a traceback, because no nu.conf available.
"touch"ed that .conf-file and now above command gave me a better msg: NuBox isn’t running

Then I started NuBox via “nubox -start”, but there is not much feedback. It just stays like that.
I tried other commands (e.g. nubox -addr) in another terminal, but they tell me NuBox is not running, though I started it.
Is there some kind of log file (besides the debug.log) I can look at?

Could it be b/c I haven’t yet downloaded the whole NU blockchain? if so, would be great to display such an info to the user also when I type: "nubox -start"
I’ll be downloading the blockchain now via the UI: nu, since I see there progress.
Then close the UI and try the “nubox -start” again

(1)
during NuBox install, for one of my choices I got:
“Poor misguided one. Why are you installing this, then ?”

peerchemist 2016-05-19 17:19:25 UTC #17

Create .nu/nu.conf file manually. Then start.

erkan 2016-05-19 17:21:14 UTC #18

see above: yes, I did that already via touch.
Could it be because the file is empty ?

irritant 2016-05-19 19:45:58 UTC #19

yes you have to put some values for rpcuser and rpcpassword

irritant 2016-05-19 19:50:32 UTC #20

did you read the choice for which you got this? it is for the name of the box on the network, if you want to call it nubox type yes, you typed no, maybe there should be some smiley faces added, and some “ha ha ha” to make it more clear, or change the words so it reads more yoda like?

irritant 2016-05-19 20:40:44 UTC #21

erkan 2016-05-19 23:54:07 UTC #22

@irritant @peerchemist

I got it to work, thx for the input.

I am seeing nearly same as in your pic, though my protocolversion is different:

erkan 2016-05-20 00:07:35 UTC #23

about tor:

I didn’t have the command nud-tor (also tried to install via apt-get),
so I am running nud over socks-proxy for now

edit:

I see now nubox has the “nubox -tor” commandline, will try this later also
I tried “nubox -onion”, but it seems to “hang” (for 5 mins now). I’d expect a faster response

irritant 2016-05-20 04:32:44 UTC #24

have you done
apt-get install tor

erkan 2016-05-20 06:21:55 UTC #25

yes,
I also verfiied that it works:
by running check.torproject.org in the browser with the socks proxy

irritant 2016-05-20 07:40:15 UTC #26

i think “nubox -tor” should work

Cybnate 2016-05-20 07:52:59 UTC #27

Erkan has qualified for this and I have transferred 5 NBT to him. Thanks for testing Erkan.
Still 2 x 5 NBT available!

masterOfDisaster 2016-05-20 08:18:25 UTC #28

Mmmhh…

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
nu : Depends: libboost-filesystem1.55.0 but it is not installable
Depends: libboost-program-options1.55.0 but it is not installable
Depends: libboost-system1.55.0 but it is not installable
Depends: libboost-thread1.55.0 but it is not installable
Depends: libc6 (>= 2.15) but 2.13-38+rpi2+deb7u10 is to be installed
Depends: libdb4.8++ but it is not going to be installed
Depends: libminiupnpc10 (>= 1.9.20140610) but it is not installable
Depends: libstdc++6 (>= 4.9) but 4.8.2-21~rpi3rpi1 is to be installed
E: Unable to correct problems, you have held broken packages.

My Raspberry runs on wheezy. Looks like that doesn’t work out of the box.
Or is something wrong with my Raspbian (“Unable to correct problems, you have held broken packages”)?

erkan 2016-05-20 08:22:31 UTC #29

from @peerchemist 's original info above:

sudo sh -c “echo ‘deb http://peerbox.me/nubox/test-repo jessie main’ >> /etc/apt/sources.list.d/nubox-testing.list”

so I assume the packages are only for now for Debian 8.4 (jessie)
and Debian 7.10 (Wheezy) might come later ?

erkan 2016-05-20 08:23:44 UTC #30

yes, I will try that soon (still waiting for the blockchain to finish, so I can do some more testing)

backpacker 2016-05-20 09:05:57 UTC #31

i wish nubox helper script helped with initial nu.conf creation with default settings as seen in journal, after adding them all by hand it works:

peerchemist 2016-05-20 09:09:01 UTC #32

@masterOfDisaster Jessie please.

Okay, next release will have auto configure nu.conf on install if it is not present.

peerchemist 2016-05-20 19:54:02 UTC #33

New release.

sudo apt-get update && sudo apt-get upgrade

It now auto-configures .nu directory and .nu/nu.conf file during install.

To test it on existing installation, just remove $HOME/.nu/nu.conf before update.

rm $HOME/.nu/nu.conf

erkan 2016-05-20 20:17:56 UTC #34

I.
something seems to have gone wrong, when I try now: e.g. nubox -public I get a python missing library:
ImportError: No module named nu_node

II. also, it asks me to rename the box again to peerbox, though it is named already
it asks me now thus also to reboot the box
better would be: to check if the hostname exists already

III. OK: the new nu.conf was created with rpcuser, rpcpassword and server entries

peerchemist 2016-05-20 20:19:57 UTC #35

Okay, I’ve implemented this on old branch and it seems that I forgot to merge with some other tweaks. Give me a moment, I know where the problem is.