blkmond and testnet

[ElSuede]

I've seen a couple of posts asking about blkmond and testnet.  Blkmond has to be running between bitcoind and pushpoold.  Here's the startegy I've used:

(bitcoind) <-> (blkmond) <-> pushpoold

Blkmond needs to point at the bitcoind testnet port of 18333 (bitcoind uses this port so you don't accidently connect to testnet.  It has to be an explicit decision)  In order to keep blkmond running, I've used this script

Code:

#!/bin/bash
while true
do
  blkmond /etc/pushpool/blkmon.testnet.cfg
done

When blkmond crashes after a little bit (10s to 2m) this starts it up without a hitch and pushpoold doesn't appear to care.  I have 600mhash pointed at it and there is no problem connecting and no dropped connections from pushpoold.

[1714032631]

1714032631

[1714032631]

1714032631

[1714032631]

1714032631

[Orodben]

I've been using this method and have found things work well with testnet and pushpoold.  It really helps the debugging process!

[phorensic]

Hmm, blkmond has never crashed for our pool.  I just start it up in the background and forget about it, and just watch my client logs say "LP new work pushed". You might have a bad version of blkmond or a wonky config file for it.

[Orodben]

I've only had it crash when the pool was running on testnet to double check our statistics