Hi Phoenix, FWIW, here's a small "potential bug" I found:

I use Monitorig to keep track of all my rigs:
https://bitcointalk.org/index.php?topic=1448855.0

Everything goes fine, except for single GPU rig, where for some weird reason Monitorig won't pick it up.

I'd be inclined to 'blame' Monitorig, but here's the catch: I switched all single GPU rigs back to Claymore, and they worked fine!

My guess: it has something to do with your log file format, because that's how Monitorig output the information. 

***If you could please change/mimic Claymore's in your future updates, that'd be great!***

Thanks and keep up the good work!  I have to switch back to Claymore for now for single GPU rigs though

Hi th00ber, I'm stumped with this one:

After PhoenixMiner updated their log to the correct time, I've set up 15 rigs just fine....

... except for ONE rig.  I've got the dreaded "miner not found/not hashing" error:

##########################################
#  Monitorig v2.0 : Windows RIG Monitor  #
##########################################
----------- Credit to th00ber ------------


           Updated : 12:48:07


[INFO] Sending mining informations to Monitorig server
[ERROR] The miner is not running or is not hashing
{
  hash: 0
  share: 0
  infos: 00:00:00.000 -> main GPUs: 1: 0.000 MH/s (0)
}
[SUCCES] Succesfully updated

The checklist I've done:
- log file is working fine, the clock times match
- I've re-downloaded/reinstalled both Monitorig and PhoenixMiner
- restarted the rig a few times
- let the rig run overnight (hoping it'd catch up eventually), no luck
- I even let Windows Firewall communicate freely both .exe for PhoenixMiner and Monitorig

Any other suggestions?  Like I've mentioned, I've successfully done 15 rigs, so I know for sure it **should** work:
- the non-working rig shares the same IP (location, internet connection) as 4 others that work

The only quirk: this non-working rig has only one GPU, the rest have multi-GPU.

FYI, PhoenixMiner just released 2.8b, and they did indeed fix the timezone issue.  Monitorig working perfectly now.

Hi Phoenix,

FYI the readme.txt that comes with 2.8b still says the -mi paramaters is up to 12, with 10 being default i.e. the old values.

Hi Phoenix, great job on the miner, I've switched all my rigs completely to yours.

One quirk: I noticed your log is giving out a time that is one hour behind.  For example, if it's 1:40pm in real time, the log will display current time as 12:40pm.

I'm based in Australia, where daylight savings is on currently.  In about a couple weeks' time, our time will move 'behind' and essentially if the log does output the same time, the real time and log time will match.

Nonetheless, the problem still exists now.  It's weird that the log is displaying 'timezone time disregarding daylight savings' instead of simply taking the computer's system time.

Could you please look into this?  I have to manage 30+ rigs and little things like this can add up to a huge headache.

Thanks!

Yes th00ber, the "miner software" seems to be outputting time that is 1 hour behind.  I'm using Phoenix Miner 2.7c by the way.

The rig system's timezone (which is my computer right here right now) is correct; the Monitorig software's header is picking up the correct time.

The problem seems to lie with Phoenix Miner's timezone then???  I went through their readme, doesn't seem to have anything to do with time/timezone.

Hi th00ber, could you please help me out with this problem:

In the "Windows PowerShell" window, I noticed the "updated time" and the "log time" is off by one hour:

##########################################
#  Monitorig v2.0 : Windows RIG Monitor  #
##########################################
----------- Credit to th00ber ------------


           Updated : 20:53:19


[INFO] Sending mining informations to Monitorig server
[ERROR] The miner is not running or is not hashing
{
  hash: 0
  share: 0
  infos: 19:53:13.973 -> main GPUs: 1: 24.644 MH/s (2) 2: 24.873 MH/s (6)
}
[SUCCES] Succesfully updated

I doubled checked the log file, sure enough the log times are behind by one hour (the "Updated" time is the correct local time).

The PowerShell window therefore always reports "miner is not hashing" even though it does pick up something from the log file...

Thanks!