[∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved! - page 425.

notbatman

legendary

Activity: 2212

Merit: 1038

Quote from: dkaufman on March 04, 2015, 11:25:26 AM

Quote from: notbatman on March 03, 2015, 07:58:35 PM

FYI

While streaming Invasion of the Body Snatchers (1978) I had CGMiner 4.9.1 close & exit twice while mining at solo.ckpool.org, I switched pools to bitcoind running locally and it's been going without exiting for about 30 mins now. I'm running the Windows build of CGMiner and it had been running for about 24 hours and only started crashing while watching the movie.

I haven't seen this behavior before, I just upgraded the miner to CGMiner from BFGMiner yesterday.

You've clearly run into that rare incompatibility between CGMiner, Windows and the streaming of a bad horror video on the same wifi network. Such unwelcome bandwidth harmonics only affects CGMiner 4.7 and higher. It is recommended that you downgrade CGMiner or switch back to BFGMiner immediately, or upgrade to Linux.

And count yourself lucky it wasn't a good horror movie. I bricked a whole stack of S4's binge-watching the Saw movies that way!

I streamed one of the Superman animated movies (low res off YouTube) last night and all the eruptors lit up again. I alt-tabbed out of full-screen to find the system had ground to halt, I even had no mouse action for a few seconds and CGMiner complained about lack of work but it didn't crash like while mining at solo.ckpool.org.

dkaufman

member

Activity: 84

Merit: 10

Quote from: notbatman on March 03, 2015, 07:58:35 PM

FYI

While streaming Invasion of the Body Snatchers (1978) I had CGMiner 4.9.1 close & exit twice while mining at solo.ckpool.org, I switched pools to bitcoind running locally and it's been going without exiting for about 30 mins now. I'm running the Windows build of CGMiner and it had been running for about 24 hours and only started crashing while watching the movie.

I haven't seen this behavior before, I just upgraded the miner to CGMiner from BFGMiner yesterday.

You've clearly run into that rare incompatibility between CGMiner, Windows and the streaming of a bad horror video on the same wifi network. Such unwelcome bandwidth harmonics only affects CGMiner 4.7 and higher. It is recommended that you downgrade CGMiner or switch back to BFGMiner immediately, or upgrade to Linux.

And count yourself lucky it wasn't a good horror movie. I bricked a whole stack of S4's binge-watching the Saw movies that way!

notbatman

legendary

Activity: 2212

Merit: 1038

FYI

While streaming Invasion of the Body Snatchers (1978) I had CGMiner 4.9.1 close & exit twice while mining at solo.ckpool.org, I switched pools to bitcoind running locally and it's been going without exiting for about 30 mins now. I'm running the Windows build of CGMiner and it had been running for about 24 hours and only started crashing while watching the movie.

I haven't seen this behavior before, I just upgraded the miner to CGMiner from BFGMiner yesterday.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: lowbander80 on March 03, 2015, 07:27:37 AM

also pool must have restarted yesterday

Pool stats reported here:
http://solo.ckpool.org/pool/

Recent snapshot:

Code:

{"runtime": 2023818, "lastupdate": 1425386722, "Users": 167, "Workers": 389, "Idle": 146, "Disconnected": 17}

i.e. it's been up for over 3 weeks based on that runtime continuously so no restart. Next scheduled downtime is in 5 days as mentioned earlier for VPS provider security upgrades.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: lowbander80 on March 03, 2015, 07:27:37 AM

rented yesterday some 150 ths for 90mins without any luck... also pool must have restarted yesterday
I have read people doing it all the time but dont know what are the chances...for limited time and high hash...

This will give you the average expected time to find a current block:
http://tradebtc.net/bitcalc.php
Just can enter your hash rate as the pool.
So ... if your average expected time to find a block is 100hrs and you mine for 10hrs then ... you do the math Cheesy

lowbander80

legendary

Activity: 1036

Merit: 1000

rented yesterday some 150 ths for 90mins without any luck... also pool must have restarted yesterday
I have read people doing it all the time but dont know what are the chances...for limited time and high hash...

darkasleep

newbie

Activity: 1

Merit: 0

pointed 2 antminer s5 to your pool : ) hope i get lucky
thanks for this great pool im quite new and to inexperienced to start my own ^^.

Mikestang

legendary

Activity: 1274

Merit: 1000

Quote from: -ck on March 02, 2015, 04:14:27 AM

Quote from: Mikestang on March 02, 2015, 02:03:15 AM

Now to figure out why my U3 is a ZOMBIE. It's always something...

Oh that one's easy to answer. Because the U3 is a steaming pile of shit. Keep downclocking/downvolting it till it's stable for at least 24 hours. Then unplug everything and restart it daily.

I had it stable for a week stock voltage/freq with the factory power supply, then got a new 850watt psu to use with the S1 and hooked the U3 to it as well. Messed around with overclocking, went as high as 800v/250freq, it ran stable for several hours, then ZOMBIE. Full reset it and everything else, re-zadig, and running stock volt/freq again, was stable overnight. Seems to only be stable at stock settings unfortunately. I see about 42-50gh out of it, was getting 60gh oc'd.

Quote from: Kexkey on March 02, 2015, 07:45:21 AM

Quote from: Mikestang on March 01, 2015, 07:44:41 PM

Hmm, that's concerning. Why would my wallet generate an address that's no good? I'll try the S1 with the same address my U3 is using, I know that one works.

I'd like to know what tool you used to generate invalid addresses? Did you copy-paste them or manually retyped them?

Thanks!

I used Bitcoin Wallet on my android phone, had it send the address directly to my email account, and I copy/pasted it from there. Not sure where I lost a digit in that process, but I'll assume it must be user error because I've used that walled to generate keys several times and not had an issue before.

Kexkey

full member

Activity: 237

Merit: 100

Smile while thinking.

Quote from: Mikestang on March 01, 2015, 07:44:41 PM

Hmm, that's concerning. Why would my wallet generate an address that's no good? I'll try the S1 with the same address my U3 is using, I know that one works.

I'd like to know what tool you used to generate invalid addresses? Did you copy-paste them or manually retyped them?

Thanks!

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: Mikestang on March 02, 2015, 02:03:15 AM

Now to figure out why my U3 is a ZOMBIE. It's always something...

Oh that one's easy to answer. Because the U3 is a steaming pile of shit. Keep downclocking/downvolting it till it's stable for at least 24 hours. Then unplug everything and restart it daily.

Mikestang

legendary

Activity: 1274

Merit: 1000

Well I'll toss that address out. I generated another one and verified it was valid, thanks for the heads ups.

Figured out the rest of my issue, was a dns problem. Working on the pool successfully now, thank you.

Now to figure out why my U3 is a ZOMBIE. It's always something...

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Code:

# ./bitcoin-cli validateaddress 1Mse8cAQAshfunhwY7msQdsoTayuuuFp
{
    "isvalid" : false
}

philipma1957

legendary

Activity: 4354

Merit: 9201

'The right to privacy matters'

Quote from: Mikestang on March 01, 2015, 07:44:41 PM

Quote from: philipma1957 on March 01, 2015, 07:04:20 PM

yeah I typed that address into the blockchain I got bad address

https://blockchain.info/search/1Mse8cAQAshfunhwY7msQdsoTayuuuFp

Hmm, that's concerning. Why would my wallet generate an address that's no good? I'll try the S1 with the same address my U3 is using, I know that one works.

double and triple check the typing. I am pretty sure I copied you exactly.

So if you are correct and I am correct. Then your wallet is wrong or blockchain info is wrong.

Mikestang

legendary

Activity: 1274

Merit: 1000

Quote from: philipma1957 on March 01, 2015, 07:04:20 PM

yeah I typed that address into the blockchain I got bad address

https://blockchain.info/search/1Mse8cAQAshfunhwY7msQdsoTayuuuFp

Hmm, that's concerning. Why would my wallet generate an address that's no good? I'll try the S1 with the same address my U3 is using, I know that one works.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

I've received notice that the server will be receiving a critical security update which will involve rebooting it so there will be some pool downtime, hopefully only a few minutes so I'm giving you all advance notice that it will be occurring at approximately: 2015-03-08 4:00:00 AM UTC. I'll be using that as an opportunity to update to the latest stable ckpool code since it has been showing good stability of late.

philipma1957

legendary

Activity: 4354

Merit: 9201

'The right to privacy matters'

Quote from: Mikestang on March 01, 2015, 06:38:26 PM

I generated a new address and used that for the worker input. I tried removing the 'stratum+tcp://' from the pool input and leaving it there. I rebooted the S1 after each change to be sure it took. The pool shows as dead no matter.

The machine is still mining on one of the default pools which I have set as the back-up, so I am confident that it is generally configured correctly. Any other ideas?

yeah I typed that address into the blockchain I got bad address

https://blockchain.info/search/1Mse8cAQAshfunhwY7msQdsoTayuuuFp

Mikestang

legendary

Activity: 1274

Merit: 1000

I generated a new address and used that for the worker input. I tried removing the 'stratum+tcp://' from the pool input and leaving it there. I rebooted the S1 after each change to be sure it took. The pool shows as dead no matter.

The machine is still mining on one of the default pools which I have set as the back-up, so I am confident that it is generally configured correctly. Any other ideas?

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: Mikestang on March 01, 2015, 05:07:25 AM

Picked up an S1, did a factory reset, and then flashed the latest firmware. Trying to point it at the pool but it's not quite happening. It was mining 170gh on the default pools the firmware update comes with so I know the unit works and is set up correctly, but I seem to be missing something in my configuration. Thanks for the help.

If you can't mine here, check your username is actually a valid BTC address.

hedgy73

legendary

Activity: 1414

Merit: 1077

Quote from: Mikestang on March 01, 2015, 05:07:25 AM

Picked up an S1, did a factory reset, and then flashed the latest firmware. Trying to point it at the pool but it's not quite happening. It was mining 170gh on the default pools the firmware update comes with so I know the unit works and is set up correctly, but I seem to be missing something in my configuration. Thanks for the help.

Try it without the stratum+tcp:// at the front so just use solo.ckpool.org:3333 and see if that works.

Mikestang

legendary

Activity: 1274

Merit: 1000

Picked up an S1, did a factory reset, and then flashed the latest firmware. Trying to point it at the pool but it's not quite happening. It was mining 170gh on the default pools the firmware update comes with so I know the unit works and is set up correctly, but I seem to be missing something in my configuration. Thanks for the help.

Topic: [∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved! - page 425. (Read 1514880 times)