Open boxpenguin opened 6 years ago
Thanks for that...yeah, anything above 16.04 isn’t currently supported. It’s something that I’ve been putting off for a while as it wasn’t a high priority but considering we’re now a major LTS behind (as 17.04 wasn’t an LTS) it’s getting to the point that I need to allocate some time to it once I get some critical things dealt to so I can push my systems up off 16.04. You won’t have issues with 16.04.
I upgraded one of my slaves to 18.04...hit the exact same issue you had and I believe I might have found the issue. It was with the standard 18.04 configuration it pushes on the users. I’m going to let the slave run for a few days to be sure I’ve correctly identified & resolved the root cause. But so far so good! I’ll just need to look at upgrading the master at some point then I’ll update the wiki with the details & supported version too.
Master is now on 18.04 so it’s looking good (apart from Ubuntu issues with the upgrade which I’ve fixed all but one which isn’t critical or PMS/PRT impacting and I’ll sort that soon) but again I’ll give it a few days to bed in before officially saying it’s supported.
I spun up three Ubuntu 18 LTS VMs in Virtual Box. Connected the compute-node (master) to the other two compute-00 and compute-01. Linked all the NFS and the setup as suggested in the wiki. Media is a NFS share from local server with the correct NFS settings. However I keep getting these errors on the compute-00/01 at the start of each task.
It previously had issues with the libcrypto
I resolved that by moving the libs in /usr/lib/pms away and linking the local (/usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
So no activity on any of the nodes and I can get the media to read just fine and appear on the web app. Direct media also works and is logged on the node as normal but anything needing trans coding sits in limbo and gives up.
I might try throwing 14 LTS and 16 LTS at this but just wanted to share my efforts.