DoeBoye

Do we need to upgrade all the alt coin DBs as well to v2? I've done the main Chia one, and am currently doing the Flax one (as per instructions above), but what about the rest? They all seem to have v1 dbs in their mainnet/db folders...

I only noticed this warning after I had completed a full 3 cycle pre clear on one drive and started a new 3 cycle preclear on the next. The first one passed without issue, and the second one is chugging along. I'm seeing people comment with random errors/failures, but if my preclear finishes normally, should I be concerned? Do I need to rerun preclear with the UD Preclear on the first drive and cancel the preclear running on the second one, or if it finishes without error, I'm ok? (But will be removing and replacing script once the process is done).

Total shot in the dark, but could it have anything to do with using the same directory for directory 1 and 2?

I had the same problem. I ended up finding some guidance that recommended opening up your radarr.db file in Browser for SQLite (free app). Once open, export it to a flat SQL file, then re-import it and save. That fixed me right up. Seems like something got malformed, and the export/import process fixed the issue while processing... NOTE: Though I shouldn't have to say it, Backup your radarr.db first!!!

So just an update. I tried the develop branch, but still couldn't connect. Switched back to stable when you released 0.6.9, and next time I checked, I had started pooling again..... The only caveat is that Machinaris still seems to think that I am not connected (Though my payouts from space pool have restarted)... Weird eh? See attached screenshot... EDIT: Can't seem to attach my screenshot today. Keeps failing. In a nutshell, the radio button beside the 'connected to a pool' option is not selected, though the field is reflecting the url for space pool. At the top of the page in the pinkish alert box, it says: 'Unknown pool save choice provided: None'

Sigh. I hate to be the squeaky wheel, but now I have a new problem. I seem to be able to self pool on one wallet, by I am unable to self pool on my original wallet, and I can't join a pool on either wallet. I keep getting an error when I try. list index out of range I deleted and rebuilt my wallet again, thinking that was the issue, but it doesn't seem to have helped. Any other thoughts?

So the plot thickens! I deleted my config.yaml file, waited 30 minutes, and error was still there... Then, for unrelated issues, I had to reboot my server. After rebooting, I started all my dockers, then didn't look again till now... Blockchain is fully synced! Not sure if it was the config file or the full reboot, but problem seems to be gone!! 😅

Ackkk! Just checked again, and the error has returned!! Exception from 'show' Traceback (most recent call last): File "/chia-blockchain/chia/cmds/show.py", line 41, in show_async blockchain_state = await client.get_blockchain_state() File "/chia-blockchain/chia/rpc/full_node_rpc_client.py", line 27, in get_blockchain_state response = await self.fetch("get_blockchain_state", {}) File "/chia-blockchain/chia/rpc/rpc_client.py", line 49, in fetch raise ValueError(res_json) ValueError: {'error': "b'\\xd7\\x80\\xd2,z\\x87\\xc9\\xe0\\x1d\\x98\\xb4\\x9a\\t\\x10\\xf6p\\x1c;\\x95\\x01WA1k?\\xda\\x04.]{\\x81\\xd2'", 'success': False}

Hi! Thanks for the idea. Lots of space though :(. That would have been an easy fix if it was the issue!

So the Chia blockchain was finally almost resynced last night. I just checked this morning, and it seems to have reset to the beginning again! (March 2021) without any intervention!... 😢. Any ideas?

Chia stopped harvesting earlier today so I stopped and restarted, and now in the blockchain tab, I get this error (For Chia only. Forks are fine) Exception from 'show' Traceback (most recent call last): File "/chia-blockchain/chia/cmds/show.py", line 41, in show_async blockchain_state = await client.get_blockchain_state() File "/chia-blockchain/chia/rpc/full_node_rpc_client.py", line 27, in get_blockchain_state response = await self.fetch("get_blockchain_state", {}) File "/chia-blockchain/chia/rpc/rpc_client.py", line 49, in fetch raise ValueError(res_json) ValueError: {'error': "b'\\xd7\\x80\\xd2,z\\x87\\xc9\\xe0\\x1d\\x98\\xb4\\x9a\\t\\x10\\xf6p\\x1c;\\x95\\x01WA1k?\\xda\\x04.]{\\x81\\xd2'", 'success': False} Any ideas?

Try stopping machinaris, delete machinaris.db, restart. It'll rebuild and clean up any orphaned references.

NP

Chive requires k29 to k31 sized plots. Are you using the standard k32 sized plot?

The latest version seems to have fixed these connection refused errors as well for all my coins. ShibGreen is now working, and all logs are clean and happy! Thanks @guy.davis!!! Another awesome release!! EDIT: Except for Staicoin, but that seems to be a known issue. I can wait for the next release for that fix

I was just about to post! Awesome!

20! Hmmmm.... I don't know. We started at around the same time, but I have 3x the plots and a tenth of your coins.... That's got to be something else other than super bad luck... Here's my Maize log. There's an odd connection refused error for port 8926 (that appears in all my coin logs as well). Could that be causing issues? And what do I need to do to fix it? Welcome to Machinaris v0.6.7! maize - fullnode on x86_64 Configuring Maize... Adding key at path: /root/.chia/mnemonic.txt Daemon not started yet Starting daemon maize_harvester: started maize_farmer: started maize_full_node: started maize_wallet: started Configuring Plotman... Starting Machinaris API server... Starting Machinaris Web server... Completed startup. Browse to port 8926. connect: Connection refused connect: Connection refused connect: Connection refused connect: Connection refused connect: Connection refused connect: Connection refused connect: Connection refused error: stat of /root/.chia/farmr/log*txt failed: No such file or directory error: stat of /root/.chia/farmr/log*txt failed: No such file or directory error: stat of /root/.chia/farmr/log*txt failed: No such file or directory error: stat of /root/.chia/farmr/log*txt failed: No such file or directory error: stat of /root/.chia/farmr/log*txt failed: No such file or directory error: stat of /root/.chia/farmr/log*txt failed: No such file or directory error: stat of /root/.chia/farmr/log*txt failed: No such file or directory error: stat of /root/.chia/farmr/log*txt failed: No such file or directory error: stat of /root/.chia/farmr/log*txt failed: No such file or directory error: stat of /root/.chia/farmr/log*txt failed: No such file or directory error: stat of /root/.chia/farmr/log*txt failed: No such file or directory error: stat of /root/.chia/farmr/log*txt failed: No such file or directory error: stat of /root/.chia/farmr/log*txt failed: No such file or directory /usr/lib/python3.9/threading.py:233: RuntimeWarning: coroutine 'HarvesterAPI.new_signage_point_harvester.<locals>.lookup_challenge' was never awaited self.acquire = lock.acquire RuntimeWarning: Enable tracemalloc to get the object allocation traceback

Is there an issue with Maize coin farming? I've been farming it since it was added in Machinaris, and the GUI tells me Expected time to win is around a day, yet after weeks, I have only won 2.5 maize coins. I farm all the coins, and the rest are behaving as expected... Is this normal, and the time to win is just out of whack?

I think I've found the issue. It looks like the chiadog config for the Cactus fork somehow got duplicated in the Chia chiadog config. I'm pretty sure I didn't do it, but can't say for sure as I was in there yesterday trying to get the smtp alert working.... though I was doing that because it had already gone offline...... Anyhow, I believe this issue can be marked as solved as I copied over the correct config and the repeating error has stopped. I assume the offline messages will stop as well...

I'm on the newest version and I'm getting some weird Alert behaviour. I keep getting a 'Chia is offline' error, under the Alert page, but the Blockchain shows fully synced, and I have 82 connections in the Connections tab. Also, none of the other forks are showing the error... Also, probably unrelated, but I'm seeing a repeating error in my chia log:

Sounds like a plan! I will leave Silicoin disabled until further notice!

Thanks for this! One issue. Cactus and Silicoin seem to be using the same port. Since Silicoin is not working, I can just disable it for now, but if it ever gets up and running, there will be a conflict... Can we manually assign a new port, or is it something you need to do?

Thanks for the tip! I had this issue, but your suggestion fixed it for all but staicoin. It is still giving me a parameter error. Also, now that we are using a path to the 'master' mnemonic, do we delete the actual key in each fork? Replace it with the folder of the same name (like in staicoin), or am I getting ahead of myself? Thanks again for your awesome work!

Just wanted to report that I have all the alternative coins farming without a hitch (Well, I forgot to copy the key to the flora folder at first, but I figured it out ). Thanks again @guy.davis This is an awesome Docker and a HUGE help with this whole farming thing !!!

Ah! Got it! Thank you! Hypothetically speaking, due to limited space and trying to be efficient, if I were to recreate all my existing plots and set them k29, k30 or k31, would I see any negative effects on the other coins being farmed?