Debian 8.0 Jessie installation missing dependencies

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?

Also, how is the install going?
:slight_smile:

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.

Did you use the http://installrepo.kaltura.org/repo/apt/debian/install_kaltura_all_in_1.sh script to install?
It seems like something went wrong during the deployment of the DB, which happens in the kaltura-db postinst phase.

Can you try dpkg-reconfigure kaltura-db and see if it passes correctly?

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.

Hello,

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.

This error is due to a half baked DB that currently exists. Please drop it /opt/kaltura/bin/kaltura-drop-db.sh and reconfigure again.

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?

Certainly should be added as dep. Doing it now. Thanks.
Is the deployment functional now?

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!

My pleasure. Let me know if there are issues. I also pushed a new kaltura-base deb and declared curl as a dep.

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:

192.168.4.17 - - [30/Apr/2015:11:29:36 -0600] “GET /admin_console/index.php/user/login HTTP/1.1” 200 1867 “-” "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.90 Safari/537.36"
127.0.0.1 - - [30/Apr/2015:11:29:38 -0600] “POST /api_v3/index.php?service=livestream&action=list HTTP/1.1” 404 459 “-” "-"
127.0.0.1 - - [30/Apr/2015:11:29:43 -0600] “POST /api_v3/index.php?service=system&action=ping HTTP/1.1” 404 459 “-” "-"
127.0.0.1 - - [30/Apr/2015:11:29:59 -0600] “POST /api_v3/index.php?service=system&action=ping HTTP/1.1” 404 459 “-” "-"
127.0.0.1 - - [30/Apr/2015:11:30:02 -0600] “POST /api_v3/index.php?service=batch&action=updatePartnerLoadTable HTTP/1.1” 404 459 “-” "-"
127.0.0.1 - - [30/Apr/2015:11:30:02 -0600] “POST /api_v3/index.php?service=batch&action=cleanExclusiveJobs HTTP/1.1” 404 459 “-” "-"
127.0.0.1 - - [30/Apr/2015:11:30:02 -0600] “POST /api_v3/index.php?service=batch&action=suspendJobs HTTP/1.1” 404 459 “-” "-"
127.0.0.1 - - [30/Apr/2015:11:30:09 -0600] “POST /api_v3/index.php?service=livestream&action=list HTTP/1.1” 404 459 “-” "-"
127.0.0.1 - - [30/Apr/2015:11:30:15 -0600] “POST /api_v3/index.php?service=system&action=ping HTTP/1.1” 404 459 “-” "-"
127.0.0.1 - - [30/Apr/2015:11:30:21 -0600] “POST /api_v3/index.php?service=user&action=loginByLoginId HTTP/1.1” 404 459 “-” "-"
192.168.4.17 - - [30/Apr/2015:11:30:21 -0600] “POST /admin_console/index.php/user/login HTTP/1.1” 500 1015 “http://kcetest/admin_console/index.php/user/login” "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.90 Safari/537.36"
192.168.4.17 - - [30/Apr/2015:11:30:21 -0600] “GET /admin_console/css/style.css HTTP/1.1” 404 542 “http://kcetest/admin_console/index.php/user/login” "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.90 Safari/537.36"
127.0.0.1 - - [30/Apr/2015:11:30:29 -0600] “POST /api_v3/index.php?service=dropfolder_dropfolder&action=list HTTP/1.1” 404 459 “-” “-”

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?

Can you run:
# . /etc/profile.d/kaltura_base.sh
# kaltlog

and then make the request and check for errors. error 500 means that the PHP code throws some fatal error, lets find it:)

Here is the log of the error and some surrounding errors. I have modified it slightly to protect email and password information.

--
#6 {main}
2015-04-30 15:39:10 [115726407] [InfraBootstrapper->_initNavigation] ERR: exception 'Exception' with message 'Class [DropFolderSetStatusAction] requires permissions [Array
(
--
]' in /opt/kaltura/app/infra/log/KalturaLog.php:82
Stack trace:
#0 /opt/kaltura/app/ui_infra/InfraBootstrapper.php(113): KalturaLog::err('Class [DropFold...')
--
#6 {main}
2015-04-30 15:39:10 [115726407] [InfraBootstrapper->_initNavigation] ERR: exception 'Exception' with message 'Class [EventNotificationTemplatesListAction] requires permissions [Array
(
--
]' in /opt/kaltura/app/infra/log/KalturaLog.php:82
Stack trace:
#0 /opt/kaltura/app/ui_infra/InfraBootstrapper.php(113): KalturaLog::err('Class [EventNot...')
--
#6 {main}
2015-04-30 15:39:10 [115726407] [InfraBootstrapper->_initNavigation] ERR: exception 'Exception' with message 'Class [EventNotificationTemplateConfigureAction] requires permissions [Array
(
--
]' in /opt/kaltura/app/infra/log/KalturaLog.php:82
Stack trace:
#0 /opt/kaltura/app/ui_infra/InfraBootstrapper.php(113): KalturaLog::err('Class [EventNot...')
--
#6 {main}
2015-04-30 15:39:10 [115726407] [InfraBootstrapper->_initNavigation] ERR: exception 'Exception' with message 'Class [EventNotificationTemplateUpdateStatusAction] requires permissions [Array
(
--
]' in /opt/kaltura/app/infra/log/KalturaLog.php:82
Stack trace:
#0 /opt/kaltura/app/ui_infra/InfraBootstrapper.php(113): KalturaLog::err('Class [EventNot...')
--
2015-04-30 15:39:10 [115726407] [Kaltura_Client_ClientBase->doCurl] DEBUG: curl: http://kcetest:80/api_v3/index.php?service=user&action=loginByLoginId&format=2&ignoreNull=1&clientTag=Kaltura-admin&apiVersion=3.2.0&loginId=jramer%40email.com&password=password&partnerId=-2&privileges=disableentitlement&kalsig=64304a389fb2c13017569788b5a6db45
2015-04-30 15:39:10 [115726407] [ErrorController->errorAction] ERR: exception 'Kaltura_Client_ClientException' with message '. RC : 404' in /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php:242
Stack trace:
#0 /opt/kaltura/app/admin_console/lib/Kaltura/Client/UserService.php(177): Kaltura_Client_ClientBase->doQueue()
--
==> /opt/kaltura/log/batch/dbcleanup-0-2015-04-30.err.log <==
PHP Fatal error:  Uncaught exception 'KalturaClientException' with message 'failed to unserialize server result
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
--
' in /opt/kaltura/app/batch/client/KalturaClientBase.php:401
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1309): KalturaClientBase->doQueue()
--
==> /opt/kaltura/log/batch/partnerloadcleanup-0-2015-04-30.err.log <==
PHP Fatal error:  Uncaught exception 'KalturaClientException' with message 'failed to unserialize server result
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
--
' in /opt/kaltura/app/batch/client/KalturaClientBase.php:401
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1127): KalturaClientBase->doQueue()
--
==> /opt/kaltura/log/batch/jobsuspender-0-2015-04-30.err.log <==
PHP Fatal error:  Uncaught exception 'KalturaClientException' with message 'failed to unserialize server result
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
--
' in /opt/kaltura/app/batch/client/KalturaClientBase.php:401
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1144): KalturaClientBase->doQueue()
--

2015-04-30 15:39:16 [2052456025] [KScheduleHelper->run] ERR: exception 'Exception' with message 'System is not yet ready - ping failed' in /opt/kaltura/app/infra/log/KalturaLog.php:82
Stack trace:
#0 /opt/kaltura/app/batch/batches/KScheduleHelper.class.php(44): KalturaLog::err('System is not y...')
--
==> /opt/kaltura/log/batch/validatelivemediaservers-0-2015-04-30.err.log <==
PHP Fatal error:  Uncaught exception 'KalturaClientException' with message 'failed to unserialize server result
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
--
' in /opt/kaltura/app/batch/client/KalturaClientBase.php:401
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(4175): KalturaClientBase->doQueue()

Hello,

It seems calls to the service URL fail, like:
http://kcetest:80/api_v3/index.php?service=user&action=loginByLoginId&format=2&ignoreNull=1&clientTag=Kaltura-admin&apiVersion=3.2.0&loginId=jramer%40email.com&password=password&partnerId=-2&privileges=disableentitlement&kalsig=64304a389fb2c13017569788b5a6db4

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.

Looks like it was an issue with the vhosts.

# apachectl -t -DDUMP_VHOSTS
VirtualHost configuration:
*:80                   is a NameVirtualHost
         default server kcetest.domain.com (/etc/apache2/sites-enabled/000-default.conf:1)
         port 80 namevhost kcetest.domain.com (/etc/apache2/sites-enabled/000-default.conf:1)
         port 80 namevhost kcetest.domain.com (/etc/apache2/sites-enabled/zzzkaltura.conf:1)
                 alias kcetest.domain.com
                 alias kcetest

The default server was using the same name. I changed the default server name and now the calls are working.

One last thing. I can’t seem to log in with the admin user I created during the install. Is there a way to set up that user manually, or do I need to reconfig a package?

Please follow:

To reset the passwd. You can also just hit the forgot passwd href and it will send you an email with a link to reset.

Hmm, looks like my user does not exists at all:

mysql> use kaltura
mysql> select * from user_login_data;
Empty set (0.00 sec)

Similar exception in the logs

--
#7 {main}
2015-05-01 09:33:39 [0.000392] [127.0.0.1] [2087144562] [API] [KalturaFrontController->getExceptionObject] ERR: exception 'KalturaAPIException' with message 'User was not found' in /opt/kaltura/app/api_v3/lib/KalturaBaseUserService.php:187
Stack trace:
#0 /opt/kaltura/app/api_v3/services/UserService.php(360): KalturaBaseUserService->loginImpl(NULL, 'jramer@emaildom...', 'password', -2, 86400, 'disableentitlem...')

So I could probably add a line to the DB, but I am wondering if this indicates something wasn’t set up properly. Maybe I should drop the kaltura db and start all reconfigures from scratch…

I suggest you drop the DB with kaltura-drop-db.sh and then reconfigure kaltura-db.

Please make sure it completes correctly. Other packages do not need reconfiguration. Before you commence, just make sure the call to http://$SERVICE_URL/api_v3 returns with HTTP 200.

That did the trick. Clearly the vhost settings from earlier were causing an issue with the API calls made during DB setup. Login seems to be working now. Thanks again Jess!