[~1000 GH/sec] BTC Guild - 0% Fee Pool, LP, SSL, Full Precision, and More - page 154.

Nythain

newbie

Activity: 56

Merit: 0

Quote from: MrGaSp on May 11, 2011, 02:22:43 AM

I am throwing my 420MH/s at it from deepbit..might stick with this. I do appreciate the donate option, seems to fit the rest of the bitcoin community.

to tell you the truth, i thought of doing 99% donation tonight...idk yet though.. =P

Edit: I also really love how 'reset' doesn't wreck your ever total, ty for that..

As a fairly small contributing member of the pool (mere 78Mh/s) I would personally like to say thanks for bringing more power over.

MrGaSp

sr. member

Activity: 418

Merit: 253

I am throwing my 420MH/s at it from deepbit..might stick with this. I do appreciate the donate option, seems to fit the rest of the bitcoin community.

to tell you the truth, i thought of doing 99% donation tonight...idk yet though.. =P

Edit: I also really love how 'reset' doesn't wreck your ever total, ty for that..

Nythain

newbie

Activity: 56

Merit: 0

~~Wow my stales have gone through the roof since that last brief downtime, and a whole loooooot of long poll exceptions.~~

Scratch that. Must have just been a temporary side effect of the short downtime. Been runnin good for a while now.

eleuthria

legendary

Activity: 1750

Merit: 1007

Thank you for the support all. It has been stable since the last crash (although it normally crashes about 1 minute after I say that).

It will go down for about 3 seconds shortly so that the auto-restart script can run during the night.

Worker rename and password resets are working in testing, but there's no nice way to fit them in the current page. Tomorrow morning I will be splitting workers into two pages. "My Account" will show the current worker stats table (with reset buttons). Then you will have a "Manage Workers" page which has the ability to add, hide, rename, reset, and change the passwords for your workers.

Nythain

newbie

Activity: 56

Merit: 0

I'm stickin with it. So far been stable since it came back up. Kinks are bound to happen, at least eleuthria tends to be on top of them. Also a fan of the very quick updates about whats going on. I do need to figure out how to set up guiminer to treat a second pool as a "fallover" in case of downtimes.

shat

newbie

Activity: 21

Merit: 0

I have faith in it. Buddy turned me on to it today at the office. I've been in slush's and solo for a while now. Let us know if we can help at all mate.

travex

member

Activity: 158

Merit: 10

I will join again when the pool is completely stable lol, down again.

shat

newbie

Activity: 21

Merit: 0

back to down Sad

shat

newbie

Activity: 21

Merit: 0

hopefully it isn't one of mine Sad

back up and running @ 600Mhps. Sent you an email btw. Check it tomorrow when you have some time. I'm off to sleep.

eleuthria

legendary

Activity: 1750

Merit: 1007

Looks like we still have one worker that has caused a crash every time they try to communicate with the server...they're causing something completely different from the others. Back to running a fully logged version to see what they're doing differently.

travex

member

Activity: 158

Merit: 10

Just joined with 1.5Gh/s and got comm error after 5 mins . Sad, back to BTCmine Sad

shat

newbie

Activity: 21

Merit: 0

Average makes sense. Started up working again for a bit and is now back to comm errors Sad

eleuthria

legendary

Activity: 1750

Merit: 1007

Quote from: error on May 10, 2011, 10:52:26 PM

Always assume your users are going to try to screw with you when dealing with their input.

Oh I know that one. Problem was I just finished setting up the password hashing on the website (PHP) when I added it to the pool (C). So my habits of PHP carried over. Worked fine with standard data, but C doesn't fail quite as softly when passed bad data as what PHP allows. The curse of higher level languages!

eleuthria

legendary

Activity: 1750

Merit: 1007

Quote from: shat on May 10, 2011, 10:46:05 PM

eleuthria:

Additionally, I am showing I am pushing out 624Mhash/s right now and your site is only showing me: 62.04 mH/sec on 1 worker and 81.13 mH/sec on the other.

Ideas?

The hash rate shown by the pool is your average hash rate over the past 15 minutes, and is calculated based on submitted shares in that window. It is only an ESTIMATE. Your luck on reporting getwork results will always cause some variance over what is shown by your client. Since you only recently started, the rate will be much lower until you've been running for 15 minutes.

error

hero member

Activity: 588

Merit: 500

Always assume your users are going to try to screw with you when dealing with their input.

eleuthria

legendary

Activity: 1750

Merit: 1007

The crash should now be fixed! All my time working in PHP/MySQL the past few years, I forgot some very basic memory management in good old C. The crash was caused when somebody forgot to send a password with their worker. Because I added a function to combine the password with the salt, and then hash it, I was trying to work in unallocated memory (the password was a NULL value).

Running in a debugger for the next hour and a half to make sure it got caught (I can only test it so many dozens of ways). If it looks stable again, the pool will be down for about 3 seconds in an hour when I switch it out of gdb and run it through the auto-restart script.

shat

newbie

Activity: 21

Merit: 0

eleuthria:

Additionally, I am showing I am pushing out 624Mhash/s right now and your site is only showing me: 62.04 mH/sec on 1 worker and 81.13 mH/sec on the other.

Ideas?

shat

newbie

Activity: 21

Merit: 0

I just attached one of my rigs to your pool, ~ 800Mhash/s and it ran fine for about 5 minutes and now I'm getting connection issues : Problems communicating with bitcoin RPC

eleuthria

legendary

Activity: 1750

Merit: 1007

The bug causing all these crashes has finally been identified. Pool will be resuming in approximately 10 minutes and should not be seeing any more crashes related to the problem.

eleuthria

legendary

Activity: 1750

Merit: 1007

A few of the new features were added to the website, but meanwhile the pool is getting crashed during a user authentication again. Just added a massive amount of debug lines (it's quite beautiful to see the spam of log strings) to pinpoint exactly where it crashes next time, because the backtrace wasn't being particularly useful.

Currently added:
Hide Workers (and Reveal)
Block Statistics include your share count, reward, and donation amount

Almost finished:
Worker password reset
Worker rename

Topic: [~1000 GH/sec] BTC Guild - 0% Fee Pool, LP, SSL, Full Precision, and More - page 154. (Read 379078 times)