Topic: [ANN][AUTO-SWITCH] Profit-switch auto-exchange pool: CleverMining.com - page 114. (Read 554380 times)

hmmm, well i guess if they say web crawlers can scan it, there has to be a way. what's the link where you read this?

I went the python route a few weeks back, but got no where.  After reading your post, i fired wireshark back up and it looks like there's a hidden form that needs some special key to return in order to let us through ... so I also think we'll need some code to accept their cookie/whatever and respond back similar to how a browser would.  still kind of pain to grab some data  

update: ok so i did some digging. got this from the cloudflare site:
Javascript and cookies are required for the tests, and to record the fact that the tests were correctly passed. The page which your visitors see when in IUAM can be fully customized to reflect your branding. I'm Under Attack mode does not block search engine crawlers or your existing CloudFlare whitelist.

My guess is they whitelisted known and allowed search engine crawlers which is why those bots work where as ours dont.  Add to it that it looks like Terk opted to put the domain in a permanent I'm Under Attack Mode and we are where we are. So pretty much we need to mimic the expected behavior if we want anything to work ... lovely

A prime example of what we techie people hate.  You try everything under the sun to get something working again, and it winds up being the thing that can't possibly have anything to do with it.
"I just got this great new lamp at the thrift store!  Oddly every time I turn it on my computer BSOD's."

No good ideas, but having the same issue.  In trying 800 MHz and 900MHz each separately for about 24 hours, I received even lower hash rates on CM.

I'm running 20 Gridseeds, RaPi, and CGMiner 3.7.2 showing ~7.2Mh/s on miner, but only showing up ~5.0Mh/s on CM.  That puts each GS averaging about 250 Kh/s on CM, but showing 360 Kh/s on CGMiner.  My GS have fairly equal accepted work, are mining pretty efficiently at 850 MHz, with minimal (0-3) HW errors per unit per 24 hours.  Reject rate is just over 1%.

I'd too would like comments back if others are experiencing lower hash rates on CM and any tweeks or adjustments to increase real, recognized hash rates on CM.  Hey - not complaining though - with the recent ~200% returns, it was like getting real 500 KH/s from each GS! 

Thanks for a great pool and the professional efforts/information from everyone!

I have noticed that on this pool there is a long delay, several hours usually, before mined coins are exchanged for bitcoins.
My question is: doesn't this undermine the very concept of multi-coin mining, i.e. mining the coins that are most profitable in that moment? If you wait several hours before trading at the exchange don't you risk to lose profitability (or to take a loss)?

Ok... I'll try to explain this problem again and hopefully someone else has experience and can help me.

Problem #1:  11 GS miners hashing power degrading and not maintaining advertised hash rates.  This is a  problem on 3 sites currently.  I continue to see the hash rate degrade on MP, IPOM and CM.  It does not matter the coin or site.  GS's supposedly should run at 0.333MH/s but mine are degrading over time until all 11 are at 0.27MH/s.   

  Suggestions I have tried but will not work... MP suggested setting share difficulty to 64.  Tried but no improvement observed.
                                                                 Mine on equip set for mining only.  Rasp Pi is dedicated 100% to GS mining. i.e. suggestion no help!
                                                                 
Problem #2:  Eventually, all 11 miners will shutdown... MinePeon shows no miners active even though miners are still running?  Failover fails (no pun) and backup pools never activated even though software is set and supposedly is capable of restarting on backup?


Here are my settings from MinePeon.... Please if anyone has success running GS's with minepeon and can give me some real help, please contact me.

#!/bin/bash
sleep 10
/usr/bin/screen -dmS miner /opt/minepeon/bin/bfgminer -S all -c /opt/minepeon/etc/miner.conf --scrypt --set-device gridseed:clock=805

I had a day when all my gridseeds shut down at once.  I did "this and that" and they finally started up.
I left the house, came back.  Again they all shut down.

Long story short, I finally concluded that plugging my phone into a port on the front of the computer that runs my mining software was what caused it.

Pardon me for not qualifying what "this and that" includes,  nor detailing what mining software I am using and etc.  I tied a knot in the cable that I was using to charge my phone so I would recognize it and never use it again (but I kept it in case I wanted to prove it was the culprit).

...I use a USB mapping utility called UsbTreeView, and on its diagram the port where my phone was plugged in, it showed a yellow "i" indicating a problem. 

I am not suggesting that your telephone is causing your problem, but rather I am encouraging you to maybe look elsewhere besides the gridseeds and power supply, as I had to do.

Ok... I'll try to explain this problem again and hopefully someone else has experience and can help me.

Problem #1:  11 GS miners hashing power degrading and not maintaining advertised hash rates.  This is a  problem on 3 sites currently.  I continue to see the hash rate degrade on MP, IPOM and CM.  It does not matter the coin or site.  GS's supposedly should run at 0.333MH/s but mine are degrading over time until all 11 are at 0.27MH/s.   

  Suggestions I have tried but will not work... MP suggested setting share difficulty to 64.  Tried but no improvement observed.
                                                                 Mine on equip set for mining only.  Rasp Pi is dedicated 100% to GS mining. i.e. suggestion no help!
                                                                 
Problem #2:  Eventually, all 11 miners will shutdown... MinePeon shows no miners active even though miners are still running?  Failover fails (no pun) and backup pools never activated even though software is set and supposedly is capable of restarting on backup?


Here are my settings from MinePeon.... Please if anyone has success running GS's with minepeon and can give me some real help, please contact me.

#!/bin/bash
sleep 10
/usr/bin/screen -dmS miner /opt/minepeon/bin/bfgminer -S all -c /opt/minepeon/etc/miner.conf --scrypt --set-device gridseed:clock=805
 
Ok just had GS's shutdown (no hash) when multipool switched to new coin?

I am having the same problem in trying to "data scrape" as you call it.  I read on the CloudFlare site that their protection does not prevent web crawlers from scanning the site (so I am confident we can find a way to do it), and I'm thinking what I will try next is to write code to accept their cookie(s).  Of course, my guess is worthless until I have it running.

What I unsuccessfully tried in php was to file_get_contents, then do a javascript setTimeout of 10 seconds, after which I do a window.location.reload.  

so I may have missed this in the many pages here, but have we ever gotten an API?

The whole cloudflare/ddos protection stuff is nice to keep the pool up, but incredibly annoying for both checking hte pages and trying to write data scrapers to track my performance.

If there is no API (still) any one have any suggestions on how to scrape data from their miner pages?  I cant seem to get around the cloudflare junk

Yes my miners have been slowly losing hash rate until they shut down completely on CM.  So I switched to ipominer, CINNI and they had problems with cinni servers and again my miners shutdown, but never switched to backup.  So down all day.   Ahhhhhhhhhhhhhhh.

So I switched back to CM and gridseeds shutdown again.   Not sure what is going on?

Yes my miners have been slowly losing hash rate until they shut down completely on CM.  So I switched to ipominer, CINNI and they had problems with cinni servers and again my miners shutdown, but never switched to backup.  So down all day.   Ahhhhhhhhhhhhhhh.

So I switched back to CM and gridseeds shutdown again.   Not sure what is going on?