I upgraded to kaltura to 12.9.0 and tried to add an installtion of the ngninx server in my all-in-one installation.
After installation of the kaltura-nginx package i got the message output:
Preparing to unpack …/kaltura-nginx_1.10.2-3_amd64.deb …
Unpacking kaltura-nginx (1.10.2-3) …
Processing triggers for systemd (215-17+deb8u6) …
Setting up kaltura-nginx (1.10.2-3) …
sed: can’t read /opt/kaltura/nginx/conf/kaltura.conf.template: No such file or directory
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
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.2-3) …
sed: can’t read /opt/kaltura/nginx/conf/kaltura.conf.template: No such file or directory
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
Press Return to continue.
journalctl -xn
…
Feb 08 14:25:47 VIRTSRVBLC03 systemd[1]: Unit kaltura-nginx.service cannot be reloaded because it is inactive.
I think there is a file missing or something is wrong in an installation script?
I am using debian.
And another question is: In a cluster installation must the nginx be accessable for the clients or just for the kaltura servers?
Should see:
/opt/kaltura/nginx/conf/kaltura.conf.template
If the file is not present, try aptitude reinstall kaltura-nginx
As for the other question: yes, when using the Nginx VOD module for delivery, Nginx must be accessible from all machines playback should happen from. The player will be making requests to Nginx to get the manifest and segments.
You can choose any port you wish for it during the configuration phase and you can also use a LB accessible to all clients and balance between Nginx nodes who are not accessible to the outside world.
When taking that approach, you will need to modify the DB records in the kaltura.delivery_profile table so that they point to the LB’s addr rather than the node directly.
…
of the command # dpkg -x kaltura-nginx_1.10.2-3_amd64.deb /tmp/nginx.deb/
i got:
dpkg-deb: error: failed to read archive `kaltura-nginx_1.10.2-3_amd64.deb’: No such file or directory
So I run: # dpkg -x /var/cache/apt/archives/kaltura-nginx_1.10.2-3_amd64.deb /tmp/nginx.deb/ # ls -al /tmp/nginx.deb/opt/kaltura/nginx/conf/kaltura.conf.template
-rw-r–r-- 1 root root 4237 Dec 28 18:43 /tmp/nginx.deb/opt/kaltura/nginx/conf/kaltura.conf.template
OK, meaning /opt/kaltura/nginx/conf/kaltura.conf.template is definitely included in the kaltura-nginx_1.10.2-3_amd64.deb.
What happens if you try:
# dpkg -i kaltura-nginx_1.10.2-3_amd64.deb
?
You can always try to remove kaltura-nginx completely with:
# aptitude purge kaltura-nginx
and then try to reinstall it.
Just make sure beforehand that you have no manual configuration changes you may have made in /opt/kaltura/nginx/conf/ since these will be deleted.
# dpkg -i kaltura-nginx_1.10.2-3_amd64.deb (Reading database … 119257 files and directories currently installed.) Preparing to unpack kaltura-nginx_1.10.2-3_amd64.deb … Unpacking kaltura-nginx (1.10.2-3) over (1.10.2-3) … Setting up kaltura-nginx (1.10.2-3) … sed: can’t read /opt/kaltura/nginx/conf/kaltura.conf.template: No such file or d irectory Job for kaltura-nginx.service failed. See ‘systemctl status kaltura-nginx.servic e’ and ‘journalctl -xn’ for details. dpkg: error processing package kaltura-nginx (–install):
_ 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_
I purged the package now and reinstalled it. Now the install process went successfully throught.
I try now to configure it in my environment.