2024-07-24, 07:38 PM
(This post was last modified: 2024-07-24, 07:39 PM by Jam. Edited 1 time in total.)
So i've just had my latest hold up, I didn't let it get to the point of crashing but everything was seizing up as usual.
I have captured another log file, incase anything shows.
https://gist.githubusercontent.com/JamsR...tfile1.txt
Also, this time I took a look at system usage and I see that Jellyfin is using a LOT more than than it normally does. It normally grabs about 9GB max, we're now up to 16.
![[Image: OMESB7m.png]](https://i.imgur.com/OMESB7m.png)
Also, you can't see it too clearly in these next photos but Jellyfin is spiking up and using a lot of CPU power too.
![[Image: ZQwjq3W.png]](https://i.imgur.com/ZQwjq3W.png)
![[Image: FwcV1qK.png]](https://i.imgur.com/FwcV1qK.png)
I also went as far as rolling back to the previous Unraid version to rule out the factor of it being that update that could've potentially caused it, as the last one was where I had the most stability and it still occurs.
You can also see the CPU_TOTAL alert ran for a total of 2 hours and 13 minutes with 98% CPU usage.
I'm leaning more towards there's an underlying cause within Jellyfin.
I have captured another log file, incase anything shows.
https://gist.githubusercontent.com/JamsR...tfile1.txt
Also, this time I took a look at system usage and I see that Jellyfin is using a LOT more than than it normally does. It normally grabs about 9GB max, we're now up to 16.
Also, you can't see it too clearly in these next photos but Jellyfin is spiking up and using a lot of CPU power too.
I also went as far as rolling back to the previous Unraid version to rule out the factor of it being that update that could've potentially caused it, as the last one was where I had the most stability and it still occurs.
You can also see the CPU_TOTAL alert ran for a total of 2 hours and 13 minutes with 98% CPU usage.
I'm leaning more towards there's an underlying cause within Jellyfin.