bmrowe

Members
 View Profile  See their activity

  • Posts

    25

  • Joined

  • Last visited

Recent Profile Visitors

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

bmrowe's Achievements

Noob

Noob (1/14)

0

Reputation

2

Community Answers

  1. bmrowe
    An update - I changed several things: -I updated my DHCP server to only share out IPs in the .200-250 range thinking that perhaps there was an IP address conflict despite having IPs reserved for most clients including unraid. -I have had issues with dockers talking to eachother and had added a script to check if the unraid shim was in place, and if not, add it. I disabled this script. -I disabled netdata, cadvisor, and the prometheus exporter for adguard. I did this primarily because there was so much network chatter it was hard to troubleshoot w/ wireshark None of these changes solved the problem. However, I noticed CPU use was pretty high and the top two processes were firefox-bin being launched from the /tmp/ directory. I had no clue what this process was, so I decided to restart. Since restarting, this issue has not reoccured once. I'm not sure which change, if any, fixed this problem - but I wanted to share the latest.
  2. bmrowe
    Thanks for chiming in. I might be missing a setting, but I have this configured in network: I'll do a basic rundown of my network too: 192.168.1.1 is my router 192.168.1.3 is an adguard home docker running as DNS 192.168.1.24 is a pi hole docker running as secondary DNS 192.168.1.13 is an unbound docker running as upstream DNS for both adguard and the pi hole. Here is the config in the router: Finally, I will also add that when unraid is unreachable on one pc, it may still be reachable on another.
  3. bmrowe started following Updated CPU and motherboard, now constant restarts , Can't ping or access unraid unless I remove entry from arp table and Replaced drive, now not all SMB shares showing up
  4. bmrowe
    I have a super weird issue where my unraid server will frequently become inaccessible from any computer on the network. The web gui will not be accessible and pings will fail. All dockers are still accessible, only unraid itself it impacted. This will only be resolved by either removing the entry in the arp table for the ip address of the unraid server, or turning wifi off and back on for a client. I have also verified that the router cannot ping unraid during these outages. I've made a few changes lately - adding nginx as an internal proxy to avoid memorizing ip/port combos, and sonarr/radarr/prowlarr/overseerr. I don't see how either would be impacting this. Thoughts? Attaching diagnostics. unraid-diagnostics-20231107-1714.zip
  5. bmrowe
    I am having a weird issue with, what has been, a working Adguard Home install on unraid. The symptom I see is that on computers with adguard home as the DNS provider, they will occasionally stop being able to get to any app hosted on docker within unraid, including unraid itself, until I turn their wifi off and back on. While a device has no access, I can ping adguard home, but get no ping response when I ping unraid. I also see some weird connectivity issues within unraid: -I cannot access the console of adguard home docker from the web ui. I get this error: Nov 8 11:45:29 unraid nginx: 2023/11/08 11:45:29 [error] 7285#7285: *696028 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.184, server: , request: "GET /logterminal/AdGuard-Home/ws HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/ws", host: "192.168.1.198" Adguard-exporter will work for hours and then randomly: 2023/11/08 10:05:10 An error has occurred during login to AdguardGet "http://192.168.1.3:80/control/status": dial tcp 192.168.1.3:80: connect: no route to host I have made a couple changes to the system recently. Primarily adding nginx as an internal reverse proxy (basically to give friendlier names to things that you had to memorize the port on). I also added radarr/sonarr/prowlarr/overseerr. Those all are working fine. Edit: Some updates on testing - if I remove the entry for the unraid server ip from the arp table on the client, things go back to normal. I'm way beyond my depth with networking at this point - what could be causing this to be required? Attaching diags as well. Appreciate the help in advance. unraid-diagnostics-20231108-0952.zip
  6. bmrowe
    Reporting back. Nothing changed here. I was fixing up some VMs and thought to retry connecting. The media share showed up. Super weird. The only thing I can think of is that there were file not found errors being thrown because I lost a couple .iso files that were stored on the array. I replaced those files as part of fixing up a couple VMs. I don't see how that could have fixed it, but sharing for potential future searches.
  7. bmrowe
    I can do that. That would be a weird occurrence for a brand new drive, right?
  8. bmrowe
    Sure. unraid-diagnostics-20231029-2147.zip
  9. bmrowe
    I replaced a hard drive and now only two of my three shared SMB folders (all three are user shares) are showing up. 'media' is the missing share. I see appdata and isos. I have done the following so far: Double checked global share settings: Double checked user share setting to make sure export is on for the media share: Despite this, I only see appdata and isos but not media: I thought maybe permissions related, but I'm a bit out of my depth there. Things seem (?) fine:
  10. bmrowe
    Following up on this. Replaced motherboard - same issue. However, I tried the new power supply and it worked! I'm super confused how a power supply could fail at the exact time I was replacing other parts. Has to somehow be connected, right? I thought maybe cable related and a cable got pinched while doing the install, but I used the old cables with the new power supply.
  11. bmrowe
    I've got a replacement motherboard coming tomorrow and I ordered an extra power supply to test. I can't imagine its the CPU, but that would be the last possible thing. I don't have a way to boot in legacy since this motherboard needs a graphics card to enable legacy boot and I just use the igpu.
  12. bmrowe
    I updated a working system to an ASUS TUF b760M D4 and an intel 13500 (from an 11500 and b560m motherboard). Things look fine in bios, and I can leave the machine in bios forever. However once I boot to unraid, the system will restart after exactly 15 seconds and do this over and over. I think I've eliminated most potential hardware issues - I've simplified the system down to just the motherboard and CPU. I've tried GUI mode and safe mode, and all restart in 15s. The memtest sends it back to the bios splash screen. I tried a random distro of linux on a different USB. Same issue occurred once I booted into it. I also tried a fresh download of unraid, same problem. Any ideas on things to try or what might be happening?
  13. bmrowe started following {6.10.3} AdguardHome docker container randomly stopped in the middle of the night and Lost Access to Host from Docker on Custom br0 after reboot
  14. bmrowe
    Just experienced this myself on 6.12.3 so the bug is definitely not 'closed'. Power outage and battery backup failure led to a non-clean shutdown. Upon restart, this bug was present. Stopping and starting docker fixed the problem. But took me hours of troubleshooting to find this post. Please reopen bug and fix.
  15. bmrowe
    Hi all, Recently upgraded to 6.10.3. My containers and system have been remarkably stable in general. However, last night when my auto-update process started at 2am a few errors were thrown that included my DNS server AdguardHome being taken offline and not restarted. syslog below and diagnostics attached. Ideas on what might have happened? Thanks! Jun 21 02:00:01 unraid Plugin Auto Update: Checking for available plugin updates Jun 21 02:00:01 unraid Docker Auto Update: Community Applications Docker Autoupdate running Jun 21 02:00:01 unraid Docker Auto Update: Checking for available updates Jun 21 02:00:18 unraid Plugin Auto Update: Community Applications Plugin Auto Update finished Jun 21 02:00:26 unraid Docker Auto Update: Stopping prometheus Jun 21 02:00:26 unraid kernel: docker0: port 2(veth34aee03) entered disabled state Jun 21 02:00:26 unraid kernel: veth24aca89: renamed from eth0 Jun 21 02:00:27 unraid avahi-daemon[5679]: Interface veth34aee03.IPv6 no longer relevant for mDNS. Jun 21 02:00:27 unraid avahi-daemon[5679]: Leaving mDNS multicast group on interface veth34aee03.IPv6 with address fe80::78ab:54ff:fece:1bbd. Jun 21 02:00:27 unraid kernel: docker0: port 2(veth34aee03) entered disabled state Jun 21 02:00:27 unraid kernel: device veth34aee03 left promiscuous mode Jun 21 02:00:27 unraid kernel: docker0: port 2(veth34aee03) entered disabled state Jun 21 02:00:27 unraid avahi-daemon[5679]: Withdrawing address record for fe80::78ab:54ff:fece:1bbd on veth34aee03. Jun 21 02:00:27 unraid Docker Auto Update: Stopping netdata Jun 21 02:00:30 unraid Docker Auto Update: Installing Updates for prometheus netdata Jun 21 02:00:50 unraid Docker Auto Update: Restarting prometheus Jun 21 02:00:50 unraid kernel: docker0: port 2(veth5772f77) entered blocking state Jun 21 02:00:50 unraid kernel: docker0: port 2(veth5772f77) entered disabled state Jun 21 02:00:50 unraid kernel: device veth5772f77 entered promiscuous mode Jun 21 02:00:51 unraid kernel: eth0: renamed from veth62cf8ca Jun 21 02:00:51 unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth5772f77: link becomes ready Jun 21 02:00:51 unraid kernel: docker0: port 2(veth5772f77) entered blocking state Jun 21 02:00:51 unraid kernel: docker0: port 2(veth5772f77) entered forwarding state Jun 21 02:00:51 unraid Docker Auto Update: Restarting netdata Jun 21 02:00:51 unraid sSMTP[18423]: Creating SSL connection to host Jun 21 02:00:51 unraid sSMTP[18423]: SSL connection using TLS_AES_256_GCM_SHA384 Jun 21 02:00:51 unraid nginx: 2022/06/21 02:00:51 [error] 5166#5166: *4520115 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?auto HTTP/1.1", host: "localhost" Jun 21 02:00:51 unraid nginx: 2022/06/21 02:00:51 [error] 5166#5166: *4520116 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?auto HTTP/1.1", host: "127.0.0.1" Jun 21 02:00:51 unraid nginx: 2022/06/21 02:00:51 [error] 5166#5166: *4520117 open() "/usr/local/emhttp/status/format/json" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status/format/json HTTP/1.1", host: "127.0.0.1" Jun 21 02:00:52 unraid avahi-daemon[5679]: Joining mDNS multicast group on interface veth5772f77.IPv6 with address fe80::88e0:dbff:fe45:d01c. Jun 21 02:00:52 unraid avahi-daemon[5679]: New relevant interface veth5772f77.IPv6 for mDNS. Jun 21 02:00:52 unraid avahi-daemon[5679]: Registering new address record for fe80::88e0:dbff:fe45:d01c on veth5772f77.*. Jun 21 02:00:52 unraid nginx: 2022/06/21 02:00:52 [error] 5166#5166: *4520127 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status HTTP/1.1", host: "localhost" Jun 21 02:00:52 unraid nginx: 2022/06/21 02:00:52 [error] 5166#5166: *4520128 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status HTTP/1.1", host: "127.0.0.1" Jun 21 02:00:52 unraid nginx: 2022/06/21 02:00:52 [error] 5166#5166: *4520129 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: ::1, server: , request: "GET /status HTTP/1.1", host: "[::1]" Jun 21 02:00:53 unraid sSMTP[18423]: Sent mail for {REDACTED}(221 2.0.0 closing connection d11-20020a05622a15cb00b00304fe5247bfsm12495826qty.36 - gsmtp) uid=0 username=root outbytes=713 Jun 21 02:00:53 unraid Docker Auto Update: Community Applications Docker Autoupdate finished Jun 21 02:01:11 unraid nginx: 2022/06/21 02:01:11 [error] 5166#5166: *4520330 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /admin/api.php?version HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "127.0.0.1" Jun 21 02:01:11 unraid nginx: 2022/06/21 02:01:11 [error] 5166#5166: *4520332 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /admin/api.php?version HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "localhost" Jun 21 02:01:12 unraid nginx: 2022/06/21 02:01:12 [error] 5166#5166: *4520336 open() "/usr/local/emhttp/basic_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /basic_status HTTP/1.1", host: "127.0.0.1" Jun 21 02:01:12 unraid nginx: 2022/06/21 02:01:12 [error] 5166#5166: *4520337 open() "/usr/local/emhttp/stub_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /stub_status HTTP/1.1", host: "localhost" Jun 21 02:01:12 unraid nginx: 2022/06/21 02:01:12 [error] 5166#5166: *4520338 open() "/usr/local/emhttp/stub_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /stub_status HTTP/1.1", host: "127.0.0.1" Jun 21 02:01:12 unraid nginx: 2022/06/21 02:01:12 [error] 5166#5166: *4520339 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status?full&json HTTP/1.1", host: "localhost" Jun 21 02:01:12 unraid nginx: 2022/06/21 02:01:12 [error] 5166#5166: *4520340 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status?full&json HTTP/1.1", host: "127.0.0.1" Jun 21 02:01:12 unraid nginx: 2022/06/21 02:01:12 [error] 5166#5166: *4520341 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: ::1, server: , request: "GET /status?full&json HTTP/1.1", host: "[::1]" Jun 21 02:01:12 unraid nginx: 2022/06/21 02:01:12 [error] 5166#5166: *4520342 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?format=plain HTTP/1.1", host: "localhost" Jun 21 02:01:12 unraid nginx: 2022/06/21 02:01:12 [error] 5166#5166: *4520343 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?format=plain HTTP/1.1", host: "127.0.0.1" Jun 21 02:01:12 unraid nginx: 2022/06/21 02:01:12 [error] 5166#5166: *4520344 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?auto HTTP/1.1", host: "localhost" Jun 21 02:01:12 unraid nginx: 2022/06/21 02:01:12 [error] 5166#5166: *4520345 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?auto HTTP/1.1", host: "127.0.0.1" Jun 21 02:01:12 unraid nginx: 2022/06/21 02:01:12 [error] 5166#5166: *4520346 open() "/usr/local/emhttp/us" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /us HTTP/1.1", host: "localhost" Jun 21 02:01:12 unraid nginx: 2022/06/21 02:01:12 [error] 5166#5166: *4520347 open() "/usr/local/emhttp/us" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /us HTTP/1.1", host: "127.0.0.1" Jun 21 02:15:48 unraid sshd[7843]: Connection from 192.168.1.11 port 50229 on 192.168.1.131 port 22 rdomain "" Jun 21 02:15:48 unraid sshd[7843]: error: kex_exchange_identification: Connection closed by remote host Jun 21 02:15:48 unraid sshd[7843]: Connection closed by 192.168.1.11 port 50229 Jun 21 03:15:56 unraid sshd[24129]: Connection from 192.168.1.11 port 51410 on 192.168.1.131 port 22 rdomain "" Jun 21 03:15:56 unraid sshd[24129]: error: kex_exchange_identification: Connection closed by remote host Jun 21 03:15:56 unraid sshd[24129]: Connection closed by 192.168.1.11 port 51410 Jun 21 04:15:36 unraid sshd[7095]: Connection from 192.168.1.11 port 52587 on 192.168.1.131 port 22 rdomain "" Jun 21 04:15:36 unraid sshd[7095]: error: kex_exchange_identification: Connection closed by remote host Jun 21 04:15:36 unraid sshd[7095]: Connection closed by 192.168.1.11 port 52587 Jun 21 05:15:29 unraid sshd[23170]: Connection from 192.168.1.11 port 53781 on 192.168.1.131 port 22 rdomain "" Jun 21 05:15:29 unraid sshd[23170]: error: kex_exchange_identification: Connection closed by remote host Jun 21 05:15:29 unraid sshd[23170]: Connection closed by 192.168.1.11 port 53781 Jun 21 06:12:30 unraid kernel: veth00ad854: renamed from eth0 Jun 21 06:12:31 unraid sSMTP[9211]: Creating SSL connection to host Jun 21 06:12:31 unraid sSMTP[9211]: SSL connection using TLS_AES_256_GCM_SHA384 Jun 21 06:12:35 unraid sSMTP[9211]: Sent mail for [email protected] (221 2.0.0 closing connection h4-20020a05620a400400b006a6d4261f40sm16111695qko.111 - gsmtp) uid=0 username=root outbytes=4268247 Jun 21 06:15:50 unraid sshd[7063]: Connection from 192.168.1.11 port 54976 on 192.168.1.131 port 22 rdomain "" Jun 21 06:15:50 unraid sshd[7063]: error: kex_exchange_identification: Connection closed by remote host Jun 21 06:15:50 unraid sshd[7063]: Connection closed by 192.168.1.11 port 54976 Jun 21 07:15:38 unraid sshd[22845]: Connection from 192.168.1.11 port 56116 on 192.168.1.131 port 22 rdomain "" Jun 21 07:15:38 unraid sshd[22845]: error: kex_exchange_identification: Connection closed by remote host Jun 21 07:15:38 unraid sshd[22845]: Connection closed by 192.168.1.11 port 56116 Jun 21 08:15:41 unraid sshd[6153]: Connection from 192.168.1.11 port 57215 on 192.168.1.131 port 22 rdomain "" Jun 21 08:15:41 unraid sshd[6153]: error: kex_exchange_identification: Connection closed by remote host Jun 21 08:15:41 unraid sshd[6153]: Connection closed by 192.168.1.11 port 57215 Jun 21 09:15:36 unraid sshd[22119]: Connection from 192.168.1.11 port 58322 on 192.168.1.131 port 22 rdomain "" Jun 21 09:15:36 unraid sshd[22119]: error: kex_exchange_identification: Connection closed by remote host Jun 21 09:15:36 unraid sshd[22119]: Connection closed by 192.168.1.11 port 58322 Jun 21 10:15:43 unraid sshd[5439]: Connection from 192.168.1.11 port 59433 on 192.168.1.131 port 22 rdomain "" Jun 21 10:15:43 unraid sshd[5439]: error: kex_exchange_identification: Connection closed by remote host Jun 21 10:15:43 unraid sshd[5439]: Connection closed by 192.168.1.11 port 59433 Jun 21 10:56:51 unraid kernel: eth0: renamed from vethc9b7ea0 unraid-diagnostics-20220621-1130.zip
  16. bmrowe
    I don't think so. This is the manual: https://images-na.ssl-images-amazon.com/images/I/A1kRDk8X1iL.pdf It mentions: "USB port of your PC must support power-off function so that the device would go to sleeping mode. Setting up motherboard’s (power management ) in S3 is strongly recommended. For more details, please refer to user guide of motherboard BIOS setting." I'm not sure if that is referencing the functionality it has called 'sync' where it sleeps when the pc sleeps. I have that turned off.
  17. bmrowe
    Or would an e-sata to usb cable get around this issue?