SOLVED: Audio Transcode Failing

[roughnecknine0]

Code:

journalctl -u jellyfin.service -xe
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit jellyfin.service has begun execution.
░░
░░ The job identifier is 431.
Mar 24 23:08:46 Jellyfinx13x8096 systemd[1]: jellyfin.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit jellyfin.service has successfully entered the 'dead' state.
Mar 24 23:08:46 Jellyfinx13x8096 systemd[1]: Stopped Jellyfin Media Server.
░░ Subject: A stop job for unit jellyfin.service has finished
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit jellyfin.service has finished.
░░
░░ The job identifier is 431 and the job result is done.
Mar 24 23:08:46 Jellyfinx13x8096 systemd[1]: jellyfin.service: Consumed 24min 31.384s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit jellyfin.service completed and consumed the indicated resources.
-- Boot 08fff356a6ab449e9ecc2170cf12141d --
Mar 24 23:10:09 Jellyfinx13x8096 systemd[1]: Started Jellyfin Media Server.
░░ Subject: A start job for unit jellyfin.service has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit jellyfin.service has finished successfully.
░░
░░ The job identifier is 104.
Mar 24 23:10:12 Jellyfinx13x8096 jellyfin[103]: [23:10:12] [WRN] The WebRootPath was not found: /var/lib/jellyfin/wwwroot. Static files may be unavailable.

or via privatebin

[TheDreadPirate]

I have no idea what is going on. Something is fundamentally broken. And I'm leaning towards something with the OS.

[roughnecknine0]

Well thanks for looking, I do appreciate it.

My thought at this point is to delete the container and rebuild. I originally used a VE Helper script to install but maybe this time I try it manually.

ETA: Spun up a new container & install, logs seem to be functioning normally. I'm going to file this as complete and create a new thread if I see the original issue again.