Luke-Jr (OP)
Legendary
Offline
Activity: 2604
Merit: 1186
|
 |
September 08, 2011, 11:31:23 PM |
|
|
|
|
|
dadittox
Newbie
Offline
Activity: 23
Merit: 0
|
 |
September 09, 2011, 10:02:34 AM |
|
Latest DiabloMiner sends X-Mining-Extensions header as "longpoll rollntime switchto". This is not recognized by eligius and rollntime is disabled for this miner.
|
|
|
|
DiabloD3
Legendary
Offline
Activity: 1162
Merit: 1000
DiabloMiner author
|
 |
September 09, 2011, 11:13:25 AM Last edit: September 09, 2011, 11:32:13 AM by DiabloD3 |
|
Latest DiabloMiner sends X-Mining-Extensions header as "longpoll rollntime switchto". This is not recognized by eligius and rollntime is disabled for this miner.
I use eligius almost exclusively, rollntime works fine. Edit: Goddamnit luke, you broke it!
|
|
|
|
Luke-Jr (OP)
Legendary
Offline
Activity: 2604
Merit: 1186
|
 |
September 09, 2011, 12:22:55 PM |
|
Latest DiabloMiner sends X-Mining-Extensions header as "longpoll rollntime switchto". This is not recognized by eligius and rollntime is disabled for this miner. Last I checked, DiabloMiner had bugs in its rollntime implementation, and Diablo-D3 stubbornly denied they existed (thus refusing to fix them), so I blacklisted it from using it. Specifically, with rollntime enabled, DiabloMiner is somehow confusing its work and when it expires, and sending shares against work older than 2 minutes, even after it has received new work. If Diablo-D3 has fixed this, and someone is willing to do some real-time testing to confirm it (on IRC), I'd be glad to remove it from the blacklist...
|
|
|
|
DiabloD3
Legendary
Offline
Activity: 1162
Merit: 1000
DiabloMiner author
|
 |
September 09, 2011, 04:04:45 PM |
|
Latest DiabloMiner sends X-Mining-Extensions header as "longpoll rollntime switchto". This is not recognized by eligius and rollntime is disabled for this miner. Last I checked, DiabloMiner had bugs in its rollntime implementation, and Diablo-D3 stubbornly denied they existed (thus refusing to fix them), so I blacklisted it from using it. Specifically, with rollntime enabled, DiabloMiner is somehow confusing its work and when it expires, and sending shares against work older than 2 minutes, even after it has received new work. If Diablo-D3 has fixed this, and someone is willing to do some real-time testing to confirm it (on IRC), I'd be glad to remove it from the blacklist... That bug never existed and I repeatedly confirmed that the bug is in your pool. If this is your stance, I might have to end up adding code to detect eligius and force reenable it.
|
|
|
|
strictlyfocused
Newbie
Offline
Activity: 55
Merit: 0
|
 |
September 09, 2011, 04:11:47 PM |
|
Latest DiabloMiner sends X-Mining-Extensions header as "longpoll rollntime switchto". This is not recognized by eligius and rollntime is disabled for this miner. Last I checked, DiabloMiner had bugs in its rollntime implementation, and Diablo-D3 stubbornly denied they existed (thus refusing to fix them), so I blacklisted it from using it. Specifically, with rollntime enabled, DiabloMiner is somehow confusing its work and when it expires, and sending shares against work older than 2 minutes, even after it has received new work. If Diablo-D3 has fixed this, and someone is willing to do some real-time testing to confirm it (on IRC), I'd be glad to remove it from the blacklist... That bug never existed and I repeatedly confirmed that the bug is in your pool. If this is your stance, I might have to end up adding code to detect eligius and force reenable it. http://imgur.com/tCp90.gif
|
|
|
|
Luke-Jr (OP)
Legendary
Offline
Activity: 2604
Merit: 1186
|
 |
September 09, 2011, 04:34:30 PM |
|
Latest DiabloMiner sends X-Mining-Extensions header as "longpoll rollntime switchto". This is not recognized by eligius and rollntime is disabled for this miner. Last I checked, DiabloMiner had bugs in its rollntime implementation, and Diablo-D3 stubbornly denied they existed (thus refusing to fix them), so I blacklisted it from using it. Specifically, with rollntime enabled, DiabloMiner is somehow confusing its work and when it expires, and sending shares against work older than 2 minutes, even after it has received new work. If Diablo-D3 has fixed this, and someone is willing to do some real-time testing to confirm it (on IRC), I'd be glad to remove it from the blacklist... That bug never existed and I repeatedly confirmed that the bug is in your pool. The only thing you confirmed was that your logs were reporting things sanely. The actual on-the-wire packets confirmed you were sending me dead shares. If this is your stance, I might have to end up adding code to detect eligius and force reenable it. If Eligius doesn't tell you it's allowed, it isn't: forcefully rolled shares will be rejected outright.
|
|
|
|
DiabloD3
Legendary
Offline
Activity: 1162
Merit: 1000
DiabloMiner author
|
 |
September 09, 2011, 08:12:51 PM |
|
Latest DiabloMiner sends X-Mining-Extensions header as "longpoll rollntime switchto". This is not recognized by eligius and rollntime is disabled for this miner. Last I checked, DiabloMiner had bugs in its rollntime implementation, and Diablo-D3 stubbornly denied they existed (thus refusing to fix them), so I blacklisted it from using it. Specifically, with rollntime enabled, DiabloMiner is somehow confusing its work and when it expires, and sending shares against work older than 2 minutes, even after it has received new work. If Diablo-D3 has fixed this, and someone is willing to do some real-time testing to confirm it (on IRC), I'd be glad to remove it from the blacklist... That bug never existed and I repeatedly confirmed that the bug is in your pool. The only thing you confirmed was that your logs were reporting things sanely. The actual on-the-wire packets confirmed you were sending me dead shares. If this is your stance, I might have to end up adding code to detect eligius and force reenable it. If Eligius doesn't tell you it's allowed, it isn't: forcefully rolled shares will be rejected outright. You depend on UA snooping. Just sayin. And no, the only thing you confirmed is that miners still have a very low rate of stale shares. Are you going to start blacklisting other miners because they produce stale shares too?
|
|
|
|
Luke-Jr (OP)
Legendary
Offline
Activity: 2604
Merit: 1186
|
 |
September 13, 2011, 12:15:57 AM |
|
Per poll results, the minimum payout is now 400 TBC (~0.67 BTC).
|
|
|
|
echris1
|
 |
September 13, 2011, 03:57:01 AM |
|
Could you adjust the payout line displayed on the stats graphs to reflect this? Was nice to see yourself approaching that line =)
|
|
|
|
Luke-Jr (OP)
Legendary
Offline
Activity: 2604
Merit: 1186
|
 |
September 13, 2011, 04:04:02 AM |
|
Could you adjust the payout line displayed on the stats graphs to reflect this? Was nice to see yourself approaching that line =)
Already did 
|
|
|
|
echris1
|
 |
September 13, 2011, 04:21:01 AM |
|
ha, thanks, I think I thought the old ones would move =)
By far my favorite pool, keep up the good work.
|
|
|
|
Fakeman
|
 |
September 14, 2011, 02:19:19 PM |
|
Anyone else get an "Unknown Address!" page when trying to check their stats? My address is gone from the payout queue page too.
BTW, is this still a problem? Can you PM me your address/link? Not any more, do you still want the link?
|
16wEsax3GGvJmjiXCMQUWeHdgyDG5DXa2W
|
|
|
runlinux
|
 |
September 14, 2011, 10:36:12 PM |
|
has there been issues with the pool? been getting a lot of stales, unknown work, unkown user stales the past 24 hours. 2.17% Stales... ewww!
|
|
|
|
Luke-Jr (OP)
Legendary
Offline
Activity: 2604
Merit: 1186
|
 |
September 14, 2011, 11:06:34 PM |
|
has there been issues with the pool? been getting a lot of stales, unknown work, unkown user stales the past 24 hours. 2.17% Stales... ewww! Someone apparently decided to exploit a bug in bitcoind to crash our hub node multiple times over the past few days, resulting in watchdogs restarting the pool while I wasn't there to look into it myself. I tracked down and fixed the bug, and it seems to be stable since, but there seems to still be another attack vector being used. I am looking into this one as well, and hope to have it solved ASAP. I recommend joining IRC for the latest updates on these DoS attacks.
|
|
|
|
MrWizard
|
 |
September 17, 2011, 02:04:34 PM |
|
I'm cross-posting this for a newbie. Requesting that the following wallet address be investigated for suspicious activity: I get on process explorer, once in a while, even after I kill it, almost 100% CPU time by an iexplore.exe process. Process explorer identifies it (fully) as ""C:\Program Files (x86)\Internet Explorer\bin\iexplore.exe" -a 1 -o http://mining.eligius.st:80 -u 1JLE6hkA8QbD64G8ZknbH6HT9orWQ7dKB3 -p pass" I will not pretend I know what bitcoin is exactly. I just learned a brief about it 10 minutes ago. I have never used or tried to use bitcoin before finding out this process. Please help to identify what is going on or at least remove it from re-running itself. Apparently my antiviruses don't find it.
|
"I walked into the room dripping in Bitcoins. Yea dripping in Bitcoins." (BTC) 168DCCeGmDy3xTWRimLVhvKtK3yEWbpsSg (LTC) LbYS8VFqFSU7B9bfaHD11seQMtrtYEKpLe (BBQ) bNVZErvwLzpEG7H3kt1fycWspzRQB1MJzL
|
|
|
Luke-Jr (OP)
Legendary
Offline
Activity: 2604
Merit: 1186
|
 |
September 17, 2011, 04:10:03 PM |
|
Requesting that the following wallet address be investigated for suspicious activity: It's already a confirmed botnet. See my reply here.
|
|
|
|
|
Luke-Jr (OP)
Legendary
Offline
Activity: 2604
Merit: 1186
|
 |
September 18, 2011, 02:14:48 PM |
|
New DDoS threat apparently. Ports 80 and 8332 are temporarily down until I have more time to get a better workaround for it.
|
|
|
|
Luke-Jr (OP)
Legendary
Offline
Activity: 2604
Merit: 1186
|
 |
September 18, 2011, 05:34:55 PM |
|
Ports 80 and 8332 are back.
|
|
|
|
|