I just downloaded the new release .28 R30 and I even built and imported new .sql file as well. My stats shows I have like 12,087 workers connected and I have none in reality? Not sure what is happening.
Peace!
Edit: oops...forgot to edit server.json file to new database.....lets see if that will straighten things out...
Topic: mmcFE v2.1.23-stable - A Clean & Simple Pushpool frontend (PHP/BASH/JS/MYSQL) - page 6. (Read 25060 times)
July 08, 2011, 08:49:54 AM
July 13, 2011, 09:53:59 AM
As usual your correct Anni...
The shares always seems to report accurate....it was just the MHash/sec and miners connected that would be off every once in a while....it was the slow test miner I had connected.....
We officially opened our new mining pool site using your software and also support forums for bitcoins that is opened to the public.....
The site and forums is located at www.coolcoin.net
If you want to see this front end code in action plz stop by and check us out!
Thanks again for all your help and the great running front end software Anni!
Peace!
The shares always seems to report accurate....it was just the MHash/sec and miners connected that would be off every once in a while....it was the slow test miner I had connected.....We officially opened our new mining pool site using your software and also support forums for bitcoins that is opened to the public.....
The site and forums is located at www.coolcoin.net
If you want to see this front end code in action plz stop by and check us out!
Thanks again for all your help and the great running front end software Anni!
Peace!
lol! you really didnt edit much visually did you
You could at least change the background images you know Its templated so you can customize it July 11, 2011, 02:14:12 PM
I have a interesting new problem..hehe...seems the stats will show correctly one moment, then when I come back later it will show 0 except for the bitcoin to usd ...that part seems always accurate....any idea what might be causing the mining workers and MHash/sec stats to work one minute and then show 0 the next???
Peace!
Peace!
Are already counted shares also not correct when this happens? Are you mining with a really slow card? If a share isnt submitted within 10 mins the worker will be considered dead by the stats calcualations.
July 08, 2011, 09:15:53 AM
Forgot to ask also, about how long do you suggest to run the pool_update.sh script? Should we set the crontab to run it every 60 seconds? I am wondering about the sleep commands you used for the different update php files and how this relates to how I should setup the crontab to run the .sh master script?
I am assuming this "timing" would be based on the size of the DB and how they start to take to run or should I say complete.
Thanks as always for your help and time Anni!
Peace!
I am assuming this "timing" would be based on the size of the DB and how they start to take to run or should I say complete.
Thanks as always for your help and time Anni!
Peace!
Im still running every 60 seconds. This should be fine until you are very large or unless your server is very slow. Just watch the overall time it takes for the master script to run and then make sure your load is ok if you run it in windows of time smaller than the time it takes for the script to complete.
July 08, 2011, 08:53:40 AM
I just downloaded the new release .28 R30 and I even built and imported new .sql file as well. My stats shows I have like 12,087 workers connected and I have none in reality? Not sure what is happening.
Peace!
Peace!
Oh shit your DB got overwritten with default data then. You should only update your db if specified. That DB schema included is only meant for a fresh install (hence the name 'install.sql')
Hope nothing else was messed up. Try running the cronjobs once and hopefully that fixes it.
July 08, 2011, 07:21:02 AM
- Too many places with the hardcoded $includeDirectory. Should be in a config file or setup through the admin section.
- Forcing Apache and its rewrite might still be valid, although we're not in 1998 anymore, but making it more generic (lighttpd, nginx) would be adequate.
- Forcing Apache and its rewrite might still be valid, although we're not in 1998 anymore, but making it more generic (lighttpd, nginx) would be adequate.
totally agree.... its on the list!
that special user var should be the same way. configurable from admin panel would make the most sense. Trying to get some useful user management for the admin in there first and also tweaking the design a bit as well. July 05, 2011, 08:23:47 PM
Awesome! Thanks!
I noticed that my remote clients that connect outside my local network seem to be updating perfectly in the stats page. But my local connected client seems to report as being not active and shows 0 for Mhash/sec rates. Any reson why this might be happening? I have made sure all my rpc settings match. Do I need a local bitcoin.conf file for the mining client pc? I dont really need this local client to report as I just set it up for testing ports and connections. Just curious at this point.
Peace!
I noticed that my remote clients that connect outside my local network seem to be updating perfectly in the stats page. But my local connected client seems to report as being not active and shows 0 for Mhash/sec rates. Any reson why this might be happening? I have made sure all my rpc settings match. Do I need a local bitcoin.conf file for the mining client pc? I dont really need this local client to report as I just set it up for testing ports and connections. Just curious at this point.
Peace!
July 08, 2011, 07:18:34 AM
- Too many places with the hardcoded $includeDirectory. Should be in a config file or setup through the admin section.
- Forcing Apache and its rewrite might still be valid, although we're not in 1998 anymore, but making it more generic (lighttpd, nginx) would be adequate.
- Forcing Apache and its rewrite might still be valid, although we're not in 1998 anymore, but making it more generic (lighttpd, nginx) would be adequate.
July 07, 2011, 08:30:04 PM
Version 1.0.28 tagged.
Summary of changes:
- if a block has not been found dont display a time since last block.
- added special user code (see README)
- bugfix: mismatching max length on input fields
- updated a debug script
- bugfix: scoring
- misc bug fixes and a new spcial_user feature
- add early adopter code for $x number of users (configureable or removeable at install)
- default stats to top 15 instead of top 20
- update some debugging scripts
- small style updates
- user search feature (alpha)
- enable properly working proportional payout method again.
- tweaked proportional calculations
- style updates (new style stats and admin panel)
- round estimate to 6 dec (cleaner)
Summary of changes:
- if a block has not been found dont display a time since last block.
- added special user code (see README)
- bugfix: mismatching max length on input fields
- updated a debug script
- bugfix: scoring
- misc bug fixes and a new spcial_user feature
- add early adopter code for $x number of users (configureable or removeable at install)
- default stats to top 15 instead of top 20
- update some debugging scripts
- small style updates
- user search feature (alpha)
- enable properly working proportional payout method again.
- tweaked proportional calculations
- style updates (new style stats and admin panel)
- round estimate to 6 dec (cleaner)
July 05, 2011, 07:07:06 PM
I just downloaded version 1.0.21 and really like the modification to the cronjob scripting. Very nice!
Question I had was I originally downloaded the trunk18 package and imported the .sql file from there. Should I import and rebuild with the sql file from 1.0.21 or will just replacing all the webserver files surfice?
Thanks again!
Question I had was I originally downloaded the trunk18 package and imported the .sql file from there. Should I import and rebuild with the sql file from 1.0.21 or will just replacing all the webserver files surfice?
Thanks again!
July 05, 2011, 08:32:20 PM
Awesome! Thanks!
I noticed that my remote clients that connect outside my local network seem to be updating perfectly in the stats page. But my local connected client seems to report as being not active and shows 0 for Mhash/sec rates. Any reson why this might be happening? I have made sure all my rpc settings match. Do I need a local bitcoin.conf file for the mining client pc? I dont really need this local client to report as I just set it up for testing ports and connections. Just curious at this point.
Peace!
I noticed that my remote clients that connect outside my local network seem to be updating perfectly in the stats page. But my local connected client seems to report as being not active and shows 0 for Mhash/sec rates. Any reson why this might be happening? I have made sure all my rpc settings match. Do I need a local bitcoin.conf file for the mining client pc? I dont really need this local client to report as I just set it up for testing ports and connections. Just curious at this point.
Peace!
sounds like a client config issue or something with pushpoold/bitcoind.... yer on yer own for this one. If some are working and others arent its not an issue with the front end. try checking yer pushpool logs, enable and running in debug mode, or explaining in more detail what you are talking about. which client, how is it connected etc. more detail is better!
July 05, 2011, 07:21:47 PM
yuh just the webserver files need replaced. no changes to the database have been made since revision 18
July 05, 2011, 05:08:35 PM
Installed this fork and I must say it is one of the cleanest, and best working front ends that I have tried or used! Most excellent work Anni!
I am currently working on tweaking the stats but I really like the way the cronjobs are handled. Not only does it seem to make things secure, but it also is easier to manage IMHO.
If your looking for a clean, simple and fast front end then the mmcFE fork is for you my friend!
Happy pooling!
I am currently working on tweaking the stats but I really like the way the cronjobs are handled. Not only does it seem to make things secure, but it also is easier to manage IMHO.
If your looking for a clean, simple and fast front end then the mmcFE fork is for you my friend!
Happy pooling!
July 05, 2011, 05:12:15 PM
Installed this fork and I must say it is one of the cleanest, and best working front end that I have tried or used! Most excellent work Anni!
I am currently working on tweaking the stas but I really like the way the cronjobs are handled. Not only does it seem to make things secure, but it also is easier to manage IMHO.
If your looking for a clean, simple and fast front end then the mmcFE fork is for you my friend!
Happy pooling!
I am currently working on tweaking the stas but I really like the way the cronjobs are handled. Not only does it seem to make things secure, but it also is easier to manage IMHO.
If your looking for a clean, simple and fast front end then the mmcFE fork is for you my friend!
Happy pooling!
Glad you like! Those stats still need my attention. Thats one of the things i will be getting to next. That code was brought in by Mike from Simplecoin and he got it from the ozcoin fork and IMHO the code is a mess. Thats why ive been putting it off
(when i say its a mess i mean no disrespect - im referring mostly to formatting and readability) July 05, 2011, 04:33:27 PM
Just tagged version 1.0.21. See notes below:
Download HERE:
- make sure some stats are still sane even when we havent yet found our first block
- make the pool_update.sh script a littler saner and nicer. gives some output when run
manually from the cmd line now.
- disable (and later make optional) spamming the db with users hashrate info. This is only useful if you
want to build a chart which mmcFE does not endeavor to do.
- update README for cronjobs
- small updates to stats
- allow users to register without an email address (but warn them of the consequences). We are privacy
sensitive and bitcoins are anonymous - we dont need your email unless you want to give it to us
(for when you might forget your password.)
------------------------------------------------------------------------
Download HERE:
- make sure some stats are still sane even when we havent yet found our first block
- make the pool_update.sh script a littler saner and nicer. gives some output when run
manually from the cmd line now.
- disable (and later make optional) spamming the db with users hashrate info. This is only useful if you
want to build a chart which mmcFE does not endeavor to do.
- update README for cronjobs
- small updates to stats
- allow users to register without an email address (but warn them of the consequences). We are privacy
sensitive and bitcoins are anonymous - we dont need your email unless you want to give it to us
(for when you might forget your password.)
------------------------------------------------------------------------
July 04, 2011, 04:48:55 AM
New improvements, updates, and bugfixes committed.
July 02, 2011, 04:30:24 PM
You probably should move to github for get more contributors/commiters.
Nobody uses subversion anymore?
July 02, 2011, 04:27:34 PM
You probably should move to github for get more contributors/commiters.
July 02, 2011, 04:16:47 PM
Announcing a new pushpool mining frontend package called - mmcFE
This is the same software that the Mainframe Mining Cooperative (https://mining.mainframe.nl) uses.
A Live example of this software running can be found here:
https://mining.mainframe.nl/
(while you are there throw us some hashes! Its for a good cause!)
svn is at:
http://mmcfe.mfis.net/
The idea is to keep a frontend very simple to install, easy to use, secure, and easy to customize. More stats for the analytically minded are planned - as well as eventual integration with some of the bigger exchanges. Other than that anything could be possible but i decided that the direction the original code base was heading was not where i wanted to go with something i would run live on my own servers.
Props and respect to simplecoin, ozcoin, & xenland from whom this code was originally forked.
Cheers,
AnnihilaT
This is the same software that the Mainframe Mining Cooperative (https://mining.mainframe.nl) uses.
A Live example of this software running can be found here:
https://mining.mainframe.nl/
(while you are there throw us some hashes! Its for a good cause!)
svn is at:
http://mmcfe.mfis.net/
The idea is to keep a frontend very simple to install, easy to use, secure, and easy to customize. More stats for the analytically minded are planned - as well as eventual integration with some of the bigger exchanges. Other than that anything could be possible but i decided that the direction the original code base was heading was not where i wanted to go with something i would run live on my own servers.
Props and respect to simplecoin, ozcoin, & xenland from whom this code was originally forked.
Cheers,
AnnihilaT
Jump to: