You are not logged in.
GNU nano 5.3 test
I have a subvolume I created to manage my emby server. I mounted it where the server is supposed to live at
/var/lib/emby. I then made the appropriate fstab>
After syncing some files there and not seeing a response from the server, I investigated and the volume was instead mounted at
/var/lib/private/emby. Assuming I made a mistake, I double-checked my fstab, unmounted the device and rebooted. When the system came back up, it was again at the private mount point.
Why is this happening and how can I fix this. Oddly, emby, works just fine when I put it's configs there. As though the emby user made a decision of sorts to just live there instead.
I uninstalled emby-server, deleted the user and group associated with the service, deleted the 'private' directory itself, reconfigured and again, the subvolume is mounted in the wrong place.
I am running kernel 5.4.73-1-lts
Offline
I deleted the subvolume in question, purged emby service, and rebooted. The device does in fact mount properly now. However when I re-installed emby and loaded the service, systemd had this to say:
Nov 01 07:20:38 kyzer systemd[1]: Started Emby brings together your videos, music, photos, and live television..
Nov 01 07:20:38 kyzer systemd[1344]: Found pre-existing public StateDirectory= directory /var/lib/emby, migrating to /var/lib/private/emby.
Nov 01 07:20:38 kyzer systemd[1344]: Apparently, service previously had DynamicUser= turned off, and has now turned it on.
Nov 01 07:20:38 kyzer systemd[1344]: emby-server.service: Failed to set up special execution directory in /var/lib: Device or resource busy
Nov 01 07:20:38 kyzer systemd[1344]: emby-server.service: Failed at step STATE_DIRECTORY spawning /usr/bin/emby-server: Device or resource busy
Nov 01 07:20:38 kyzer systemd[1]: emby-server.service: Main process exited, code=exited, status=238/STATE_DIRECTORY
Nov 01 07:20:38 kyzer systemd[1]: emby-server.service: Failed with result 'exit-code'.I mean, I guess I can work with emby running at /var/lib/private but it is really sub-optimal to my setup and I'm quite curious how I can avoid this happening again.
Offline
I am reading this: Dynamic_Users_with_systemd right now...
Offline