Einsteinjr

Latest issue with the webui not starting can be fixed here: https://github.com/linuxserver/docker-qbittorrent/issues/432 It was an upstream issue.

Thanks for this 2 years later. I have a unique set up where I have 48 4TB SSDs (ZFS) on an hba in a server that was built in 2017. My performance was 1/4 of what a single SSD drive should perform at and it took me an embarrassingly long time to figure out the FUSE was the bottle neck. I wish I could upgrade since the chassis is great (2U). Super micro is proprietary though so I can't just slap an AMD Milan generation board. Single core performance is critical for my set up.

Same for me, as well! Running 6.12.10. I've tried using a global "0" and all 18 of my drives get alerts. Ridiculous that this isn't being addressed or at least a bug hasn't been assigned.

FYI - for a while now, I've been getting much higher skipped SPs than normal (>20%). Did a bit of research and debugging the logs and found that modifying [machinaris.Config]/mainnet/config/config.yaml file fixed the issue. target_peer_count needs to be changed from 80 to 20 and the errors I was seeing seemed to have disappeared and the skipped rates is <1%.

CPU usage is going to depend on the age and power of your CPU but the RAM usage is expected. Apparently reducing the Node targets would help with the memory usage but I don't know if Machinaris supports that. There's lots of online material talking about how much memory Chia farming consumes - it needs to load the database in memory and is not a unique problem to just Machinaris. FWIW, I have a 64 core CPU @ 2400mhz running Chia + 10 forks tagged to just 8 cores in the docker and I never see the CPUs spike to 100%. Usually 0-60%. I'm guessing you have an old CPU?

If anyone was wondering if there was any power difference between splitting the different harvesters onto the same CPU cores, there isn't a lot. (<2%) Currently running (for testing) a 64 core AMD EPYC processor. I put all the dockers on 4 cores (and its corresponding hyperthread) and it had just a small decrease in power usage. (about 4 watts). Related, 4 cores/8 threads seems plenty for ALL the harvesters to run on.

Anybody else have their x265 transcoding suddenly stop working? I have an nVidia T600. Running the latest driver (530.41.03) with the BinHex container. Currently on the RC5 build of 6.12.0 which I think may be related since it seemed to coincide when I upgraded? What's strange is that my GPU dashboard tool shows that a PlexTranscoder tool running inside the docker is holding onto a GPU transcode instance when I try to transcode a 4K x265 file - but the amount of RAM being used is much less than normal when doing a 4K video. (300MB vs. 30MB) Here are the logs from Plex that show the error: May 12, 2023 12:03:43.404 [22944562506552] ERROR - [Req#8228/Transcode] [FFMPEG] - Failed to initialise VAAPI connection: -1 (unknown libva error). May 12, 2023 12:03:43.404 [22944562506552] DEBUG - [Req#8228/Transcode] Codecs: hardware transcoding: opening hw device failed - probably not supported by this system, error: I/O error log.txt

Profit probably needs to be removed. I can't start a timelord server either. 2023-03-27T14:02:00.730 timelord profit.timelord.timelord : ERROR Not active for 60 seconds, restarting all chains 2023-03-27T14:02:00.730 timelord profit.timelord.timelord : INFO reset_chains new_unfinished_blocks: 0

Is it just me or do at least 1 or 2 appear to me out of sync at any given time for anyone else? Currently Ecostake, Petroleum, Profit, and Tad are all out of sync. =/ I wonder if I'd have better luck if my ISP supported ipv6.

I've done the same thing using an unassigned SSD drive. Just stop the containers, move the appdata folders over to the new location, update the appdata location in each container, and start containers back up. As long as you make the root path consistent, it's easy.

FYI Moon is missing for the Community Plugin. As always, thanks!

Same Issue: 2022-11-09T09:54:22.051 farmer flax.farmer.farmer : WARNING No keys exist. Please run 'flax keys generate' or open the UI. I even deleted the entire app-data for this container and redownloaded the DB.

I think the Flax test build is broken. When I start it, it says it cannot find the key and therefore sits in the "paused" state in the machinaris webgui. It just started happening since I updated to the latest test build.

So maybe I didn't need to upgrade to farm them all! Thanks for the update!

I've been blindly installing the TEST build for all the different dockers but I don't know which of the dockers need to have their database upgraded to save disk space. A cool new feature might be a tool that at least identifies which of the dockers need to be upgraded with the new datastore. v2 could be the actual upgrading process.