tucansam

Noticed unraid was due for an upgrade, upgraded it, rebooted, sonarr is back to being completely inaccessible.

LOL now sonarr reponds, kinda, as if it was running on a 10Mhz 286, no icon images load, searches for new shows return errors, and now the console is not responding.

Inexplicably, after some random period of time (I've been away for hours), sonarr's webserver is now responding, however I just get the grey screen with the background logo and the white dots going left to right like KITT from Knight Rider. Never fully loads. Log shows it scanning shows and what not. I remain confused.

I can no longer bring up the sonarr web page. The last download sent to Sab was 25 March. I have reset the docker, and turned the entire docker system off/on, no effect. Sonarr shows CPU use in the docker tab, however it is inaccessible. -- [Info] OwinHostController: Listening on the following URLs: [Info] OwinHostController: http://*:8989/ [Info] NancyBootstrapper: Starting Web Server --------------> [Error] TaskExtensions: Task Error -------------->[v2.0.0.5344] System.Net.WebException: DNS Name Resolution Failure: 'services.sonarr.tv' at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x00169] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\Dispatchers\ManagedHttpDispatcher.cs:101 at NzbDrone.Common.Http.Dispatchers.FallbackHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x000b5] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\Dispatchers\FallbackHttpDispatcher.cs:53 at NzbDrone.Common.Http.HttpClient.ExecuteRequest (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookieContainer) [0x0007e] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\HttpClient.cs:121 at NzbDrone.Common.Http.HttpClient.Execute (NzbDrone.Common.Http.HttpRequest request) [0x00008] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\HttpClient.cs:57 at NzbDrone.Common.Http.HttpClient.Get (NzbDrone.Common.Http.HttpRequest request) [0x00007] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\HttpClient.cs:264 at NzbDrone.Common.Http.HttpClient.Get[T] (NzbDrone.Common.Http.HttpRequest request) [0x00000] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\HttpClient.cs:269 at NzbDrone.Core.Update.UpdatePackageProvider.GetLatestUpdate (System.String branch, System.Version currentVersion) [0x00099] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Update\UpdatePackageProvider.cs:46 -- Seems relevant. But unraid server can resolve this web address no problem. Opening up the console for the docker in question, I see that ping, traceroute, and nslookup are not available commands, so I cannot test network connectivity from inside the container. Tried to install it, go this: -- root@515f04519ab1:/sbin# apt-get ping E: Invalid operation ping root@515f04519ab1:/sbin# apt-get install iputils-ping Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libcap2 libcap2-bin libidn11 libpam-cap The following NEW packages will be installed: iputils-ping libcap2 libcap2-bin libidn11 libpam-cap 0 upgraded, 5 newly installed, 0 to remove and 9 not upgraded. Need to get 142 kB of archives. After this operation, 537 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://archive.ubuntu.com/ubuntu bionic/main amd64 libcap2 amd64 1:2.25-1.2 [13.0 kB] Err:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libidn11 amd64 1.33-2.1ubuntu1.2 Could not connect to archive.ubuntu.com:80 (91.189.88.152), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.88.142), connection timed out [IP: 91.189.88.142 80] Err:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 iputils-ping amd64 3:20161105-1ubuntu3 Unable to connect to archive.ubuntu.com:http: [IP: 91.189.88.142 80] Err:4 http://archive.ubuntu.com/ubuntu bionic/main amd64 libcap2-bin amd64 1:2.25-1.2 Unable to connect to archive.ubuntu.com:http: [IP: 91.189.88.142 80] Err:5 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpam-cap amd64 1:2.25-1.2 Unable to connect to archive.ubuntu.com:http: [IP: 91.189.88.142 80] Fetched 13.0 kB in 1min 2s (211 B/s) E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/libi/libidn/libidn11_1.33-2.1ubuntu1.2_amd64.deb Could not connect to archive.ubuntu.com:80 (91.189.88.152), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.88.142), connection timed out [IP: 91.189.88.142 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/i/iputils/iputils-ping_20161105-1ubuntu3_amd64.deb Unable to connect to archive.ubuntu.com:http: [IP: 91.189.88.142 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/libc/libcap2/libcap2-bin_2.25-1.2_amd64.deb Unable to connect to archive.ubuntu.com:http: [IP: 91.189.88.142 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/libc/libcap2/libpam-cap_2.25-1.2_amd64.deb Unable to connect to archive.ubuntu.com:http: [IP: 91.189.88.142 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? -- root@515f04519ab1:/sbin# apt-get update Err:1 https://mediaarea.net/repo/deb/ubuntu bionic InRelease Temporary failure resolving 'mediaarea.net' Err:2 http://download.mono-project.com/repo/ubuntu bionic/snapshots/5.20 InRelease Temporary failure resolving 'download.mono-project.com' Err:3 http://archive.ubuntu.com/ubuntu bionic InRelease Temporary failure resolving 'archive.ubuntu.com' Err:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease Temporary failure resolving 'archive.ubuntu.com' Err:5 http://archive.ubuntu.com/ubuntu bionic-security InRelease Temporary failure resolving 'archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-security/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch https://mediaarea.net/repo/deb/ubuntu/dists/bionic/InRelease Temporary failure resolving 'mediaarea.net' W: Failed to fetch http://download.mono-project.com/repo/ubuntu/dists/bionic/snapshots/5.20/InRelease Temporary failure resolving 'download.mono-project.com' W: Some index files failed to download. They have been ignored, or old ones used instead. root@515f04519ab1:/sbin# -- No other host on my network, and no other docker, is having dns issues. Assuming that's even the problem.

Despite dedicating four cores to this in the config, this software is pegging my CPU and turning it into the surface of the sun. How to fix? Found the "use no more than XX%" in the RDP config, looks like that works for now. Got Rosetta@Home, couldn't find Unraid team.

So this drive is not recommended for use in unraid as a member disk?

I have an ssd, on which lives docker stuff. I have a small spinner, on which lives the downloads folders for a few of the docker apps. I read a while ago about putting these drives in the array so the contents are actually parity protected. But then creating a share (or whatever) that made it so where only the dockers wrote to these drives exclusively, etc. Can't find that post now. How can I parity protect these drives by putting them in the array? I can't get the steps down in my mind.

What fans did you use? I removed the fans from the three cages I use as my server has enough exhaust fans to pull air over the disks.

I have been using the iStarUSA 5-in-1s since before the unraid 5.3 days and I've never had a single issue.

Semi-worked, it appears. Two devices are still showing STUN failure, two are GTG. Will try to reset the two problem devices when network traffic allows.

Thanks! Will try.

stun issues. Every time I upgrade the docker container to the latest version, I have to ssh into most/alll devices (four total) and manually 'set-inform' in order for them to appear in the unifi controller as provisioned, and in order to see attached clients. When I do, they still show up with yellow exclamation icons, indicating stun failure. Same thing happens whenever I reboot an AP; they show as "adopting" and I have to manually 'set-inform' and still get the stun failure icon. The container is being run in bridged mode with its own IP address. Any suggestions?

No cursor under Windows 10 on a Lenovo Yoga (touchsreen) with Mint 19.3 under unraid 6.7.2 Mouse trails have no effect.

plugin: updating: fix.common.problems.plg plugin: downloading: https://raw.githubusercontent.com/Squidly271/fix.common.problems/master/archive/fix.common.problems-2019.10.12-x86_64-1.txz ... failed (Invalid URL / Server error response) plugin: wget: https://raw.githubusercontent.com/Squidly271/fix.common.problems/master/archive/fix.common.problems-2019.10.12-x86_64-1.txz download failure (Invalid URL / Server error response) Unable to update. -------------- DISREGARD That was strange. From the plugins page, I got the aforementioned error. However, when I went to the update assistant under tools, a yellow bar appeared on the top of the browser window telling me Fix Common had an update, and "click here", so I did. Updated fine at that point.

Perfect, that worked. Thanks.

This worked for me as well, thanks.

I don't know exactly where to post this, so I am posting it here. Most of my dockers think they need to update 24/7. This is new. The only thing that has changed in the last few days, I believe, is Community Applications updated. Otherwise I believe nothing else meaningful has changed, except I moved to a new Plex docker and installed Radarr. This screenshot is what my docker page looks like every time I view it. If I update all, it runs through the motions, and then shows all of them are up to date. All I have to do is refresh my browser windows, and they all go back to needing updating again. Any ideas?

https://github.com/Radarr/Radarr/issues/2311 Am experiencing this exact issue. Many movies are showing "file not found" despite having an MKV or MP4 file in its folder. Anyone else seeing this?

Crashing right out of the gate, fresh install, copied all of the config stuff over from my previous (limetech) now depreciated plex container. I've tried priviledged and non-priviledged modes, seems to have file permissions issues????? -- 2019-08-31 12:51:38,530 INFO exited: plexmediaserver (terminated by SIGABRT; not expected) 2019-08-31 12:51:38,531 DEBG received SIGCHLD indicating a child quit 2019-08-31 12:51:38,531 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly 2019-08-31 12:51:47,541 WARN received SIGTERM indicating exit request Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2019-08-31 12:51:48.182401 [info] System information Linux 10db7d69425f 4.19.56-Unraid #1 SMP Tue Jun 25 10:19:34 PDT 2019 x86_64 GNU/Linux 2019-08-31 12:51:48.215076 [info] PUID defined as '99' 2019-08-31 12:51:48.251595 [info] PGID defined as '100' 2019-08-31 12:51:48.309291 [info] UMASK defined as '000' 2019-08-31 12:51:48.342060 [info] Permissions already set for volume mappings 2019-08-31 12:51:48.372572 [info] TRANS_DIR defined as '/mnt/disks/ssd/appdata/PlexMediaServer' 2019-08-31 12:51:48.404666 [info] Starting Supervisor... 2019-08-31 12:51:48,568 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2019-08-31 12:51:48,568 INFO Set uid to user 0 succeeded 2019-08-31 12:51:48,571 INFO supervisord started with pid 6 2019-08-31 12:51:49,574 INFO spawned: 'plexmediaserver' with pid 48 2019-08-31 12:51:49,574 INFO reaped unknown pid 7 2019-08-31 12:51:49,588 DEBG 'plexmediaserver' stderr output: mkdir: cannot create directory ‘/mnt/disks’: Permission denied 2019-08-31 12:51:49,605 DEBG 'plexmediaserver' stderr output: terminate called after throwing an instance of 'std::runtime_error' what(): Codecs: Initialize: 'boost::filesystem::temp_directory_path: Not a directory: "/mnt/disks/ssd/appdata/PlexMediaServer"' 2019-08-31 12:51:49,606 DEBG 'plexmediaserver' stderr output: ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Plex Media Server/Crash Reports/1.16.6.1592-b9d49bdb7/PLEX MEDIA SERVER/619f37cd-4edd-aa9f-5a619d85-6d0780ed.dmp 2019-08-31 12:51:49,617 DEBG 'plexmediaserver' stderr output: Error in command line:the argument for option '--serverUuid' should follow immediately after the equal sign Crash Uploader options (all are required): --directory arg 2019-08-31 12:51:49,617 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22989104644840 for <Subprocess at 22989104644784 with name plexmediaserver in state STARTING> (stdout)> 2019-08-31 12:51:49,617 DEBG 'plexmediaserver' stderr output: Directory to scan for crash reports --serverUuid arg UUID of the server that crashed --userId arg User that owns this product --platform arg Platform string --platformVersion arg Platform version string --vendor arg Vendor string --device arg Device string --model arg Device model string --sentryUrl arg Sentry URL to upload to --

What did everyone switch to? I though I downloaded the binhex container but mine still says limetech.

Only change I made was moving a physical pihole to a docker, and all hosts on the network, unraid included, are resolving dns queries just fine. No idea what's causing it, but when I click "plugins" on the top menu, it takes 3-4 minutes to come up.

On previous docker screens (as in prior to yesterday), all addresses were "192.168.0.5" with their associated ports listed after that. 172.x.x.x is totally new to me, I have never seen it on the docker screen before. I could access all of my dockers via their 192.168.0.5:<port> addresses, however none of them could talk to each other. I have now given each of them their own IP address on the br1 interface, and reconfigured all of them to talk among themselves using their new addresses. A major PITA, but its working again. No idea what happened.

Network connectivity is up. I mean I see the orange animation bar graph bridge thing whenever I go to the plug-ins page. I let it sit for a while and came back and it had loaded, no idea how much time it actually took. Used to be it was loaded within about 10 seconds, now its a matter of minutes.

I can still access the apps, ie, 192.168.0.5:8085 brings up sab, so its at least listening on that address. But no inter-docker communication is occurring, ie, sab is not talking to sonarr and vice versa.

How do I tell?