Topic: Pushpool - Tech Support - page 16. (Read 135173 times)

I am getting an error "[2011-07-10 18:00:35.988488] mysql sharelog failed at execute".

Any suggestions?

Here's what my table looks like:

Read the most recent updated Pushpoold tutorial for 5.1 over at the original post it describes how to install MySql package

you need to install i believe its called mysql dev....   then reconfigure.  If you dont have the mysql dev package it wont work

When compiling pushpool on ubuntu 11 I get a database.engine error message and then it quits compilation.

I have tried multiple database setups and I still get the same error. Any help please?

Thanks

Patches welcome...

To gigabytecoin, Miningfarm dosn't use log files becuase of the extra steps it would take to parse them. It does a series of checks and balances

Thanks jgarzik for that insight full info btw

Hello,

i've played a bit aroung with pushpoold and everything worked just fine.
But when I asked a friend for a little test something strange happened.
I have about 100MH/s my friend has 1500MH/s.
As soon as my friend joined for testing i got a lot of stales,
I looked it up in the datase and the reason is "unknown-work".
Where does this come from?

Help with this would be really nice.


regards, redshark1802

Awesome! Thanks guys!

I think I like the "sudo killall pushpoold" one the best though all methods dsescribed do indeed work.

Thanks again!

You must rotate/trim the logs yourself.

The logrotate package can help you with that.

Just thought I'd update the install tut scince I have to reinstall the whole thing on my VPS for further testing of my Mining Farm software, might as well get this outta the way.

Thanks!

Yeah i dont know what happens in a scientifc proven method to the log files but i do alot of testing with pusgpool on my local server and the log files seem to stay in the same range from a first glance. Im pretty curious about this problem as well and will be sure to try it out after celebrating.

Happy 4th of July everyone.

Sending a normal SIGTERM signal is the normal way to shut down pushpoold.  So killall works... provided that it does not send a SIGKILL (kill -9) immediately.

pushpoold will receive the SIGTERM, and initiate safe shutdown procedures, closing files and database connections properly, etc.

Stupid question time plz......can someone tell me how to properly shut down pushpoold please? I cant seem to find the command documented anywhere? Also, is there a clear example of how one's startup line should look to enable pushpoold to output display to the open terminal window?

like: ./pushpoold -F -E

This command seems to sorta work I think....all I get with that is the port list that pushpoold is listening on and that it is initialized..I dont however get output like for when a remote client connects?

Thanks in advance!

Thanks for that reply Xenland.

And yes you are right, I should just get on to trying it and let everybody know! I will do so in the next few hours and report back on this thread as to whether or not you can safely comment out the two .log files specified in the server.json file that pushpool writes to.

(I was just hoping somebody had already attempted it!)

So what you are saying is you are not sure whether or not the .log files are automatically trimmed/kept in check by pushpoold?

If you are not doing anything with the .log files from mining farm and it has been used by a few pools now in actual production, I would assume that pushpool deals with them directly otherwise people's servers would probably be getting overloaded with them by now, or soon.

But why then would jgarzik mention how to "re-open the logs (such as after rotation or deletion)." if pushpool dealt with them directly?!

So confused!

I will try it out myself and report back ASAP.

Yes and no, The log files for for those who don't do terminal based debugging so I believe(don't quote the following) they are hard coded into pushpool to output them in case of a crash.
I think that log files usually trim the older lines of logs. Most developers(especially anyone that can program a pool servicing) has probubly been around for a while long before the days of when 512mb was unheard of and text data could file a whole hard drive within minutes. So I personally believe that they do stop getting bigger at some point

Can you easlity remove the two log file lines... Idk, i don't think anybody has tried, you should be the first. Let us know what your results are and we'll assist you wit what we can.

You should really install Mining Farm and check out the database structure to see how it all works I do something similar. Basically current rounds go to the `shares` table then upon a found block they get converted to the `shares_history` where they wait for the block to be confirmed, changing tables ensures better performance when doing reward counting. After its done rewarding and counting shares it moves all shares for that round into the `shares_dead` which is like a back up for operators in the case that the code went horribly wrong(hopefully never) and everyone got offset rewards. the operator can realy on a "backup" sorta of speak other then that `shares_dead` is just a back up

Can anybody answer the above question?

Is it necessary to create the two log files when we are already backing up everything to MySQL?

Can I easily remove the two log file lines (or send them to a blackhole type script or a file that never saves or something?)

I plan on removing old "shares" from my MySQL table on the fly as a new block is found.

sudo killall pushpoold also works....

I usually just..
then kill -9 puspoold's process number.

Brutal but effective.
   

d3c0n808, is correct pushpool is a cut and dry application it is very shy about giving details about what is happening although the command that you are using should display when users are connecting. I should note that it will only display when users are connecting on 2 of the 4 ports set in the .json file. One of the 2 ports I mentioned just now will work and the other wont, although they both report they are connected/connecting

No unfortunely the ammount of debbugging information provided by pushpoold is very very limited.   In my experience with pushpool.  I wasn't able to get it to compile without using the latest version of memcached.  But thats slackware not Debian.  I was able to compile on debian squeeze.  But I imagine the libs and binaries for lenny are older than for squeeze.    Though if pushpool can't connect to memcached it usually just exitted on my system.