Yeah, this is probably something that could be done. The red display is pretty easy to do; the shell script will require DB schema changes and a bit more work, but will still be possible. I assume this would be used to, for example, email you if one of the miners stops requesting work?
Correct. One could specify a shell script in the database, and perhaps two other user-defined arguments which would be called like:
`$script $minerip $timedelta $userdefinedarg1 $userdefinedarg2`
And would hopefully cause the script to send me an email letting me know that miner 1.2.3.4 has been down for 300 seconds.
Thanks again for all of your hard work!
No problem! I'm glad you find the software useful.
[/quote]
Useful indeed, if only I could make it function as flawlessly in my environment as it does in yours. So as I mentioned, Phoenix 1.2 prints periodic "disconnected" messages. Phoenix 1.45 seems to sporadically connect to the long-polling URL. Phoenix 1.2 will connect, but it disconnects after a period of time. I think I see why. I hit my local mining proxy and fetched the long polling URL. The first time it worked, and actually sent me info on a new block. But the next time I tried it, I encountered a problem that almost surely explains what I'm seeing in Phoenix:
GET /index.php?lpurl=http%3A%2F%2Fdeepbit.net%3A8332%2FlistenChannel&pool=1 HTTP/1.1
Connection: close
Host: bitproxy.xxxxx.com
Authorization: Basic xxx
User-Agent: phoenix/v1.2
(((2 minutes elapse, and then...)))
HTTP/1.1 200 OK
Date: Tue, 10 May 2011 06:00:12 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.1.6
X-Source-Code:
https://github.com/cdhowie/Bitcoin-mining-proxySet-Cookie: PHPSESSID=4j2r53dsse5afoa5u9k3oratn0; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Length: 78
Connection: close
Content-Type: application/json-rpc
{"error":"Invalid response from long-poll request.","result":null,"id":"json"}Connection closed by foreign host.
Based on the 3 or 4 times I've done this, it seems to happen when there is in fact a new block. This should be easily duplicable for you. If not, I can PM you the info on my proxy and let you see for yourself. Hope that helps.