Prohashing Mining Pool Forums

Hello all,
Having issues with my Antminer D3 and PH pool.
Been here for about a week, and every day the pool appears to go DEAD according to my miner for between 10 min some times, and 60 min other times.
It goes dead about 5 to 10 times a day.
Worker history agrees with my miner DEAD time, PH is pool 0 in my miner config, and the miner then falls over to pool 1.
When this happens, and PH becomes ALIVE again, my 2hr share estimate starts at 0 again, seriously affecting my payouts...
My setup is:-
URL = prohashing.com:3333
Worker = "My Username"
Password = a=x11 w=1220 p=0.08 n=Cameron3

Any help will be appreciated.
Regards,
Tim

i dont see anything wrong with your password argument. what firmware are you using????

Other than a small restart today i dont recall any issues since before Christmas.

Thanks greaseman316,

Here is my miners info below, and two snippets from the kernel log, hope we can resolve this problem.

Miner Type Antminer D3
Hostname antMinerTim
Model GNU/Linux
Hardware Version 1.0.0.7
Kernel Version Linux 3.8.13 #22 SMP Tue Dec 2 15:26:11 CST 2014
File System Version Thu Nov 2 22:18:40 CST 2017
CGminer Version 4.9.0
Uptime 2
Load Average 1.25, 0.92, 0.92

---==== kernel log ====---
Dec 28 17:52:45 (none) local0.warn cgminer[361]: Pool 0 stratum+tcp://prohashing.com:3333 not responding!
Dec 28 17:52:45 (none) local0.warn cgminer[361]: Switching to pool 1 Stratum+tcp://dash.suprnova.cc:9991
Dec 28 17:59:22 (none) local0.warn cgminer[361]: Pool 0 stratum+tcp://prohashing.com:3333 alive, testing stability
Dec 28 18:04:06 (none) local0.warn cgminer[361]: Pool 0 stratum+tcp://prohashing.com:3333 stable for 5 mins
Dec 28 18:04:06 (none) local0.warn cgminer[361]: Switching to pool 0 stratum+tcp://prohashing.com:3333

Dec 28 19:48:58 (none) local0.warn cgminer[361]: Lost 2 shares due to stratum disconnect on pool 0
Dec 28 19:48:59 (none) local0.warn cgminer[361]: Pool 0 stratum+tcp://prohashing.com:3333 not responding!
Dec 28 19:48:59 (none) local0.warn cgminer[361]: Switching to pool 1 Stratum+tcp://dash.suprnova.cc:9991
Dec 28 19:50:34 (none) local0.warn cgminer[361]: Pool 0 stratum+tcp://prohashing.com:3333 alive, testing stability
Dec 28 19:55:06 (none) local0.warn cgminer[361]: Pool 0 stratum+tcp://prohashing.com:3333 stable for 5 mins
Dec 28 19:55:06 (none) local0.warn cgminer[361]: Switching to pool 0 stratum+tcp://prohashing.com:3333

Regards,
Tim

you are running Blissz firmware. it switches pools every couple hours for you to mine his DEV fee. change your firmware back to the latest bitmain version unless you think the cost savings for power is worth the dev fee.


if you are not running Blissz firmware, is supernova your second pool.

I am asking because that log looks alot like blissz firmware switching pools

Dec 28 17:52:45 (none) local0.warn cgminer[361]: Pool 0 stratum+tcp://prohashing.com:3333 not responding!
Dec 28 17:52:45 (none) local0.warn cgminer[361]: Switching to pool 1 Stratum+tcp://dash.suprnova.cc:9991
Dec 28 17:59:22 (none) local0.warn cgminer[361]: Pool 0 stratum+tcp://prohashing.com:3333 alive, testing stability
Dec 28 18:04:06 (none) local0.warn cgminer[361]: Pool 0 stratum+tcp://prohashing.com:3333 stable for 5 mins
Dec 28 18:04:06 (none) local0.warn cgminer[361]: Switching to pool 0 stratum+tcp://prohashing.com:3333

this is from server restart. it is my logs also

but no other log entries seen on any on my miners except one im testing Blissz firmware, log shows i also connected to supernova about same time as you and since i don use supernova at all i know that it is his dev fee kicking in

Hello again greaseman316,

Only got one D3 miner, received mid November.
Never flashed the unit or upgraded to new firmware.

If the D3 mines to other pools, I don't have issues with DEAD pools like i'm having now.
I really want to sort this out, I like PH's ability to pay out in any coin.

Regards,
Tim

Hello greaseman316,

dash.suprnova.cc is pool 1 on my machine.

regards,
Tim

that is weird to say the least. maybe try adding d=256 or d=128 to your password line.

i have 1 stray miner that just wont run right unless i use static difficulty. if that dont help with the disconnects try reflashing your firmware.

other than the restart today i been going non stop for almost 3 days now without a hiccup

Hello greaseman316,

I think your idea of a static difficulty might just help.
Why I say that, is my Hashrate History is all over the place on this pool .(5G -> 60G)
I'll be setting it to 128 for today and see what happens, thanks.

Regards,
Tim

Hello all,

A slight update on my Antminer D3 and PH pool.
By setting the difficulty to static (d=128) the miner seems a lot more stable, and has been mining for just over 5 hours now without seeing the pool as DEAD.

It has now climbed from a starting hashrate of 8.2 GH/s to an average hashrate of 20.8 GH/s after 5 hours 14 min, and to a 2hr share estimate of 264.
Will continue to monitor.
Regards,
Tim