Quote from: jarkle on October 08, 2017, 09:47:16 PM

Quote from: dstm on October 08, 2017, 09:45:16 PM

Quote from: jarkle on October 08, 2017, 07:43:55 PM

Quote from: dstm on October 08, 2017, 07:38:18 PM

Quote from: jarkle on October 08, 2017, 07:24:51 PM

Got an output that said 'msg buffer full'. What does this mean? Is it an issue? I also notice the pool hashrate for this rig dropped drastically like some cards were not submitting shares.?

This might happen if one of your GPUs crashes/gets unresponsive and stops consuming messages - so check your overclocking.

So this error would be a good one to trigger a rig reboot?

This is a very bad idea, you can easily end up in a boot loop, which might damage your hardware.

Gotcha. What I found interesting is that the api was still reporting normal hashrate for all the cards.. Is there a debug option I can set that will create a debug file?

Right, this happens if one of the GPUs crashes and stops updating its stats. I'll improve this in one of the next versions. There is no debug option, however I'm pretty verbose if something violates assertions.