+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Conflict on Nixos (/t-conflict-on-nixos)
Conflict on Nixos - Smithoo4 - 2023-10-23
I have been playing around with building a media server using Jellyfin along with Sonarr, Radarr and Jackett on Nixos using the native packages. I can get everything working, but I am running into an issue where Jellyfin play back will stop working. When I go play something the poster will come up but will never play. Also, when I log into the web app and am not playing anything the blue circle in the center of the page indicating processing will always be there.
I have been watching the Jellyfin error logs and will get stuff like:
Code:
Jellyfin.Server.Middleware.ExceptionMiddleware: Error processing request. URL "GET" "/LiveTv/Programs/Recommended".
System.UnauthorizedAccessException: Access to the path '/dev/shm/lttng-ust-wait-8-276' is denied.Or
Code:
Jellyfin.Server.Middleware.ExceptionMiddleware: Error processing request. URL "GET" "/LiveTv/Programs/Recommended".
System.UnauthorizedAccessException: Access to the path '/dev/shm/mono.1607' is denied.When I look in /dev/shm:
Code:
sudo ls -la /dev/shm/
total 12
drwxrwxrwt 2 root root 100 Oct 23 11:30 .
drwxr-xr-x 19 root root 3540 Oct 23 12:12 ..
-rw-rw-rw- 1 jackett media 4096 Oct 23 08:04 lttng-ust-wait-8
-rw-r----- 1 jackett media 4096 Oct 23 08:04 lttng-ust-wait-8-276
-rw-r----- 1 sonarr media 4096 Oct 23 08:04 mono.1607 I should point out that don’t think I have ever seen a Radarr file here, but I am lumping it in with the rest.
I think what is going on here is that Sonarr, Radarr or Jackett are creating these files first and setting the permission such that Jellyfin can’t access them. I have tested this by disabling Sonarr, Radarr or Jackett and removing the files and when I do so Jellyfin works fine.
I am not sure if this is an issue with Nixos, Jellyfin, etc. or an underlining library like mono so I am not sure where to post a bug report. I am posting here to see if someone smarter than me has any idea how to procced. Or point out its user error and I am just doing something wrong.
Thank you!
RE: Conflict on Nixos - TheDreadPirate - 2023-10-23
Can you replicate the problem and share your log with us? Upload to pastebin. Are you having trouble with all your media or just live TV? Is your transcode directory /dev/shm?
RE: Conflict on Nixos - Smithoo4 - 2023-10-24
Hello
Below is a Pastebin link to the logs with the problem replicate.
https://pastebin.com/8TnQwibg
I am having trouble with all media on both the web interface, Ios and Android tv apps; it will just not play. The web interface itself does not seem to work correct, as it always acts like it is trying to load something. Also, I don't use the live TV function.
My Transcode directory is /dev/shm. The hardware I plan on using has a fair amount of ram and an old SSD that am worried is near the end of its life. Transcoding in memory (/dev/shm) seemed like a good choice. I have changed the Transcode directory to another location and everything seems to work. So I guess this could be a solution.
There is probably some good documentation out there on different options to transcode in memory if /dev/shm does not work, and I just need to do some Googling. However, does anyone have some recommendation here? Would creating a separate tmpfs directory be a good option? Or am I just worrying too much about the life of my SSD?
Thank you for your help
RE: Conflict on Nixos - TheDreadPirate - 2023-10-24
Taking another look at the permissions in your first post, jellyfin does not have write permissions to /dev/shm/. I use a separate tmpfs for my RAM disk transcode directory (see my signature). It allows me to control the permissions for exactly this reason.
When I get some time later I will screenshot my /etc/fstab for your reference.
RE: Conflict on Nixos - TheDreadPirate - 2023-10-25
Attached.
Code:
sudo mkdir /media/ramdisk
sudo nano /etc/fstab
**Make sure you change the size to fit in your total RAM minus typical memory usage minus some headroom**
mount -a