Error in kaltura-nginx package on Debian Jessie

[hebert_freitas]

I’m trying install kaltura-server in a Debian server using all in 1 server script. (./install_kaltura_all_in_1.sh).
I’m getting this error:

Unpacking kaltura-nginx (1.10.3-4+b3) ...
Processing triggers for systemd (215-17+deb8u6) ...
Setting up kaltura-nginx (1.10.3-4+b3) ...
Job for kaltura-nginx.service failed. See 'systemctl status kaltura-nginx.service' and 'journalctl -xn' for details.
dpkg: error processing package kaltura-nginx (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (215-17+deb8u6) ...
Processing triggers for libc-bin (2.19-18+deb8u7) ...
Errors were encountered while processing:
 kaltura-nginx
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to perform requested operation on package.  Trying to recover:
Setting up kaltura-nginx (1.10.3-4+b3) ...
Job for kaltura-nginx.service failed. See 'systemctl status kaltura-nginx.service' and 'journalctl -xn' for details.
dpkg: error processing package kaltura-nginx (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin (2.19-18+deb8u7) ...
Errors were encountered while processing:
 kaltura-nginx

The result of systemctl status kaltura-nginx.service

● kaltura-nginx.service - LSB: starts the nginx web server
   Loaded: loaded (/etc/init.d/kaltura-nginx)
   Active: inactive (dead)

Apr 17 13:54:53 kaltura-server systemd[1]: Unit kaltura-nginx.service cannot be reloaded because it is inactive.
Apr 17 13:54:55 kaltura-server systemd[1]: Unit kaltura-nginx.service cannot be reloaded because it is inactive.

And the result of journalctl -xn

-- Logs begin at Sun 2017-04-16 12:36:21 UTC, end at Mon 2017-04-17 13:55:19 UTC. --
Apr 17 13:54:53 kaltura-server systemd[1]: Reloading.
Apr 17 13:54:53 kaltura-server systemd[1]: Started ACPI event daemon.
-- Subject: Unit acpid.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit acpid.service has finished starting up.
-- 
-- The start-up result is done.
Apr 17 13:54:53 kaltura-server systemd[1]: Listening on ACPID Listen Socket.
-- Logs begin at Sun 2017-04-16 12:36:21 UTC, end at Mon 2017-04-17 13:55:19 UTC. --
Apr 17 13:54:53 kaltura-server systemd[1]: Reloading.
Apr 17 13:54:53 kaltura-server systemd[1]: Started ACPI event daemon.
-- Subject: Unit acpid.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit acpid.service has finished starting up.
-- 
-- The start-up result is done.

and this is result of debconf-show “kaltura-nginx”

 kaltura-nginx/ssl_cert:
* kaltura-nginx/nginx_hostname: myip
* kaltura-nginx/nginx_port: 88
  kaltura-nginx/nginx_ssl_port: 8443
* kaltura-nginx/is_ssl: false
* kaltura-nginx/rtmp_port: 1935
  kaltura-nginx/ssl_key:
* kaltura-nginx/kaltura_service_url: myip

I’m replace myip for my public ip address. I’m don’t use a hostname in this moment.

The folder /opt/kaltura/log/nginx/ is empty.

How can I solve it?
Where to find more detailed logs for this error?

[jess]

Hi @hebert_freitas,

What do you see in /opt/kaltura/log/nginx/error_log?
Thanks,

[hebert_freitas]

The folder /opt/kaltura/log/nginx/ is empty. Does not exist the folder error_log inside this.

[jess]

Let’s try:
# /opt/kaltura/nginx/sbin/nginx -t
and also:
# bash -x /etc/init.d/kaltura-nginx start
and see what the output is…

[hebert_freitas]

When I run # /opt/kaltura/nginx/sbin/nginx -t

nginx: the configuration file /opt/kaltura/nginx/conf/nginx.conf syntax is ok
nginx: [alert] mmap(MAP_ANON|MAP_SHARED, 536870912) failed (12: Cannot allocate memory)
nginx: configuration file /opt/kaltura/nginx/conf/nginx.conf test failed

And when run # bash -x /etc/init.d/kaltura-nginx start

+ PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
+ DAEMON=/opt/kaltura/nginx/sbin/nginx
+ PID_FILE=/opt/kaltura/nginx/logs/nginx.pid
+ NAME=nginx
+ DESC=nginx
+ '[' -f /etc/default/nginx ']'
+ test -x /opt/kaltura/nginx/sbin/nginx
+ set -e
+ . /lib/lsb/init-functions
+++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 2>/dev/null)'
++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']'
++ . /lib/lsb/init-functions.d/20-left-info-blocks
++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 2>/dev/null)'
++ '[' -r /lib/lsb/init-functions.d/40-systemd ']'
++ . /lib/lsb/init-functions.d/40-systemd
+++ _use_systemctl=0
+++ '[' -d /run/systemd/system ']'
+++ '[' -n '' ']'
+++ '[' 1413 -ne 1 ']'
+++ '[' -z '' ']'
+++ '[' -z '' ']'
+++ case $(readlink -f "$0") in
++++ readlink -f /etc/init.d/kaltura-nginx
+++ _use_systemctl=1
+++ prog=kaltura-nginx
+++ service=kaltura-nginx.service
++++ systemctl -p CanReload show kaltura-nginx.service
+++ '[' CanReload=yes = CanReload=no ']'
+++ '[' 1 = 1 ']'
+++ set +e
+++ set +u
+++ '[' xstart = xstart -o xstart = xstop -o xstart = xrestart -o xstart = xreload -o xstart = xforce-reload -o xstart = xstatus ']'
+++ systemctl_redirect /etc/init.d/kaltura-nginx start
+++ local s
+++ local rc
+++ local prog=kaltura-nginx
+++ local command=start
+++ case "$command" in
+++ s='Starting kaltura-nginx (via systemctl)'
+++ service=kaltura-nginx.service
++++ systemctl -p LoadState show kaltura-nginx.service
+++ state=LoadState=loaded
+++ '[' LoadState=loaded = LoadState=masked ']'
+++ '[' start = status ']'
+++ log_daemon_msg 'Starting kaltura-nginx (via systemctl)' kaltura-nginx.service
+++ '[' -z 'Starting kaltura-nginx (via systemctl)' ']'
+++ log_daemon_msg_pre 'Starting kaltura-nginx (via systemctl)' kaltura-nginx.service
+++ log_use_fancy_output
+++ TPUT=/usr/bin/tput
+++ EXPR=/usr/bin/expr
+++ '[' -t 1 ']'
+++ '[' xxterm-256color '!=' x ']'
+++ '[' xxterm-256color '!=' xdumb ']'
+++ '[' -x /usr/bin/tput ']'
+++ '[' -x /usr/bin/expr ']'
+++ /usr/bin/tput hpa 60
+++ /usr/bin/tput setaf 1
+++ '[' -z ']'
+++ FANCYTTY=1
+++ case "$FANCYTTY" in
+++ true
+++ echo -n '[....] '
[....] +++ '[' -z kaltura-nginx.service ']'
+++ echo -n 'Starting kaltura-nginx (via systemctl): kaltura-nginx.service'
Starting kaltura-nginx (via systemctl): kaltura-nginx.service+++ log_daemon_msg_post 'Starting kaltura-nginx (via systemctl)' kaltura-nginx.service
+++ :
+++ /bin/systemctl start kaltura-nginx.service
Job for kaltura-nginx.service failed. See 'systemctl status kaltura-nginx.service' and 'journalctl -xn' for details.
+++ rc=1
+++ '[' start = status ']'
+++ log_end_msg 1
+++ '[' -z 1 ']'
+++ local retval
+++ retval=1
+++ log_end_msg_pre 1
+++ log_use_fancy_output
+++ TPUT=/usr/bin/tput
+++ EXPR=/usr/bin/expr
+++ '[' -t 1 ']'
+++ '[' xxterm-256color '!=' x ']'
+++ '[' xxterm-256color '!=' xdumb ']'
+++ '[' -x /usr/bin/tput ']'
+++ '[' -x /usr/bin/expr ']'
+++ /usr/bin/tput hpa 60
+++ /usr/bin/tput setaf 1
+++ '[' -z 1 ']'
+++ true
+++ case "$FANCYTTY" in
+++ true
++++ /usr/bin/tput setaf 1
+++ RED=''
++++ /usr/bin/tput setaf 2
+++ GREEN=''
++++ /usr/bin/tput setaf 3
+++ YELLOW=''
++++ /usr/bin/tput op
+++ NORMAL=''
+++ /usr/bin/tput civis
+++ /usr/bin/tput sc
+++ /usr/bin/tput hpa 0
+++ '[' 1 -eq 0 ']'
+++ '[' 1 -eq 255 ']'
+++ /bin/echo -ne '[FAIL'
[FAIL+++ /usr/bin/tput rc
+++ /usr/bin/tput cnorm
+++ log_use_fancy_output
+++ TPUT=/usr/bin/tput
+++ EXPR=/usr/bin/expr
+++ '[' -t 1 ']'
+++ '[' xxterm-256color '!=' x ']'
+++ '[' xxterm-256color '!=' xdumb ']'
+++ '[' -x /usr/bin/tput ']'
+++ '[' -x /usr/bin/expr ']'
+++ /usr/bin/tput hpa 60
+++ /usr/bin/tput setaf 1
+++ '[' -z 1 ']'
+++ true
+++ case "$FANCYTTY" in
+++ true
++++ /usr/bin/tput setaf 1
+++ RED=''
++++ /usr/bin/tput setaf 3
+++ YELLOW=''
++++ /usr/bin/tput op
+++ NORMAL=''
+++ '[' 1 -eq 0 ']'
+++ '[' 1 -eq 255 ']'
+++ /bin/echo -e ' failed!'
 failed!
+++ log_end_msg_post 1
+++ :
+++ return 1
+++ return 1
+++ exit 1

[jess]

Seems like you’re out of RAM…
What’s the output for:
# free -m
# ipcs -lm
and:
# ulimit -a

[hebert_freitas]

I see this problem. I started a fresh machine on DigitalOcean and did not pay attention in memory, the machine has 500MB of memory only.

I will increase memory and test again.
I will return with the result.

[jess]

Sure. You’ll need at least 2G of RAM for a full Kaltura Server to function.

[hebert_freitas]

@jess I resize my droplet to 2BG of memory.
When I reinstall kaltura i receive the same error in kaltura-nginx.service.

The result of journalctl -xn is

-- Logs begin at Tue 2017-04-18 12:59:19 UTC, end at Tue 2017-04-18 13:15:25 UTC. --
Apr 18 13:14:01 kaltura-server systemd[1]: Unit kaltura-nginx.service cannot be reloaded because it is inactive.
Apr 18 13:14:01 kaltura-server cron[486]: (*system*kaltura-dwh) RELOAD (/etc/cron.d/kaltura-dwh)
Apr 18 13:14:34 kaltura-server sshd[20395]: Disconnecting: Too many authentication failures for root from 119.193.140.178 port 39541 ssh2 [preauth]
Apr 18 13:14:34 kaltura-server systemd[1]: Starting Cleanup of Temporary Directories...
-- Subject: Unit systemd-tmpfiles-clean.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-tmpfiles-clean.service has begun starting up.
Apr 18 13:14:34 kaltura-server systemd[1]: Started Cleanup of Temporary Directories.
-- Subject: Unit systemd-tmpfiles-clean.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-tmpfiles-clean.service has finished starting up.
-- 
-- The start-up result is done.
Apr 18 13:14:47 kaltura-server systemd[1]: Starting LSB: starts the nginx web server...
-- Subject: Unit kaltura-nginx.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit kaltura-nginx.service has begun starting up.
Apr 18 13:14:48 kaltura-server kaltura-nginx[20413]: Starting nginx: nginx.
Apr 18 13:14:48 kaltura-server systemd[1]: Started LSB: starts the nginx web server.
-- Subject: Unit kaltura-nginx.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit kaltura-nginx.service has finished starting up.
-- 
-- The start-up result is done.
Apr 18 13:14:54 kaltura-server systemd[1]: Started memcached daemon.
-- Subject: Unit memcached.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit memcached.service has finished starting up.
-- 
-- The start-up result is done.
Apr 18 13:15:25 kaltura-server sshd[20464]: Connection closed by 139.219.225.70 [preauth]

I’m suspecting this line:

Disconnecting: Too many authentication failures for root from 119.193.140.178 port 39541 ssh2 [preauth]

[jess]

Hi @hebert_freitas,

Disconnecting: Too many authentication failures for root from 119.193.140.178 port 39541 ssh2 [preauth]

Just means someone is trying to SSH to this machine from 119.193.140.178 and is failing, does not affect Kaltura in any way though if you see many such attempts, you can just block this IP using iptables.

Please provide the output for all the commands I’ve listed thus far and let’s see what the actual issue is.

[hebert_freitas]

Ok.

/opt/kaltura/nginx/sbin/nginx -t

nginx: the configuration file /opt/kaltura/nginx/conf/nginx.conf syntax is ok
nginx: configuration file /opt/kaltura/nginx/conf/nginx.conf test is successful

bash -x /etc/init.d/kaltura-nginx start

+ PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
+ DAEMON=/opt/kaltura/nginx/sbin/nginx
+ PID_FILE=/opt/kaltura/nginx/logs/nginx.pid
+ NAME=nginx
+ DESC=nginx
+ '[' -f /etc/default/nginx ']'
+ test -x /opt/kaltura/nginx/sbin/nginx
+ set -e
+ . /lib/lsb/init-functions
+++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 2>/dev/null)'
++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']'
++ . /lib/lsb/init-functions.d/20-left-info-blocks
++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 2>/dev/null)'
++ '[' -r /lib/lsb/init-functions.d/40-systemd ']'
++ . /lib/lsb/init-functions.d/40-systemd
+++ _use_systemctl=0
+++ '[' -d /run/systemd/system ']'
+++ '[' -n '' ']'
+++ '[' 1847 -ne 1 ']'
+++ '[' -z '' ']'
+++ '[' -z '' ']'
+++ case $(readlink -f "$0") in
++++ readlink -f /etc/init.d/kaltura-nginx
+++ _use_systemctl=1
+++ prog=kaltura-nginx
+++ service=kaltura-nginx.service
++++ systemctl -p CanReload show kaltura-nginx.service
+++ '[' CanReload=yes = CanReload=no ']'
+++ '[' 1 = 1 ']'
+++ set +e
+++ set +u
+++ '[' xstart = xstart -o xstart = xstop -o xstart = xrestart -o xstart = xreload -o xstart = xforce-reload -o xstart = xstatus ']'
+++ systemctl_redirect /etc/init.d/kaltura-nginx start
+++ local s
+++ local rc
+++ local prog=kaltura-nginx
+++ local command=start
+++ case "$command" in
+++ s='Starting kaltura-nginx (via systemctl)'
+++ service=kaltura-nginx.service
++++ systemctl -p LoadState show kaltura-nginx.service
+++ state=LoadState=loaded
+++ '[' LoadState=loaded = LoadState=masked ']'
+++ '[' start = status ']'
+++ log_daemon_msg 'Starting kaltura-nginx (via systemctl)' kaltura-nginx.service
+++ '[' -z 'Starting kaltura-nginx (via systemctl)' ']'
+++ log_daemon_msg_pre 'Starting kaltura-nginx (via systemctl)' kaltura-nginx.service
+++ log_use_fancy_output
+++ TPUT=/usr/bin/tput
+++ EXPR=/usr/bin/expr
+++ '[' -t 1 ']'
+++ '[' xxterm-256color '!=' x ']'
+++ '[' xxterm-256color '!=' xdumb ']'
+++ '[' -x /usr/bin/tput ']'
+++ '[' -x /usr/bin/expr ']'
+++ /usr/bin/tput hpa 60
+++ /usr/bin/tput setaf 1
+++ '[' -z ']'
+++ FANCYTTY=1
+++ case "$FANCYTTY" in
+++ true
+++ echo -n '[....] '
[....] +++ '[' -z kaltura-nginx.service ']'
+++ echo -n 'Starting kaltura-nginx (via systemctl): kaltura-nginx.service'
Starting kaltura-nginx (via systemctl): kaltura-nginx.service+++ log_daemon_msg_post 'Starting kaltura-nginx (via systemctl)' kaltura-nginx.service
+++ :
+++ /bin/systemctl start kaltura-nginx.service
+++ rc=0
+++ '[' start = status ']'
+++ log_end_msg 0
+++ '[' -z 0 ']'
+++ local retval
+++ retval=0
+++ log_end_msg_pre 0
+++ log_use_fancy_output
+++ TPUT=/usr/bin/tput
+++ EXPR=/usr/bin/expr
+++ '[' -t 1 ']'
+++ '[' xxterm-256color '!=' x ']'
+++ '[' xxterm-256color '!=' xdumb ']'
+++ '[' -x /usr/bin/tput ']'
+++ '[' -x /usr/bin/expr ']'
+++ /usr/bin/tput hpa 60
+++ /usr/bin/tput setaf 1
+++ '[' -z 1 ']'
+++ true
+++ case "$FANCYTTY" in
+++ true
++++ /usr/bin/tput setaf 1
+++ RED=''
++++ /usr/bin/tput setaf 2
+++ GREEN=''
++++ /usr/bin/tput setaf 3
+++ YELLOW=''
++++ /usr/bin/tput op
+++ NORMAL=''
+++ /usr/bin/tput civis
+++ /usr/bin/tput sc
+++ /usr/bin/tput hpa 0
+++ '[' 0 -eq 0 ']'
+++ /bin/echo -ne '[ ok '
[ ok +++ /usr/bin/tput rc
+++ /usr/bin/tput cnorm
+++ log_use_fancy_output
+++ TPUT=/usr/bin/tput
+++ EXPR=/usr/bin/expr
+++ '[' -t 1 ']'
+++ '[' xxterm-256color '!=' x ']'
+++ '[' xxterm-256color '!=' xdumb ']'
+++ '[' -x /usr/bin/tput ']'
+++ '[' -x /usr/bin/expr ']'
+++ /usr/bin/tput hpa 60
+++ /usr/bin/tput setaf 1
+++ '[' -z 1 ']'
+++ true
+++ case "$FANCYTTY" in
+++ true
++++ /usr/bin/tput setaf 1
+++ RED=''
++++ /usr/bin/tput setaf 3
+++ YELLOW=''
++++ /usr/bin/tput op
+++ NORMAL=''
+++ '[' 0 -eq 0 ']'
+++ echo .
.
+++ log_end_msg_post 0
+++ :
+++ return 0
+++ return 0
+++ exit 0

#systemctl status kaltura-nginx.service

● kaltura-nginx.service - LSB: starts the nginx web server
   Loaded: loaded (/etc/init.d/kaltura-nginx)
   Active: active (running) since Tue 2017-04-18 13:14:48 UTC; 33min ago
  Process: 20413 ExecStart=/etc/init.d/kaltura-nginx start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/kaltura-nginx.service
           ├─20417 nginx: master process /opt/kaltura/nginx/sbin/nginx
           ├─20418 nginx: worker process
           ├─20419 nginx: worker process
           ├─20420 nginx: worker process
           ├─20421 nginx: worker process
           └─20422 nginx: cache manager process

#/opt/kaltura/log/nginx/error_log

The file exists but is empty
There is also the error.log file which is also empty

#free -m
total used free shared buffers cached
Mem: 2010 1865 144 48 118 1274
-/+ buffers/cache: 472 1537
Swap: 0 0 0

#ipcs -lm

max number of segments = 4096
max seg size (kbytes) = 18014398509465599
max total shared memory (kbytes) = 18014398442373116
min seg size (bytes) = 1

#ulimit -a

core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 7972
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 65536
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 7972
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

#debconf-show “kaltura-nginx”

 kaltura-nginx/nginx_ssl_port: 8443
* kaltura-nginx/is_ssl: false
* kaltura-nginx/kaltura_service_url: myip
* kaltura-nginx/nginx_port: 88
  kaltura-nginx/ssl_cert:
* kaltura-nginx/rtmp_port: 1935
  kaltura-nginx/ssl_key:
* kaltura-nginx/nginx_hostname: myip

I’m replace myip for my public ip address. I’m don’t use a hostname in this moment.

[jess]

OK, so looks as though kaltura-nginx is running now… what seems to be the issue?

[hebert_freitas]

When I run the installation script i received this error:

 ...   
    The following NEW packages will be installed:
      kaltura-nginx 
    0 packages upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
    Need to get 0 B/783 kB of archives. After unpacking 1,852 kB will be used.
    Preconfiguring packages ...              
    Selecting previously unselected package kaltura-nginx.
    (Reading database ... 120945 files and directories currently installed.)
    Preparing to unpack .../kaltura-nginx_1.10.3-4+b3_amd64.deb ...
    Unpacking kaltura-nginx (1.10.3-4+b3) ...
    Processing triggers for systemd (215-17+deb8u6) ...
    Setting up kaltura-nginx (1.10.3-4+b3) ...
    Job for kaltura-nginx.service failed. See 'systemctl status kaltura-nginx.service' and 'journalctl -xn' for details.
    dpkg: error processing package kaltura-nginx (--configure):
     subprocess installed post-installation script returned error exit status 1
    Processing triggers for systemd (215-17+deb8u6) ...
    Processing triggers for libc-bin (2.19-18+deb8u7) ...
    Errors were encountered while processing:
     kaltura-nginx
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    Failed to perform requested operation on package.  Trying to recover:
    Setting up kaltura-nginx (1.10.3-4+b3) ...
    Job for kaltura-nginx.service failed. See 'systemctl status kaltura-nginx.service' and 'journalctl -xn' for details.
    dpkg: error processing package kaltura-nginx (--configure):
     subprocess installed post-installation script returned error exit status 1
    Processing triggers for libc-bin (2.19-18+deb8u7) ...
    Errors were encountered while processing:
     kaltura-nginx

The same error that occurred previously

[jess]

Hi @hebert_freitas,

Not sure why it fails during the dpkg-configure phase since again, according to your output, it is currently running.
Please edit /var/lib/dpkg/info/kaltura-nginx.postinst and change:

#!/bin/bash

to read:

#!/bin/bash -x

Then run:

# dpkg-reconfigure kaltura-nginx

and look at the output as well as any errors in /opt/kaltura/log/nginx/error_log and let’s see what we can find out.

[hebert_freitas]

I edited the file and when run # dpkg-reconfigure kaltura-nginx I received this output
/usr/sbin/dpkg-reconfigure: kaltura-nginx is broken or not fully installed

[jess]

OK, please run:
# aptitude install -f

[hebert_freitas]

OK, the output is

The following partially installed packages will be configured:
  kaltura-nginx 
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Setting up kaltura-nginx (1.10.3-4+b3) ...
+ ldconfig
+ '[' configure = configure ']'
+ . /usr/share/debconf/confmodule
++ '[' '!' '' ']'
++ PERL_DL_NONLAZY=1
++ export PERL_DL_NONLAZY
++ '[' '' ']'
++ exec /usr/share/debconf/frontend /var/lib/dpkg/info/kaltura-nginx.postinst configure ''
+ ldconfig
+ '[' configure = configure ']'
+ . /usr/share/debconf/confmodule
++ '[' '!' 1 ']'
++ '[' -z '' ']'
++ exec
++ '[' '' ']'
++ exec
++ DEBCONF_REDIR=1
++ export DEBCONF_REDIR
+ db_get kaltura-nginx/nginx_hostname
+ _db_cmd 'GET kaltura-nginx/nginx_hostname'
+ _db_internal_IFS=' 	
'
+ IFS=' '
+ printf '%s\n' 'GET kaltura-nginx/nginx_hostname'
+ IFS=' 	
'
+ IFS='
'
+ read -r _db_internal_line
+ RET=162.243.45.200
+ case ${_db_internal_line%%[ 	]*} in
+ return 0
+ '[' -z 162.243.45.200 ']'
+ db_input critical kaltura-nginx/nginx_hostname
+ _db_cmd 'INPUT critical' kaltura-nginx/nginx_hostname
+ _db_internal_IFS=' 	
'
+ IFS=' '
+ printf '%s\n' 'INPUT critical kaltura-nginx/nginx_hostname'
+ IFS=' 	
'
+ IFS='
'
+ read -r _db_internal_line
+ RET='30 question skipped'
+ case ${_db_internal_line%%[ 	]*} in
+ return 30
+ true
+ db_go
+ _db_cmd 'GO '
+ _db_internal_IFS=' 	
'
+ IFS=' '
+ printf '%s\n' 'GO '
+ IFS=' 	
'
+ IFS='
'
+ read -r _db_internal_line
+ RET=ok
+ case ${_db_internal_line%%[ 	]*} in
+ return 0
+ db_get kaltura-nginx/nginx_hostname
+ _db_cmd 'GET kaltura-nginx/nginx_hostname'
+ _db_internal_IFS=' 	
'
+ IFS=' '
+ printf '%s\n' 'GET kaltura-nginx/nginx_hostname'
+ IFS=' 	
'
+ IFS='
'
+ read -r _db_internal_line
+ RET=162.243.45.200
+ case ${_db_internal_line%%[ 	]*} in
+ return 0
+ VOD_PACKAGER_HOST=162.243.45.200
+ db_input critical kaltura-nginx/nginx_port
+ _db_cmd 'INPUT critical' kaltura-nginx/nginx_port
+ _db_internal_IFS=' 	
'
+ IFS=' '
+ printf '%s\n' 'INPUT critical kaltura-nginx/nginx_port'
+ IFS=' 	
'
+ IFS='
'
+ read -r _db_internal_line
+ RET='30 question skipped'
+ case ${_db_internal_line%%[ 	]*} in
+ return 30
+ true
+ db_go
+ _db_cmd 'GO '
+ _db_internal_IFS=' 	
'
+ IFS=' '
+ printf '%s\n' 'GO '
+ IFS=' 	
'
+ IFS='
'
+ read -r _db_internal_line
+ RET=ok
+ case ${_db_internal_line%%[ 	]*} in
+ return 0
+ db_get kaltura-nginx/nginx_port
+ _db_cmd 'GET kaltura-nginx/nginx_port'
+ _db_internal_IFS=' 	
'
+ IFS=' '
+ printf '%s\n' 'GET kaltura-nginx/nginx_port'
+ IFS=' 	
'
+ IFS='
'
+ read -r _db_internal_line
+ RET=88
+ case ${_db_internal_line%%[ 	]*} in
+ return 0
+ VOD_PACKAGER_PORT=88
+ db_input critical kaltura-nginx/rtmp_port
+ _db_cmd 'INPUT critical' kaltura-nginx/rtmp_port
+ _db_internal_IFS=' 	
'
+ IFS=' '
+ printf '%s\n' 'INPUT critical kaltura-nginx/rtmp_port'
+ IFS=' 	
'
+ IFS='
'
+ read -r _db_internal_line
+ RET='30 question skipped'
+ case ${_db_internal_line%%[ 	]*} in
+ return 30
+ true
+ db_go
+ _db_cmd 'GO '
+ _db_internal_IFS=' 	
'
+ IFS=' '
+ printf '%s\n' 'GO '
+ IFS=' 	
'
+ IFS='
'
+ read -r _db_internal_line
+ RET=ok
+ case ${_db_internal_line%%[ 	]*} in
+ return 0
+ db_get kaltura-nginx/rtmp_port
+ _db_cmd 'GET kaltura-nginx/rtmp_port'
+ _db_internal_IFS=' 	
'
+ IFS=' '
+ printf '%s\n' 'GET kaltura-nginx/rtmp_port'
+ IFS=' 	
'
+ IFS='
'
+ read -r _db_internal_line
+ RET=1935
+ case ${_db_internal_line%%[ 	]*} in
+ return 0
+ RTMP_PORT=1935
+ db_get kaltura-nginx/kaltura_service_url
+ _db_cmd 'GET kaltura-nginx/kaltura_service_url'
+ _db_internal_IFS=' 	
'
+ IFS=' '
+ printf '%s\n' 'GET kaltura-nginx/kaltura_service_url'
+ IFS=' 	
'
+ IFS='
'
+ read -r _db_internal_line
+ RET=162.243.45.200
+ case ${_db_internal_line%%[ 	]*} in
+ return 0
+ db_input critical kaltura-nginx/kaltura_service_url
+ _db_cmd 'INPUT critical' kaltura-nginx/kaltura_service_url
+ _db_internal_IFS=' 	
'
+ IFS=' '
+ printf '%s\n' 'INPUT critical kaltura-nginx/kaltura_service_url'
+ IFS=' 	
'
+ IFS='
'
+ read -r _db_internal_line
+ RET='30 question skipped'
+ case ${_db_internal_line%%[ 	]*} in
+ return 30
+ true
+ db_go
+ _db_cmd 'GO '
+ _db_internal_IFS=' 	
'
+ IFS=' '
+ printf '%s\n' 'GO '
+ IFS=' 	
'
+ IFS='
'
+ read -r _db_internal_line
+ RET=ok
+ case ${_db_internal_line%%[ 	]*} in
+ return 0
+ db_get kaltura-nginx/kaltura_service_url
+ _db_cmd 'GET kaltura-nginx/kaltura_service_url'
+ _db_internal_IFS=' 	
'
+ IFS=' '
+ printf '%s\n' 'GET kaltura-nginx/kaltura_service_url'
+ IFS=' 	
'
+ IFS='
'
+ read -r _db_internal_line
+ RET=162.243.45.200
+ case ${_db_internal_line%%[ 	]*} in
+ return 0
+ WWW_HOST=162.243.45.200
+ db_input critical kaltura-nginx/is_ssl
+ _db_cmd 'INPUT critical' kaltura-nginx/is_ssl
+ _db_internal_IFS=' 	
'
+ IFS=' '
+ printf '%s\n' 'INPUT critical kaltura-nginx/is_ssl'
+ IFS=' 	
'
+ IFS='
'
+ read -r _db_internal_line
+ RET='30 question skipped'
+ case ${_db_internal_line%%[ 	]*} in
+ return 30
+ true
+ db_go
+ _db_cmd 'GO '
+ _db_internal_IFS=' 	
'
+ IFS=' '
+ printf '%s\n' 'GO '
+ IFS=' 	
'
+ IFS='
'
+ read -r _db_internal_line
+ RET=ok
+ case ${_db_internal_line%%[ 	]*} in
+ return 0
+ db_get kaltura-nginx/is_ssl
+ _db_cmd 'GET kaltura-nginx/is_ssl'
+ _db_internal_IFS=' 	
'
+ IFS=' '
+ printf '%s\n' 'GET kaltura-nginx/is_ssl'
+ IFS=' 	
'
+ IFS='
'
+ read -r _db_internal_line
+ RET=false
+ case ${_db_internal_line%%[ 	]*} in
+ return 0
+ IS_NGINX_SSL=false
+ '[' false = true ']'
+ touch /opt/kaltura/nginx/conf/ssl.conf
+ PROTOCOL=http
+ sed -e s#@VOD_PACKAGER_HOST@#162.243.45.200#g -e s#@VOD_PACKAGER_PORT@#88#g -e s#@RTMP_PORT@#1935#g -e s#@LOG_DIR@#/opt/kaltura/log/nginx# -e s#@WWW_HOST@#162.243.45.200#g /opt/kaltura/nginx/conf/nginx.conf.template
+ sed -e s#@STATIC_FILES_PATH@#/opt/kaltura/nginx/static#g -e s#@PROTOCOL@#http#g /opt/kaltura/nginx/conf/kaltura.conf.template
+ update-rc.d kaltura-nginx defaults
+ chown -R kaltura /opt/kaltura/log/nginx
+ service kaltura-nginx reload
Processing triggers for libc-bin (2.19-18+deb8u7) ...

Does that mean that the server was installed correctly?

[jess]

Yep, looks fine.
You can run:

# /opt/kaltura/bin/kaltura-sanity.sh

This will run a lot of tests to verify all is well.

[hebert_freitas]

Some tests have failed, but I believe they are not serious problems.
I’m logged in server interface this moment. Apparently all it’s ok. Thanks for lot of explanations and help