5.6 KiB
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc source ~/.bashrc claude
we broke host ip look up or something ❌ [ERROR] Failed to resolve Tailscale IP for unRAID-Jayred365 ❌ [ERROR] Check: tailscale status | grep unRAID-Jayred365 in tailscale manage consel, it shows unRAID-Jayred365, but in tailscale plugin it shows as
error starting emby --mount type=bind,source=/mnt/ram-transcode,target=/ext-ram-transcode,bind-propagation=shared 'lscr.io/linuxserver/emby'
0e616c065aebad2604d2120fbf9c6bb449cdfc4021d68f167e4b5bc01741c133 docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error jailing process inside rootfs: open /proc/self/mountinfo: no such file or directory
Run 'docker run --help' for more information
The command failed. had to use --mount type=bind,source=/mnt/ram-transcode,target=/ext-ram-transcode instead, for now, just to get it back online
arrs system error, can we delete movies from radar when dropped from tmdb, 99% of the time its future movies that get dropped movie Silent Hill 2: The Movie (tmdbid 466226) was removed from TMDb. same logic for sonarr.
fail overhand back needs to happen in stages and in reverse...... so if i hit tier 3, i want it to only stop the services in tier 3 then rsync, then hand abck, then tier 2, shutdown containers rsync, and handback, same for 1.... this will allow emby to stay up during possible long writebacks. and ensure all data issynced back before emby it handed back.
later. . fix failover strike list timing, maybe 30 seconds. them a t 90 seconds 3 stike triggers. just gotta test buffer. never had the strike system . verify silent toggle switches back on good notifications
. add to partnership, on offboard, remove all of containers that belonged to remote, example remotes vaultwarden-jayred from my machine and leave my vaultwarden-Gmer4Lfe alone. and it does nothing to remote, thier side will hadle thier pc and remove my stuff from thier pc. now i use folders in docker, and have a folder i put my buddies failover containers in. dont know if we can utilize that.
. add updater to update containers while daily runs, along with a toggle to dissable in master.
. add a script to check all docker containers and update any that still need it to run after the containers that get synced and updated.
. add a script to find missing artist and album cover from fanart and itunes, or itunes as a fallback
tailscale seperated, now each user has to share thier machines to the other. make sure tailscale ssh in the tailscale setting is turned off, we will be ssh through tailscale. each user will need to run , Separate “automation key” (cleanest design) Keep your main key secure Create a dedicated rsync key with no passphrase ssh-keygen -t ed25519 -f /root/.ssh/_rsync_automation -N "" , example = gmer4lfe_rsync_automation Copy it to remote: ssh-copy-id -i /root/.ssh/_rsync_automation.pub root@100.97.4.47 that sets up passwordless syncs
we should look into a rsync setup script. then tailscale users already running tailscale. share each others servers then each runs the script. keys are made and the remote side is gets ssh'd and copied to remote. and it should update master with the new key could start a new folder called Initial_run. and eventualy maybe even an orch script. or set it up in the partner dcript under onboard
we need to delete those keys from both servers on offboard. like it gets triggered. remote key removed then removed from local then, and new key is made next time we onboard. even if we use a file to trck keys. less perfered, but maybe a good fallback. all host keys that get added, maybe with a specific *_rsync_automation "tag" gets added to the list and then deleted on offboard, but that would only handle a 2 pc setup, unles we can link hosts to keys when descovered. then if 5 pcs are in a group and host 3 leaves, the script can look it up and remove it from the local pc.
cant use tailscale api, so
i think we need to just make a block list so user cant get back into the system then they are blocked machine level untill we accually get to tailscale, worst case u see it when you join with someone else
What your block list actually does (in real terms) Your system becomes: ✔ On exit revoke keys / session access locally add identifier to blocklist ✔ On future access attempts (your scripts) check blocklist before allowing or trusting anything refuse automation actions tied to that identity So it functions as: “Even if they reappear on the network, my server won’t trust them” 🔒 Why this works well with Tailscale’s model Tailscale already handles: transport security identity authentication device connectivity Your layer adds: policy after connection exists human-defined lifecycle rules ✔ Script layer manages lifecycle only when told ✔ Exit triggers: revoke keys block future re-entry clean state locally No auto-provisioning. No implicit trust expansion.
WAY LATER when a user offboards and there is more than 1 server left, one needs to become the owner, we could do this in multiple ways or a combination, strongest server and BANDWIDTH,whos contributing more.... maybe we just promt and ask them
rsync, look into cross sync. newest timestamp wins, so if a show 1 updates on server 1, show 2 on server 2, show 3 on server3, when rsync runc, each machine would run this, and add remove based on time stamp, and have arrs pull after sync
look into an overall, setup script, pull as many vars as possible without user having to add. like docker names, and so on.