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

Lamalicious

member

Activity: 148

Merit: 10

Quote from: AussieHash on January 22, 2014, 03:45:20 AM

More then 10% of the blocks. I wonder what causing it.

AussieHash

hero member

Activity: 692

Merit: 500

eleuthria

legendary

Activity: 1750

Merit: 1007

There was a small bug over the last 12 hours approximately affecting the interaction between the website and backend servers when modifying worker settings like names, payment methods, and minimum difficulty. The load balancer and backends were updated to run twice as many server processes, but only the original set of processes were able to receive notifications from the website when updating worker settings. As a result, your difficulty and payment method may be different depending on which backend you connect to.

If you're experiencing this (shares paid to the wrong method or difficulty starting higher/lower than it should), you can toggle your settings back and forth to force an update to the mining servers.

This bug only affects *changes* made in the last ~12 hours. If you have not changed any settings, this would not have any affect on your miners.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: eleuthria on January 21, 2014, 03:10:20 PM

Quote from: -ck on January 21, 2014, 03:08:29 PM

Quote from: eleuthria on January 21, 2014, 12:23:41 PM

Sounds like the solution for those having cgminer crashes is to downgrade to a non 3.10 version. Quite curious what the hell he did to break such a basic feature that has been working flawlessly for the last 6 months.

EDIT: You can connect to 'cgminer.btcguild.com:3333' as a temporary workaround. This server may disappear with little (or even 0) notice once the bug is known to be fixed.

You didn't read the quote. It's been broken forever.

Then it must be extremely rare, because I haven't seen any reports about it causing segfaults until 3.10.

The changes on it in 3.10 was my half arsed attempt to fix it when I was heading out to go overseas with little time to spare for it.

eleuthria

legendary

Activity: 1750

Merit: 1007

Quote from: -ck on January 21, 2014, 03:08:29 PM

Quote from: eleuthria on January 21, 2014, 12:23:41 PM

Sounds like the solution for those having cgminer crashes is to downgrade to a non 3.10 version. Quite curious what the hell he did to break such a basic feature that has been working flawlessly for the last 6 months.

EDIT: You can connect to 'cgminer.btcguild.com:3333' as a temporary workaround. This server may disappear with little (or even 0) notice once the bug is known to be fixed.

You didn't read the quote. It's been broken forever.

Then it must be extremely rare, because I haven't seen any reports about it causing segfaults until 3.10. BTC Guild has been using client.reconnect for a very long time.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: eleuthria on January 21, 2014, 12:23:41 PM

Sounds like the solution for those having cgminer crashes is to downgrade to a non 3.10 version. Quite curious what the hell he did to break such a basic feature that has been working flawlessly for the last 6 months.

EDIT: You can connect to 'cgminer.btcguild.com:3333' as a temporary workaround. This server may disappear with little (or even 0) notice once the bug is known to be fixed.

You didn't read the quote. It's been broken forever.

matt4054

legendary

Activity: 1946

Merit: 1035

I'm hashing on BTC Guild with a KnC Saturn 0.99.1-tune without any issue

eleuthria

legendary

Activity: 1750

Merit: 1007

Quote from: AussieHash on January 21, 2014, 01:10:28 PM

Quote from: eleuthria on January 21, 2014, 12:23:41 PM

Sounds like the solution for those having cgminer crashes is to downgrade to a non 3.10 version.

Does this affect any kncminer firmware version(s) ?

I have no idea. The only ASICs I have are USB Block Erupters.

AussieHash

hero member

Activity: 692

Merit: 500

Quote from: eleuthria on January 21, 2014, 12:23:41 PM

Sounds like the solution for those having cgminer crashes is to downgrade to a non 3.10 version.

Does this affect any kncminer firmware version(s) ?

matt4054

legendary

Activity: 1946

Merit: 1035

Thanks for the quick server side workaround, very much appreciated. I will try it upon next crash.
I didn't have any other crash since my last post as far as I'm concerned.

eleuthria

legendary

Activity: 1750

Merit: 1007

Sounds like the solution for those having cgminer crashes is to downgrade to a non 3.10 version. Quite curious what the hell he did to break such a basic feature that has been working flawlessly for the last 6 months.

EDIT: You can connect to 'cgminer.btcguild.com:3333' as a temporary workaround. This server may disappear with little (or even 0) notice once the bug is known to be fixed.

HellDiverUK

hero member

Activity: 1246

Merit: 501

According to CK, there's a bug in cgminer which BTCGuild breaks.

Quote from: -ck on January 21, 2014, 08:29:29 AM

Yes, btcguild is a separate bug, sorry. BTCguild is the only pool that uses the redirect feature in stratum which was added blindly a long time ago when stratum support was first added and no pool used it. Cgminer's implementation is unfortunately buggy and the only workaround till I can fix it is to connect directly to btcguild's redirected url directly or use a different pool to avoid the crash.

frederikhk

newbie

Activity: 35

Merit: 0

can't connect with cgminer since yesterday Sad

i took a screenshot of cgminer right before it crashed: http://i.imgur.com/ibOj6fw.png

HellDiverUK

hero member

Activity: 1246

Merit: 501

cgminer is still crashing on me too. Now as soon as it connects to BTCGuild it segfaults. Same instance of cgminer has been running on Eligius perfectly for 24 hours. I've also tried it on p2pool, and also on ghash.io. It's ONLY BTCGuild that makes cgminer crash out instantly. bfgminer on the same machine connects perfectly to all pools.

NOTHING has changed in my setup, as the machine wasn't plugged in for a few days, and was working perfectly before.

eleuthria

legendary

Activity: 1750

Merit: 1007

Quote from: matt4054 on January 21, 2014, 02:02:48 AM

Hey, I'm sorry for the missing log file and debugging etc. but I thought it was worth mentioning that:

ALL of my cgminer instances that were connected to BTC Guild, that is various versions from 3.0.x to the latest have crashed at the same time, approximately 06:31 GMT today 21 Jan 2014. I could see a "cannot parse output" and then a Segmentation Fault on the terminal just before crashing, while other instances just exited like they had received a SIGTERM, SIGKILL (or SIGSEGV?).

Even my Antminer S1 with factory built-in firmware running modified cgminer crashed, too. It also crashed on my KnC Miner, but this one is the only one that respawned automagically thanks to the init scripts and monitoring.

Has anyone else experienced this? I'm cross-posting this here but I also posted on the cgminer thread.

That's...interesting. I can't think of anything that happened in the last 2 hours that could've caused such a crash. Were all the machines behind the same router? Have you been able to reconnect?

matt4054

legendary

Activity: 1946

Merit: 1035

Hey, I'm sorry for the missing log file and debugging etc. but I thought it was worth mentioning that:

ALL of my cgminer instances that were connected to BTC Guild, that is various versions from 3.0.x to the latest have crashed at the same time, approximately 06:31 GMT today 21 Jan 2014. I could see a "cannot parse output" and then a Segmentation Fault on the terminal just before crashing, while other instances just exited like they had received a SIGTERM, SIGKILL (or SIGSEGV?).

Even my Antminer S1 with factory built-in firmware running modified cgminer crashed, too. It also crashed on my KnC Miner, but this one is the only one that respawned automagically thanks to the init scripts and monitoring.

Has anyone else experienced this? I'm cross-posting this here but I also posted on the cgminer thread.

eleuthria

legendary

Activity: 1750

Merit: 1007

Quote from: Trongersoll on January 20, 2014, 11:23:03 PM

Quote from: eleuthria on January 20, 2014, 08:41:23 PM

Quote from: jesse11 on January 20, 2014, 08:40:05 PM

Yeah, my Cubes really took a hit, there running 94-97% on my end. Down 90% Sad

I'll move them till the problem is fixed.

All problems are fixed now, every BTC Guild server (including validation server) has been reverted to the same software it was using for the last year.

And my machine is back to running at the proper rate. When the old stuff works and the new stuff doesn't... You have your work cut out for you.

It's unfortunate that the only way to find out the new stuff doesn't work is by putting it live. Every local test I can do turns out fine, but there are so many thousands of hardware configurations, software configurations, and just plain VOLUME of network activity that you can't properly test in a sterile development environment.

For now, I think I might hang up this attempt at a rewrite and fall back to what I know at least one other pool has done to get better multi-core utilization: Just run the server process multiple times on multiple ports and have a proxy split the load on the same machine over the different ports. It feels like a cop out, but I noticed during the live testing that a significant load still hit one core: The one used for the primary network IO processing, which is extremely difficult to split over multiple cores/threads without significant overhead in mutex locking. I get the feeling it wouldn't be any more efficient than just running multiple instances of the server.

Trongersoll

hero member

Activity: 490

Merit: 501

Quote from: eleuthria on January 20, 2014, 08:41:23 PM

Quote from: jesse11 on January 20, 2014, 08:40:05 PM

Yeah, my Cubes really took a hit, there running 94-97% on my end. Down 90% Sad

I'll move them till the problem is fixed.

All problems are fixed now, every BTC Guild server (including validation server) has been reverted to the same software it was using for the last year.

And my machine is back to running at the proper rate. When the old stuff works and the new stuff doesn't... You have your work cut out for you.

BrandonMcPherson

full member

Activity: 205

Merit: 100

GL with the bug finding, Eleuthria.

jesse11

sr. member

Activity: 333

Merit: 250

Ants Rock

Thanks eleuthria

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