Jump to content

weirdcrap

Members
  • Content Count

    202
  • Joined

  • Last visited

Community Reputation

3 Neutral

About weirdcrap

  • 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 just logged into my server and noticed this as well. Running UnRAID 6.7.2. I have no browsers left open and the server hasn't been restarted in a week. It doesn't seem to happen every day and it isn't always at the same time (it is not happening at all when I am accessing the server webUI). So far it has happened July 6th, 7th, and 8th at 630AM. Then it stopped for a day, continuing on the 10th at 4:45AM & 11AM , and most recently today at around 11AM. I would not have been accessing the server at any of these times as I am gone at work so I'm thinking a plugin or docker is the most likely culprit. I have some scripts and things scheduled, but nothing that would be running at any of the times these errors appeared. I did have a few plugin updates available which I have installed. I will reboot later once everyone is done streaming for the night. Diagnostics attached. I know I have a bunch of out of memory errors, freaking mono is always trying to gobble up all the RAM between sonarr, radarr, and lidarr (those have been going on long before this ever started). node-diagnostics-20190711-2021.zip
  2. I had several issues with accessing Plex with a PFSense router. It would tell me I had no remote access, my connection wasn't secure (even locally), etc. This thread helped me get it up and running, maybe it can assist you as well: https://forums.plex.tv/t/secure-connections-lan-and-pfsense/123319
  3. I am trying to troubleshoot a play back issue with files reporting their codec as "aac_lc" over on the Plex Forums. The Plex team member Movie.Fan is saying that he believes Plex isn't starting properly. Or possibly because Plex is dockerized he isn't seeing the normal startup procedure. Either way this has brought my troubleshooting efforts to a stand still as I don't have the knowledge necessary to explain the difference between docker plex vs non-docker plex and how they startup/shutdown. Any of the LinuxServer.io folks or any docker creator really want to take a stab at assisting me? Is there somewhere in UnRAID I can get the info he wants? It looks like most of the container startup is scripted and isn't very verbose in the docker logs... Relevant thread on plex forums: https://forums.plex.tv/t/error-transcoder-unknown-decoder-aac-lc/409225/ EDIT: Nevermind, apparently one of the new server or web player updates must have resolved my issue. All episodes play back fine now.
  4. I haven't had more time to look at your diags unfortunately, I'm on the road all day today. I'm going to page @johnnie.black He is always helping me out lol and is a wealth of knowledge. Everyone here is super helpful so have no fear someone will come in and help you out.
  5. I'm still going through your diagnostics (I am at work so I can only look intermittently) but I don't see anything else immediately wrong yet. I don't see any documented cases of failing to decrypt the disks causing the WebUI to fail to load either. I do see PHP-FPM and NGINX starting in the Syslog so I'll have to dig deeper into what else goes into getting the webUI started.
  6. I'm no expert but it looks like something has happened to your array encryption? I assume your array is encrypted and this setting wasn't turned on by mistake or something of the like? I don't use encryption in UnRAID so I'm trying to find some info for you, hopefully someone with experience with it can jump in and help. Mar 19 19:08:03 Holt emhttpd: shcmd (41): udevadm settle Mar 19 19:08:03 Holt emhttpd: Opening encrypted volumes... Mar 19 19:08:03 Holt emhttpd: shcmd (43): /usr/sbin/cryptsetup luksOpen /dev/md1 md1 --key-file /root/keyfile Mar 19 19:08:03 Holt kernel: device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: email@removed.com Mar 19 19:08:03 Holt root: Failed to open key file. Mar 19 19:08:03 Holt emhttpd: shcmd (43): exit status: 1 Mar 19 19:08:03 Holt emhttpd: shcmd (45): /usr/sbin/cryptsetup luksOpen /dev/md2 md2 --key-file /root/keyfile Mar 19 19:08:03 Holt root: Failed to open key file. Mar 19 19:08:03 Holt emhttpd: shcmd (45): exit status: 1 Mar 19 19:08:03 Holt emhttpd: shcmd (47): /usr/sbin/cryptsetup luksOpen /dev/md3 md3 --key-file /root/keyfile Mar 19 19:08:03 Holt root: Failed to open key file. Mar 19 19:08:03 Holt emhttpd: shcmd (47): exit status: 1 Mar 19 19:08:03 Holt emhttpd: shcmd (50): /usr/sbin/cryptsetup luksOpen /dev/md5 md5 --key-file /root/keyfile Mar 19 19:08:03 Holt root: Failed to open key file. Mar 19 19:08:03 Holt emhttpd: shcmd (50): exit status: 1 Mar 19 19:08:03 Holt emhttpd: shcmd (52): /usr/sbin/cryptsetup luksOpen /dev/md6 md6 --key-file /root/keyfile Mar 19 19:08:03 Holt root: Failed to open key file. Mar 19 19:08:03 Holt emhttpd: shcmd (52): exit status: 1 Mar 19 19:08:03 Holt emhttpd: shcmd (54): /usr/sbin/cryptsetup luksOpen /dev/md7 md7 --key-file /root/keyfile Mar 19 19:08:03 Holt root: Failed to open key file. Mar 19 19:08:03 Holt emhttpd: shcmd (54): exit status: 1 Mar 19 19:08:03 Holt emhttpd: shcmd (56): /usr/sbin/cryptsetup luksOpen /dev/nvme0n1p1 nvme0n1p1 --key-file /root/keyfile Mar 19 19:08:03 Holt root: Failed to open key file. Mar 19 19:08:03 Holt emhttpd: shcmd (56): exit status: 1 Mar 19 19:08:03 Holt emhttpd: shcmd (58): /usr/sbin/cryptsetup luksOpen /dev/nvme1n1p1 nvme1n1p1 --key-file /root/keyfile Mar 19 19:08:03 Holt root: Failed to open key file. Mar 19 19:08:04 Holt emhttpd: shcmd (58): exit status: 1 Mar 19 19:08:04 Holt emhttpd: Missing encryption key Mar 19 19:08:04 Holt kernel: mdcmd (44): stop
  7. If you checked the "anonymize statistics" box during diagnostics creation there should be no personally identifiable information in the diagnostics so it can be left if you want.
  8. Winner! I do not, not sure when I lost it or maybe I forgot to ever set it up and I just never noticed until the new dashboard UI.
  9. I am seeing what appears to be fan RPMs displayed under the motherboard temperature area. I am on the latest BIOS now (F3, this was taken before I updated) and still have the RPMs showing up in the temp area. Diagnostics: node-diagnostics-20190305-1449.zip Perl is installed and up to date. This does not happen on my server at home which is also on RC5 with the Dynamix system temp plugin but with a different motherboard.
  10. ah, didn't realize that came from the system temps plugin. Will do!
  11. This is being handled here as it is a plugin issue: As you can see in (underlined in red) on the current RC5--which is my first RC of this version--I am seeing what appears to be fan RPMs displayed under the motherboard temperature area. I am on the latest BIOS now (F3, this was taken before I updated) and still have the RPMs showing up in the temp area. This does not happen on my server at home which is also on RC5 but with a different motherboard.
  12. After using it for a few weeks I am satisfied with how everything is working, as always thanks for your help Johnnie.
  13. Ok so I installed the plugin and even after spinning up all drives it detects one drive as spundown. I ran hdparm on each disk and one of the disks on the H200 is reporting a status of "Unknown". The offending disk is /dev/sdg and it is a Seagate NAS HDD. I have another one of the same disk model installed and it reported it's status fine (sdf). EDIT: weird after spinning SDG down and back up it is now detecting correctly. EDIT2: Spoke to soon, left it for a minute or so and now SDG is back to unknown. It seems to snap out of it once I start copying data. root@Node:/home/chris# hdparm -C /dev/sdh /dev/sdh: drive state is: active/idle root@Node:/home/chris# hdparm -C /dev/sde /dev/sde: drive state is: active/idle root@Node:/home/chris# hdparm -C /dev/sdj /dev/sdj: drive state is: active/idle root@Node:/home/chris# hdparm -C /dev/sdk /dev/sdk: drive state is: active/idle root@Node:/home/chris# hdparm -C /dev/sdl /dev/sdl: drive state is: active/idle root@Node:/home/chris# hdparm -C /dev/sdb /dev/sdb: drive state is: active/idle root@Node:/home/chris# hdparm -C /dev/sdf /dev/sdf: drive state is: active/idle root@Node:/home/chris# hdparm -C /dev/sdg /dev/sdg: drive state is: unknown root@Node:/home/chris# hdparm -C /dev/sdg /dev/sdg: drive state is: unknown root@Node:/home/chris# hdparm -C /dev/sdi /dev/sdi: drive state is: active/idle root@Node:/home/chris# hdparm -C /dev/sdd /dev/sdd: drive state is: active/idle
  14. Sweet, I'll give it a try then thanks!
  15. I was getting ready to try this out but it sounds like it may not work for me either (all my cards are Perc H200s). @Squid Is this a confirmed issue?