Version 2.3.0

[guydavis]

Version 2.3.0 of Machinaris is now available, for those that like to try the very latest Chia and Gigahorse releases.

Added

• Gigahorse: Optionally launch chia-exporter metrics endpoint for Prometheus reporting if env var chia_exporter=true is set.

Updated

• Chia to v2.3.0 - misc improvements, see their release notes.
• Gigahorse to v2.3.0.giga36.

Notes

• Support for updated blockchain (and their bugs) DOES NOT imply my endorsement for them. Only run those you are comfortable with.

---

This discussion was created from the release Version 2.3.0.

[danktankk]

Thank you for your excellent work on this project.

I am having an issue getting staicoin to work in machinaris v2.3.0. I waited about a week for the height of the blockchain to get right but after that happened, I am getting zero connectivity. Its just plain offline. Is Staicion down or dead perhaps? The log files in chiadog are pretty sparse, so it seems more likely that this one went the way of the dinosaur. Any help would be greatly appreciated. Thank you again for your time and effort on this project!

[guydavis]

Sorry, don't know what to tell you about Staicoin. It's always been flaky for me as well. Currently, my local farmer is synced, but not common:

I would recommend first trying to refresh the Staicoin config, then rebuild the entire Staicoin database.

[danktankk]

thank you for the advice. I will give it a shot. Otherwise I will just delete it. It hasnt connected once in almost a month now and just says worker not responding to pings.

[danktankk]

sorry for what may be a stupid question, but each of these forks needs its own DB, correct? I read this "One workaround is to download a Chia DB checkpoint manually."

Can I use this instead of waiting for 5-6 days to get the database synced again?

[guydavis]

Yes, I don't know of a recent staicoin database download, so you'll have to let it sync up from scratch over a few days. Try just the config file reset first though.

…

On Sat, Jun 8, 2024, 6:55 a.m. danktankk ***@***.***> wrote: sorry for what may be a stupid question, but each of these forks needs its own DB, correct? I read this "One workaround is to download a Chia DB checkpoint manually <https://www.chia.net/downloads/>." Can I use this instead of waiting for 5-6 days to get the database synced again? — Reply to this email directly, view it on GitHub <#989 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAADFCHPQHQDP2ZX57W3YZTZGL5N5AVCNFSM6AAAAABHJKZ4XSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TOMJTGQZTI> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[danktankk]

Thanks again,

I did try that and it did not help. I guess ill have to try it the db resync. It takes over 5 days now to do that :( If it fails a 2nd time, ill just accept defeat lol