Whilst there were issues in installing Jellyfin after the rebuild, it did eventually load up, however the port used for accessing wasn’t 8096 but another which caused problems when opening/starting the Rockon (Of course it did), one of the issues was getting Jellyfin to load up which was eventually managed by changing the port addresses.
There were also other minor irritations (once running) such as selecting a film for adding to a collection, Jellyfin just added all of the titles to the collection and removing them couldn’t be accomplished.
So
Tried the reboot trick. No Joy
Uninstalled Jellyfin
Deleted all Jellyfin configs.
A new Jellyfin Config was generated with the (assumed) correct port addresses (This time located in the Root pool).
Went through the set process which failed, tried several times, deleted the config share, generated a new one repeated the install.
But
The set up process didn’t request a Config file only a media file.
Rebooted
No install
Rebooted No Jellyfin Config share present in share list (Just checking that it had been deleted)
Still no request on Jellyfin set up screen for a Config share. Anyone have any ideas on this? How to install without a Config Share?
This is very strange indeed. After the de-installation, did you also explicitly delete the Rockon and run a refresh on the overall Rockon list? Usually, that would not be necessary, but in your case, where stuff seems to be messed up, it’s probably the prudent thing to do:
from the WebUI:
su -
(will ask for the root password)
cd /opt/rockstor/
poetry run delete-rockon 'jellyfin'
The only difference between my and your summary, aside the missing config share is the VAAPI device, though I don’t think that will fundamentally sabotage jellyfin from coming up.
Since you rebuilt the system, I do assume that there is no custom version of the jellyfin Rockon anywhere on that box, so that should not be a factor.
Thanks @Hooverdan
Applied the CL code and reinstalled Jellyfin with new config, install process didn’t like the entry for the VAAPI section, tried your suggestion, then just the /dev/dri option without any success, reviewed the log and found the vaapi entry not recognised in any attempt so left it blank and Jellyfin installed.
Went through the set up process (including DLNA plug in this time) and all seems to be working.
Thinking that the it might be a bonus to use the GPU ability of the Xeon E3 1285L V4 The Transcoder section was initiated with the /dev/dri/renderD128 option selected as well as the Intel Quicksync. Hopefully that should be all functional, time will tell.
The collections library also works correctly.
There must be somewhere (on each individual system) that retains data that has caused this bug, rather beyond me I’m afraid.
Thanks again @Hooverdan
By the way, have you improved your setup with case badges available either FREE or on ebay for dirt cheap? They come pre-balanced for easy installation and zero vibration whilst controlling electron flow through chassis buggy bumpers…
