Andrew255

Members
  • Posts

    12
  • Joined

  • Last visited

Posts posted by Andrew255

  1. 8 hours ago, guy.davis said:

     

    Sorry to hear that.  Some recent updates to blockchains have required some users (not all) to reset the config.yaml file they may have from an older version of the blockchain, to the latest version (default).  Try this quick fix first.  If that doesn't work, you may need to remove the wallet folder entirely and restart.  This should perform a wallet resync.  Details for both fixes are on the wiki.

    thanks for getting back on my issue @guy.davis Forgot to mentioned. I already deleted `db` subfolder within /wallet/, but still only new blockchain_wallet_v1_mainnet files created and they are not growing in size after boot at all. how i can reset config.yaml file to the latest version?

  2. Hi,

    I have machinaris-maize up and farming: `Active` for quite some time already until today I discovered that there is no wallet DB synced for this crypto at all. 

    Blockchain DB is fully synced, showing Farming status. Wallet process  is up and I can see active traffic for Wallet entry within Connections tab, but sqlite file timestamp in ../wallet/db/ folder gets only updated with container boot time and then no changes at all. Even `Wallet height` shows just 0

    Wallet height: 0
    Sync status: Not synced

    I restarted docker couple of times - same result.

    Does anyone had similar issue?

    This is first time for me, all other fork works just fine.

    Thanks 

    Andrew

  3. 30 minutes ago, guy.davis said:

     

    Thanks for bringing that unsupported "Machinaris-Silicoin" package to my attention.  Those old images were two months out of date and definitely had stale code. I've now cleaned that up.  Machinaris does not offer a tested Silicoin package. See the old #silicoin channel in the Discord for details.

    Can I still use different socket for  Silicoin since it worked for me and I already have some balance there? How can I change controller/worker port on Machinaris for different from the one you defined?

  4. @guy.davis thanks for the new release!

    I was successfully farming Silicoin from your develop branch until decided to add Maize fork which conflicts on controller/worker communication port 8933  

    Quote

    The TCP port to reach this worker at. Leave at 8933 for Silicoin blockchain.

    Quote

    The TCP port to reach this worker at. Leave at 8933 for Maize blockchain.

    I assume if i choose different port for controller/worker communication it must be linked back on main Machinaris docker as well.

    can you point where the changes has to be done

    Thanks again

  5. 3 hours ago, cjizzle said:


    Not sure if this helps, but Chives cannot use the same plots as Chia and most other Chia forks, it only supports k29, k30 and k31. Chia and most forks by default use k32 or higher. Granted the plot sizes are smaller for Chives, but you would need to dedicate space just for making Chives plots that arent compatible with many other forks. For me anways, this makes Chives a no go, since I cant use what I already have.

    Thanks for explanation, that make sense then

  6. 4 minutes ago, Andrew255 said:

     

    Thank you so much for quick reply.

    It worked like a charm.

    One more question non related to this topic:

    Plots are not recognized for Chives coin farming (see screenshot)

    Public key set looks kinda different from any other coins.

    Could it be the reason? I did not make any changes other than adding my mnemonic keys as per your doc.

    Thanks again

     

    Screen Shot 2021-10-31 at 3.09.42 PM.png

    For any other coins it shows 646 Plots

  7. 14 hours ago, guy.davis said:

     

    Hi! Easiest way to clear stale status in that case is:

    1) Stop Machinaris container

    2) Remove file on Unraid: /mnt/user/appdata/machinaris/machinaris/dbs/machinaris.db
    3) Start Machinaris container

    4) Wait about 10 minutes for active status to re-populate in the WebUI

    Hope this helps.

     

    Thank you so much for quick reply.

    It worked like a charm.

    One more question non related to this topic:

    Plots are not recognized for Chives coin farming (see screenshot)

    Public key set looks kinda different from any other coins.

    Could it be the reason? I did not make any changes other than adding my mnemonic keys as per your doc.

    Thanks again

     

    Screen Shot 2021-10-31 at 3.09.42 PM.png

  8. Hi,

    Can I remove unused worker nodes if they are not in workers tab?

    I have very first chia worker node which is offline, so on Summary tab it displays `Farming: Offline`, however over CLI it says Active.

    Prior 0.6.0 they appear within  `Workers` tab so I was able to prune them there, but they are not there anymore.

    Is there a way I can delete them somehow over command line?

    Thanks

    Andrew

  9. 10 hours ago, Andrew255 said:

    Thank you for quick reply,

    I mounted single share for completed plots. 

    I believe that would be it, I'll pass my `plots_dir` env variable "/plots/completed_plots" and will reload once plotting cycle completed.

    I'll post here if it would fix it. Pretty sure it should.

    @guy.davis I can confirm after updating "plots_dir" env all completed plots are successfully loaded within `Farming` tab. Everything is working as expected. Really neatly done product. Thanks again 

    • Like 1
  10. 5 minutes ago, guy.davis said:

     

    Hi, glad you like it!  So the summary line is the output of "chia farm summary" and that looks good. You're farming.


    The table rows are a listing of all the plots found at the in-container paths of the "plots_dir" env variable.  Did you mount multiple plots volumes?  If so, be sure to update "plots_dir" from its default of one at "/plots".  See the FAQ, but remember a change to Machinaris docker config in Unraid, will result in a restart of container, killing plotting, so just schedule it when you're ready.  Hope this helps.

    Thank you for quick reply,

    I mounted single share for completed plots. 

    I believe that would be it, I'll pass my `plots_dir` env variable "/plots/completed_plots" and will reload once plotting cycle completed.

    I'll post here if it would fix it. Pretty sure it should.

    • Like 1
  11. @guy.davis Thanks so much, Awesome docker, works beautifully with my Unraid.

    I set it up Yesterday, no issue. 

    After sync was completed, it starts farming, showing Active status along with all other stats on the Summary tab.

    The only data i'm still missing is within `Farming` tab.

    It does say correctly number of plots discovered, but does not display any details in table below.

    Forgot to mention, I migrated all config from official Chia docker including keys as well.

    I just created 4 plots with your docker plotman and other 103 plots were imported from official chia, which I guess shouldn't be an issue. However new plots were NOT loaded or discovered until I restart docker. I updated plotting and farming config with proper temp dirs and dir for completed plots  

    Screen Shot 2021-05-31 at 3.52.30 PM.png