Hello,

since the 4th of july there is this warning (an others?) in my logs.

Could this be critical? And what could cause this?

 

Thanks for your help!

 

 

server-diagnostics-20230712-1137.zip

I'm used to see that segfault in various diags, so most likely normal and harmless.

I only very recently started noticing these segfaults as well and wondered if I have RAM that is starting to fail or something.  Server seems to be running normally. 

Shooting from the hip here.  Looks like Plex having an issues during audio scans (probably during maintenance).

 

If it were me, I would delete all of the files in my Plex codecs folder.  This is a common fix for funky encoding issues with Plex, which has been going on for years.  Your Plex application will download and reinstall a fresh copy of the codecs automatically.  I typically stop the docker, delete the contents of the folder, then restart the container.

 

It may solve the issue.  It may not.  But worth a try.

Thanks ConnerVT, your explanation could have been possible, because my system is just running a vm with homeassistant and the Plex Server Docker. But after deleting the codec and waiting for one night (the segfault errors take place just nearly at the same time every night), there are just the same errors again.

@Janosch I'm having the same issue. Did you ever find a solution?

I also deleted the contents of the Plex codecs folder. The errors didn't appear for a couple of nights, but during the third night they appeared again.

On 10/21/2023 at 11:43 AM, LordShaaver said:

@Janosch I'm having the same issue. Did you ever find a solution?

I also deleted the contents of the Plex codecs folder. The errors didn't appear for a couple of nights, but during the third night they appeared again.

Hey @LordShaaver, no, there´s no solution yet, every night at nearly the same time, there are 6 new warnings in the log. Even deactivating the Plex Docker didn´t help.

I spoke to a Linux Expert and he notes that this problem also could indicate some hardware issues, but he isn´t knowing something about Unraid in special.

@Janosch I'm so sorry for not seeing your response until now! I kind of solved the issue from my end by reducing the maintenance time for Plex and in doing so reducing how long Plex do the audio scan. I had it previously set to almost a full day and not only during the night. I noticed that if I let Plex do the audio scan for a long period of time, my unraid server became unstable and would crash after a while. I haven't been seeing the issue since I reduced the maintenance time. I still see the error though, but not as frequent. The error became more frequent the longer the scan would go for.

@LordShaaver thanks for sharing your idea. I´ve not found the options about audio scan and managing the maintenance time for this special section. But I shifted the whole maintenance time and it proves, that the warnings in the log are somehow relaited to Plex, because they shifted also.

On 12/22/2023 at 5:59 AM, Janosch said:

@LordShaaver thanks for sharing your idea. I´ve not found the options about audio scan and managing the maintenance time for this special section. But I shifted the whole maintenance time and it proves, that the warnings in the log are somehow relaited to Plex, because they shifted also.

 

I'm also seeing this issue in the logs.  As for the setting mentioned if you go to your config settings and under Settings-->Library you'll see the following two settings:

 

Analyze audio tracks for loudness

Analyze audio tracks for sonic features 

 

Both of these have the text "It can take a long time to complete when analyzing many tracks, and cause high CPU usage."

 

I've set mine to never and will see if the logs clear up.