Andiroo2

Trying to set up SSH keys between Mac OS and Unraid. The intent is to log into Unraid from MacOS. I followed a few different guides here but always get to the same result...the login fails and falls back to password. I get this in the Unraid log: Dec 21 09:26:41 Tower sshd[29312]: Connection from 192.168.1.14 port 53913 on 192.168.1.10 port 22 rdomain "" Dec 21 09:26:41 Tower sshd[29312]: Failed publickey for root from 192.168.1.14 port 53913 ssh2: ED25519 SHA256:<blah blah blah> Dec 21 09:26:41 Tower sshd[29312]: Postponed keyboard-interactive for root from 192.168.1.14 port 53913 ssh2 [preauth] Dec 21 09:26:44 Tower sshd[29312]: Connection closed by authenticating user root 192.168.1.14 port 53913 [preauth] I have created ED25519 keys and used ssh-copy-id to copy them to the server, but I get this in the output there which seems different from others: Number of key(s) added: 1 Some people get 2 there, not sure if that's relevant. I have persisted the changes to the flash following another guide as well. I have verified that the public key is showing correctly in my Root user settings in the GUI. What else can I try here?

I used to get a nice secure handshake and a long URL into the address bar, but lately I just have my server IP and a certificate warning. My Servers plugin is installed and updated, and the api report looks ok: <-----UNRAID-API-REPORT-----> SERVER_NAME: Tower ENVIRONMENT: production UNRAID_VERSION: 6.10.3 UNRAID_API_VERSION: 2.49.2 (running) NODE_VERSION: v14.15.3 API_KEY: valid MY_SERVERS: authenticated MY_SERVERS_USERNAME: Andiroo2 CLOUD: ok RELAY: connected MINI-GRAPH: connected ONLINE_SERVERS: Tower OFFLINE_SERVERS: HAS_CRASH_LOGS: no </----UNRAID-API-REPORT-----> Anything I should be checking, or is this the new default behaviour? I am using a Ubiquiti router if that makes a difference (I recall some issues with those posted in the past). Thanks!

I just fixed my grafana with brute force: chmod -R 775 /mnt/user/appdata/grafana Add --user 99:100 to Extra Parameters in the container settings

Anyone else having issues using the Grafana container since the 6.10 upgrade? In another thread on Docker permissions after the upgrade, some users are having permissions issues with existing containers post-upgrade: My Grafana error is: logger=ngalert.multiorg.alertmanager t=2022-05-25T09:34:45.41-0400 lvl=eror msg="unable to create Alertmanager for org" org=1 err="error writing file notifications: unable to create the working directory \"/var/lib/grafana/alerting/1\": mkdir /var/lib/grafana/alerting/1: permission denied" I've made various wholesale changes to the permissions on the appdata folder with no luck, but I think this error is happening with file access within the container.

Same issue here. Some of the containers can't write to their own files in Appdata. Grafana initially for me, but maybe others.

Follow up on this one. My Unifi setup had created an internal honeypot on 192.168.1.99, but this wasn't listed in the clients section of the router. This is why I thought it was available when I deployed Pihole to the same address. Just in case anyone else has this issue in the future with their Unifi setup.

I don’t see that message in the logs. See attached.

Quick note on the “Move all files from cache pool selected above” option. When running this, my turbo write doesn’t engage. Can the Mover Tuning plugin check for this setting and enable turbo write when moving one share? I have “force turbo write on during mover” set in Mover Tuning settings for regular moves. Thanks!

I just updated from 2.00.10 (working) to 2.00.13 and I'm getting this error: [ERROR] Tdarr_Node - [39mBinary test 3: mkvpropeditPath not working It was working on my previous version. My json is blank for all 3 of these binaries: "handbrakePath": "", "ffmpegPath": "", "mkvpropeditPath": "", Do I need to point it to a specific path?

Success! I deleted the ../appdata/pihole/ directory completely and pulled a new image. No go. Then I changed the IP from .99 to .98 and it worked. Something must be using .99 on my network already, even though my Unifi controller shows it as available. More research to come, but for now my backup Pihole is running. Thanks!

I just tried a fresh pull and still the same behaviour. I can't get the GUI to load, but the system reports positive status: pihole status [✓] FTL is listening on port 53 [✓] UDP (IPv4) [✓] TCP (IPv4) [✓] UDP (IPv6) [✓] TCP (IPv6) [✓] Pi-hole blocking is enabled ...and if I tail the log, I see activity: # pihole -t [i] Press Ctrl-C to exit 08:09:17: forwarded 197.1.168.192.in-addr.arpa to 1.0.0.2 08:09:17: forwarded 197.1.168.192.in-addr.arpa to 1.0.0.2 08:09:19: query[AAAA] diag.meethue.com from 192.168.1.103 08:09:19: forwarded diag.meethue.com to 1.1.1.2 08:09:19: forwarded diag.meethue.com to 1.0.0.2 08:09:19: forwarded diag.meethue.com to 1.0.0.2 08:09:22: query[PTR] 197.1.168.192.in-addr.arpa from 127.0.0.1 I just can't get the GUI to load to set it up fully. Screenshot of the docker page is attached. What am I missing?

For those that are coming here to troubleshoot a new Pihole docker setup in 2022, the app marked "Official" in Community Apps doesn't yet work on Unraid out of the box. The template being pulled from docker has changed and the Unraid template hasn't been updated to use the new/correct variables yet. There are some changes listed in the thread here that may get it working for you, but for now, don't pull your hair out if it's not working out of the box. If I'm wrong, please delete this post or flag it...I'm not a spokesperson for this docker template...just someone that has pulled some hair out and now (I think?) understands where things stand.

I'm seeing this error in my logs over and over: Dec 28 08:23:15 Tower root: Starting Samba: /usr/sbin/smbd -D Dec 28 08:23:15 Tower root: /usr/sbin/nmbd -D Dec 28 08:23:15 Tower root: /usr/sbin/wsdd Dec 28 08:23:15 Tower root: /usr/sbin/winbindd -D Dec 28 08:23:15 Tower wsdd[5326]: set_multicast: Failed to set IPv4 multicast Dec 28 08:23:15 Tower wsdd[5326]: Failed to add multicast for WSDD: Address already in use Dec 28 08:23:15 Tower wsdd[5326]: set_multicast: Failed to set IPv4 multicast Dec 28 08:23:44 Tower emhttpd: Starting services... Dec 28 08:23:44 Tower emhttpd: shcmd (101438): /etc/rc.d/rc.samba restart Dec 28 08:23:46 Tower root: Starting Samba: /usr/sbin/smbd -D Dec 28 08:23:46 Tower root: /usr/sbin/nmbd -D Dec 28 08:23:46 Tower root: /usr/sbin/wsdd Dec 28 08:23:46 Tower root: /usr/sbin/winbindd -D Dec 28 08:23:46 Tower wsdd[8659]: set_multicast: Failed to set IPv4 multicast Dec 28 08:23:46 Tower wsdd[8659]: Failed to add multicast for WSDD: Address already in use Dec 28 08:23:46 Tower wsdd[8659]: set_multicast: Failed to set IPv4 multicast Dec 28 08:24:19 Tower emhttpd: Starting services... Dec 28 08:24:19 Tower emhttpd: shcmd (101481): /etc/rc.d/rc.samba restart Dec 28 08:24:22 Tower root: Starting Samba: /usr/sbin/smbd -D Dec 28 08:24:22 Tower root: /usr/sbin/nmbd -D Dec 28 08:24:22 Tower root: /usr/sbin/wsdd Dec 28 08:24:22 Tower root: /usr/sbin/winbindd -D Dec 28 08:24:22 Tower wsdd[12383]: set_multicast: Failed to set IPv4 multicast Dec 28 08:24:22 Tower wsdd[12383]: Failed to add multicast for WSDD: Address already in use Dec 28 08:24:22 Tower wsdd[12383]: set_multicast: Failed to set IPv4 multicast Dec 28 08:24:40 Tower emhttpd: Starting services... Dec 28 08:24:40 Tower emhttpd: shcmd (101510): /etc/rc.d/rc.samba restart Dec 28 08:24:43 Tower root: Starting Samba: /usr/sbin/smbd -D Dec 28 08:24:43 Tower root: /usr/sbin/nmbd -D Dec 28 08:24:43 Tower root: /usr/sbin/wsdd Dec 28 08:24:43 Tower root: /usr/sbin/winbindd -D Dec 28 08:24:43 Tower wsdd[14670]: set_multicast: Failed to set IPv4 multicast Dec 28 08:24:43 Tower wsdd[14670]: Failed to add multicast for WSDD: Address already in use Dec 28 08:24:43 Tower wsdd[14670]: set_multicast: Failed to set IPv4 multicast Thoughts on where to start looking?

+1 for the H O T C A C H E.

Do I MV the files to /mnt/cache/<share>/ or CP them? Is that the correct path I should be targeting? When I want them to go back to the array, do I run mover, or MV/CP them pack to /mnt/disk#/<share>/?

My movies folder is set to use cache (cache:yes) until cache hits 90%, then mover runs. I’d like to move most of my Christmas movies back to the cache while they are in demand and save my array from spinning up. Can I move files BACK to the cache without forcing the whole share to Cache:Prefer? My cache is a raid1 pool, so I’m not concerned about protection for the files.

One of us.

My container suddenly won't start on a server reboot. Logs show one error but apparently unrelated. ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 45-plex-claim: executing... [cont-init.d] 45-plex-claim: exited 0. [cont-init.d] 50-gid-video: executing... [cont-init.d] 50-gid-video: exited 0. [cont-init.d] 60-plex-update: executing... No update required [cont-init.d] 60-plex-update: exited 0. [cont-init.d] 90-custom-folders: executing... [cont-init.d] 90-custom-folders: exited 0. [cont-init.d] 99-custom-scripts: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-scripts: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Starting Plex Media Server. Critical: libusb_init failed Dolby, Dolby Digital, Dolby Digital Plus, Dolby TrueHD and the double D symbol are trademarks of Dolby Laboratories. If I manually start the docker it works fine.

I started removing plugins based on their update dates. I removed only one: CA Mover Tuning ...and I was able to restart. I then saw there is an update today for the Unassigned Devices plugin that I still had installed. This is in the release notes for that update: Unassigned.devices 2021.12.08 Fix: Deal gracefully with udev not returning any information on a partition. Fix: Issue with loss of GUI on 6.9. 2021.12.07 Add: Show a disk that drops out of the array and ends up as an unassigned device as unmountable and mark it as 'Array'. Fix: Rewrite check for used share name because the scheme used interferred with a device mount. I wonder if the "Loss of GUI on 6.9" is my issue. In any case, I updated to it and was able to reboot again. I'll mark this SOLVED for now.

Been an interesting few days. Timeline: Tried to remove some cache drives, borked it. Had to rebuild my cache from backups and resize the pool. Got the system working as usual again, backups restores, parity synced, etc. All set. Installed a new plugin (VM Backup) and ran it once. Rebooted the system, and no GUI came up. I can log into the terminal and SSH without issue Booted into safe mode, all seems fine. Removed the VMBackup .plg and folder from /boot/config/plugins Still can't boot into normal mode Diagnostics attached. I do have a brand new flash drive handy if drive corruption is suspected. Thoughts? Thanks for the help. tower-diagnostics-20211209-0803.zip

This explains my hangs over the last few weeks. Tdarr running must be causing this.

Any options to configure the Speedtest docker to use Appdata so we can edit the telemetry settings? I would love to log the Speedtest results from external users.

This is where a cache disk will be helpful. Large capacity SSD or ideally NVME used as a write cache will speed up your writes as fast as your network and sending disks can handle.

Restarting the server fixed it for me.

Running into this issue today myself. Did you ever figure this out? My error is coming from Telegraf when connecting to the Docker service to get the CPU and memory stats.