[20 gh] NMCBit pool 3% fee prop 6.6% PPS

[DavinciJ15]

Hi everyone sorry for the delayed down time was packing and could not keep an eye on my miners anyhow got it resolved there was a bug in my stored procedure that updates the counts and it ended up taking a long time because the cron job failed and it fell behind long enough for the bug to show up.

I am having serious problems with crontab it keeps messing up and calling the job over and over again every once and a while this caused the problem but showed me another bug.  Any one know why the crontab would screw up like this from time to time?  I can't use it to reset pushpool right now cuz it does the same thing when I set it to reset pushpool every 8 hours it works for a day or two and then starts resetting pushpool ever second.  Only when I edit the crontab remove the job and add it back in does everything go back to normal.

If the system goes down and you don't mind you can call my cell at 416-275-3557.

[DutchBrat]

I keep getting these RPC problems

2011-08-28 05:30:59: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 05:30:59, Problems communicating with bitcoin RPC 0 2
2011-08-28 05:41:09: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 05:41:09, Problems communicating with bitcoin RPC 0 2
2011-08-28 05:47:38: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 05:47:38, Problems communicating with bitcoin RPC 0 2
2011-08-28 05:54:59: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 05:54:59, Problems communicating with bitcoin RPC 0 2
2011-08-28 05:59:36: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 05:59:36, Problems communicating with bitcoin RPC 0 2
2011-08-28 06:00:37: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 06:00:37, Problems communicating with bitcoin RPC 0 2
2011-08-28 06:05:16: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 06:05:16, Problems communicating with bitcoin RPC 0 2
2011-08-28 06:15:27: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 06:15:27, Problems communicating with bitcoin RPC 0 2
2011-08-28 06:17:20: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 06:17:20, Problems communicating with bitcoin RPC 0 2
2011-08-28 06:19:13: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 06:19:13, Problems communicating with bitcoin RPC 0 2
2011-08-28 06:22:57: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 06:22:57, Problems communicating with bitcoin RPC 0 2
2011-08-28 06:23:54: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 06:23:54, Problems communicating with bitcoin RPC 0 2
2011-08-28 06:24:51: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 06:24:51, Problems communicating with bitcoin RPC 0 2

Miners do connect again, but still, something on my end or do other people have these issues as well ?

Brat

[DavinciJ15]

I keep getting these RPC problems

2011-08-28 05:30:59: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 05:30:59, Problems communicating with bitcoin RPC 0 2
2011-08-28 05:41:09: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 05:41:09, Problems communicating with bitcoin RPC 0 2
2011-08-28 05:47:38: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 05:47:38, Problems communicating with bitcoin RPC 0 2
2011-08-28 05:54:59: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 05:54:59, Problems communicating with bitcoin RPC 0 2
2011-08-28 05:59:36: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 05:59:36, Problems communicating with bitcoin RPC 0 2
2011-08-28 06:00:37: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 06:00:37, Problems communicating with bitcoin RPC 0 2
2011-08-28 06:05:16: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 06:05:16, Problems communicating with bitcoin RPC 0 2
2011-08-28 06:15:27: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 06:15:27, Problems communicating with bitcoin RPC 0 2
2011-08-28 06:17:20: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 06:17:20, Problems communicating with bitcoin RPC 0 2
2011-08-28 06:19:13: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 06:19:13, Problems communicating with bitcoin RPC 0 2
2011-08-28 06:22:57: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 06:22:57, Problems communicating with bitcoin RPC 0 2
2011-08-28 06:23:54: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 06:23:54, Problems communicating with bitcoin RPC 0 2
2011-08-28 06:24:51: Listener for "HennyNMC": nmcbit.com:8332 28/08/2011 06:24:51, Problems communicating with bitcoin RPC 0 2

Miners do connect again, but still, something on my end or do other people have these issues as well ?

Brat

I have not seen anything like this has anyone else?

I need to enable ping to check latency.

[DavinciJ15]

WOW my pool luck has sucked for so long and it still does at 27 Gh.
Ok so in the last 12 hours only 6 blocks where found but but in the last round, 19 blocks where found before we found one.
I hope this is not another issue since moving to Amazon.  I'll try moving namcoind to it's own server with more memory on Tuseday if my bad luck continues.

Davinci.

[John Tobey]

I have not seen anything like this has anyone else?

My miners are hosted, I don't have access to their logs.  But I am seeing less than half the expected hash rate (3.25G) and a good deal of traffic to my failover pool.

[DavinciJ15]

I have not seen anything like this has anyone else?

My miners are hosted, I don't have access to their logs.  But I am seeing less than half the expected hash rate (3.25G) and a good deal of traffic to my failover pool.

Can you give me any kind of details? Settings miner software etc?

[DutchBrat]

Davinci,

I am using GUI-Miner:

2011-08-28 08:19:21: Running command: poclbm.exe --user=xxx@xxx.com_Meyer --pass=xxx -o nmcbit.com -p 8332 --device=0 --platform=0 --verbose -v -w128 BFI_INIT FASTLOOP=false AGGRESSION=9 -- backup=http://xxx@xxx.com_Meyer:xxx@pit.deepbit.net:8332 --failback=10000
2011-08-28 08:19:21: Listener for "HennyNMC" started
2011-08-28 08:19:22: Listener for "HennyNMC": 28/08/2011 08:19:22, Setting pool xxx@xxx.com_Meyer @ nmcbit.com:8332
2011-08-28 08:19:23: Listener for "HennyNMC": 28/08/2011 08:19:23, Using new LP URL /LP
2011-08-28 08:19:23: Listener for "HennyNMC": 28/08/2011 08:19:23, LP connected to nmcbit.com:8332
2011-08-28 08:24:00: Listener for "HennyNMC": 28/08/2011 08:24:00, Problems communicating with bitcoin RPC 0 2
2011-08-28 08:26:48: Listener for "HennyNMC": 28/08/2011 08:26:48, Problems communicating with bitcoin RPC 0 2

Haven't had this before until this weekend

Brat

[macbook-air]

[Update]Reward doubled!

Mine with 5 GHashs from Saturday end of day Monday UTC for ever 24 hours you mine with 5 + GHashs you will receive  8 BTC and you can keep the namecoins on top!!!

NO LIMITS! 5+ GHash per account will get 8 BTC.  If you give me 12 Hhrs on saturday then 12 hours on monday that gets you 8 BTC if you hash with 5+ GHashs over 48hrs that's 16 BTC!!!

Everyone will get paid on Tuesday and you must agree to post on my topic here:
https://bitcointalk.org/index.php?topic=33612.0
That you got paid.

I am doing this promo to tests the system load and because I am moving I will be taking down my miners so I don't want my stats to go so low.

Thanks for you help!  Look forward to paying out lots of BTC.  

Although I don't understand what you are talking about, 5+ Ghash/s is yours for the next 24 hours.

[DutchBrat]

Davinci,

We found a block and we're disconnected again, could it be Crontab

Anyway, mining in my backup pool 

Brat

[DutchBrat]

Here we go again,

i assume we found a block since our total shares turned negative and all my miners are failing to the backup-pool since they can't connect anymore

Database problem again me thinks 

At least if it's the same bug over and over Davinci will know what to do after his move

Good Luck !

Brat

[DavinciJ15]

Here we go again,

i assume we found a block since our total shares turned negative and all my miners are failing to the backup-pool since they can't connect anymore

Database problem again me thinks 

At least if it's the same bug over and over Davinci will know what to do after his move

Good Luck !

Brat

Yeah there must be another DB bug as soon as you find a block it slows down the MySQL but not as bad as the last time.  The last time it would of taken hours to update the DB right not it took 5 minutes but that's not acceptable.

[DavinciJ15]

Hi Everyone.

Thanks for all you hashs I am working hard right now in my new house trying to fix all the problems I've observed from the past 24 hours.   We have had several outages and many bugs show up this is what I need to do in order to create a solid pool.  Thanks everyone it is bitcoins well spent. 


BTW
Right now my back is killing me, I'm surrounded by boxes but I am going to work on nmcbit.com for most of the night and all day everyday for rest of the week.  My wife will be pissed.     Oh well.

[DutchBrat]

Hey Davinci,

Just my 2 cents worth: could it be that MySQL locks-up during the rounds as well ? I am still experiencing lots and lots of RPC communication errors, across all my miners which causes a high % of stales

I can see that I am not the only one since we are running a total stale % of close to 8%

First I thought that was caused by the database problems at the beginning of each new round, but it seems the problems remain during the entire round

Mind you, I have no knowledge of pushpool or the database, so I might be way off

Brat

[DutchBrat]

Davinci,

Sorry for being the bearer of bad news again, but that's why I love testing:
It's  not allowed to shoot the messenger 

Having LongPolling problems now

2011-08-29 14:04:34: Listener for "HennyNMC" started
2011-08-29 14:04:34: Listener for "HennyNMC": 29/08/2011 14:04:34, Setting pool xxx@xxx.com_Meyer @ nmcbit.com:8332
2011-08-29 14:04:35: Listener for "HennyNMC": 29/08/2011 14:04:35, Using new LP URL /LP
2011-08-29 14:04:35: Listener for "HennyNMC": 29/08/2011 14:04:35, LP connected to nmcbit.com:8332
2011-08-29 14:05:09: Listener for "HennyNMC": 29/08/2011 14:05:09, long poll exception:
2011-08-29 14:05:10: Listener for "HennyNMC": 29/08/2011 14:05:10, Using new LP URL /LP
2011-08-29 14:05:10: Listener for "HennyNMC": 29/08/2011 14:05:10, LP connected to nmcbit.com:8332
2011-08-29 14:05:11: Listener for "HennyNMC": 29/08/2011 14:05:11, long poll exception:
2011-08-29 14:05:12: Listener for "HennyNMC": 29/08/2011 14:05:12, Using new LP URL /LP
2011-08-29 14:05:12: Listener for "HennyNMC": 29/08/2011 14:05:12, LP connected to nmcbit.com:8332
2011-08-29 14:05:13: Listener for "HennyNMC": 29/08/2011 14:05:13, long poll exception:
2011-08-29 14:05:14: Listener for "HennyNMC": 29/08/2011 14:05:14, Using new LP URL /LP
2011-08-29 14:05:14: Listener for "HennyNMC": 29/08/2011 14:05:14, LP connected to nmcbit.com:8332
2011-08-29 14:05:15: Listener for "HennyNMC": 29/08/2011 14:05:15, long poll exception:
2011-08-29 14:05:16: Listener for "HennyNMC": 29/08/2011 14:05:16, Using new LP URL /LP
2011-08-29 14:05:16: Listener for "HennyNMC": 29/08/2011 14:05:16, LP connected to nmcbit.com:8332
2011-08-29 14:05:18: Listener for "HennyNMC": 29/08/2011 14:05:18, long poll exception:
2011-08-29 14:05:19: Listener for "HennyNMC": 29/08/2011 14:05:19, Using new LP URL /LP
2011-08-29 14:05:19: Listener for "HennyNMC": 29/08/2011 14:05:19, LP connected to nmcbit.com:8332
2011-08-29 14:05:31: Listener for "HennyNMC": 29/08/2011 14:05:31, Problems communicating with bitcoin RPC 0 2

Still using GUI miner with t he same settings

Brat

[DavinciJ15]

Davinci,

Sorry for being the bearer of bad news again, but that's why I love testing:
It's  not allowed to shoot the messenger 

Having LongPolling problems now

2011-08-29 14:04:34: Listener for "HennyNMC" started
2011-08-29 14:04:34: Listener for "HennyNMC": 29/08/2011 14:04:34, Setting pool xxx@xxx.com_Meyer @ nmcbit.com:8332
2011-08-29 14:04:35: Listener for "HennyNMC": 29/08/2011 14:04:35, Using new LP URL /LP
2011-08-29 14:04:35: Listener for "HennyNMC": 29/08/2011 14:04:35, LP connected to nmcbit.com:8332
2011-08-29 14:05:09: Listener for "HennyNMC": 29/08/2011 14:05:09, long poll exception:
2011-08-29 14:05:10: Listener for "HennyNMC": 29/08/2011 14:05:10, Using new LP URL /LP
2011-08-29 14:05:10: Listener for "HennyNMC": 29/08/2011 14:05:10, LP connected to nmcbit.com:8332
2011-08-29 14:05:11: Listener for "HennyNMC": 29/08/2011 14:05:11, long poll exception:
2011-08-29 14:05:12: Listener for "HennyNMC": 29/08/2011 14:05:12, Using new LP URL /LP
2011-08-29 14:05:12: Listener for "HennyNMC": 29/08/2011 14:05:12, LP connected to nmcbit.com:8332
2011-08-29 14:05:13: Listener for "HennyNMC": 29/08/2011 14:05:13, long poll exception:
2011-08-29 14:05:14: Listener for "HennyNMC": 29/08/2011 14:05:14, Using new LP URL /LP
2011-08-29 14:05:14: Listener for "HennyNMC": 29/08/2011 14:05:14, LP connected to nmcbit.com:8332
2011-08-29 14:05:15: Listener for "HennyNMC": 29/08/2011 14:05:15, long poll exception:
2011-08-29 14:05:16: Listener for "HennyNMC": 29/08/2011 14:05:16, Using new LP URL /LP
2011-08-29 14:05:16: Listener for "HennyNMC": 29/08/2011 14:05:16, LP connected to nmcbit.com:8332
2011-08-29 14:05:18: Listener for "HennyNMC": 29/08/2011 14:05:18, long poll exception:
2011-08-29 14:05:19: Listener for "HennyNMC": 29/08/2011 14:05:19, Using new LP URL /LP
2011-08-29 14:05:19: Listener for "HennyNMC": 29/08/2011 14:05:19, LP connected to nmcbit.com:8332
2011-08-29 14:05:31: Listener for "HennyNMC": 29/08/2011 14:05:31, Problems communicating with bitcoin RPC 0 2

Still using GUI miner with t he same settings

Brat

thanks Brat Im getting them as well Im working on it.  to many fires to put out making it difficult to focus on just one as each has the potential to burn the house down.
most of the time i try contain the fire but not put it out like the LP problem grows until it shuts the system down. the next big fire is the db update, another is the openssl using up 100% cpu to build keys.


thanks for helping and giving me feedback.

[DutchBrat]

No Problem Davinci, as always: Thanks for your hardwork

It's fun to be in on this from the beginning

That being said: More bad news

Looks like all my miners have lost connection at the same time now (9 miners hasing at a total 273 MH rate indicates something is wrong)

Sorry to have to be the one to tell you

Brat

[DavinciJ15]

No Problem Davinci, as always: Thanks for your hardwork

It's fun to be in on this from the beginning

That being said: More bad news

Looks like all my miners have lost connection at the same time now (9 miners hasing at a total 273 MH rate indicates something is wrong)

Sorry to have to be the one to tell you

Brat

Yeah with the block found the DB is gone nuts trying to update the tables don't know why yet as I am trying to contain other fires ah well I will get it all fixed by the 5th one way or another.

Davinci

[Transisto]

[30/08/2011 02:10:37] Result: 26458332 accepted
[30/08/2011 02:10:43] Warning: work queue empty, miner is idle
[30/08/2011 02:10:45] Result: 0bdb0062 accepted
[30/08/2011 02:11:00] Warning: work queue empty, miner is idle
[30/08/2011 02:11:01] Result: 83c8e921 accepted

lots of trouble connecting lately

[DavinciJ15]

[30/08/2011 02:10:37] Result: 26458332 accepted
[30/08/2011 02:10:43] Warning: work queue empty, miner is idle
[30/08/2011 02:10:45] Result: 0bdb0062 accepted
[30/08/2011 02:11:00] Warning: work queue empty, miner is idle
[30/08/2011 02:11:01] Result: 83c8e921 accepted

lots of trouble connecting lately

Another new bug when 2 block are found right after each other the DB goes crazy.

I would shut it down but there is no point I will let it run until it sets all the values.  Then see if its correct and fix that bug if the values are not correct.  Oh well no one said programming is easy.
I feel a bit embarrassed as I thought I had it all working fine. 

[bcpokey]

I apologize that I had been running my clients with GUIMiner rather than a console client, so I couldn't really keep track of warning messages. My stales were fairly low throughout though, I just got a lot of random inability to connecto. Possibly the database overloaded or something, because I could usually access the website (but it was slow) even when my miners were all dropped off. Just from the temperature of my mining room I could tell that it was a systemic problem though, the temperature was significantly cooler than usual, suggesting that the cards were idling up and down a lot.

If there is another round I'll run a console version next time to give more detailed feedback.


In the meantime, thought it would be prudent to point out that Davinci did indeed pay out for my/our time as he promised, his good word continues to hold merit