[ANN][LTC][Pool][PPLNS][STRATUM] - ltc.kattare.com - burnside's Mining Pool

[burnside]

To reduce the requests into pushpoold I have bumped up the rpc.target.bits to 22.  This means that you will have to do twice as much computing in-between submitting shares.

Everything else stays equal.  Payouts per hashrate, solved block rates, etc, will stay consistent.

Cheers.

[1714254846]

1714254846

[1714254846]

1714254846

[1714254846]

1714254846

[muqali]

To reduce the requests into pushpoold I have bumped up the rpc.target.bits to 22.  This means that you will have to do twice as much computing in-between submitting shares.

Everything else stays equal.  Payouts per hashrate, solved block rates, etc, will stay consistent.

Cheers.

Do we need to change anything on our end? Will the client and your end just auto figure it out?

[burnside]

To reduce the requests into pushpoold I have bumped up the rpc.target.bits to 22.  This means that you will have to do twice as much computing in-between submitting shares.

Everything else stays equal.  Payouts per hashrate, solved block rates, etc, will stay consistent.

Cheers.

Do we need to change anything on our end? Will the client and your end just auto figure it out?

Nothing to change on your end.  Most clients will just figure it out.  If they don't a restart will fix it.

Cheers.

[muqali]

Are we down?

[dickcheney]

Looks like we are, not able to connect on my end.

[tacotime]

Yup

[dickcheney]

Back Up for me, DDoS attack still ?

[burnside]

Yeah, I had to restart pushpool again.  I've worked out a script to test if it's up or down and will auto restart it.  It just starts spewing errors about being out of file handlers.  (which I have capped around 32000 using ulimit)  So I'm testing if the connection count is above 1500 or below 10 and restarting if it's outside that.

Hopefully that'll improve reliability!

Cheers.

[axilla]

tried to connect to your pool, but getting

Oct 26 20:56:26 localhost cpuminer[15224]: HTTP request failed: The requested URL returned error: 403

[burnside]

tried to connect to your pool, but getting

Oct 26 20:56:26 localhost cpuminer[15224]: HTTP request failed: The requested URL returned error: 403

Can you post your cpuminer config file and/or command line args?  I'm guessing you're using port 80 or 443 instead of 9332.

Also, see: http://ltc.kattare.com/gettingstarted.php

I know it works with cpuminer 2.2.2 and up, that's the version I'm using on the pool. 

Cheers.

[KfrogCT]

tried to connect to your pool, but getting

Oct 26 20:56:26 localhost cpuminer[15224]: HTTP request failed: The requested URL returned error: 403

Same here today, connection dropped this morning and is still down.

[axilla]

tried to connect to your pool, but getting

Oct 26 20:56:26 localhost cpuminer[15224]: HTTP request failed: The requested URL returned error: 403

Can you post your cpuminer config file and/or command line args?  I'm guessing you're using port 80 or 443 instead of 9332.

Also, see: http://ltc.kattare.com/gettingstarted.php

I know it works with cpuminer 2.2.2 and up, that's the version I'm using on the pool.  

Cheers.

I figured it out, i had to install libidn and curl via macports and add some stuff to my .profile

however it went down this morning

[burnside]

It definitely went down this morning for several hours.  Then again this evening.  My restart script isn't catching it... I need to find another way of detecting when it's been attacked.

[powersync]

Hashrate: 436.78 kH/s   Workers: 1   Round Shares: 504 (1.4% stale)   Estimate: Ł0.41562211

Why is it taking forever to mine on here shares etc seems really ubba slow compared to others tested and rating 3 out of 10

Even tho this is a test for 3 to 4 hours this is no where near cutting it and giving good results.

I know my hash is not the best in the world but other places within 3 to 4 hours would of mined around 60k shares

Any advise on why its so low on here.

Also within posting this post my earnings and estimate are dropping and not increasing.

Estimate: Ł0.41562211 before making this post
Estimate: Ł0.40337119 in between making post
Estimate: Ł0.40663006 Round Shares: 551
Estimate: Ł0.40536190 Round Shares: 554 (1.3% stale)
Estimate: Ł0.40433025 Round Shares: 558 (1.3% stale)
Estimate: Ł0.40131831 Round Shares: 565 (1.2% stale)   

How the £$%^^& is that meant to work out more shares for the round and am actually earning less this does not quite work out
   

Looks like am done here testing over until admins respond to why and whats going on with pool

LOL wow epic

[tacotime]

round share difficulty is higher and dynamic.  as network difficulty increases so does round share difficulty with this pool.  this decreases traffic for you and the server.

the amount i've received in payouts is equal to the number of blocks i've solved, so i can verifying the pool works and i've been mining on it for over a month.

i would come back to this pool because with pplns you will not get rewards unless you keep mining within the pool for extended periods of time.

[powersync]

round share difficulty is higher and dynamic.  as network difficulty increases so does round share difficulty with this pool.  this decreases traffic for you and the server.

the amount i've received in payouts is equal to the number of blocks i've solved, so i can verifying the pool works and i've been mining on it for over a month.

yeah but it should be this slow on a network difficulty of what it currently is BTC mines faster than this so does others so am a out of this pool unless things speed up in producing work etc.

You should read up on Pay Per Last N Shares pool.  They are setup to make pool hopping unprofitable.  4 hours isn't long enough.  I have mined on this pool for about a month and I can assure you the payout is legit.  I moved only because of the ddos attacks, but they are going most any pool now.

PS

[Nicksasa]

round share difficulty is higher and dynamic.  as network difficulty increases so does round share difficulty with this pool.  this decreases traffic for you and the server.

the amount i've received in payouts is equal to the number of blocks i've solved, so i can verifying the pool works and i've been mining on it for over a month.

yeah but it should be this slow on a network difficulty of what it currently is BTC mines faster than this so does others so am a out of this pool unless things speed up in producing work etc.

You should read up on Pay Per Last N Shares pool.  They are setup to make pool hopping unprofitable.  4 hours isn't long enough.  I have mined on this pool for about a month and I can assure you the payout is legit.  I moved only because of the ddos attacks, but they are going most any pool now.

PS

Not saying i am hopping around but at the rates am earning on it is not worth it and the actual est the more i mine the less i see

If you want your earnings asap ... go with PPS then.

[tacotime]

Not saying i am hopping around but at the rates am earning on it is not worth it and the actual est the more i mine the less i see

I know, it's just awful paying that 0% fee 

[rapeghost]

can we PLEASE have a second port?

[burnside]

can we PLEASE have a second port?

Hey,

Minor issues connecting to the pool some times.

I was wondering if you could open up another port on pushpoold? Any port is fine.

The public IP is xxx , I'm getting '502 Gateway' errors, is this your DoS filter ? I didn't mean to piss it off :<

Posted a related PM for context.

Pushpool is getting restarted at regular intervals now, and each restart a bunch of miners get 502's during the time between when the previous one shuts down and the new one starts up.

Tailing the logs in fact, all the 502's I see correspond with the last restart.   

I've load balanced two pushpools now behind nginx and setup cron to restart them alternately.  There will still be a few 502's, but there should be far less.  (one or two until nginx realizes it's down and redirects the traffic.)

Cheers.