Prohashing Mining Pool Forums

Hi

This might be related to

D3 connection issues
and
L3+ randomly dropping from activity....

but i'm not sure so I'm creating another post.

From the 21st of December I've had constant dropouts on my KNC Titans to Prohashing. They are in separate locations so I've ruled out any internet connectivity problems on my end.

Here are some log examples,
[2017-12-31 09:15:31] inet / pool(s) / bfg-api came up. Resuming monitoring.
[2017-12-31 09:28:46] inet / all pool(s) are down - monitoring paused. Retesting every 30 seconds.
[2017-12-31 09:29:17] inet / pool(s) / bfg-api came up. Resuming monitoring.
[2017-12-31 09:30:48] inet / all pool(s) are down - monitoring paused. Retesting every 30 seconds.
[2017-12-31 09:31:18] inet / pool(s) / bfg-api came up. Resuming monitoring.
[2017-12-31 09:40:01] inet / all pool(s) are down - monitoring paused. Retesting every 30 seconds.
[2017-12-31 09:40:32] inet / pool(s) / bfg-api came up. Resuming monitoring.
[2017-12-31 09:42:15] inet / all pool(s) are down - monitoring paused. Retesting every 30 seconds.
[2017-12-31 09:42:46] inet / pool(s) / bfg-api came up. Resuming monitoring.
[2017-12-31 09:48:46] inet / all pool(s) are down - monitoring paused. Retesting every 30 seconds.
[2017-12-31 09:49:17] inet / pool(s) / bfg-api came up. Resuming monitoring.
[2017-12-31 09:50:46] inet / all pool(s) are down - monitoring paused. Retesting every 30 seconds.
[2017-12-31 09:51:17] inet / pool(s) / bfg-api came up. Resuming monitoring.
[2017-12-31 09:59:01] inet / all pool(s) are down - monitoring paused. Retesting every 30 seconds.
[2017-12-31 09:59:31] inet / pool(s) / bfg-api came up. Resuming monitoring.
[2017-12-31 10:04:46] inet / all pool(s) are down - monitoring paused. Retesting every 30 seconds.
[2017-12-31 10:05:17] inet / pool(s) / bfg-api came up. Resuming monitoring.
[2017-12-31 10:09:16] inet / all pool(s) are down - monitoring paused. Retesting every 30 seconds.
[2017-12-31 10:09:47] inet / pool(s) / bfg-api came up. Resuming monitoring.


And here is an image showing electricity usage from one site. I don't have any other monitoring but you can see around 21 December that the miners stop hashing regularly.

https://www.dropbox.com/s/37ehlwx7od7et ... r.png?dl=0

--

The logfile is from site #1 while the electricity image is from site #2.

So what happened to Prohashing from 21 December?

what password setting are you using on the titan?

AppleMiner wrote:what password setting are you using on the titan?

a=scrypt h=5

https://prohashing.com/help.html#tuning-titan


""""Optimizing for KnC Titan hardware
Prohashing's mining server has been optimized to extract the maximum hashrate from KnC Titan miners, which typically have longer work restart times than other miners. To ensure that your miner achieves the optimal hashrate, we recommend that the following configuration settings:

Download the newest firmware (at least version 2.0.0), which has BFGMiner 5.1 installed with a number of Titan fixes for faster coins.
Use skipcbcheck when connecting to Prohashing. This eliminates errors in the BFGMiner console.
A difficulty is 8192 is suggested, although you may find a different difficulty to be more optimal.
GenTarkin created a custom KNC Titan Firmware at http://gentarkincustomtitan.pcriot.com that he has optimized to increase performance of Titans.

Thank you to user kires for these suggestions."""""""




if its of any use thats from prohashing help page, so many a static difficulty as well in your password?

I don't get the difference between "d=" and "h=". In the help you also have this "Working around KNC Titan limitations: Use "h=3" or "h=5.". Should I use "h=5 d=8192"?

sorry unsure ,maby summit a support ticket as its their help page and your finding it conflicting

try setting:

a=scrypt c=litecoin

see if you can connect in and stay static mining in the pool on just litecoins.
My titan used to have issues restarting on new coins, the delay and restart times were horrible.
The newer ASIC machines...sorta snap on. The warm up time is...50...150....350....500
The hashrate spin up times on the titans took a long long time to connect and start to rev up to speed, so if there were frequent jumps on coins I found it seemed on my system it would have problems ever getting up to full speed. When I swapped to litecoinpool with it and it stayed static on just 1 coin I had no issues like I did on the flipping coins for the titans.

So maybe see if you stick to just the 1 coin if that will do any better for you as a test.
And go from there.

Let us know if any changes.

No difference when setting c=litecoin

And also. Let me say again. This problem started 21 December. I've been mining with these KNC Titans for over 2 years now on Prohashing without this problem.

FYI. I changed to NiceHash and I am not seeing the disconnects like I do with prohashing. I consider this a Prohashing problem and nothing on my end. So until it is fixed I will use Nicehash. I'll check back here every day and change back one of the miners to prohashing from time to time to see how it looks.