Jump to content

tucansam

Members
  • Content Count

    818
  • Joined

  • Last visited

Community Reputation

11 Good

About tucansam

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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?
  2. 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?
  3. 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 --
  4. What did everyone switch to? I though I downloaded the binhex container but mine still says limetech.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. Brand new issue. Diags attached. ffs2-diagnostics-20190825-0043.zip
  10. My server is 192.168.0.5 Today, I rebooted the server. All of my docker containers went from 192.168.0.5:(whatever bridged ports I had defined) to 172.17.0.2, 0.3, 0.4, etc. Now nothing is accessible. ffs2-diagnostics-20190825-0033.zip
  11. Slowly but surely, over the least few months all Windows (7 and 10) systems in my home have had trouble seeing my unraid server's shares, and now, the server itself on the network. It went from all mapped drives being visible, to having to manually enter "\\192.168.0.5\share" in the text bar at the top of the file explorer, to then having to find the system manually under the "network" icon on the bottom right, to now several systems simply cannot access the server at all (the server is online and other systems can access it, although with varying degrees of failure). Any ideas? Currently set to local master browser as well.
  12. I switched, but its showing I'm on 1.16.4.1469 and 5.1488 is available. I know updates take a while, just making sure I'm on the latest version of the docker.