Debian 8.0 Jessie installation missing dependencies

jramer · May 1, 2015, 3:22pm

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?

jess · May 1, 2015, 3:39pm

Please follow:

github.com

kaltura/platform-install-packages/blob/Jupiter-10.9.0/doc/kaltura-packages-faq.md#cannot-login-to-admin-console

# Frequently Asked Questions

### Before You Get Started Notes
* If you see a `#` at the beginning of a line, this line should be run as `root`.

### Commercial Editions and Paid Support

The Open Source Kaltura Platform is provided under the [AGPLv3 license](http://www.gnu.org/licenses/agpl-3.0.html) and with no commercial support or liability.  

[Kaltura Inc.](http://corp.kaltura.com) also provides commercial solutions and services including pro-active platform monitoring, applications, SLA, 24/7 support and professional services. If you're looking for a commercially supported video platform  with integrations to commercial encoders, streaming servers, eCDN, DRM and more - Start a [Free Trial of the Kaltura.com Hosted Platform](http://corp.kaltura.com/free-trial) or learn more about [Kaltura' Commercial OnPrem Edition™](http://corp.kaltura.com/Deployment-Options/Kaltura-On-Prem-Edition). For existing RPM based users, Kaltura offers commercial upgrade options.

### How to contribute
We value contributions from our CE user base very much. To make a contribution, follow the [See our CONTRIBUTERS doc](https://github.com/kaltura/platform-install-packages/blob/IX-9.19.0/doc/CONTRIBUTERS.md).


### Changing Apache configurations post install.

Sometimes, you may want to change deployment settings post installation, for example: replacing the domain, port or protocol, or changing the system to use SSL or stop using SSL.   
You can run `/opt/kaltura/bin/kaltura-front-config.sh` as many times as you'd like with different values. The script will re-configure the system accordingly.   
For instance, you may want to change the service URL, port or protocol.

This file has been truncated. show original

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.

jramer · May 1, 2015, 3:56pm

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…

jess · May 1, 2015, 4:17pm

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.

jramer · May 1, 2015, 5:11pm

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!