P.S. I just looked at ozcion (the donation pool). Your miner was not mining for me so I don't know what it was doing.
Now it's getting weird ^^ I haven't remembered the exact pool configurations (should have made an screenshot... well... if ifs and buts...). That's what I memorize: There were 3 unknown pools/usernames (something with minepeon or donate), two were alive, one was marked red als dead. One of them was btcguild. I'm not sure if it was the dead one.
Edit: My hashrate on bitminter was gone for this miner at 11:30-ish PM yesterday (CEST+2). I've noticed that (and set up back to my pools) when I posted it here. So it was running about ~12 hours on them. The hashrate on the minepeon graphs was all the same - but it made a litte break in at 0:00 AM.
Edit2: Just a guess: On an unconfigurized minepeon, aren't there 3 donation pools set up, per default? Maybe it was them?
Not weird, just a glitch, they happen (it is in early beta after all).
I spent a few hours last night working on a supervisory process that I have in early alpha. The idea behind the supervisory process is that it loads the miner config file and then verifies with the miner API that it is doing what it is meant to be doing.
If it is not it can do a set list of responses like killing the miner process (systemd with then restart it), rebooting the Pi, emailing you or even sending you a SMS or Android/iOS PUSH (Those last two require me to spend money, so keep donating
).
That will lead onto another feature that people often ask for witch is 'mining schedules' where the miner will automatically switch between pools on a set of rules defined by the user (time for example).
Like I said though, all in development. A cut down version of the supervisor will be in the next release that should have caught your problem though.
Neil
P.S. Once again, sorry about that.
