We are installing kaltura 16.4.0 on ubuntu 16.04, a procedure we have done multiple times successfully in the past, using the links at the end of this post.
With everything prepared (Apache, MySQL) whenever we run install_kaltura_all_in_1.sh it throws the following error
The following NEW packages will be installed:
kaltura-base
0 packages upgraded, 1 newly installed, 0 to remove and 56 not upgraded.
Need to get 79.8 MB of archives. After unpacking 279 MB will be used.
Get: 1 http://installrepo.kaltura.org/repo/apt/xenial propus/main amd64 kaltura-base all 16.4.0-2 [79.8 MB]
Fetched 79.8 MB in 1s (72.8 MB/s)
Preconfiguring packages …
Selecting previously unselected package kaltura-base.
(Reading database … 60996 files and directories currently installed.)
Preparing to unpack …/kaltura-base_16.4.0-2_all.deb …
Unpacking kaltura-base (16.4.0-2) …
Setting up kaltura-base (16.4.0-2) …
sed: -e expression #7, char 24: unknown option to s' dpkg: error processing package kaltura-base (--configure): subprocess installed post-installation script returned error exit status 1 E: Sub-process /usr/bin/dpkg returned an error code (1) Failed to perform requested operation on package. Trying to recover: Setting up kaltura-base (16.4.0-2) ... tr: write error: Broken pipe tr: write error sed: -e expression #7, char 24: unknown option to s’
dpkg: error processing package kaltura-base (–configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
kaltura-base
This error didn’t appear in our previous installations, it stops at the beginning of the shell script. What can we be doing wrong?
One of your inputs is causing one of the sed commands in /var/lib/dpkg/info/kaltura-base.postinst to fail.
To discern which one, I recommend that you edit that file so that:
#!/bin/bash
Becomes:
#!/bin/bash -x
Then run:
# apt-get install -f
This would cause bash to output a lot of debug info, including the full sed command that’s failing (sed: -e expression #7, char 24: unknown option to s' in your output).
If you find that your input is valid, please post it here and I’ll apply whatever fix is needed, if the output isn’t valid, correct it:)
Hi Jess, thanks for your help. We noticed that we were using the “#” character in one of the settings’ passwords, and that was causing the error. We solved that error, but now it is throwing a different error. As you may see in the image, there’s an error on the kaltura-playkit-bundler package
Auth failures for root on a public facing machine is common. You might want to install fail2ban or DenyHosts, but that’s in a scope outside of Kaltura.