Gridcoin-Research: Raspberry Pi crash
I have been running a self compiled version of 3…5.8.5 on a raspberry pi 3, os raspian-lite, occasionally when I SSH in gridcoinresearchd is no longer running. I created a systemd service to auto-restart on failure and this has cured the symptom, but I wanted to report here the last lines of the debug.log for a potential fix:
Signing Block for cpid db3cf00a057e85fa2d8fa41cebca423c and blockhash dd6c88fbbafba6dd64c45468b0a48d5669f2db9e1a8ea6a579447ec3ad639f23 with sig MEQCIBVUh17EHOs2jCYHzJsBJWAu50EBcChCn4aHGI0wo31UAiBPC8u1S4ad6mVc2JWoc1TxNb4YfSmXLS9MUC$
01/28/17 14:21:16
Signing Block for cpid db3cf00a057e85fa2d8fa41cebca423c and blockhash dd6c88fbbafba6dd64c45468b0a48d5669f2db9e1a8ea6a579447ec3ad639f23 with sig MEUCIQDbhDBUl1ZQi6k8RrtxZ5lInroZ/CUS6PepB9qz93eIxAIgKF+8IRE+EIXA33KFgNuHVcsS4hJo+kI+do$
01/28/17 14:21:18 * Received block c2a74b3343836adf726326031ae6629d34d9e41762a6d381ab10ee2ad74126a1; Operation ProcessBlock_checkblock_researcher_doublecheck, ComputedAccrual 9.984375, StakeHeight 802797.000000, RABlockSpan 1776.$
01/28/17 14:21:18 -{CheckStakeKernelHashV3::INFO::} PaymentAge 170400.000000, BitsAge 3295.842534, Magnitude 24.000000, Coin_Age 973072.000000, RSAWeight 24.000000
01/28/17 14:21:18 {CheckStakeKernelHashV3::INFO:::: RSA_WEIGHT 24.000000, TimeBlockFrom 1484640192.000000, PrevnTime 1484640192.000000, PrevOutHash dbaf5bcee56604d363f3be74d44ed6d2164a94df34feff92159d41edbcecc7ab, PrevOut 1.000000$
01/28/17 14:21:21 ping timeout: 1200.007183s
01/28/17 14:22:23 Operation ConnectBlock_checkblock_researcher, ComputedAccrual 9.984375, StakeHeight 802797.000000, RABlockSpan 1776.000000, HistoryHeight801021.000000, AccrualAge 1.972222, AvgMag 22.500000, MagUnit 0.225000, PP$
01/28/17 14:22:23 Stake Reward of 10.072501 , DPOR PAID 0.000000 Operation connectblock_researcher, ComputedAccrual 9.984375, StakeHeight 802798.000000, RABlockSpan 1777.000000, HistoryHeight801021.000000, AccrualAge 1.972222,$
01/28/17 14:22:23
[DoTallyRA_START] {SBC} SetBestChain: new best=c2a74b3343836adf7263 height=802798 trust=3275838333972824660711873320762369734724920483558585417587747496401915111063 blocktrust=98303832610 date=01/28/17 14:21:04
01/28/17 14:22:23 {ACC}{PB}: ACC;
01/28/17 14:22:23 {SVC}
Signing Block for cpid db3cf00a057e85fa2d8fa41cebca423c and blockhash dd6c88fbbafba6dd64c45468b0a48d5669f2db9e1a8ea6a579447ec3ad639f23 with sig MEUCIQD3owPtgtzqqgJvaoniHEyWoQdwuZcZKgG9wSboYia3PQIgKuGnu0J/jTyLFngwT5T2Aa2Tqf0rBRxgbQ$
AppInit
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 40 (39 by maintainers)
Same as #166?
A trigger for shutting down could be downloading the official snapshot and starting from there. At least it used to be for me at a snapshot of about 660k blocks
Sure no worries @Peppernrino its late here now I will update this tomorrow