Thank you for taking lead on the project. It’s good to see activity again.
The Tor issues are sporadic, and searching the history there are several users reporting the same problem.
It could be occurring when Tor updates the circuit path and ppcoind is not handling this event properly. Or some other change/update in Tor that is not updated in ppcoind.
Or maybe even firewall.
Though I think we can help by adding debugging logic and instrumenting the code and collecting the data and relevant events.
However, I think we as a community need a way to package and modify Peerbox ourselves. If we can figure out how to run the debian package scripts I think this will be a good start as there are already several members who are willing and are compiling themselves.
OK, ran peerbox -tor, got an obfuscated IP address which has apparently not yet flipped back to my local IP (that’s good), but again only 8 connections.
There is a debug.log in the .ppcoin directory - is that what you are looking for? I’ve saved that as a file. What is the best way to get it to you? Is it OK to just upload that file included in a reply, or is there sensitive info in there that should concern me?
Sorry for the paranoia & inexperience,
Yes exactly, it’s the debug.log I was asking for. Not sure if it works, but I’d suggest that you send me a PN and attach the debug.log. I guess that should work. If not, we’ll find another way
I’m sure some of you might have already seen it, but I’d also like to post it here, because this thread it getting more active again in the last days and it fits here quite well.
I also plan to design some enclosures for Pi B+/2/3. But before I do so, I’d like to know whether someone’s interested in such enclosures. So if someone’s interested, please like this post. This does not mean, that you finally have to take one ;-).
Please write any comments or questions related to the enclosures in the appropriate thread, thanks.
So I checked Bitinfocharts, the only site I am aware of which maps full nodes, and I’m not listed there. For now, I’m not going to worry about using my real IP
I have bought a new SD card in order to do a fresh raspbian install and try this peerbox.
I thought it would really take 20 mins, but i’ve lost half a day while putting on the image and fiddling with it
I have booted up, connected with SSH and updated everything. While installing “peerbox” it stops saying it needs “ppcoin” installed first. So now, many opened tabs later i’m still compiling it from the source.
Ok thanks, I’ve exported the .dat from the GUI Peercoin program and put it under that folder.
Restarted peerbox but now if I do -health it tells:
EDIT: Had error on -balance, I guess it just needs more time to update all the blocks
pi@peerbox:~ $ peerbox -health
Checking if we are on the right chain…
Using peercoin.mintr.org as reference.
(“error: Can’t reach remote API server!”, ConnectionError(ProtocolError(‘Connection aborted.’, gaierror(-2, ‘Name or service not known’)),))
Traceback (most recent call last):
File “/usr/bin/peerbox”, line 443, in
health_check()
File “/usr/bin/peerbox”, line 278, in health_check
r = _check()
File “/usr/bin/peerbox”, line 246, in _check
remote = _remote()
File “/usr/bin/peerbox”, line 222, in _remote
a = requests.get(“https://peercoin.mintr.org/api/block/latest”, timeout=3, verify=False).json()
File “/usr/lib/python2.7/dist-packages/requests/api.py”, line 60, in get
return request(‘get’, url, **kwargs)
File “/usr/lib/python2.7/dist-packages/requests/api.py”, line 49, in request
return session.request(method=method, url=url, **kwargs)
File “/usr/lib/python2.7/dist-packages/requests/sessions.py”, line 457, in request
resp = self.send(prep, **send_kwargs)
File “/usr/lib/python2.7/dist-packages/requests/sessions.py”, line 569, in send
r = adapter.send(request, **kwargs)
File “/usr/lib/python2.7/dist-packages/requests/adapters.py”, line 407, in send
raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: (‘Connection aborted.’, gaierror(-2, ‘Name or service not known’))
@irritant Hi, after that I managed to get everything synchronized and started minting. It went on for a day and I checked it regularly via ssh. This morning I find this error: i’m unable to restart it and I’m stuck in this loop, what can I do? I have already rebooted, restarted, killed the process…
Waiting changes nothing, even rebooting or killing the process and restarting… It can also show up python error stacks for connection error. Does anyone else get this issue? I can only safe mint at random times
It now started working again, so the output is quite the same of “peerbox - info”, as soon as it will start showing the “wait some seconds” error I’ll try again and post the output here