mmcFE v2.1.23-stable - A Clean & Simple Pushpool frontend (PHP/BASH/JS/MYSQL)

[AnnihilaT]

ahh thats another interesting one i hadnt thought of...

yeah i have all kinds of plans but just not enough time to get it all done   since the admin panel is for the smallest amount of viewers its sort of the last thing im working on tho.  im very comfortable at the command line so its not the highest priority at the moment... i built in some viewing features and made the tables sortable so you can get a good overview of whats going on in the database and for now thats enough for me but for sure more will come.

Are you starting a pool?

[1713548400]

1713548400

[1713548400]

1713548400

[1713548400]

1713548400

[1713548400]

1713548400

[dlasher]

yeah i have all kinds of plans but just not enough time to get it all done  since the admin panel is for the smallest amount of viewers its sort of the last thing im working on tho.  im very comfortable at the command line so its not the highest priority at the moment... i built in some viewing features and made the tables sortable so you can get a good overview of whats going on in the database and for now thats enough for me but for sure more will come.

I appreciate all your hard work, after a little teething it seems to be up and alive.

As an admin, however, I'd like to see more detailed, "live" views on how "alive" the pool is at the moment.Things I may or may not want to expose to the other users, but things like most shares last (x) minutes per user, reject %'s, luck, etc... I have a little stack of queries I've been playing with, but PHP isn't my strength...  Right now the web interface is pretty "dead" in spite of all the activity going on underneath.

Maybe some of the "bitcoinD" things, like "getinfo" ?

Are you starting a pool?

Considering it, primarily private use, not trying to take on the big guys..

[dlasher]

one more problem found from having pushpoold up and running before mmcFE -- shares table is formatted differently....


Another interesting thing in the "shoot, that's broken" category... If your bitcoinD is NOT running on 8332, you're going to have problems.. Mine is running on 7332, and LOTS of pieces break on the web pages, as you can imagine.. Stats don't exist, the cronjobs all complain because they can't connect to bitcoinD. Even placing "x.x.x.x:7332" in the "rpcHost" field didn't fix it..

my fix?

update requiredFunctions.php to include an "$rpcPort" field:

$rpcType = "http";                              // http or https
$rpcUsername = "bigPHATuser";                             // username as specified in your bitcoin.conf configuration file
$rpcPassword = "bigPHATpass";                             // password
$rpcHost = "127.0.0.1";
$rpcPort = "7332";

then update all the cronjobs and web pages with the PHP bitcoinController call:

FROM :
$bitcoinController = new BitcoinClient($rpcType, $rpcUsername, $rpcPassword, $rpcHost);

TO :
$bitcoinController = new BitcoinClient($rpcType, $rpcUsername, $rpcPassword, $rpcHost, $rpcPort);

Voila!

[AnnihilaT]

I probabaly would have just changed it in the bitcoin.inc.php file then you only had to change it once:

from:

public function __construct($scheme, $username, $password, $address = "localhost", $port = 8332, $certificate_path = '', $debug_level = 0) {

to:

 public function __construct($scheme, $username, $password, $address = "localhost", $port = 7332, $certificate_path = '', $debug_level = 0) {

But im lazy like that

Ill tag this as an improvement for later commit.  Thanks for all the input.

[Keninishna]

quick question, does this have to be in the root /www directory? or can I put it in sub dir?

[AnnihilaT]

if you put it in a sub dir stuff might break but is probably fixable by making sure you change all the paths to your webroot+subdir

[moonboon]

Oh boy, running the stock template got me blamed for ripping off your site at mainframe..  More template options required!

[Keninishna]

ok google probably knows this but can I have two webroots?

[moonboon]

Just a few questions about mmcFE..

I have a pool running that tends to neglect to pay out the odd block, which then causes me to have to do this manually.. there doesn't seem to be any pattern to when it does this..  Not just 1 specific user, time, etc.. Any ideas?  Paying out manually can become very time consuming..  Is there perhaps a way to set a round from paid out to not paid out in the sql database somewhere to have the cron job re-run to actually pay it out the next time through?

In your code you have specified the odd thing that says something like "DO NOT HARD CODE", yet its hardcoded anyways... Such as the block payout amount for BTC as an example..  Could things like that not be made a variable?

That way when a new coin fork comes out, a pool could very quickly implement it by changing a few variables and then they're off to the races without having to scour through many different php files to make those very same changes that the variables could really just deal with?


Thanks for a decent looking front-end though..

[AnnihilaT]

if you are missing the random block here and there you either need to upgrade or run your crontabs more often (i run mine every 60 secs).

For the other things you mentino... yuh those are all things on the todo list.   The hardcoded stuff is inherited from simple coin.  ive remarked things here and there as notes of stuff to redo properly later.    As with any software its always a work in progress.

[Icoin]

Hello
I have setup the mmcFE on http://mine.icoin.ch, cause im running plesk a have a bit a different path structure so i changed all paths to /includes... allso i installed all needed php packages like you suggested in your earlyer posts
I did set the .htaccess file with the rename function and since then the frontend is working

But i have now a problem: i was able to create successfuly a user but when i try to login i just come to the news page and thats it. And the side bar shows me the login page, im allso unable to see the personal or extended stats, i wonder how i can fix this to make the mine work.

Thanks

Icoin

[AnnihilaT]

I think you have not changed your cookiename or set it at all and that your cookie domain is also wrong.  Read the top section of requiredFunctions.php

[Icoin]

I think you have not changed your cookiename or set it at all and that your cookie domain is also wrong.  Read the top section of requiredFunctions.php

Here my settings in requiredFunctions.php

$cookieName = ".mineicoinch";             //Set this to what ever you want (text string)
$cookiePath = "/";            //Choose your path!
$cookieDomain = "icoin.ch";         //Set this to your domain

[AnnihilaT]

I think you have not changed your cookiename or set it at all and that your cookie domain is also wrong.  Read the top section of requiredFunctions.php

Here my settings in requiredFunctions.php

$cookieName = ".mineicoinch";             //Set this to what ever you want (text string)
$cookiePath = "/";            //Choose your path!
$cookieDomain = "icoin.ch";         //Set this to your domain

remove . from cookie name and add dot to front of domain

[Icoin]

Thanks a lot it works great now !!!

Damn dot
 

[Icoin]

well i realized an other problem this time with cronjobs:

when i run pool_update.sh (i made it executable) by cronjob or manual nothing happens - but when i run the cronjobs in command line like:
php /..../cronjobs/cronjob.php the cronjob works, so now i wonder where the php bin is located on ubuntu 10.4 anyone runnung mmcFE on ubuntu 10.4 aswell ?

[moonboon]

I've run into that problem before.. Make sure there is a proper carriage return at the end of your crontab line or it won't execute.. dumb I know, but that has solved the issue for me in the past...

[moonboon]

if you are missing the random block here and there you either need to upgrade or run your crontabs more often (i run mine every 60 secs).

For the other things you mentino... yuh those are all things on the todo list.   The hardcoded stuff is inherited from simple coin.  ive remarked things here and there as notes of stuff to redo properly later.    As with any software its always a work in progress.

Mine also runs every 60 seconds.. I think I may have found the issue though.. my php max_execution_time was set to 30 seconds... the scripts in general may take longer than that if the block was quite long so I have bumped php time to 2 minutes instead.. May fix the glitch, will keep you posted if that indeed solves it..

As for the other things, sounds good.. and look forward to future enhancements.

[AnnihilaT]

max_execution_time integer

    This sets the maximum time in seconds a script is allowed to run before it is terminated by the parser. This helps prevent poorly written scripts from tying up the server. The default setting is 30. When running PHP from the command line the default setting is 0.

    The maximum execution time is not affected by system calls, stream operations etc. Please see the set_time_limit() function for more details.

    You can not change this setting with ini_set() when running in safe mode. The only workaround is to turn off safe mode or by changing the time limit in the php.ini.

    Your web server can have other timeout configurations that may also interrupt PHP execution. Apache has a Timeout directive and IIS has a CGI timeout function. Both default to 300 seconds. See your web server documentation for specific details.

This shouldnt matter unless you are running from the webserver and not the command line.

[moonboon]

max_execution_time integer

    This sets the maximum time in seconds a script is allowed to run before it is terminated by the parser. This helps prevent poorly written scripts from tying up the server. The default setting is 30. When running PHP from the command line the default setting is 0.

    The maximum execution time is not affected by system calls, stream operations etc. Please see the set_time_limit() function for more details.

    You can not change this setting with ini_set() when running in safe mode. The only workaround is to turn off safe mode or by changing the time limit in the php.ini.

    Your web server can have other timeout configurations that may also interrupt PHP execution. Apache has a Timeout directive and IIS has a CGI timeout function. Both default to 300 seconds. See your web server documentation for specific details.

This shouldnt matter unless you are running from the webserver and not the command line.

Noted. 
Good point, I have no flippin' idea then.. lol