it has fully synced, that was quick. It seems the filters/headers in the transactions and minting tabs are empty.
clicking on them still make the tables sort, so it is just text thats empty
I went with sudo dpkg -i peercoin-qt_0.8.3-1_armhf.deb,
but I have these errors. What do to?
Install the missing dependencies.
sudo apt install libevent-dev libprotobuf-dev
Raspbian (stretch) .deb packages can now be found on the github/releases.
2 Likes
Installed raspbian-stretch-peercoin-qt_0.8.4-1_armhf.deb and it seems to be working fine for me, have synched and now processing blocks, thanks 
1 Like
I have tried synching twice: first time the whole raspberry froze at 45%, I restarted it and it went back from 0.
I left it there around 24h, now I just came home and gave a look with vnc: peercoin was closed. I started it and it apparently has lost all the progress again, now I need to start from 0 
What can I do?
Is your SD card full?
I’m running my Pi in CLI mode. I downloaded and installed the raspbian-stretch-peercoind_0.8.4-1_armhf.deb package. Before the update I was running 0.7.1 and I was able to check the peercoin wallet status with command peercoind getinfo and I could also start minting.
Now this commands seems to be removed or renamed. What command shall I use now to check the system and start minting via CLI? Is it still possible?
yes use peercoin-cli for the commands, getinfo is deprecated, but peercoin-cli -getinfo should still show things
Thanks @irritant, it worked fine. Minting is now also running again with peercoin-cli walletpassphrase command. Is this command deprecated too?
As -getinfo is deprecated, is there a new parameter to get the same output? Normally deprecated calls will be removed by the time and for now it seems to be the only chance to get a short system overview. Or is there a chance to get the same information via several other calls? In this case I could create a small script to get the same output again.
This call was removed in version 0.8. Use the appropriate fields from:
- getblockchaininfo: blocks, difficulty, chain
- getnetworkinfo: version, protocolversion, timeoffset, connections, proxy, relayfee, warnings
- getwalletinfo: balance, keypoololdest, keypoolsize, paytxfee, unlocked_until, walletversion
peercoin-cli has the option -getinfo to collect and format these in the old format. (code -32601)
1 Like
gettxoutsetinfo for total amount of coins circulating
1 Like
I still have 10GB available. Have tried many times restarting it, but nothing changes, what can I do?
Certanly nothing I can do about it, looks like some random error on your end.
I mean: is there any debug log on the file system I can see, in order to understand why it crashes? Error codes or something that could help back trace it
have you looked at ~/.peercoin/debug.log?
1 Like
Ok perfect, thank you.
I did a tail on that file and it says:
2019-10-14 22:58:34 UpdateTip: new best=9d2546914beb6d8725e281e98eeb25601ff54bf37702a0fd08b8fd12b66cb908 height=19146 version=0x00000001 log2_trust=46.125948 moneysupply=14665608.00054845 tx=76839 date='2012-12-11 07:24:09' progress=0.046278 cache=5.3MiB(40284txo)
2019-10-14 22:58:34 ERROR: ContextualCheckBlockHeader: forked chain older than last checkpoint (height 421468)
2019-10-14 22:58:34 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 38b006d51caecaa37a65243fe0cbc541eefa00dbc45f048e6f5a5c51f497e7e1, bad-fork-prior-to-checkpoint (code 67)
2019-10-14 22:58:34 ERROR: invalid header received
2019-10-14 22:58:34 connect() to 91.122.151.198:9901 failed after select(): Connection refused (111)
2019-10-14 22:58:57 connect() to 91.58.136.252:9901 failed after select(): No route to host (113)
2019-10-14 22:59:26 connect() to 169.57.0.228:9901 failed after select(): Connection refused (111)
2019-10-14 22:59:43 connect() to 46.106.195.244:9901 failed after select(): Connection refused (111)
2019-10-14 22:59:44 connect() to 155.41.19.95:9901 failed after select(): Connection refused (111)
2019-10-14 22:59:50 connect() to [2003:dd:870f:ce6c:c92f:13af:2362:7808]:9901 failed: Network is unreachable (101)
2019-10-14 23:00:24 connect() to 151.62.16.66:9901 failed after select(): Connection refused (111)
2019-10-14 23:00:25 connect() to 188.238.169.61:9901 failed after select(): Connection refused (111)
2019-10-14 23:01:04 connect() to 193.117.160.194:9901 failed after select(): Connection refused (111)
2019-10-14 23:01:20 UPnP Port Mapping successful.
2019-10-14 23:01:43 connect() to 188.22.200.212:9901 failed after select(): Connection refused (111)
2019-10-14 23:01:43 connect() to 188.233.24.167:9901 failed after select(): Connection refused (111)
2019-10-14 23:01:55 connect() to 86.127.230.192:9901 failed after select(): Connection refused (111)
2019-10-14 23:02:08 ERROR: too many consecutive pos headers
2019-10-14 23:02:14 connect() to 79.219.54.39:9901 failed after select(): No route to host (113)
2019-10-14 23:02:53 connect() to [2003:de:7741:a900:8cf9:4b64:9588:cbfd]:9901 failed: Network is unreachable (101)
2019-10-14 23:03:26 connect() to 63.142.123.78:9901 failed after select(): Connection refused (111)
2019-10-14 23:03:27 connect() to [2601:1c0:5200:61:4883:ef38:3a00:ead3]:9901 failed: Network is unreachable (101)
2019-10-14 23:03:27 connect() to 78.26.151.72:9901 failed after select(): Connection refused (111)
2019-10-14 23:03:42 New outbound peer connected: version: 70001, blocks=421476, peer=36
2019-10-14 23:03:42 ERROR: CAlert::CheckSignature(): verify signature failed
2019-10-14 23:03:42 Misbehaving: 209.239.123.108:9901 peer=36 (0 -> 10)
2019-10-14 23:03:42 ERROR: CAlert::CheckSignature(): verify signature failed
2019-10-14 23:03:42 Misbehaving: 209.239.123.108:9901 peer=36 (10 -> 20)
2019-10-14 23:03:43 UpdateTip: new best=5b2f01ad1e302ddb901ea2f98a7cb997386e970d49e0195a5e56dec4ea0f7173 height=19147 version=0x00000001 log2_trust=46.126064 moneysupply=14665608.00374845 tx=76841 date='2012-12-11 07:29:08' progress=0.046279 cache=5.3MiB(40287txo)
2019-10-14 23:03:51 Error: Out of memory. Terminating.