First, just to make sure, you are logging into KMC with a partner you created in the admin console and not with the admin console credentials, correct?
Next, best way to start debugging it would be to run:
from the server’s shell while making the request and look at the output. Then go to the actual log where the error occurs and look at the lines leading to the error.
Feel free to paste the log entries here so we can further help you.
This has never been updated as far as I’m aware, this was a clean install of 10.19.0 - we hired a freelancer to install it as we were having numerous issues with the SSL install and we didn’t have the Linux knowledge to fix all the SSL issues we kept experiencing during the setup process.
I’ve been away for the past 2 weeks, but everything worked prior to that (the server was rebooted whilst I was away, but as far as i know nothing has changed).
Its possible that your server is configured to automatically update packages upon init…
In any event, just run the following in that order:
# aptitude update
# aptitude install ~Nkaltura
# dpkg-reconfigure kaltura-base
# dpkg-reconfigure kaltura-front
# dpkg-reconfigure kaltura-batch
And you should be good. debconf will remember the answers from your last run, unless something changed, there is no need to touch the default values shown to you during the reconfig stage.
That means that aptitude is not installed on your machine, only apt-get.
You can just replace the command ‘aptitude’ with ‘apt-get’ but I advise you to install aptitude with:
# apt-get install aptitude
both tools can be used but aptitude has a better API and somewhat improved decision making algorithms.
LSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch
Distributor ID: RedHatEnterpriseServer
Description: Red Hat Enterprise Linux Server release 6.7 (Santiago)
Please excuse the silly questions, but does that mean everything under the heading Upgrade Kaltura
I only ask as i don’t want to run something that may potentially stop the server from working, and since this was originally setup by a third party, i just want to be sure that any actions i take are the correct ones.
This being Linux there are multiple ways of doing everything, including auto updates. It can be done by adding a line to /etc/rc.local, by adding a cron job and many many other ways, including https://fedoraproject.org/wiki/AutoUpdates. Therefore, you should consult the people who setup the server.
In general, I’d recommend against auto updates on Prod. servers. Instead, you can have the machine email you when new updates are pending so you can decide what you want to do. Ideally, what you want to do is test them on a test ENV first:)