TheNotoriousFlow

Good Morning @guy.davis, thanks for your latest release. Is it possible that for cryptodoge there is a bug regarding the used port? According to the cryptodoge docker template Port 15994 needs to be opened in the FW, but i didnt get any peer connections over night. For curiosity i ran the "check port forwarding" on the cryptodoge connections page, which is pointing me to https://www.yougetsignal.com/tools/open-ports/?port=9699. anything wrong here? Regards from Austria!

@guy.davis thanks for your reply. in the meantime i checked our last conversation months ago in this thread and also the cleaning of machinaris.db did the trick last time. already did that, the phantom records are gone. many thanks and as always KEEP UP THAT GOOD WORK. adding the additional coin containers now one by one. working like a charm

hi @guy.davis, since the update today i have 2 issues so far. I got two chia tabs in the connections tab and an error message appears on clicking to connections: also 2 tabs of chia appear when i click on blockchain. When i click on wallet, i see all of a sudden two wallets which seem to be the same. One is outdated (not synced) with the sync date when i updated the container. the other one seems to be synched with current date. any advise? i did follow the upgrade advisory. regards Florian

Hi again, you were totally right. after 5-6h the messages about the harvester dissappeared and the chiadog is working correctly now. Thanks for pointing me into the right direction. Keep up the good work! Regards from Austria

MANY THX FOR YOUR QUICKSUPPORT. with your help i managed to solved issue #1 with the missing challenges. From the original chia docker i was used to set log_stdout to true for the unraid docker log function to work. this was set now to false again -> restarted docker and the challenges arrived! Very nice. But i am still struggeling with Chiadog, still showing " Your harvester appears to be offline! No events for the past XXX seconds. ". I checked the following settings, see below: chia_logs: file_log_consumer: enable: true file_path: '~/.chia/mainnet/log/debug.log' and script: # DON'T CHANGE THIS SCRIPT NOTIFIER, IT'S USED BY MACHINARIS! enable: true daily_stats: true wallet_events: true script_path: '/root/.chia/chiadog/notifier.sh' I already received notifications via Telegram, but the daily summary also shows as follows: Hello farmer! 👋 Here's what happened in the last 24 hours: Received ☘️: 0 XCH Proofs 🧾: None Search 🔍: - average: 0.00s over 0 searches - over 5s: 0 occasions (0.0%) - over 15s: 0 occasions (0.0%) Plots 🌱: 0 Eligible plots 🥇: None Skipped SPs ⚠️: Unknown Seems like chia dog doesnt read the debug... Regards!

Hi @guy.davis, i am overwelmed what you did with Machinaris and i love especially the last update which truely enhances the farming/plotting experience. I updated yesterday to 3.0 and stumbled upon the issue that i constantly get alerts that the harvester seems to be offline, but to my view everything is up and running. Secondly i dont see current challenges, only some old ones from may 24. I already changed the log level from info to debug in config.yaml for the chiadog. but i dont get a clue. could it be that there is an access problem only for chiadog resulting in accessing logfiles from plotting//farming? Any good approaches where to start and look for? Regards