Ubuntu miners dropped from pool still happen. Any clue?
I believe that was just before the pool upgraded to 1.0.3.4. Should be good now.
This message was found with miner 1.0.3.4 to pool 1.0.3.4. Actually it happened since 1.0.3.1, and weird issue is some miners do not have this problem at all... Any other info do you want me to provide so that you can trace the issue?
I can confirm that I have the same issue running 1.0.3.4 on Debian Linux.
Lots of:
2017-09-13 23:46:28 socket recv error Connection reset by peer (104)
2017-09-13 23:48:35 socket recv error Connection reset by peer (104)
2017-09-13 23:50:42 socket recv error Connection reset by peer (104)
2017-09-13 23:52:49 socket recv error Connection reset by peer (104)
2017-09-13 23:54:57 socket recv error Connection reset by peer (104)
2017-09-13 23:57:04 socket recv error Connection reset by peer (104)
2017-09-13 23:59:11 socket recv error Connection reset by peer (104)
2017-09-14 00:01:18 socket recv error Connection reset by peer (104)
2017-09-14 00:03:25 socket recv error Connection reset by peer (104)
2017-09-14 00:05:32 socket recv error Connection reset by peer (104)
2017-09-14 00:07:40 socket recv error Connection reset by peer (104)
And still have:
2017-09-13 23:07:35 ProcessNewBlock : ACCEPTED
2017-09-13 23:07:54 socket recv error Connection reset by peer (104)
2017-09-13 23:08:06 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 7361.000000 pindexPrev 271c540a2ff535f1a76095333af4be559dc03344063a8240cbe6c57f2b319383
2017-09-13 23:08:06 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3213187)^M
** ProcessGetData:Cannot load block from disk.^M
2017-09-13 23:08:08 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 7335.000000 pindexPrev 7c8ebea50332103b657ffae35b44a568473db479abe1ddda751e856d3101e618
2017-09-13 23:08:08 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3202733)^M
** ProcessGetData:Cannot load block from disk.^M
2017-09-13 23:08:10 UpdateTip: new best=3fa7e67c94be8d98ab261a3e4bd987d9109d5581d7cbdcc8197875e400ac38aa height=7496 log2_work=49.133899 tx=11543 date=2017-09-13 23:08:06 progress=1.000000 cache=0.0MiB(38tx)
2017-09-13 23:08:10 ProcessNewBlock : ACCEPTED
2017-09-13 23:10:01 socket recv error Connection reset by peer (104)
2017-09-13 23:11:48 UpdateTip: new best=88b6821089d7bca250e5319957b5489ba79625d479a6674003a4da980b9a8424 height=7497 log2_work=49.135977 tx=11545 date=2017-09-13 23:11:40 progress=0.999999 cache=0.0MiB(40tx)
2017-09-13 23:11:48 ProcessNewBlock : ACCEPTED
It still seems to think it is submitting to the pool, but the pool is not showing or counting it (phaseshift.w2):
$ ../biblepay/bin/biblepay-cli getmininginfo
{
"blocks": 7550,
"currentblocksize": 1000,
"currentblocktx": 0,
"difficulty": 441.3595706618963,
"errors": "",
"genproclimit": 8,
"networkhashps": 45819800310.70996,
"hashps": 56562.73997076839,
"minerstarttime": "09-13-2017 22:43:42",
"pooledtx": 0,
"testnet": false,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; ",
"poolinfo2": "RMC_09-14-2017 07:06:21; RMC_09-14-2017 07:12:12; RMC_09-14-2017 07:06:53; ",
"poolinfo3": "CFW 09-14-2017 07:06:20; CFW 09-14-2017 07:12:11; CFW 09-14-2017 07:06:51; ",
"miningpulse": 52683,
"poolmining": true
}
On the plus side, the error below seems to not happen any more when stopping biblepay under Linux with 1.0.3.4:
"terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
terminate called recursively"