I am installing Kaltura on Debian 8.0 (Jessie) following these instructions.
Some of the packages are failing to install due to missing dependencies. For example when installing kaltura-batch I get the following error.
The following packages have unmet dependencies:
kaltura-batch : Depends: mencoder which is a virtual package.
kaltura-ffmpeg : Depends: libass4 which is a virtual package.
Depends: libopenjpeg2 which is a virtual package.
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) kaltura-batch [Not Installed]
2) kaltura-ffmpeg [Not Installed]
It appears that libass4 is not available in Jessie, but has been replaced with libass5. It seems that libopenjpeg2 is similar. The install document above says that the process has been tested on Debian 8, so I am wondering if I am missing some repositories, or if there is a way to update the dependencies. Or do I need to roll back to Debian 7?
Seems fine on my Debian 8:
root@debian:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie
Would you mind sharing part of your sources.list so I can see which wheezy repos need to be present in addition to the jessie ones? Right now my sources.list has jessie only.
deb htp://ftp.us.debian.org/debian/ wheezy main
deb htp://security.debian.org/ wheezy/updates main
I needed security as well for the mencoder package.
So now my sources.list looks like this:
deb htp://ftp.us.debian.org/debian/ jessie main non-free
deb-src htp://ftp.us.debian.org/debian/ jessie main
deb htp://security.debian.org/ jessie/updates main non-free
deb-src htp://security.debian.org/ jessie/updates main
deb htp://ftp.us.debian.org/debian/ jessie-updates main
deb-src htp://ftp.us.debian.org/debian/ jessie-updates main
deb htp://ftp.us.debian.org/debian/ wheezy main
deb htp://security.debian.org/ wheezy/updates main
Note that I also had to downgrade the package libdvdnav4 to the wheezy version so mencoder and mplayer did not break.
Note also that I had to modify all the urls in the sources.list here due to the forum rules (new users can only post 2 links).
Thanks for the update.
I’ll see if we may want to just include the libass4 packages in our own repo so this won’t be needed. Was it the only package that was amiss in the official Jessie repos?
There were several other packages, unfortunately they have disappeared off my terminal history now. Here are the ones I remember:
mencoder
mplayer
libopenjpeg2
I have run into an issue now with the install in the kaltura-front package. Here is the error that is occurring:
# dpkg-reconfigure kaltura-front
Site zzzkaltura disabled.
To activate the new configuration, you need to run:
service apache2 reload
Enabling site zzzkaltura.
To activate the new configuration, you need to run:
service apache2 reload
Site apps already enabled
Site var already enabled
Site admin already enabled
PHP Fatal error: Uncaught exception 'Exception' with message 'Storage Profile [] not found' in /opt/kaltura/app/alpha/apps/kaltura/lib/storage/kPathManager.php:77
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/storage/kFileSyncUtils.class.php(953): kPathManager::getFilePathArr(Object(FileSyncKey))
#1 /opt/kaltura/app/alpha/apps/kaltura/lib/storage/kFileSyncUtils.class.php(215): kFileSyncUtils::getLocalFilePathArrForKey(Object(FileSyncKey))
#2 /opt/kaltura/app/alpha/lib/model/uiConf.php(340): kFileSyncUtils::file_put_contents(Object(FileSyncKey), '{"version":"v1....')
#3 /opt/kaltura/app/alpha/lib/model/uiConf.php(143): uiConf->saveConfFileToDisk('{"version":"v1....', 'config', false)
#4 /opt/kaltura/app/deployment/uiconf/deploy_v2.php(356): uiConf->save()
#5 /opt/kaltura/app/deployment/uiconf/deploy_v2.php(181): uiConfDeployment::addUiConfThroughPropel(Object(uiConf))
#6 /opt/kaltura/app/deployment/uiconf/deploy_v2.php(49): uiConfDeployment::deploy(Object(Zend_Config_Ini))
#7 {main}
thrown in /opt/kaltura/app/alpha/apps/kaltura/lib/storage/kPathManager.php on line 77
chown: cannot access ‘/opt/kaltura/web/content/generatedUiConf/’: No such file or directory
I ignored the error initially, but I am getting an error with API calls in the configure of the kaltura-db package so I assume that kaltura-front is not properly set up yet.
Yes I did use that script to do the install. I have done dpkg-reconfigure kaltura-db and it fails trying to make a call to the API. I don’t have access to the machine right now, but I will get you the specific error when I do.
However, since the install of kaltura-front happens earlier in the script than kaltura-db I assumed that the kaltura-front error was causing the kaltura-db error.
Yes, the DB population phase requires making REST calls to the server, if the kaltura-front setup did not end correctly, DB phase will fail. Let me know when you have findings.
So dpkg-reconfigure kaltura-front is failing with the error posted in my earlier repsonse above (item 7).
I think I caused confusion in that post by mentioning kaltura-db failures. But the main failure I am seeing right now is with kaltura-front.
Ah, yes I dropped the DB and now dpkg-reconfigure kaltura-front is successful. Thanks!
dpkg-reconfigure kaltura-db was also failing until I installed the curl package. Maybe it should be a dependency, or at least noted in the install process that curl is required?
Just running through a final dpkg-reconfigure kaltura-dwh which is taking a long time, but that appears to be expected. I expect all the issues are resolved now.
Thanks for your help!
I thought about starting a new thread, but thought the history here might be important.
I am getting a 500 response when trying to log in to the admin console. Here are the access logs:
There are a lot of 404 responses to the other services so it seems like something is not quite right. I was thinking maybe I should run the drop database script and then dpkg-reconfigure everything. Does that make sense or is there other things to try first?
firstly, is kcetest resolvable from both the machine itself and your client [machine where the browser runs]?
secondly, if so, is the Kaltura Vhost correctly configured? it must have been at some point because otherwise the DB deployment would have failed but perhaps something changed? check with:
# apachectl -t -DDUMP_VHOSTS
and then run the curl yourself to see if it correctly replies with HTTP 200.
