SeattleBandit

frustratingly - my server refused to boot today - it was hanging on the rclone plugin install - so I landed here and nuked the rclone plugin folder and rebooted - and it worked - where is the plugin install script so that I can modify it for the 10 second wait to see if that works for repeated reboots? EDIT: so after deleting the plugin folder and then rebooting (restoring my config etc) I had no issues - dunno what the issue was

moving network.cfg in /boot/config to network.cfg.bak and rebooting solved my issues ... wtf

* Host api.themoviedb.org:80 was resolved. * IPv6: 2a03:2880:f111:83:face:b00c:0:25de * IPv4: 173.252.108.3 * Trying 173.252.108.3:80... * Trying [2a03:2880:f111:83:face:b00c:0:25de]:80... * Immediate connect fail for 2a03:2880:f111:83:face:b00c:0:25de: Network is unreachable ^C

so sometime last week (I have made no changes to my setup) my unraid server stopped being able to talk to tmdb api - my proxmox server in the same rack on the same switch can curl the tmdb api no issues tried curl'ing wttr.in from my unraid server with no issue - but I get timeouts trying to hit tmdb - networking is def my weakest area - its not my pihole blocking things otherwise it would block my proxmox queries - but I turned them all off to test anyways - with the same result - I checked my firewall rules and nothing is set that would block tmdb connection issues any help would be appreciated

I was initially - but then switched it to my docker network hoping that would change things - no change I'll switch it back to bridge mode and test again now though EDIT :: docker run is including the ports -p '3232:8080/tcp' -p '32331:8081/tcp' post switching back to bridge mode Host is up (0.00048s latency). PORT STATE SERVICE VERSION 32331/tcp closed unknown

So I'm coming here because I'm at a bit of a loss - I've configured my calibre server happily and its been running for years - but I just recently decided to set up readarr and have it integrate with calibre - but for whatever reason - Unraid isn't opening the web server port used for running calibre's content server - I've configured it for port 32331 in the Unraid config and restarted the container several times - turned on the server in calibre and configured a user and pass etc - but when I run nmap against the port on my Unraid server it is closed - I would expect to see a what.. bonjour opds service running on that port yeah? going to do a reboot of my entire Unraid server and report back EDIT :: just did a full reboot - VNC gui comes up fine - but nmap pulls still show port is closed - is this a version issue? I'm running the :latest container

you figure out your issues? this has been working for like a charm for the past year + feeding data to my influxdb and all of a sudden i'm getting the speedtest fail log message edit i seem to be getting ssl errors - still digging edit sounds like this might be related to the underlying docker framework update in 6.12.1 ... based on some errors from another similar docker

Super helpful - thank you very much - late to the game by three years - but was setting up a new box and this was helpful as i was relearning how to set things up

I just had to recover my isb stick that unRAID runs on - got everything back up and running but for whatever reason shinysdr can open the USB connection to my rtl-sdr - has anyone experienced similar issues? If I use the sdr I have connected for my fr24 adsb it works fine so it's not the radio Updated the config per guidance in this channel - tried running in privikiged mode - removed and reinstalled - still no dice Sent from my iPhone using Tapatalk

running btrfs scrub and pulling diags

it blew away my custom docker network - recreating that and i'll hopefully be back fully operational

yeah i found a reddit post saying all your configs and stuff don't get nuked - so passwords and api keys are retained - i move my old docker image and kicked things off with a new one and am reinstalling everything and thus far no issues... i am concnerned about that btrs device loop but i'm not seeing it in the logs anymore

Jun 5 13:27:07 Nighthawks root: Fix Common Problems: Error: Unable to write to Docker Image Jun 5 13:39:01 Nighthawks kernel: BTRFS error (device loop2): unable to find ref byte nr 5920882688 parent 0 root 7 owner 0 offset 0 Jun 5 13:39:01 Nighthawks kernel: BTRFS: Transaction aborted (error -2) Jun 5 13:39:01 Nighthawks kernel: BTRFS: error (device loop2) in __btrfs_free_extent:3092: errno=-2 No such entry Jun 5 13:39:01 Nighthawks kernel: BTRFS: error (device loop2) in btrfs_run_delayed_refs:2144: errno=-2 No such entry Jun 5 13:39:01 Nighthawks rc.docker: xteve: Error response from daemon: failed to update store for object type *libnetwork.endpoint: no such file or directory Jun 5 13:39:01 Nighthawks rc.docker: Error: failed to start containers: xteve Jun 5 13:39:02 Nighthawks rc.docker: binhex-prowlarr: Error response from daemon: failed to create endpoint binhex-prowlarr on network bridge: failed to save bridge endpoint 2ca7ca3 to store: failed to update bridge store for object type *bridge.bridgeEndpoint: open /var/lib/docker/network/files/local-kv.db: read-only file system Jun 5 13:39:02 Nighthawks rc.docker: Error: failed to start containers: binhex-prowlarr Not clear what the BTRFS error (device loop2) means - not super excited about removing the docker.img and reinstalling everything ... increasing docker.im size did not help

had a kernel panic bring down my server and now i keep seeing this in my logs -> /var/lib/docker/network/files/local-kv.db some docker containers start up happily but others keep giving me these types or errors and when i try and manually start them or remove a container i get a 'server error' Jun 5 13:17:51 Nighthawks rc.docker: tautulli: Error response from daemon: failed to create endpoint tautulli on network tjvnet: failed to save bridge endpoint 7f200b4 to store: failed to update bridge store for object type *bridge.bridgeEndpoint: open /var/lib/docker/network/files/local-kv.db: read-only file system Jun 5 13:17:51 Nighthawks rc.docker: Error: failed to start containers: tautulli perhaps my docker stack was screwed up due to the unclean shutdown last night? anyone have any suggestions? FIx common problems says its unable to write to docker image because its either full or corrupted - going to try increasing the docker image size ...

boom - simple as that - thanks for the info - once the smart is done i'll just rebuild - thanks