How to: Peerbox Support Thread (Updated to v0.6.1)

Do you mean the wallet? Everything else works. But peerbox -info still don’t work.

I were online when i tried it. I tried it right now again and now i get this Error:

Traceback (most recent call last): File "/usr/bin/peerbox", line 309, in <module> print(json.dumps(info(), indent=4)) File "/usr/bin/peerbox", line 140, in info info = node.getinfo() File "/usr/lib/python2.7/dist-packages/peerbox/ppc_node.py", line 95, in getinfo return self.node.getinfo() File "/usr/lib/python2.7/dist-packages/peerbox/jsonrpc.py", line 107, in __call__ return self.__request_method(self.__method_name, args, kwargs) File "/usr/lib/python2.7/dist-packages/peerbox/jsonrpc.py", line 91, in __request return self.send_request(method_name, is_notification, args or kwargs) File "/usr/lib/python2.7/dist-packages/peerbox/jsonrpc.py", line 41, in send_request raise TransportError('Error calling method %r' % method_name, requests_exception) peerbox.jsonrpc.TransportError: ("Error calling method 'getinfo'", ConnectionError(ProtocolError('Connection aborted.', error(111, 'Connection refused')),))

I’ve located the error and will fix in the next release (0.6).

Peerbox 0.6.3 is now released.
Please update your Peerbox.

Changelog:

  • All communication with the ppcoind is now done via peercoin_rpc library.
  • Few other smaller fixes.

i installed 0.6 from scratch and still get the following:

pi@peerbox:~ $ peerbox -start
Traceback (most recent call last):
File “/usr/bin/peerbox”, line 291, in
if is_running() == False and not (args.start or args.tor):
File “/usr/bin/peerbox”, line 103, in is_running
pid = sh.pidof(“ppcoind”).stdout.strip()
File “/usr/lib/python2.7/dist-packages/sh.py”, line 769, in call
return RunningCommand(cmd, call_args, stdin, stdout, stderr)
File “/usr/lib/python2.7/dist-packages/sh.py”, line 330, in init
self.wait()
File “/usr/lib/python2.7/dist-packages/sh.py”, line 334, in wait
self._handle_exit_code(self.process.wait())
File “/usr/lib/python2.7/dist-packages/sh.py”, line 348, in _handle_exit_code
self.process.stderr
sh.ErrorReturnCode_1:

RAN: ‘/bin/pidof ppcoind’

STDOUT:

STDERR:

[quote=“thehuntergames, post:64, topic:3827”]i installed 0.6 from scratch and still get the following:

pi@peerbox:~ $ peerbox -start
Traceback (most recent call last):
File “/usr/bin/peerbox”, line 291, in
if is_running() == False and not (args.start or args.tor):
File “/usr/bin/peerbox”, line 103, in is_running
pid = sh.pidof(“ppcoind”).stdout.strip()
File “/usr/lib/python2.7/dist-packages/sh.py”, line 769, in call
return RunningCommand(cmd, call_args, stdin, stdout, stderr)
File “/usr/lib/python2.7/dist-packages/sh.py”, line 330, in init
self.wait()
File “/usr/lib/python2.7/dist-packages/sh.py”, line 334, in wait
self._handle_exit_code(self.process.wait())
File “/usr/lib/python2.7/dist-packages/sh.py”, line 348, in _handle_exit_code
self.process.stderr
sh.ErrorReturnCode_1:

RAN: ‘/bin/pidof ppcoind’

STDOUT:

STDERR:[/quote]

Thanks for the report, I will take look at it in the next few days.

Hello,

I am trying to run peerbox behind tor. Started with “peerbox -tor” though “peerbox -onion” after 10 minutes does not report that peerbox is started.

If instead start “peerbox -start” then “peerbox -tor”, “peerbox -onion” returns an address.

What is the way to start peerbox with tor?

Thanks!

It seems “peerbox -tor” does start ppcoind. Though there must be some subtle error in the is_running and info in the peerbox python file.

If I manually run the ppcoin rpc commands I do see that the node is running.

Noted few days ago, I’ve introduced some unexpected behavior with refactor of is_running function. I will get on it as soon as possible to finish new release.

0.6.4 release

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

Changelog:

upon install peerbox will now correctly recognize that machine has already been renamed to "peerbox.local"
most of ugly error messages are now hidden from the user
issues with start/info/tor commands are now fixed

Thanks, “peerbox -tor” starts ppcoind and “peerbox -info” returns the status information.

Though some reason there are no connections and no blocks are being downloaded. Any ideas?

I would guess low connectivity through tor. Try restarting to force new connection with Tor network.

It just took a really long time, eventually it got the 8 connections.

Also, submitted a pull request to be able to run in a virtual machine if it will be useful.

Is it possible to have “http://peerbox.me/” be “https” to make the entire process more secure? Services like letsencrypt are becoming more available.

Yes, I will handle that eventually.

I get the following when using ‘peerbox’ commands (e.g. peerbox -info):

Traceback (most recent call last):
  File "/usr/bin/peerbox", line 404, in <module>
    node = Client(testnet=False)
  File "/usr/lib/python2.7/dist-packages/peercoin_rpc/peercoin_rpc.py", line 29, in __init__
    self.username, self.password = self.userpass() ## try to read from ~/.ppcoin
  File "/usr/lib/python2.7/dist-packages/peercoin_rpc/peercoin_rpc.py", line 56, in userpass
    return username, password
UnboundLocalError: local variable 'username' referenced before assignment

systemctl still works and ‘ppcoind getinfo’ responds properly :slight_smile:

Update: fixed with the kludge of adding “rpcuser=XXXXXXXX” to ppcoin.conf. Still not sure why it doesn’t work OOTB, but I can definitely live with it!

1 Like

Yeah I was going to propose just that. It seems that it can’t live with too long of a password.
I’ve made it so that new default pass length is 24 chars now.

Having no luck installing peerbox this time. Is there a problem with the ‘jesse/main armhf Packages’ ?

sudo apt-get update && sudo apt-get install peerbox
Hit http://mirrordirector.raspbian.org jessie InRelease
Hit http://mirrordirector.raspbian.org jessie/main armhf Packages
Hit http://mirrordirector.raspbian.org jessie/contrib armhf Packages
Hit http://mirrordirector.raspbian.org jessie/non-free armhf Packages
Hit http://mirrordirector.raspbian.org jessie/rpi armhf Packages
Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en
Ign http://mirrordirector.raspbian.org jessie/main Translation-en
Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en
Ign http://mirrordirector.raspbian.org jessie/rpi Translation-en
Hit http://archive.raspberrypi.org jessie InRelease
Ign http://peerbox.me jesse InRelease
Get:1 http://peerbox.me jessie InRelease [2799 B]
Ign http://peerbox.me jesse Release.gpg
Ign http://peerbox.me jesse Release
Hit http://peerbox.me jessie/main armhf Packages
Hit http://archive.raspberrypi.org jessie/main armhf Packages
Hit http://archive.raspberrypi.org jessie/ui armhf Packages
Ign http://peerbox.me jessie/main Translation-en
Err http://peerbox.me jesse/main armhf Packages
404 Not Found
Ign http://archive.raspberrypi.org jessie/main Translation-en
Ign http://peerbox.me jesse/main Translation-en
Ign http://archive.raspberrypi.org jessie/ui Translation-en
Fetched 2799 B in 8s (339 B/s)
W: Failed to fetch http://peerbox.me/repo/dists/jesse/main/binary-armhf/Packages 404 Not Found

E: Some index files failed to download. They have been ignored, or old ones used instead.

some connection issue maybe? I imagine you already tried again, still that would be my suggestion…
here it works

Thank-you for your response, have it working now.
Was working with a new Raspian install that probably needed to be updated & upgraded, before attempting the Peerbox install. Though I’m still stuck at 8 connections - moar router work to do.