Fatal Error In Emby on Linux

[tmurphy2792 27]

Hello All, I've stumbled upon what appears to be a very serious error in emby running on linux.

Backstory:
Before I get into the error itself it's probably worth giving some backstory on my specific situation in case this error is very specific to my circumstances. A few months ago I migrated from running emby on a windows host machine to running it inside a Container in Proxmox. That migration itself went fine, other than the headaches of different paths making me rescan my entire libraries and bricking all of my playlists, collections, and plugins. (This ties into the issue later).
So today I was doing some additional cleanup from that and decided to get rid of some of these old playlists.

Issue:
I selected one of the playlists and selected "Delete" it warned me about deleting from /var/lib/emby which I didn't initially think much about (my mistake) because that looked about like the path I recall playlists being stored at.
After clicking confirm I got an error about "Access to path '' is denied". Weird, I'll go delete it from the host machine manually. That's when I noticed /var/lib/emby was entirely empty. A reboot of the emby server confirmed my fears and it's acting like a brand new install.
Fortunately I have my backups stored elsewhere and I'll be able to revert to a backup from a few hours ago, but still not a desired function at all.

TLDR:
Deleting a playlist that was brought in from a backup is the same as telling emby to go skydiving without a parachute, as it deletes the entire contents of /var/lib/emby folder.

[Luke 42077]

Hi there, please attach the Emby server log from when the problem occurred:

How to Report a Problem

Thanks!

 

[tmurphy2792 27]

1 minute ago, Luke said:

Hi there, please attach the Emby server log from when the problem occurred:

How to Report a Problem

Thanks!

 

Unless I'm mistaken, it looks like the logs got wiped out. Literally the entire contents of /var/lib/emby were gone, the directory was left completely empty without any of the usual sub directories (logs, for instance).

I have archived the backup from just before this happened so that it doesn't get overwritten.

If you guys need help recreating the issue for troubleshooting I can get you a cleaned up copy of this backup with a user and pass to recreate the issue yourselves? Alternatively I can spin up an LXC to recreate the issue, hopefully if I recreate the logs folder it will still have the logs in memory and attempt to write them there?

[Luke 42077]

Quote

hopefully if I recreate the logs folder it will still have the logs in memory and attempt to write them there?

Hi, that would be great. We'd certainly take a look at them. Thanks.

[tmurphy2792 27]

15 hours ago, Luke said:

Hi, that would be great. We'd certainly take a look at them. Thanks.

Ok, I'll try to get to it whenever I can get some free time.