Author Topic: Warmach's Forging Pool  (Read 14239 times)

warmach #30 on: January 02, 2016, 02:14:28 PM

  • Senior Fimker
  • ***
  • Posts: 234
    • View Profile
Perhaps you could try running FIMK from an upstart script and have it auto-restart on shutdown.
Then from a post-start stanza http://upstart.ubuntu.com/cookbook/#post-start run a script or single command line command to start forging.

There is a working example here https://github.com/fimkrypto/fimk_chef_repo/blob/master/cookbooks/fimk/templates/default/fimk.conf.erb.
Thats a part of our chef deployment setup.

I may have implement this, but I don't think it is my problem.  The server doesn't shutdown, the FIM server process is killed.  I think it is a memory limit issue as I have this running on a low resource device. 

Warmach's Forging Pool
http://fim.warmach.info/pool/
May the forge be with you...

warmach #31 on: January 02, 2016, 02:40:45 PM

  • Senior Fimker
  • ***
  • Posts: 234
    • View Profile

I wanted to give you a few updates on the pool. 

1.  The live server seems to have an issue that kills the FIM process at random.  It could be 12 hours or 12 days before it happens again.  This makes it hard to troubleshoot.  Rest assured that forging never stops.  I have two backup FIM clients running that forge for the pool.  The backup clients only forge and do not process payouts.  I am considering scrapping the live server and moving to my more reliable backup servers.


I decided to swap my live/backup servers.  My backup server ended up being much more reliable of a setup than my live setup.  The change should be transparent to the end user. 
Warmach's Forging Pool
http://fim.warmach.info/pool/
May the forge be with you...

warmach #32 on: January 06, 2016, 10:49:12 PM

  • Senior Fimker
  • ***
  • Posts: 234
    • View Profile
I have updated my two backup servers to 0.6.0 fim server.  They are running fine and ready for the hard fork in two weeks.  I'm going to give them a couple more days to run before updating the live server.
Warmach's Forging Pool
http://fim.warmach.info/pool/
May the forge be with you...

warmach #33 on: January 11, 2016, 12:07:09 AM

  • Senior Fimker
  • ***
  • Posts: 234
    • View Profile
I have updated my two backup servers to 0.6.0 fim server.  They are running fine and ready for the hard fork in two weeks.  I'm going to give them a couple more days to run before updating the live server.

The live server has been updated to 0.6.0 FIM server.  All servers are updated and running.  We are ready for the hard fork on 1/18.
Warmach's Forging Pool
http://fim.warmach.info/pool/
May the forge be with you...

warmach #34 on: January 15, 2016, 05:29:00 PM

  • Senior Fimker
  • ***
  • Posts: 234
    • View Profile

Thanks for all those forging with my pool.  At our height we had 9 lessors, including myself.  I look forward to what this coming year has in store. 


We're half way through January and we've beat our previous record for most lessor at once.  We will have a 11 total lessors once our newest lease confirms! 

I'd like to welcome our new lessors and thank our long time friends who have been forging with us.
Warmach's Forging Pool
http://fim.warmach.info/pool/
May the forge be with you...

warmach #35 on: January 24, 2016, 06:42:14 PM

  • Senior Fimker
  • ***
  • Posts: 234
    • View Profile


1.  The live server seems to have an issue that kills the FIM process at random.  It could be 12 hours or 12 days before it happens again.  This makes it hard to troubleshoot.  Rest assured that forging never stops.  I have two backup FIM clients running that forge for the pool.  The backup clients only forge and do not process payouts.  I am considering scrapping the live server and moving to my more reliable backup servers.


I figured out that this was a low memory problem.  I knew the server was running at about the max it could reasonably handle based on its memory.  I added more physical memory and the issue went away.  I think that when the java process hit that upper physical memory limit, it shutdown the FIM server to conserve memory for the OS.  My guess is that the FIM server needed more memory on occasion based on network activity and API calls I am making from the pool.  Either way, it's been running for a week with no hangups.
Warmach's Forging Pool
http://fim.warmach.info/pool/
May the forge be with you...

warmach #36 on: February 05, 2016, 03:08:17 PM

  • Senior Fimker
  • ***
  • Posts: 234
    • View Profile

I wanted to give you a few updates on the pool. 

2.  I had been starting development of new features but realized that the current Perl scripts were very limited in what they could handle.  I have decided to re-code the pool software to use Python.  This will make future development easier and quicker.  I am currently in the process of re-coding and testing.


I have finished re-coding the pool scripts into Python.  I will have the new scripts running on my development server for a week or so to make sure the numbers match up against the live and backup servers.  Once we get past this final testing, I'm going to push them live and then start working on new pool features.  Thanks for your patience!
Warmach's Forging Pool
http://fim.warmach.info/pool/
May the forge be with you...

Eliphaz Fimk #37 on: February 05, 2016, 05:04:25 PM

  • FIMKrypto coordinator
  • Administrator
  • *****
  • Posts: 825
    • View Profile
    • FIMKrypto
Nice timing! People have asked about setting up FIMK mining pool and I've referred them to your public mining scripts on this forum. Are they still relevant? Why did you switch from Perl to Python?

warmach #38 on: February 05, 2016, 08:52:59 PM

  • Senior Fimker
  • ***
  • Posts: 234
    • View Profile
Nice timing! People have asked about setting up FIMK mining pool and I've referred them to your public mining scripts on this forum. Are they still relevant? Why did you switch from Perl to Python?

Yes, the perl scripts I put up on this forum are what my live and backup pools have been running from the beginning.  They will work fine.

I switched to python because I have some new features I want to implement in the pool.  The design of python allows those updates to be easier and faster to write.  They could have been done in Perl, but they would have been messier to write and maintain.  In addition, python is a better fit for my programming style. 
Warmach's Forging Pool
http://fim.warmach.info/pool/
May the forge be with you...

OrgiOrg #39 on: March 11, 2016, 01:38:46 PM

  • Fresh Fimker
  • *
  • Posts: 31
    • View Profile
i like your pool  :cheers: :thumbup:

which new features you would like to add?

warmach #40 on: March 11, 2016, 04:03:07 PM

  • Senior Fimker
  • ***
  • Posts: 234
    • View Profile
i like your pool  :cheers: :thumbup:

which new features you would like to add?

Glad you like it! 

Right now, I'm working on setting up auto payouts at lease end.  It is taking a little longer than I expected because I needed to build an internal scheduling component to setup future payments to lessors. 

Do you have a feature request?
Warmach's Forging Pool
http://fim.warmach.info/pool/
May the forge be with you...

warmach #41 on: March 11, 2016, 04:07:16 PM

  • Senior Fimker
  • ***
  • Posts: 234
    • View Profile
As I'm working on the auto payout, I've been asking myself the question on how long should I wait once a payout request is made before issuing it?  The standard confirmation of a transaction is 1440 confirmed blocks.  To me, this seems too long.  What do you feel is an appropriate time to wait?

In a broader question, while 1440 confirmations is official, what is the practical confirmations number before a transaction is unlikely to be reversed?
Warmach's Forging Pool
http://fim.warmach.info/pool/
May the forge be with you...

OrgiOrg #42 on: March 15, 2016, 10:39:44 AM

  • Fresh Fimker
  • *
  • Posts: 31
    • View Profile
1440 conformations seems to be okay ... I don't have a problem in waiting for my free FIMKs  :cheers: :thumbup:

OrgiOrg #43 on: March 15, 2016, 10:43:00 AM

  • Fresh Fimker
  • *
  • Posts: 31
    • View Profile
Glad you like it! 

Right now, I'm working on setting up auto payouts at lease end.  It is taking a little longer than I expected because I needed to build an internal scheduling component to setup future payments to lessors. 

Do you have a feature request?

- configure a payout range ... if I earn a amount of FIMK which I like to payout it should be automatically transfered to my wallet
- automatically re-lease ... that would be really cool

warmach #44 on: March 15, 2016, 03:47:13 PM

  • Senior Fimker
  • ***
  • Posts: 234
    • View Profile
- automatically re-lease ... that would be really cool

I admit, that would be really helpful.  The problem is that I would need your secret key to renew the lease. 

Another option would be to use a script file to automatically renew the lease.  The only catch is you need an always on computer and ideally a running FIMK client.  I started a topic and uploaded a sample script here, https://forum.fimk.fi/index.php?topic=616.0

Once I get the auto payout piece done, I was going to work on end of lease notifications.  When a lease is close to ending, I would then send a blockchain message or possibly email with a reminder to renew the lease.  That is probably the best that I can do without actually holding the key to your account (which I don't want that responsibility!)  Other ideas on how to make this easier are welcome!
Warmach's Forging Pool
http://fim.warmach.info/pool/
May the forge be with you...