Page 1 of 2

L3s still not finding prohash

Posted: Fri Sep 01, 2017 1:22 am
by hashingpro
Jan 1 00:03:12 (none) local0.notice cgminer[8589]: Probing for an alive pool
Jan 1 00:03:12 (none) local0.info cgminer[8589]: Testing pool stratum+tcp://prohashing.com:3333
Jan 1 00:03:12 (none) local0.info cgminer[8589]: Testing pool stratum+tcp://scrypt.usa.nicehash.com:3333
Jan 1 00:03:12 (none) local0.info cgminer[8589]: Testing pool stratum+tcp://us.litecoinpool.org:3333
Jan 1 00:03:12 (none) local0.err cgminer[8589]: cgminer time error total_secs = 946684992.138878 last_total_secs = 1.000000
Jan 1 00:03:12 (none) local0.notice cgminer[8589]: Pool 2 difficulty changed to 4096
Jan 1 00:03:12 (none) local0.info cgminer[8589]: Stratum authorisation success for pool 2
Jan 1 00:03:12 (none) local0.notice cgminer[8589]: Switching to pool 2 stratum+tcp://us.litecoinpool.org:3333 - first alive pool
Jan 1 00:03:12 (none) local0.info cgminer[8589]: Pool 2 stratum+tcp://us.litecoinpool.org:3333 alive
Jan 1 00:03:12 (none) local0.info cgminer[8589]: Stratum authorisation success for pool 1
Jan 1 00:03:12 (none) local0.warn cgminer[8589]: Pool 1 stratum+tcp://scrypt.usa.nicehash.com:3333 alive, testing stability
Jan 1 00:03:12 (none) local0.warn cgminer[8589]: Switching to pool 1 stratum+tcp://scrypt.usa.nicehash.com:3333
Jan 1 00:03:12 (none) local0.notice cgminer[8589]: Pool 1 difficulty changed to 16384
Jan 1 00:03:12 (none) local0.notice cgminer[8589]: Network diff set to 211K
Jan 1 00:03:12 (none) local0.info cgminer[8589]: New block: a839a011906c2d297928fbd81ecd4ddc7f593100b2b5c6e57e86a2d4fd4272f9... diff 211K
Jan 1 00:03:13 (none) local0.info cgminer[8589]: New best share: 272
Jan 1 00:03:13 (none) local0.info cgminer[8589]: Failed to connect to stratum on prohashing.com:3333
Jan 1 00:03:13 (none) local0.info cgminer[8589]: New best share: 384
Jan 1 00:03:13 (none) local0.info cgminer[8589]: New best share: 2.25K
Jan 1 00:03:13 (none) local0.info cgminer[8589]: New best share: 2.55K
Jan 1 00:03:13 (none) local0.info cgminer[8589]: New best share: 4.35K
Jan 1 00:03:13 (none) local0.info cgminer[8589]: New best share: 46K
Jan 1 00:03:14 (none) local0.info cgminer[8589]: Pool 1 stratum share result lag time 1 seconds
Jan 1 00:03:14 (none) local0.info cgminer[8589]: New best share: 332K
Jan 1 00:03:18 (none) local0.warn cgminer[8589]: API running in IP access mode on port 4028 (17)
Jan 1 00:03:18 (none) local0.info cgminer[8589]: Testing pool stratum+tcp://prohashing.com:3333
Jan 1 00:03:18 (none) local0.info cgminer[8589]: Failed to connect to stratum on prohashing.com:3333
Jan 1 00:03:19 (none) local0.info cgminer[8589]: Pool 1 stratum share result lag time 1 seconds
Jan 1 00:03:23 (none) local0.info cgminer[8589]: Testing pool stratum+tcp://prohashing.com:3333
Jan 1 00:03:24 (none) local0.info cgminer[8589]: Pool 1 stratum share result lag time 1 seconds
Jan 1 00:03:24 (none) local0.info cgminer[8589]: Failed to connect to stratum on prohashing.com:3333


Open to testing ideas. anything I can ping or tracert to get some answers as to why I cant connect now, was fine for a day or so, nothing changed on my end, now cant connect in again, and the miners status pages all list the prohash site as DEAD. Finds and mines on the two backups just fine.


Tracert over to prohashing.com seems normal, not sure how to test to the stratum site address.
C:\Windows\system32>tracert http://www.prohashing.com

Tracing route to http://www.prohashing.com [167.88.14.215]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 9 ms 11 ms 9 ms 96.120.62.45
3 10 ms 9 ms 10 ms te-0-5-0-1-sur02.pittsburgh.pa.pitt.comcast.net [68.85.157.197]
4 10 ms 11 ms 10 ms te-0-0-0-0-ar01.mckeesport.pa.pitt.comcast.net [68.86.147.109]
5 17 ms 17 ms 17 ms be-7016-cr02.ashburn.va.ibone.comcast.net [68.86.91.25]
6 18 ms 16 ms 16 ms hu-0-11-0-3-pe04.ashburn.va.ibone.comcast.net [68.86.88.78]
7 15 ms 16 ms 20 ms 23.30.206.206
8 43 ms 47 ms 45 ms 89.149.141.253
9 45 ms 49 ms 44 ms 427.xe2-0-0.br1.ch2.newcontinuum.net [173.205.36.74]
10 46 ms 43 ms 51 ms xe2-0-3.br0.newcontinuum.net [173.243.122.246]
11 45 ms 45 ms 49 ms 29-96-79-64.as20278.net [64.79.96.29]
12 44 ms 48 ms 46 ms 215-14-88-167.reverse-dns [167.88.14.215]

Trace complete.


any suggestions on why it cant find the site to mine here when it could a day or so ago just fine?
Sometimes it will even show up ALIVE, send all the miners there for the next work share, then go DEAD and disconnect again, showing 12 miners doing 16megahash instead of 5.5 GH.

Re: L3s still not finding prohash

Posted: Fri Sep 01, 2017 5:04 am
by micca410evo
Try internet over your mobile phone for a second.. or try changing dns flushing locally or change dns servers in your router. I still think there are issues on the location switching

Re: L3s still not finding prohash

Posted: Fri Sep 01, 2017 8:12 am
by Steve Sokolowski
Chris has been working on this issue for days and is not able to reproduce it and has not made any progress as to the cause.

Any additional information is helpful. Unfortunately, we don't have any idea where to go from here and Chris may have to stop actively working on it. But we'll still keep monitoring the forums in the hope that maybe the reports, taken as a whole, could yield some clues.

Re: L3s still not finding prohash

Posted: Fri Sep 01, 2017 10:09 am
by mycide
Please, while connected things seem to work like it should , but we randomly keeps getting kicked off server. several hours of each day im forced on backup pool.. two nights in a row i been kicked off at the same time. Come on my two brothers, you make a lot of dollars each and every day, time to spend some of that on stability.

Re: L3s still not finding prohash

Posted: Fri Sep 01, 2017 2:57 pm
by hashingpro
Well, if Chris has been working on this for days and cant reproduce it, get ahold of me I can make my farm available to you to remote in and do testing on to figure out why the site is showing as DEAD from my miners. Its not port 3333, other pools are on it, but I did try the proxy server address same results. Its NOT dns related or the miners would NEVER find the address, sometimes 8-12 units will connect to prohash hash a few seconds then get kicked back off. And its not any settings in the password, I defaulted it to n=test on a few machines to eliminate that issue. I also used another users account name to see if the miner would mine for them on their account in case it was a database or account issue, using 2 other peoples account names to mine with, still showed the pool as DEAD from the miners.

I was fine and connected and working as well as everyone else until the service change to the new data lines, since then, it will not let me connect in for more than just a few seconds then boot me off.

And the fact others are having this issue means it must actually still be an issue. If we had a specific site to do a tracert or a ping test or some type of info gathering for all those having the issue and feed you the data would that help in anyway you finding out what the problem or issue is?

Re: L3s still not finding prohash

Posted: Fri Sep 01, 2017 3:29 pm
by hashingpro
So the miners are connected now, but still having errors thrown out on the logs not being able to find prohash.


Sep 1 18:17:36 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:18:00 (none) local0.info cgminer[25546]: Testing pool stratum+tcp://prohashing.com:3333
Sep 1 18:18:06 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:18:19 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:18:36 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:18:56 (none) local0.notice cgminer[25546]: Network diff set to 247K
Sep 1 18:18:56 (none) local0.info cgminer[25546]: New block: 0000000000000cdfbbaf614a0b48d81f84bd2aa413fda81de71efe2e4bcf53e6... diff 247K
Sep 1 18:18:56 (none) local0.notice cgminer[25546]: Stratum from pool 1 detected new block
Sep 1 18:19:00 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:19:00 (none) local0.info cgminer[25546]: Testing pool stratum+tcp://prohashing.com:3333
Sep 1 18:19:07 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:19:19 (none) local0.info cgminer[25546]: New block: fe767d35195d81647aec8d162ccc6f2f6a588c102c706bedf7ad8ae4f69d618e... diff 247K
Sep 1 18:19:19 (none) local0.notice cgminer[25546]: Stratum from pool 1 detected new block
Sep 1 18:19:37 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:20:00 (none) local0.info cgminer[25546]: Testing pool stratum+tcp://prohashing.com:3333
Sep 1 18:20:08 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:20:20 (none) local0.notice cgminer[25546]: Network diff set to 266K
Sep 1 18:20:20 (none) local0.info cgminer[25546]: New block: 0000000000003c67d0e74a5342c6533f49222e37a5269f1ea3e52f84cac4042d... diff 266K
Sep 1 18:20:20 (none) local0.notice cgminer[25546]: Stratum from pool 1 detected new block
Sep 1 18:20:38 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:20:39 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:20:42 (none) local0.info cgminer[25546]: New block: ef059d254b46934476de555c713378e0e0caf04b68e6a56d057e1a62cb122c7c... diff 266K
Sep 1 18:20:42 (none) local0.notice cgminer[25546]: Stratum from pool 1 detected new block
Sep 1 18:20:55 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:21:00 (none) local0.info cgminer[25546]: Testing pool stratum+tcp://prohashing.com:3333
Sep 1 18:21:08 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:21:21 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:21:38 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:21:45 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:22:00 (none) local0.info cgminer[25546]: Testing pool stratum+tcp://prohashing.com:3333
Sep 1 18:22:09 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:22:39 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:22:46 (none) local0.notice cgminer[25546]: Pool 1 difficulty changed to 65536
Sep 1 18:23:00 (none) local0.info cgminer[25546]: Testing pool stratum+tcp://prohashing.com:3333
Sep 1 18:23:09 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:23:17 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:23:29 (none) local0.notice cgminer[25546]: Network diff set to 215K
Sep 1 18:23:29 (none) local0.info cgminer[25546]: New block: 000000000000043f776549f49d5b430d004683e4842290fa8ca3644d9ad7aef1... diff 215K
Sep 1 18:23:29 (none) local0.notice cgminer[25546]: Stratum from pool 1 detected new block
Sep 1 18:23:39 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:24:00 (none) local0.info cgminer[25546]: Testing pool stratum+tcp://prohashing.com:3333
Sep 1 18:24:09 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:24:16 (none) local0.warn cgminer[25546]: Stratum reconnect requested from pool 1 to scrypt.usa.nicehash.com:3333
Sep 1 18:24:16 (none) local0.info cgminer[25546]: Cleared 2 work items due to stratum disconnect on pool 1
Sep 1 18:24:16 (none) local0.info cgminer[25546]: Stratum authorisation success for pool 1
Sep 1 18:24:16 (none) local0.notice cgminer[25546]: Pool 1 difficulty changed to 16384
Sep 1 18:24:16 (none) local0.notice cgminer[25546]: Stratum from pool 1 requested work restart
Sep 1 18:24:19 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:24:23 (none) local0.notice cgminer[25546]: Stratum from pool 1 requested work restart
Sep 1 18:24:37 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:24:39 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:24:41 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:24:48 (none) local0.info cgminer[25546]: New block: 0000000000000e95b4e544b08b88fc15751b56ef51102c81c8f345fe38281c75... diff 215K
Sep 1 18:24:48 (none) local0.notice cgminer[25546]: Stratum from pool 1 detected new block
Sep 1 18:24:49 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:25:00 (none) local0.info cgminer[25546]: Testing pool stratum+tcp://prohashing.com:3333
Sep 1 18:25:05 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:25:09 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:25:40 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333

Re: L3s still not finding prohash

Posted: Sat Sep 02, 2017 12:11 am
by hashingpro
Miners re-connected around 3:20 pm est today and have been on ever since rock steady.
Haven't been to backup pools now in hours, nothing changed on my end they just started detecting prohash as ALIVE and started mining on it again.

Now just don't touch any settings so I can get a solid 24-hours in please!
Thanks for all your hard work you do, and offer still stands, If you need outside access to try some remote testing or settings from some miners let me know.

Re: L3s still not finding prohash

Posted: Sat Sep 02, 2017 9:57 am
by Steve Sokolowski
Could I get an update on this one? Has the issue recurred since then?

Re: L3s still not finding prohash

Posted: Sun Sep 03, 2017 2:44 pm
by hashingpro
I woke up around 1 PM est, 3 miners still going other 5 showed DEAD on the site, all using the same account.
All on the same rack, same switch, same router, same ISP.

refreshed the webpage and the 3 working miners all showed ALIVE.

Rebooted the 5 not connecting, after reboot they still showed PH site as DEAD.

5 mins later the 3 working ones got kicked off and showed PH site as DEAD.
15 after the reboot all 8 came online and showed PH as ALIVE and are working now the past hour or so.
The 3 that were on when i woke up were never touched other than to refresh their status pages, so no reboots the site just came back up for them all after 15 mins.

Now trying one of the other account names I can log into and see if miners see that as ALIVE or DEAD.
So no, using my account it works, other account has issues.
So its not even a connection issue, its seems to more of --It cant find the account to connect in on issue.

Re: L3s still not finding prohash

Posted: Sun Sep 03, 2017 3:05 pm
by hashingpro
and 3:05 pm, all are now offline.