Will try that out again and see if I can get it to give me something other than internal server error 500 which is what I usually get.....is there a way I can check my tables for something missing maybe? I imported the .sql file included in the download with no errors. Was there any additional steps I needed to take maybe in creating any extra tables possibly?
Thanks again Mike! You can expect a donation for sure! Awseome stuff!
Peace!
There shouldn't be anything I missed in the v2 sql. That admin page loves to give errors though.... Since I usually change things in sql, sometimes little admin things slip through. |
|
|
|
Thanks everyone for your hashes!!!! I'm thinking of adding some incentive giveaways once the pool moves to a percentage  Also, once the pool moves to 1%, I'll be removing tx fees on the next block. And.... I should be getting a few more miners online myself (my daughter want's a linux box, how convenient). |
|
|
|
Hey Mike, found a bit of a nasty one...at least from a stats perspective and could maybe even cause some mayhem with payouts: ------------------------------------------------------------------------ r18 | annihilat | 2011-07-04 22:54:36 +0200 (Mon, 04 Jul 2011) | 3 lines Changed paths: M /trunk/www/accountdetails.php - make sure the user cannot set a lower than 0% donation fee ------------------------------------------------------------------------ You might want to check into that.  Ive fixed it simply by adding a less than 0 check and forcing it to 0 if true. see below: if($act == "updateDetails"){
//Update user's details
$newSendAddress = mysql_real_escape_string($_POST["paymentAddress"]);
$newDonatePercent = mysql_real_escape_string($_POST["donatePercent"]);
$newPayoutThreshold = mysql_real_escape_string($_POST["payoutThreshold"]);
if ($newPayoutThreshold > 25)
$newPayoutThreshold = 25;
if ($newPayoutThreshold < 1)
$newPayoutThreshold = 0;
if ($newDonatePercent < 0)
$newDonatePercent = 0;
Thanks, it's in the experimental branch now |
|
|
|
Thanks! Got the clients to connect succesfully! Do you have an example of about how long or in how many minutes I should run each cronjob file? I know in the thread it states from 10 to 30 minutes but how about the workers.php one for example? I like the stats to update frequently but I do not want to create to much or uneeded database traffic either...
Thanks again for all your help!
Anyone else having issues accessing the admin page? I have my account flag set to 1 in the database? Cant seem to figure that one out.
Peace!
The key to the cron jobs is to space them out enough that it doesn't keep mysql bogged down. I've tried to space them out into separate files to help, but really I kept a watch on 'top' to try and keep the cpu/mem usage down. as for the admin page not working, it could be a missing setting row in the settings table. turn errors on for a second and see if you can get an idea of the issue. The 225 errors, never seen them, I'd check file owner/permissions. |
|
|
|
Have you noticed that ozco.in looks exactly the same.
Yep, and about 20 others. I opensourced the frontend. |
|
|
|
I like the new look/options! Lots of new useful information! I'm coming back in a few days, when I get my miners set up at the new house, and have the net transferred! I'll have the perfect server room, with a ton of ventilation, built in shelving, and a dedicated A/C unit for the room, which will be ducted to each shelf of mobos!  It was a recording studio, so it's sound proof too!  I'm envious. I have to keep my miners spread around the house just to keep the temperature from fluctuating too much. |
|
|
|
|
Just a heads up.... Once I implement the 1% bonus fee, I'm also removing transaction fees.
|
|
|
|
Hi mike, version 1 of my fork released: MMCFE SVN - http://mmcfe.mfis.net (Mainframe Mining Cooperative Front End) Maybe you can update the original post with correct link and name of project? Anni Done! Too bad it's not a Git Fork.... it'd be too easy to move code back and forth. I'll peek around soon and see what to bring back from your fork. Also: going to be adding bitcoin account locking, and email notifications. |
|
|
|
|
There we go, 3Gh! Now let's get some blocks solved!
|
|
|
|
|
Hey, since my pools info is lacking...
1% proportional (is 0% but moving to 1%).
tx fees are btc client minimum (currently .01, but .005 once client allows)
Full web UI (a lot of other pools are based on my UI)
Auto Payout threshhold (1-25)
Instant Payout of confirmed
Currently 120 confirms for payout
Full control of workers, many available per username.
username is not based on email
No idle email yet, currently only JSON/Web/Android/Browser monitoring
SSL supported
IPv6 should be supported
Account changes require additional PIN
No preset support
Also have Chrome browser extension monitor
Thanks for putting up the chart.
|
|
|
|
If it's any consolation. My pool software was based off of Xenland's v1 setup. It is being used by several of the top10 pools now Several of them in the 50+Ghash range. While it's not the same, it wouldn't have become what it is without his initial base. |
|
|
|
did that already.....got nothing. I dont get it...the file is there...the path is correct.
I also cant seem to get clients to connect .....is there anything else that needs to be done with the database to get clients to connect? Maybe you could clear up the pool workers username and password...what is with the "." ? When you setup rpc should you include the "."?
Example if my website username is bean and I want to create a pool worker called pea, why do I end up with a worker called "bean.pea"? And how should I set up my RPC config file to connect? With a username of bean.pea or just pea?
The way it is, is confusing.....please help
The workers contain "." so that worker logins are based on simplecoin usernames. This keep people from fighting over worker names and having to guess one that's not already taken. the rpc user/pass only relates to bitcoin.conf, pushpool.conf, & requiredFunctions, not a simplecoin user. just pick a name/pass and make it match in all 3 places. |
|
|
|
|
Nice!
Long time vaper here.. The Ego & Ego-T are by far my favorite right now. Any chance of larger eLiquid bottles, 10ml would barely last me a week.
Also, has the Dekang RY4 gotten any closer to the original flavor? My last bottle tasted like burnt peanuts.
|
|
|
|
Pool is holding solid, looks like all we need now is more hashes! |
|
|
|
Thanks, got everything up and running. Only problem is when I try and access the admin page I get a 500 error...I have set the flag to 1 in the database ....any idea why I get this error only when trying to access the admin panel?
Thanks!
your best bet is to turn on display_errors in php.ini |
|
|
|
I have a new version out at: http://davids.webmaster.com/~davids/bitcoin-3diff.txtIt has the turbo RPC changes, the new hub mode to reduce stale/lost blocks, and native long polling support. Please read the documentation at the top of the file. CAUTION: This code was just finished and has not been well-tested. Test results are appreciated. Bug reports and success reports are equally welcome. Update: Version 0.4 is now up. It fixes a bug that could cause bitcoind to hang when directed to shutdown. Currently testing v0.5 on live server.... (a whopping 3 users since relaunch). Will let you know how it turns out. So far so good. LP notifications seem faster than a certain unnamed big pool Also it seems to favor my pool during new getwork causing my pool to get a higher share of hashrates than said big pool when using hashkill. |
|
|
|
|
Just added JoelKatz full bitcoind & longpolling mods. Should be snappier and have less stale shares!!!
Some miners may need to reconnect.
|
|
|
|
The pool stats have a nice style now...good work.
Thanks! That came from the ozco.in fork, so I can't take too much credit Also, estimates are now in the api results. |
|
|
|
|
pushpool v5, bitcoin v0.3.23 (or if you are comfortable compiling add the multi-thread diff from the 20btc bounty project page)
|
|
|
|
|
oops, server load stat was was 100x too high, thanks jine for pointing that out.
|
|
|
|
|
Show Posts
