guy.davis

Chives requires new plots as per the wiki.

Please visit the Workers page. Select all Chives rows and then click 'Prune Selected' button.

Please see this section of the wiki: For a fork on Unraid the path is: /mnt/user/appdata/machinaris-FORK/FORK/mainnet/config/config.yaml

Hi, I suspect you have an issue that requires the back and forth Discord affords. However, the wiki has lots of good information as well. In your particular case, this feels like you may have loaded more than one Chia mnemonic/key? I would recommend opening the Docker Console to Machinaris from the Unraid Admin UI | Docker tab. Then you can enter commands such as: chia farm summary chia plots show chia wallet show chia keys show Ideally, those commands return neither errors or input prompts. Hope this helps!

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.

Absolutely. Join the Discord for an interactive support session.

Hi, I haven't forgotten about this memory usage issue. Please see this discussion in the Discord's #development channel around decreasing peer counts when synced. I wonder if this would help.

Yes, Machinaris expects that you are farming Chia first and foremost with it. Forks are added secondarily. Not sure everything will work with the customized deployment (no Chia) you have taken. Hopefully most things however. Chiadog in the Chia container can be disabled by editing the Settings | Alerts page for the Chia container. See: https://github.com/guydavis/machinaris/wiki/ChiaDog#configuration It sounds like you may just be unlucky, assuming your `flax farm summary` is working (check at command-line too via `docker exec -it machinaris-hddcoin bash`). Also, you said, your blockchain challenges are happening for the Flax and HDDCoin forks so that is probably not the issue. Finally, I would recommend you check the fd-cli.log file found in: /mnt/user/appdata/machinaris-hddcoin/machinaris/logs/fd-cli.log for NFT Reward Recovery. Details here: https://github.com/guydavis/machinaris/wiki/Forks#farm-chia-plots Hope this helps.

Sorry to hear that. Yes, Chia can be a bit finicky at times. Please see the wiki for troubleshooting tips.

Stop Machinaris container. rm -rf /mnt/user/appdata/machinaris/plotman/checks rm -f /mnt/user/appdata/machinaris/plotman/status.json Reset DB: https://github.com/guydavis/machinaris/wiki/Troubleshooting#reset-machinaris-database Start Machinaris container.

Sorry, Machinaris does not offer a tested Silicoin package. See the old #silicoin channel in the Discord for details.

Sorry, just as the Chia network folks recommend, Machinaris also recommends holding appdata on an SSD. Blockchain writes on a Chia full node are simply too much to use an HDD.

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.

Good day! Machinaris v0.6.8 is now available. Changes include: SHIBGreen - cross-farming support for this blockchain fork. Support for pooling configuration of forks like Chives. Updated blockchains: Chives, Stor, Stai(coin) Various fixes for issues reported in the Discord. Thanks all! Known Issues: - Staicoin broken due to their blockchain renaming. Run test stream for a working version. - Summary page for Chives - does not show Partial Proofs to Pools chart when pooling.

Hi, not sure what that could be. All I can suggest is to try the ":develop" images which have the most recent Chives blockchain version (few days old) and improved support for Chives pooling. Can't guarantee that will fix the issue you report however. I am just starting to test the new Chives now.

Hi, Unraid UI, Docker tab, edit the Machinaris container (Chia) configuration. Change from :latest to :test for Repository line:

Hi! The log message is an unrelated message from a log rotation method in v0.6.7. This log message has been corrected in the ":test" image for a couple of weeks. I would recommend either updating to the test release, or restart the current version of the container. Chia farming services can have issues which a restart often corrects. Hope this helps.

Hi, some users of older Unraid versions have reported problems building the plotters. Please upgrade to Unraid 6.9.2 with latest Docker.

Hi, this could a weird side-effect of the latest Chia dust storm. Or perhaps something stuck on update. Either way, I would recommend using the `:test` images by updating. If that doesn't help, restart the Unraid system to force the port to be freed up. Hope this helps!

Hi, sorry to hear that. No, I haven't seen reports of the Docker image space becoming full due to plotting unless the "tmp", "dst", or optionally the "tmp2" locations were not actually defined as host mount points in the Unraid docker configuration. As long as Plotman is writing to volume-mounted locations, the Docker image space should not be affected. I recommend checking the Volumes defined in your Machinaris container on the Unraid UI's Docker tab. Hope this helps.

Hi, I'm not sure these two symptoms are related: 1) Farmr log rotation outputs a spurious warning to stdout so is seen in Machinaris - Unraid Logs. Already fixed in :test release. 2) "not plotting anymore": Please ensure you are updated to latest Machinaris images, then troubleshoot plotting. If still having an issue, please supply all relevant logs. Thanks!

Thanks for the update. Here's a view of my farming (no longer syncing) forks, using `:develop` images including latest Chives codebase: Interestingly, both Chia and Chives, show higher memory usage than I've seen recently. These are the two unique containers that go through code which lists the plots and gathers details about them for display in the WebUI. This makes me wonder if something is leaking memory in that code path. I will investigate further. Keep me appraised of any further findings and thanks for the tip!

Sorry, should have explained. No, Forktools are CLI tools available within the container CLI itself. Primary use case is trying to limit memory usage.

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.