SeattleBandit

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

So i'm moving all my stuff from a 'gravity rack/stack' (wire shelves from ace) to a proper rack - with a nice 48 port switch and patch panel etc etc etc running a supermicro 24bay hot swap chassis last night i pulled what i thought was an empty bay (i got lazy with my label maker apparently) from my live array - when i realized my mistake i brought my stack down, plugged the drive in - brought everything back up - and now my disk 5 is unhappy and is disabled and all data is running emulated. It is reading the drive and smart health - i'm currently running the extended/full smart test - only 45% complete - my question is once the smart test is complete and (i'm assuming) says there are no issues - how do i go about making disk 5 happy and healthy so i can bring my array back to full strength?? last nigth before kicking off the complete smart test i booted into maintennance mode and ran the check disk and it didn't seem to throw any errors? i'm not sure how to read that report - but it looked mostly similar to a report i ran on a healthy disk what should my next steps be? unfortunately my syslog is swamped with the below (running a couple SAS drives which i believe are causing this) i'm preclearing new drives to replace my sas drives which will hopefully fix the below Feb 2 08:44:52 Nighthawks kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Feb 2 08:44:52 Nighthawks kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Feb 2 08:44:52 Nighthawks kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Feb 2 08:44:52 Nighthawks kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Feb 2 08:44:52 Nighthawks kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Feb 2 08:44:52 Nighthawks kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Feb 2 08:44:52 Nighthawks kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Feb 2 08:44:52 Nighthawks kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Feb 2 08:44:52 Nighthawks kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Feb 2 08:44:52 Nighthawks kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Feb 2 08:44:52 Nighthawks kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Feb 2 08:44:52 Nighthawks kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Feb 2 08:44:52 Nighthawks kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!

yeah - solved my own issue - must not have had the container off when i did the initial copy

Migrating the config folder from /mnt/user/appdata/binhex-plexpass to /mnt/user/larger-cache/binhex-plexpass results in a malformed sqllite (if memory serves) Error: Unable to set up server: sqlite3_statement_backend::prepare: database disk image is malformed for SQL: PRAGMA cache_size=2000 (N4soci10soci_errorE) i used rsync -avPr will the containers were stopped to move everything - does anyone have any ideas on why this is an issue?

this allows for greater selection of the IP range as well - with the default i ran into conflicts when i tried to connect to my vpn server from a network that had the same subnet my unraid server used - with this i can assign a different unique subnet to my clients - (i couldn't figure out how to get that to work with the built in unraid plugin maybe i'm a bonehead but i didn't see a way)