Latest posts of: 4019

Hi there. I've written DataMinerWatch as a solution for miner hangs during nighttime hours, when my PC have to operate autonomously, and recently decided to comment&clear the code and push it to Github. In this form script address three things:

Is Internet connection working at all? Script periodically pings few DNS servers and checks connection carrier, then writes info to logfile if less than half of packets is received.
Is miner running at all? If not, launch again.
Did miner hang somewhere at connection after all? I had hangs lasting an hour or two with lots of force reconnect if possible! or system:111 communicates, without any [MASTER] line printed to output. If script detects such behavior, primeminer is killed, launched (if in jump mode pool is changed) and info is written to logs.

Note that automatic pool switching on errors can save you from downtime caused by pool crash, as the second of two currently running Datacoin pools is in early beta stage and still a bit unstable.

Quick how-to
(If this post gets old and howto become broken, check github readme in case when I have updated something there but not here)

I'm assuming you have primeminer binary and basic linux skills. If not, google it, check this forum, peercointalk.org forum, etc.
Get dataminerwatch script, either copy-paste from github site or use git clone https://github.com/arkhebuz/datawatch command. Use chmod +x datawatch.sh to make the script executable if necessary.
Edit datawatch.sh file, all this is commented in code. What you need to do there:
1. Change catalog where logs will be stored;
2. Set your network interface virtual filesystem catalog (like /sys/class/net/eth0);
3. Set interval in seconds between checks. Should be large enough to let the miner recover under its own steam in most cases. Also, too small will make script steal cpu cycles from miner;
4. Set primeminer binary location;
5. Edit primeminer launch parameters. This script is written with http://dtc.xpool.xram.co and http://dtc.gpool.net pools in mind, see my comments in code and check their sites;
Launch script, pass to it which pool and mode it should use, like ./datawatch.sh gpool stay.
There are two modes: "stay" and "jump". When stay (default) is used, script doesn't change the pool on connection hang. When jump is used, script will jump from one pool to another on hangs, constantly mining to the same Datacoin address. Currently xpool has 0.5 DTC payout barrier, while gpool 0.3 DTC.
You can launch it in terminal and just leave it on. I prefer keeping it inside GNU Screen, so I can easily attach it and kill when I need more computing power on my box, then relaunch when I'm done. In case of VPS you might want to keep script alive using supervisor, for example.

Quirks

Every primeminer run has it's own logfile with it's output, named with launch time (YYYY-MM-DD_hh.mm.ss). Additionally there's a netlog file, where only communicates from script about connection are stored.
In jump mode script should be able to change pool if miner can't connect at all to it at the very beginning, I hope.
Dependencies? Primeminer, pkill, pgrep, bash, grep, sed, ping... Nothing special.
Aha, works for me. May not work for you. Tested on Debian Wheezy.
Donate? Just a tip maybe?
DTC: DMy7cMjzWycNUB4FWz2YJEmh8EET2XDvqz
XPM: AV3w57CVmRdEA22qNiY5JFDx1J5wVUciBY