[CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers - page 275.

JinTu

full member

Activity: 133

Merit: 100

Quote from: JinTu on July 18, 2013, 10:19:02 AM

I have been seeing this error intermittently since some time just after 09:55 PDT on 7/17:

504 Gateway Time-out

cloudflare-nginx

It is affecting access to the web interface and API stats.

Could this be collateral damage from the Network Solutions DDOS?

Looks like this finally cleared up around 14:20 today (GMT-7), and had been happening for me since my earlier post.

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: CheezWiz on July 23, 2013, 09:58:16 PM

Quote from: eleuthria on July 23, 2013, 08:03:20 PM

Unfortunately, anything related to a worker's actual speed will need to be a local warning system. It's much more reliable, and more feasible to implement. Some kind of API monitor that sends you an email when a worker drops too low would not be hard to implement, whereas offering it as a standard feature could add a lot of extra load to the pool given how many actual workers are running at any given time.

Actually, I have just started playing with Arduinos and I think it would be more fun to make an arduino watch for the green light and email me!!
Better than my original plan of flusing a toilet, right... Grin

Use cgminer and my API

Write a little script to check it every 2 seconds for expected values.
The most useful one being 'devs' "Last Valid Work"
There are sample programs to access the API in Java, PHP, Python and C
Clicky: API-README

CheezWiz

newbie

Activity: 31

Merit: 0

Quote from: eleuthria on July 23, 2013, 08:03:20 PM

Unfortunately, anything related to a worker's actual speed will need to be a local warning system. It's much more reliable, and more feasible to implement. Some kind of API monitor that sends you an email when a worker drops too low would not be hard to implement, whereas offering it as a standard feature could add a lot of extra load to the pool given how many actual workers are running at any given time.

Actually, I have just started playing with Arduinos and I think it would be more fun to make an arduino watch for the green light and email me!!
Better than my original plan of flusing a toilet, right... Grin

eleuthria

legendary

Activity: 1750

Merit: 1007

Quote from: CheezWiz on July 23, 2013, 07:22:56 PM

Quote from: eleuthria on July 22, 2013, 12:24:21 PM

It's something I'll consider. If it's a big annoyance, one current workaround is hiding that worker. Hidden workers will not generate idle notification emails. Idle miner code is something I have been meaning to rewrite the script for to find a more efficient way to scan through the last share times of workers, so once I get to that (right now my focus is DDoS mitigation + new colocation), I will likely fit in the per-worker notification settings.

I would like to see code for a minimum threshold too. One of my ASICs dropped off and required a restart to get it active again.... The others kept churning away and I did not notice it until I saw the green light was on as I walked by... Not sure if that is really possible though due to variance over time..

Unfortunately, anything related to a worker's actual speed will need to be a local warning system. It's much more reliable, and more feasible to implement. Some kind of API monitor that sends you an email when a worker drops too low would not be hard to implement, whereas offering it as a standard feature could add a lot of extra load to the pool given how many actual workers are running at any given time.

CheezWiz

newbie

Activity: 31

Merit: 0

Quote from: eleuthria on July 22, 2013, 12:24:21 PM

It's something I'll consider. If it's a big annoyance, one current workaround is hiding that worker. Hidden workers will not generate idle notification emails. Idle miner code is something I have been meaning to rewrite the script for to find a more efficient way to scan through the last share times of workers, so once I get to that (right now my focus is DDoS mitigation + new colocation), I will likely fit in the per-worker notification settings.

I would like to see code for a minimum threshold too. One of my ASICs dropped off and required a restart to get it active again.... The others kept churning away and I did not notice it until I saw the green light was on as I walked by... Not sure if that is really possible though due to variance over time..

os2sam

legendary

Activity: 3583

Merit: 1094

Think for yourself

Quote from: eleuthria on July 22, 2013, 01:00:32 PM

Quote from: os2sam on July 22, 2013, 12:37:02 PM

Quote from: eleuthria on July 22, 2013, 12:24:21 PM

Quote from: os2sam on July 22, 2013, 12:11:39 PM

Eleuthria,
Have you thought about applying notifications on a per worker basis?

A worker was throwing spurious work at BTC Guild and I got about 10 notifications emails for that worker while it was mining another pool.
Sam

It's something I'll consider. If it's a big annoyance, one current workaround is hiding that worker. Hidden workers will not generate idle notification emails. Idle miner code is something I have been meaning to rewrite the script for to find a more efficient way to scan through the last share times of workers, so once I get to that (right now my focus is DDoS mitigation + new colocation), I will likely fit in the per-worker notification settings.

If I hide it will it still mine?

Yes, hidden workers will still mine. They just won't be visible on your charts (if you unhide it, they will show up again).

That sounds like a workable solution. If you get around to doing per worker notifications that would be great.

Thanks,
Sam

eleuthria

legendary

Activity: 1750

Merit: 1007

Quote from: os2sam on July 22, 2013, 12:37:02 PM

Quote from: eleuthria on July 22, 2013, 12:24:21 PM

Quote from: os2sam on July 22, 2013, 12:11:39 PM

Eleuthria,
Have you thought about applying notifications on a per worker basis?

A worker was throwing spurious work at BTC Guild and I got about 10 notifications emails for that worker while it was mining another pool.
Sam

It's something I'll consider. If it's a big annoyance, one current workaround is hiding that worker. Hidden workers will not generate idle notification emails. Idle miner code is something I have been meaning to rewrite the script for to find a more efficient way to scan through the last share times of workers, so once I get to that (right now my focus is DDoS mitigation + new colocation), I will likely fit in the per-worker notification settings.

If I hide it will it still mine?

Yes, hidden workers will still mine. They just won't be visible on your charts (if you unhide it, they will show up again).

os2sam

legendary

Activity: 3583

Merit: 1094

Think for yourself

Quote from: eleuthria on July 22, 2013, 12:24:21 PM

Quote from: os2sam on July 22, 2013, 12:11:39 PM

Eleuthria,
Have you thought about applying notifications on a per worker basis?

A worker was throwing spurious work at BTC Guild and I got about 10 notifications emails for that worker while it was mining another pool.
Sam

It's something I'll consider. If it's a big annoyance, one current workaround is hiding that worker. Hidden workers will not generate idle notification emails. Idle miner code is something I have been meaning to rewrite the script for to find a more efficient way to scan through the last share times of workers, so once I get to that (right now my focus is DDoS mitigation + new colocation), I will likely fit in the per-worker notification settings.

If I hide it will it still mine?

eleuthria

legendary

Activity: 1750

Merit: 1007

Quote from: os2sam on July 22, 2013, 12:11:39 PM

Eleuthria,
Have you thought about applying notifications on a per worker basis?

A worker was throwing spurious work at BTC Guild and I got about 10 notifications emails for that worker while it was mining another pool.
Sam

It's something I'll consider. If it's a big annoyance, one current workaround is hiding that worker. Hidden workers will not generate idle notification emails. Idle miner code is something I have been meaning to rewrite the script for to find a more efficient way to scan through the last share times of workers, so once I get to that (right now my focus is DDoS mitigation + new colocation), I will likely fit in the per-worker notification settings.

os2sam

legendary

Activity: 3583

Merit: 1094

Think for yourself

Eleuthria,
Have you thought about applying notifications on a per worker basis?

A worker was throwing spurious work at BTC Guild and I got about 10 notifications emails for that worker while it was mining another pool.
Sam

xmasautopsy

newbie

Activity: 6

Merit: 0

Quote from: Pinwheel on July 22, 2013, 07:39:09 AM

Quote from: dnaleor on July 22, 2013, 06:44:40 AM

Quote from: medUSA on July 22, 2013, 06:37:14 AM

I am just wondering whether we really haven't found a block for the past 3 hours, or it's it just the website not updating due to the DDOS?

Anyway, thanks for all the hardwork, Eleuthria!

indeed, good question.

It's 'funny': I started mining for the very first time when the shifts with no blocks started...
I hope the problem is fixed soon, or I maybe need to switch to another pool...

edit: saw the post above... still, it's very strange Tongue

6 trh already gone, that is exactly what those who ddos want. slush pool under ddos too.

man, that sure turned out way better than i thought those 6 shifts were gonna

Pinwheel

sr. member

Activity: 378

Merit: 250

Quote from: dnaleor on July 22, 2013, 06:44:40 AM

Quote from: medUSA on July 22, 2013, 06:37:14 AM

I am just wondering whether we really haven't found a block for the past 3 hours, or it's it just the website not updating due to the DDOS?

Anyway, thanks for all the hardwork, Eleuthria!

indeed, good question.

It's 'funny': I started mining for the very first time when the shifts with no blocks started...
I hope the problem is fixed soon, or I maybe need to switch to another pool...

edit: saw the post above... still, it's very strange Tongue

6 trh already gone, that is exactly what those who ddos want. slush pool under ddos too.

dnaleor

legendary

Activity: 1470

Merit: 1000

Want privacy? Use Monero!

Quote from: medUSA on July 22, 2013, 06:37:14 AM

I am just wondering whether we really haven't found a block for the past 3 hours, or it's it just the website not updating due to the DDOS?

Anyway, thanks for all the hardwork, Eleuthria!

indeed, good question.

It's 'funny': I started mining for the very first time when the shifts with no blocks started...
I hope the problem is fixed soon, or I maybe need to switch to another pool...

edit: saw the post above... still, it's very strange Tongue

eleuthria

legendary

Activity: 1750

Merit: 1007

Quote from: medUSA on July 22, 2013, 06:37:14 AM

I am just wondering whether we really haven't found a block for the past 3 hours, or it's it just the website not updating due to the DDOS?

Anyway, thanks for all the hardwork, Eleuthria!

We have not found a block recently. This is not directly related to the DDoS (other than losing speed = longer block solve time on average). They just happen to be occurring simultaneously.

medUSA

legendary

Activity: 952

Merit: 1005

--Signature Designs-- http://bit.ly/1Pjbx77

I am just wondering whether we really haven't found a block for the past 3 hours, or it's it just the website not updating due to the DDOS?

Anyway, thanks for all the hardwork, Eleuthria!

eleuthria

legendary

Activity: 1750

Merit: 1007

Quote from: HellDiverUK on July 22, 2013, 06:13:42 AM

Define "long term users".

Glad you're working on it anyway.

I'm running load balanced, hadn't noticed things going wrong with the pool, still seems to be accepting shares.

Long term would be a user that has been mining for more than a month or two in this circumstance.

HellDiverUK

hero member

Activity: 1246

Merit: 501

Define "long term users".

Glad you're working on it anyway.

I'm running load balanced, hadn't noticed things going wrong with the pool, still seems to be accepting shares.

eleuthria

legendary

Activity: 1750

Merit: 1007

About 45 minutes ago a DDoS attack was launched against the pool. My alarms woke me up shortly after. For the last ~40 minutes I have been actively launching proxy servers and changing DNS settings while redirecting traffic to backends without exposed IPs. I am sorry for the inconvenience this may have caused.

Long term BTC Guild users: Please contact me ([email protected]) to request direct access to one of the backend servers. There has been a private server for a long time reserved for high speed users. I am now ready to launch 1-2 additional private servers designed for slower miners who have been with the pool for a long time.

Lucko

hero member

Activity: 826

Merit: 1000

Quote from: eleuthria on June 18, 2013, 04:13:32 PM

Quote from: Lucko on June 18, 2013, 02:00:08 PM

Where are we on redistribution of PPS NMC? And how can I get NMC out. If I set auto payout I can get only the amount set per hour but not all that is in the accaunt. And I can't set auto payout to exact number of NMC...

As I stated in the beginning, NMC support is not even close to a priority. For now automatic payouts will continue to be the only method to withdraw in order to avoid heavily fragmenting the wallet. Namecoin's code is ancient and lacks a significant number of optimizations that have been added to Bitcoin over the last two years. You will likely never see amounts under 0.01 NMC available for payout. NMC's transaction fees are higher than BTC for sending small amounts.

I know you stated hire that NMC has no priority but that was long time ago. Are you kepping PPS NMC for yourself and you give as wrong information or are you doing this? At the start it was to be solved in days not months...

And I drooped that part since i didn't care enough for not even cents but now I'm writing again... About getting NMC out. I don't wont to take out 0.0023 or something like that but i would like to take out all not just a multiplication of auto-payout...

eleuthria

legendary

Activity: 1750

Merit: 1007

Sorry that the website has been up and down for the last few hours. Last night I added some extra defense to eliminate the effectiveness of the person that was basically running a distributed password scan (posting leaked database details from other websites and trying to use them to login to BTC Guild accounts). These attacks were lagging the site badly due to how hard it was hitting the database with constant login attempts.

I woke up this morning seeing a new attack, this time just flooding the server over port 80 passing complete garbage through, rather than trying to log in. Whether it is the same person or not, I am not sure at this time.

Mining should not have been affected during these attacks, everything has been limited to taking down the website so far.

Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers - page 275. (Read 903150 times)