guy2545

Pretty much out of ideas. What is the output of ls -l /mnt/user/appdata/plex/Library/ If it is not nobody:users, then maybe try running: chown -R nobody:users /mnt/user/appdata/plex/* This will step into each sub folder and set the permission to nobody:users. Shouldn't blow anything up, but can't make any promises Also, found this reddit thread that one user seems to indicate the preferences.xml file was empty. They were able to recover it from a backup and got the server up again.

This is how I would do it. Not sure if it is the right way thought. chown nobody:users /mnt/user/appdata/plex/Library/Application Support/Plex Media Server/* That will set the owner to "nobody" and the group to "users", which is the same as mine currently:

My structure looks just like that, however I do not have the "Startup Crash.log". I'm guessing its a permissions issue and Plex can't write to the logging folder.

I'm out of ideas, since the docker is starting up correctly. Just a purely random thought, but I assume you are on the same 10.0.0.0/24 subnet for whatever you are trying to connect to plex on? Outside of that, I would start looking at the plex specific logs. Mine are located here and I assume yours would be similar? /mnt/user/appdata/plex/Library/Application Support/Plex Media Server/Logs Specifically within there, probably look at "Plex Media Servier.log". I assume that the start of that log will/should give some indication of what is going on. If it is any help, this is the start of mine. (The [XXXX] is a hex code that I don't know if is server specific, and the [some token blah blah] maybe server specific). After this it jump immediately into scanning the library for any changes.

Not sure if this is the best spot, but here it is. Had some issues with some *rarr dockers where the database was corrupted. The web interface worked just fine, so I was not aware of any issues at first. I got the first issue right before my CA appdata backup ran, and I was able to restore the backup DB. Also, discovered that I miss configured where it only stored one week of backups. Second time it happened, I had multiple backups I was able to recover from. This lead me to looking for some sort of docker based log analysis tool that can send out either a Unraid UI notification if key words/phrases are found or sending something to pushover/whatever. I already have the syslog server running, but not really finding anything outside of Graylog in the app store. Any recommendations, or advise? I've ran the free version of Splunk before in a VM, and while it did work great, it was a little overkill. I was looking to see if there was another solution outside of a VM? Thanks!

Are you able to connect to the Plex web interface directly from the IP address? Either: ip_for_plex:32400 or ip_for_unraid:32400 depending on how you have the docker container setup.

Thank you to the wonderful team on the Discord server this has been sorted out! Fix listed below: /boot/config/ident.cfg look for the line "USE_SSL="false" and change it to USE_SSL="no"

Installed the my servers plugin this afternoon, with no issues. Saw the "My Servers Error, Graphql is offline", and did a quick forum search, which indicated running: unraid-api restart was the next thing to do. It hangs with the "Value 'false' is not auto/no/yes.". Okay easy enough, with everything computers I apply the reboot method of resolving issues. However, upon reboot the web GUI will not load. I'm able to SSH in, and see that nginx never started. So I start it and get the GUI back. I tried to change the SSL in the my server setting to "auto" (version 6.9.2) and made sure all plugins were updated. SSL, was already set to "auto", so change to "no", then back to "auto" to activate the "Apply" button. Click it, and it basically hangs on the fancy "I'm applying your settings" wave thingy. I give about 30 minutes, and nothing. Still waving at me. Try to run the unraid-api restart again, but it hangs at the same point. I feel I am certainly missing something, but it is late and I'm lost. Attached are some diagnostics from my reboot (I believe) when I had to manually start nginx. I have also restarted the system again, and attaching the current state of diagnositics (had to manually start nginx as well). If I boot into safe mode, can I remove the my servers plugin even though all plugins are disabled? Or is there a config file I can edit via SSH/CLI to change the "false" to "no" that unraid-api is looking for? Thanks! tower-diagnostics-20211123-2240.zip tower-diagnostics-20211123-2317.zip

So this is interesting, apparently my Traktarr Docker is basically a super computer and is using >9EB of RAM: I don't even remember installing that much RAM and it seems to be holding the entirety of the internet in memory...

Changing the temp setting (apply) then changing it back worked great for me. Thanks for the great plug-in!

Thank you! Will give that a go.

Running my monthly parity check on my system and the system became unresponsive numerous times throughout the check. The GUI and console would stop responding for ~30-60 seconds. I've attached a snip of the call trace below as well as the diagnostics, but it seems whatever core of my FX-8370 was pegged to 100% was the core that showed up in the log as "NMI backtrace for cpu X". Nov 30 04:23:03 Tower kernel: NMI backtrace for cpu 1 Nov 30 04:23:03 Tower kernel: CPU: 1 PID: 7410 Comm: unraidd Tainted: P W O 4.19.56-Unraid #1 Nov 30 04:23:03 Tower kernel: Hardware name: To be filled by O.E.M. To be filled by O.E.M./970 PRO GAMING/AURA, BIOS 0901 11/07/2016 Nov 30 04:23:03 Tower kernel: Call Trace: Nov 30 04:23:03 Tower kernel: <IRQ> Nov 30 04:23:03 Tower kernel: dump_stack+0x5d/0x79 Nov 30 04:23:03 Tower kernel: nmi_cpu_backtrace+0x71/0x83 Nov 30 04:23:03 Tower kernel: ? lapic_can_unplug_cpu+0x8e/0x8e Nov 30 04:23:03 Tower kernel: nmi_trigger_cpumask_backtrace+0x57/0xd7 Nov 30 04:23:03 Tower kernel: rcu_dump_cpu_stacks+0x91/0xbb Nov 30 04:23:03 Tower kernel: rcu_check_callbacks+0x28f/0x58e Nov 30 04:23:03 Tower kernel: ? tick_sched_handle.isra.5+0x2f/0x2f Nov 30 04:23:03 Tower kernel: update_process_times+0x23/0x45 Nov 30 04:23:03 Tower kernel: tick_sched_timer+0x36/0x64 Nov 30 04:23:03 Tower kernel: __hrtimer_run_queues+0xb1/0x105 Nov 30 04:23:03 Tower kernel: hrtimer_interrupt+0xf4/0x20d Nov 30 04:23:03 Tower kernel: smp_apic_timer_interrupt+0x79/0x91 Nov 30 04:23:03 Tower kernel: apic_timer_interrupt+0xf/0x20 Nov 30 04:23:03 Tower kernel: </IRQ> The parity check is still jugging along at ~70%. Any thoughts? tower-diagnostics-20191130-2039.zip

Thank you! Both drives are rebuilding currently.

So I fixed the power issue. Both parity drives have shown back up in the array, however they are both marked as disabled. I can see the smart status for both drives from the gui. What is the proper way to re-enable the parity drives now that they have returned? Thanks!

Doing some self diagnostics here. The smart reports for both drives do not indicate any issues. Given that none of the other drivers attached to the LSI-2008 are having issues, I think this narrows it down to one of two possibilities: 1) Power issue to the parity drives 2) Specific damage to the specific SATA break out cables attached to the parity drives. (unlikely) Both of these are easy to rule out as I have additional open SATA ports. I also believe I have additional power options for the drives. Unfortunately I can not explore these possibilities until tomorrow morning as I have pihole (VM) setup as the only DNS server and the wife is actively using the internet. This just shows me I need an additional fail-over pihole setup as a backup. As a side note the system was only direct streaming a show locally at the time this occurred. Forgot to mention the system configuration: AMD FX-8370 on a ASUS 970 Pro Gaming/Aura with 32 GB of DDR3 RAM (Non-ECC) Parity: 2x HGST NAS 4TB Data: 7x WD Red NAS 3TB, 1x WD Red NAS 4tb (25TB Total) Cache: Scandisk 480 480GB SSD Unassigned: 2x Kingston 120GB SSDs GPU: GTX 1060 for Plex (docker) Transcoding Power supply: Name brand bronze level(?) 500W -- Calculators say I maybe pushing it and will be my next upgrade Unraid PRO 6.7.2 (NVIDIA version)