• Posts

  • Joined

  • Last visited


  • Gender
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

jaj08's Achievements


Apprentice (3/14)



  1. Skipped over this portion of the reply this morning. I would say I'm doing Chia the way the developers said to, I am utilizing spare resources I have laying around the office. With that, installing a small/not obtrusive harvester exe seems harmless and low key. But installing docker service on each server starts to get a little more intrusive on office utilized equipment. Several of my harvesters are also 2012r2 servers which I believe by default do not support Dockers. I do have a couple backup only 2016 servers maybe I will see if I can expand an instance or two to those.
  2. Actually both are full nodes, but I assume the bug is the same as far as how the workers are communicating.
  3. Loving the remote workers to consolidate everything to a single interface. Wish Machinaris could be a stand alone install for all my windows remote harvesters I have running. With that, I want to report my estimated time to win has the wrong info. If I compare to Chia calculator it seems like the expected time to win is using a remote worker instance to calculate my time to win, and not combining the estimate with the primary instance. This setup has the primary +1 remote full node. 639 total plots, chia calc 4 months 166 on the remote worker, chia calc about 1 year 473 on the primary instance, chia calc 5 months Machinaris expected time to win: 1 Year
  4. Thought I report a little anomaly I just experienced, when I updated the latest docker, on startup, my databases showed not in sync anymore, like back to March when Mainnet launched date. Looking at the file sizes of the DB files they were still 4gb, so the data wasn't lost, but for some reason the docker went back in time and was trying to sync from scratch. I restarted the docker same results, luckily I manage multiple docker instances so I copied the db folder from my other instance over and got things happy again. My other 4 instances all upgraded without issues.
  5. So I see Chiadog's official recommendation for monitoring multiple harvesters is to spin up multiple Chiadog instances, similar to what you suggested with multiple dockers. https://github.com/martomi/chiadog/wiki/Monitoring-Multiple-Harvesters Multiple machinaris dockers though spins up by default a lot more services than necessary unless of course someone simply comes up with a Chiadog dedicated docker for unraid. So I am wondering, any chance you can add support and a variable for multiple chiadog instances? Perhaps a variable where we can specify how many instances we require. And then from your primary Interface you would then have Alert1 Alert2 Alert3 sections in the GUI with different configuration files for each instance number. Ideally Alert# can be named something custom so we can label each server being monitored. My home setup works perfect with machinaris, but my office setup has a total of 8 or so remote harvesters split between two locations.
  6. Is there anyway for the main summary page to show the hash challenges for harvesters connecting to the node like the normal GUI does. As I glance through the log I am guessing the answer is no, but it would be awesome if showed the plots passed status of the connecting harvesters. I think I will dabble with having multiple dockers running so that Chia dog can point at each of my harvesters for reporting. That plus pushover notifications or something should help things out. Love the new release! Update: I have 2 dockers running, with the log file overwriting from a remote harvester, but at a glance it looks like this band-aid doesn't work for Chiadog. I don't think Chia dog is expecting to see the log of a harvester as it doesn't pull out the number of plots processing time info like it does on a Full node log. Seems like the best solution for monitoring remote harvester logs will be to get the Chiadog developer to add this officially as a feature.
  7. As I eagerly await the next release to monitor logs, I was wondering if from the Docker environment I will be able to monitor logs located on a Windows system? Really hoping to have a single interface/location to keep an eye on everything. As I hit the 1400 plot mark with 0XCH it is frustrating so I keep wasting time auditing log files and such to ensure everything seems happy.
  8. Just to update, but fixing time zone ended up not fixing my syncing issues. In a way that makes sense, as time was proper, just wrong Timezone, and why would chia be broken in specific time zones? Any way, for now I was forced to migrate my full node back over to my Windows Desktop where I have been synced all day without issues. For now the docker is strictly a harvester for me.
  9. Woohoo, apt-get install systemd and following the setup worked for me. I restarted the docker for good measure, made sure time zone was right, and almost immediately went back to showing a synced status. I had things drop out of sync the other day but simply restarting the docker seemed to fix that problem. Hopefully now I can stop fiddling with the docker so I can earn some chia... I currently have 124 @home, and 632 at the office, but still a member of the 0XCH club.
  10. Since migrating to my docker being the full node I have had random times where I drops back into syncing mode. Now that I read your comment I have also noticed the Timezone is clearly wrong in my docker as well. So what's the fix?
  11. So in the above case I am then having the service run directly on unRAID? Seems like ideally would love to see this moved over to a docker setup now that the tunnel service is free.
  12. Any reason why my docker keeps telling me an update is available, appears to apply the update, and then goes back to update available? Overview of what I see when applying the update, looks like everything seems to go ok TOTAL DATA PULLED: 251 MB Successfully stopped container 'binhex-plexpass' Successfully removed container 'binhex-plexpass' The command finished successfully!
  13. Am I overlooking a setting somewhere, or is there no setting to adjust how frequently the pings are done? Would love to increase the frequency to check smaller bits of packet loss and latency.
  14. Did ICMP ever issue ever get resolved? I am seeing the Not Permitted message and my install defaulted to the --user 99:100 advanced config.
  15. jaj08


    +1 Something I never really considered until we were all stuck in quarantine, but I can see where this would be useful vs Zoom's 40 minute limitation on free accounts.