Jump to content

adminmat

Members
  • Posts

    347
  • Joined

  • Last visited

Posts posted by adminmat

  1. When i run a chia farm summary it returns Farming status: Farming.

    And chia show -s -c returns Current Blockchain Status: Full Node Synced.

    chia wallet show returns Sync status: Synced

     

    Does this mean that I'm properly connected to the "netspace"? even though I have not opened any ports on my router.
     

  2. On 4/20/2021 at 6:02 PM, SavellM said:

    Hey all,

     

    I'm looking for a way to view the current read/writes and MB/s to a specific Unassigned Device.

    Basically I have started to do Chia plotting, and found a way to get it running via docker, but I want to monitor the disk I/O to see if its running faster than in a VM. 

     

    Is there any app or anything I can run to see how my drive I/O and general server is performing?

     

    Have you found something suitable? 

     

    I've been using dstat. Specifically dstat -pcmrd

     

    You can install this with Nerd Pack. Gives you a decent (although I don't completely understand it) view of I/O. 

    I was also using top or htop to watch my CPU utilization. As the unRAID dashboard isn't the bet metric. top will tell you how many tasks are waiting for a CPU. I think this can help you tune your plotting better than just a graph. 

     

    I'm going to try out Swar next. 

     

  3. On 5/10/2021 at 10:18 AM, tjb_altf4 said:

    Out of the box this docker isn't configured optimally for logging, after some research these are two changes I've made to get better logging.

    Both changes are made to the config.yaml file that will be in chia's appdata folder:

    1. change log_level to INFO (from WARNING) 
    2. change log_stdout to true (from false)

    Change one adds more useful info to the logs, change two pushes the logs to the standard docker logging mechanism, which means it is visible from the GUI's log button.

     

    Happy hunting!

     

    I've made these changes to my config.yaml but I'm still not seeing any progress in my debug.log, only many warnings and errors.

     

    I've been getting spammed with these two errors:
    2021-05-11T19:38:45.339 full_node chia.full_node.full_node: WARNING  Wasn't able to add transaction with id....., status 3 error: Err.DOUBLE_SPEND

     

    2021-05-11T19:46:01.312 full_node chia.full_node.full_node: ERROR    Consensus error 124, not disconnecting

     

    Any idea why I see no status of plotting updates in the log? or what these errors mean? I've been successfully plotting (6 plots) prior to this.

  4. I have this up and running although I didn't use the CA template.  I have a few questions:

     

    - How do I view logs? and how do I view progress of ongoing plotting?

    - when i do a:

    Quote

    # docker exec -it chia venv/bin/chia show -s

     

    I get:

     

    Quote

    Current Blockchain Status: Full Node syncing to block 261754
    Currently synced to block: 248900
    Current Blockchain Status: Not Synced. Peak height: 248900

     

    Why is the Blockchain Status not synced? Do i have to open a port on my router or forward a port to this Docker container?

     

  5. 3 hours ago, strike said:

    You can add or remove a subdomain to trigger the renewal process. If it fails again be sure to set the staging variable to "true", this will increase the rate limiting so you don't hit the limit when testing. Set it back to false when you have it working. 

    ok, looks like it issued the new cert. I just removed the "server" domain and changed to True. Applied. Then re-added "server" changed back to false and applied. Thanks 

  6. 5 hours ago, saarg said:

    The Cron job runs every night at about 2.

    You have to check the logs for why it's not renewing the certs. I think the log is named letsencrypt. Also restart the container and post the log. Be sure to redact domain and personal info.

     

    I found in the log that it was not resolving the DNS for server.mydomain.com (example). I didnt have "server" added as a Cname. Only Nextcloud. I assume it needs this for the cert renewal. I So I added this within the Namecheap DNS section. (sorry I don't know the proper terminology here)  Now is there a way to manually renew or I just wat for the chron job at 2AM again? I confirmed that restarting the Swag container does not renew the cert. 

     

     

  7. 6 minutes ago, ich777 said:

    This process starts if you turn on the Advanced View (to show the CPU und RAM usage from your containers) on the Docker page and won't go away if you switch back to the Basic View (even if you logout or close the WebGUI).

     

    ok. So those process are still running but just not consuming as much resources when showing the basic view. So I guess nothing to be concerned about. I probably check my logs for errors a little too much. This was actually the first time I've run an htop... when I was troubleshooting the wsdd network today issue that had one CPU core at 100%.

  8. On 10/13/2020 at 2:00 PM, ich777 said:

    @LSL1337 & @INTEL

    Try to disable 'Advanced View' on the docker page and report back, I bet it will be the solution. ;)

     

    Found a few of these listed when running an htop:
     

    containerd --config /var/run/docker/container/containerd.toml --log-level error unraid

     

    Not sure if it was of any concern but it did cost about 4% of my CPU. Switching to basic view immediately remedied this. Thanks for that.

     

    But is that "error" process an issue?

     

     

     

  9. 17 minutes ago, anethema said:

    How does this actually work in practice though. If Pihole etc is on a different network VLAN how do your computers on your network see it ?

     

    It depends on how your router treats VLAN networks. My Edgerouter, by default allows communication across VLANs by default unless you add firewall rules to segregate them. Other routers may be different. 

     

    17 minutes ago, anethema said:

    Also do you know if this problem occurs if you set the network of the container to br0 but then leave it to grab an IP via DHCP ? If so I could just put an entry in the DHCP table instead.

     

    Yes, for me it still occured when my router was providing DHCP for the containers on br0.

  10. Also have a couple instinces of this in my log:

     

    Feb 14 04:40:01 Tower apcupsd[26901]: apcupsd exiting, signal 15
    Feb 14 04:40:01 Tower apcupsd[26901]: apcupsd shutdown succeeded
    Feb 14 04:40:04 Tower apcupsd[6799]: apcupsd 3.14.14 (31 May 2016) slackware startup succeeded
    Feb 14 04:40:04 Tower apcupsd[6799]: NIS server startup succeeded

     

    Maybe this happened when the apcupsd plugin was updated? Did you find anything out?

  11. Yep, this is what I'm doing. I have a couple Pis laying around. 

     

    With my google Pixel 5 it doesn't automatically choose the other DNS even if it's set in my Edgerouter. You have to set a fixed ip in Android settings. Then it won't revert back to the Pihole's dns after it comes back online. I'm really curious what everyone does who uses pihole on unRAID. Maybe most people won't run Backup/restore as frequent as I do? 

    Doesn't seem like a good fit to run on unRAID. 

  12. I've been trying to find a solution for this all day. I'm not sure if this belongs in the Pihole or Backup/Restore thread. Every night when backup/restore begins all my clients taking advantage of pihole lose internet.(DNS resolution) Yes I use my internet at 3:45am when this happens. Then in the morning you have to manually reset the network settings on some clients to reach pihole.

     

    Specifically with Android and Edgerouter this is a huge pain. As you can't set a failover DNS server. Not sure on Apple ios. Actuall you can set a failover DNS on android but when Pihole comes back online you have to basically delete your DNS settings in Android and reenter. Huge pain in the rear. I guess the only solution is to take PiHole off of unRAID and run it on a dedicated Raspberry Pi? 

  13. 22 minutes ago, Hoopster said:

     

    Quote

    Docker has no idea about the existence of your router based DHCP server and does not communicate with it.  If you want to do DHCP with docker containers, the VLAN from the unRAID/docker side needs it own IP address range.  I don't even deal with that and just assign static IP address to docker containers within the range I told it to use which is outside the range of DHCP addresses I let my router assign (so there are no conflicts).

    Got it. I have the Docker containers set to static IPs within VLAN60. And I just limited my router's IP range for VLAN60. Which I now understand as I just had to add my HDHomerun to that network and I can see how it could create a conflict.

     

    22 minutes ago, Hoopster said:

     

    Quote

    I don't know if this, by itself, could cause the issue.  I had the call trace issues long before that option even existed.  I do currently have it disabled and have never enabled that option.  There are some reports of networking/router issue with it enabled, but, those just may be DHCP conflicts.

    I have since disabled it. I can't remember the reason I needed it now.

     

    This is great. I'm glad I got this sorted. Fingers crossed that I don't have any more issues. 🤞 You don't have to have an HDHomerun that you are using across the VLANs?
     

    Thanks for all the help

  14. Ok @Hoopster, little update. I was able to get my docker containers working again. Set up br0.50 for VMs and br0.60 for Docker. Added the VLANs on my Edgerouter. Tagged the ports on the switch, updated each container and I'm up and running. Couple question:

     

    - The way I understand it, my router wont be handing out DHCP leases for Docker containers like it does for VMs? (I'm so confused how Docker works)

    - Do I have to completely segregate the VLANs with firewall rules to keep the Call Trace issue from happening?

    - Should I delete/disable br0 completely?

    - I have "Host access to custom networks" set to "Enable." I think I need this for Nextcloud to work (?) Will this cause the macvlan issues?

×
×
  • Create New...