guy.davis

It's possible that some are facing issues with the addition of ForkTools and the multi-proc patch that is applied automatically on container start. I haven't seen this but everyone has different hardware/configurations. In `:develop`, you can pass environment variable "forktools_skip_build" with value "true" to skip this patching. I need to verify this, before it gets pushed to `:test` stream in a bit. Let's see if that helps you all.

Good idea! I've added it to the GH issues list.

Good day! Machinaris v0.6.7 is now available. Changes include: - BTCGreen - cross-farming support for this blockchain fork. - Plotting page - Charts to show plotting speed for recent jobs across all workers on your farm. - Option to disable background job to Chia `plots check` and Plotman `analyze`. Set `plots_check_analyze_skip` env var. - Fix for Madmax building on certain user's hardware. Thanks @karaliux for the patch! - Fix to ensure Forktool's configs (~/.machinaris*/forktools/ftconfigs/) are persistent across container restarts. - Fix to quiet logrotate output from container stdout. Too verbose. - Fix to incorrect commenting out of `pool_contract_address` on plotter systems. Please double-check your Settings | Plotting page! Check Farming | Plots page for recent 'solo' plots. - Fix to Plotting | Workers page for graph showing tmp disk usage during plotting on mode=plotter systems. - Fix Farming | Workers page to show Daily Summaries for TrueNAS users with FQDN hostnames in their containers. - Fix - Blockchain download for fresh installs, use the new download paths provided by Maize team.

Bug alert! For those plotting for pools with Machinaris on a `plotter` worker (not your `fullnode`), please double-check your "Settings | Plotting" page after each restart of the Machinaris plotter. In particular, ensure that `pool_contract_address` is uncommented for pool-plotting with v0.6.6. `pool_pk` should be commented out with a hash character at the beginning of the line. Please check and Save on each container restart of v0.6.6. Will be fixed soon in v0.6.7.

Hi, the patch is automatically applied on every start of the container so nothing needed on your end. Please see /tmp/forktools_setup.log inside the container.

Good day! Machinaris v0.6.6 is now available. Changes include: - Maize - cross-farming support for this blockchain fork. - Forktools - utilities including a multiproc patch to limit memory usage. - Farming - right-side of Plots table offers Chia "plots check", slowly generated on background thread. - Bug Fix - hourly log rotation for `farmr`, auto-deletion log if above 20 MB in size. Sorry all!

Yes, 100% correct. The workaround is to run the main Machinaris controller (Chia fullnode), but expressly leave the `plots_dir` Variable either empty, or point to a generic empty directory like `/plots1` in the container. For the other Machinaris-FORK containers, you would provide the Volumes to all your real plots, and set `plots_dir` accordingly. Then in Machinaris WebUI on the Summary page, for Chia you should see 0 plots farmed, but for the other forks you should see the real plot count farmed. Note, on the Farming page, you wouldn't see any plots listed (excepting Chives) as the Chia container is the aggregator for that listing. Sorry about that!

Welcome! That doesn't sound right, so please join the Discord where we can address your issue interactively. This will get you going much faster.

Yes, Machinaris is not meant to be a full Chia (forks) wallet. You can definitely use the Chia CLI within the Machinaris container. As well, there are other good options such as the new Chia light wallet. More details on the wiki.

Hi, that log shows bad news about the state of the Chia database within. Log message about `corrupted` means you are best to: 1) Stop Machinaris 2) Delete /mnt/user/appdata/machinaris/mainnet 3) Start Machinaris up and wait for a re-sync of blockchain and wallet. I would recommend checking the SMART stats on your cache drive to ensure its still good. Finally, to speed up #3 you can either import a backup or use the new blockchain db download feature. Your choice of course.

Absolutely, a cold wallet is recommended for security, but not required to farm. For example, I use a cold Chia wallet, but I haven't bothered with a cold wallet for the alt-coins. With respect to luck, yes each person will experience each fork differently. In my case, HDDCoin is way behind all the other forks in luck, but that is for me. Different for everyone as that's the nature of luck. Best to keep any eye on the Flax challenges chart and watch Flax debug log (Farming page, choose Flax from drop-down menu) for errors. Also, peek at the /mnt/user/appdata/machinaris-flax/machinaris/logs/fd-cli.log file occasionally to see if 7/8 rewards are being transferred, if available. The fd-cli is just an scheduled execution of this site's script, so you can try there too. Hope this helps!

Hi, thanks for the report! I see I mixed up the Chives and Cyrptodoge ports when clicking the 'Check Port Forwarding' button. Definitely should be 9699 for Chives and 15994 for Cyrptodoge. Will fix that in the next release. Thanks again.

Good day! Machinaris v0.6.5 is now available. Changes include: Cryptodoge - cross-farming support for this blockchain fork. Docker images now roughly 1/3 the size of previous releases. Shared base image further decreases download size for forks. API endpoint /metrics/prometheus exposes plotting statistics. Thanks to @Nold360 for the contribution! Windows deployments now support automatically mounting remote plot shares (such as on a NAS) using CIFS in-container. On Wallets page, display total wallet balance including cold wallet address amounts.

No problem. I'm always on the lookout for ways to improve Machinaris and blockchain farming. Fyi, I'm running ten blockchains on a single Unraid system with 48 GB total. This Unraid system is doing a lot more than just Machinaris, including Plex etc. Still have lots of headroom:

I would not recommend running Silicoin right now. They've gone closed-source with their last releases. Would recommend you run Cactus instead, then no port conflict. CC: @AsTuRkInG

Good day! Machinaris v0.6.4 is now available. Changes include: - Farmr - include `farmr` client for optional monitoring at farmr.net - Stor - cross-farming support for this blockchain fork. - Cactus - cross-farming support for this blockchain fork. Thanks to all who helped test and provided feedback! Known-Issue Discovered: Please use ":test" images for Machinaris harvesters of Cactus and Stor to avoid issue on harvester connection to fullnode.

Hi, sorry to hear you're having issues with Machinaris. We can probably solve this faster in the Discord, however, what does `flax farm summary` output? How about your Blockchains status in WebUI for Flax? Are you still syncing? Another way to check this is `flax show -s` Hope this helps.

Currently, the Silicoin dev team has not properly released the source for their latest release. No, a tarball is not acceptable. If they do, I'll review their changes and consider rolling a new image. Until then, my recommendation is to stop the Machinaris-Silicoin container. Lots of discussion on this in the Silicoin channel of our Machinaris Discord, starting minutes before their "announcement" last night.

Thanks! Actually, there may be. Would you mind manually testing it? The idea would be to run some of the forks with the wallet off, either some of the time or all the time. My understanding is syncing the wallet is a nice-to-have, but not a 24/7 necessity the way the farmer is. So please try the following, in one Unraid shell get a "docker stats machinaris machinaris-flax machinaris-hddcoin ..." running to watch each containers resource usage. Then in another Unraid shell, get into a particular fork fullnode container like "docker exec -it machinaris-flax bash", then do a "flax stop wallet-only". This should stop only the wallet, but leave farming running. Check with "flax farm summary" and "flax wallet show". It will be interesting to see what stops updating status-wise in the Machinaris WebUI with the wallet off. I'm guessing the Summary page's Balance and Farmed amounts. Also the Wallet page. However, I expect the rest *should* keep updating. If this manual test comes back positively, particularly if wallet-off state results in a noticeable resource savings as shown in "docker stats", then I can look at automating the wallet being off. Maybe rotating each container to have their wallet in sync catch-up for 1-2 hours a day at most? Just thinking out loud here. Please let me know what you find!

Staicoin should the same as all the others, so please double-check your settings and then paste the exact error you're seeing here. Yes, with the Path config named 'mnemonic_path' on each fork container, which points to the original in /mnt/user/appdata/machinaris/mnemonic.txt, there is no need to have the file in each fork's appdata anymore. You can delete them. Just keep this one /mnt/user/appdata/machinaris/mnemonic.txt, plus make sure it's backed up safely as well.

Quite possibly! Please add each as individual issues on Github. Don't forget to vote in the #feature-ideas channel on Discord.

Good day! Machinaris v0.6.3 is now available. Changes include: Staicoin - cross-farming support for this blockchain fork. Chia - Update to version 1.2.11. See their changelog for details. NOTE: If you encounter v0.6.3 upgrade error, you are likely using a customized appdata location. Please visit Docker tab of Unraid UI. Select each Machinaris container (one by one), edit their Config, Show More Settings (at bottom), find mnemonic_path and Edit it to the location where you are storing the original mnemonic.txt. Apologies again for any inconvenience to existing users.

Hi. Yes, a coming update will make this a background function, automatically displayed alongside each plot in the WebUI. For now, please enter the Machinaris container and run 'chia plots check ...' on plots you wish. Visit the Settings | Alerts page, choose your Worker and Fork=Silicoin. Then edit the config to 'enable: false' for 'file_log_consumer' and click Save. Sorry to hear you're encountering issues. Please drop into the Discord as this sounds like misconfiguration which can best be solved in a more interactive forum.

Thanks for the report. This is being investigated and has been logged on Github. Unfortunately, I haven't been able to replicate it myself. The log file should contain the exact command executed, along with timestamp. Do the inputs to the command look correct? Perhaps Machinaris is using the wrong IDs?

Hi, it sounds like you have some stale status affecting the WebUI. This does not mean you are not Chia farming in the background successfully, just that you need to clear the WebUI's stale status after upgrade. 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.