Facing problems installing kaltura-db

I have got error while installing kaltura. It stopped while installing kaltura-db. I cannot figure it out.

The following NEW packages will be installed:
kaltura-db
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/3,984 B of archives. After unpacking 8,192 B will be used.
Preconfiguring packages …
Selecting previously unselected package kaltura-db.
(Reading database … 176156 files and directories currently installed.)
Preparing to unpack …/kaltura-db_10.10.0+b3_all.deb …
Unpacking kaltura-db (10.10.0+b3) …
Setting up kaltura-db (10.10.0+b3) …
Checking MySQL version…

CREATE USER kaltura;
CREATE USER etl@’%’;
CREATE DATABASE kaltura;
CREATE DATABASE kaltura_sphinx_log;
CREATE DATABASE kalturadw;
CREATE DATABASE kalturadw_ds;
CREATE DATABASE kalturadw_bisources;
CREATE DATABASE kalturalog;
Checking connectivity to needed daemons…
Connectivity test passed:)
ERROR: Couldn’t make an API request to http://hostname:8080/api_v3/index.php?service=system&action=ping.
dpkg: error processing package kaltura-db (–configure):
subprocess installed post-installation script returned error exit status 6
Errors were encountered while processing:
kaltura-db
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to perform requested operation on package. Trying to recover:
Setting up kaltura-db (10.10.0+b3) …
Checking MySQL version…

I am trying it on debian 8.2 and following this link for installation

Hi,

It fails with:
ERROR: Couldn’t make an API request to http://hostname:8080/api_v3/index.php?service=system&action=ping.

i.e http://hostname:8080/api_v3/index.php?service=system&action=ping cannot be accessed which is mandatory for the deployment to work as the API is used to deploy.
Start by making sure the hostname is resolvable from both within the server and from all machines you expect to use the web I/F from.

Then check that the Apache virtual host config is correct with:
# apachectl -t -DDUMP_VHOSTS

Make sure the Kaltura Vhost is correctly configured and that the request does not reach another Vhost that’s overriding the Kaltura one.