Closed pkExec closed 4 years ago
Hello @pkExec,
Thanks for reporting. This was already fixed and the updated kaltura-db
package is available in the nightly repo. It will become the stable repo tomorrow.
For the time being, you can edit /etc/apt/sources.list.d/kaltura.list
So that it reads:
deb [arch=amd64] http://installrepo.origin.kaltura.org/repo/apt/xenial-nightly orion main
Then invoke:
# apt update
# apt purge kaltura-db
and re-run the deployment script.
Cheers,
Thanks. Indeed this step was fixed. Now it fails on the "Waiting for the ElasticSearch daemon to start..." step. It displays "We've waited a minute and the ES daemon is still unreachable, we're giving up: (" sed: can't read /configurations/base.ini: No such file or directory
I've received the Elastic Search error same as @pkExec
Setting up kaltura-elasticsearch (1.0.0-1+b6) ... -> Downloading analysis-icu from elastic [=================================================] 100% -> Installed analysis-icu Waiting for the ElasticSearch daemon to start... We've waited a minute and the ES daemon is still unreachable, we're giving up:( Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.23) ... sed: can't read /configurations/base.ini: No such file or directory
used a Fresh Install of Ubuntu 16.04 minimal iso and MySQL 5.5 Percona deb package only other package installed wis openssh-server
lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.6 LTS Release: 16.04 Codename: xenial
mysql -V mysql Ver 14.14 Distrib 5.5.62-38.14, for debian-linux-gnu (x86_64) using readline 5.1
Hello @pkExec, @thecaribbean,
Kaltura CE 15.14.0 was just released.
Kindly try to upgrade. If the issue persists, please edit /var/lib/dpkg/info/kaltura-elasticsearch.postinst
so that:
#!/bin/bash
becomes:
#!/bin/bash -x
then run:
# apt install -f
or, depending on the package's current state:
# dpkg-reconfigure kaltura-elasticsearch
And paste the output here.
Thanks,
Started another fresh install and got up to:
Setting up kaltura-elasticsearch (1.0.0-1+b7) ... -> Downloading analysis-icu from elastic [=================================================] 100% -> Installed analysis-icu Waiting for the ElasticSearch daemon to start... We've waited a minute and the ES daemon is still unreachable, we're giving up:( Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.23) ... sed: can't read /configurations/base.ini: No such file or directory
edited /var/lib/dpkg/info/kaltura-elasticsearch.postinst
then run:
apt install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Then ran:
root@video:~# dpkg-reconfigure kaltura-elasticsearch
========truncated-output==============
after attempt 20. Ctl-D to kill
I noticed: sed: can't read /configurations/base.ini: No such file or directory
so ran
find / -name base.ini
and got it at this location
/opt/kaltura/app/configurations/base.ini
Looking through the installation script
vi install_kaltura_all_in_1.sh
I note the last line is
sed -i 's@(exec_elastic\s=\s)false@\1true@' $APP_DIR/configurations/base.ini
so despite the error Elastic Search is installed and I'm able to log into KMC and upload/server media. Not sure how Elastic Search error will impact operation.
Tried too, same errors as @thecaribbean on https://github.com/kaltura/platform-install-packages/issues/659#issuecomment-572049513
The first error (elasticsearch not starting) is because: a) $JAVA_HOME is not set for root user. b) Permissions are wrong as per https://stackoverflow.com/a/48390311/1543677 After following the instructions on stackoverflow and manually setting $JAVA_HOME, elasticsearch does start.
The second error (with the sed command in the install script), is because for some reason the $APP_DIR variable is not set. After replacing it with the installation path (/opt/kaltura/app), it finishes without errors.
Hi @pkExec, all,
These ENV vars are defined in /etc/profile.d/kaltura-base.sh
but of course, they will only be auto sourced when a new session is established, therefore, see this commit: https://github.com/kaltura/platform-install-packages/commit/7d36b82d303bc081b8e6a9119eecd674b016bd6f
which should take care of that.
With regards to
Not sure how Elastic Search error will impact operation.
ES is actually only utilised by the esearch service (https://developer.kaltura.com/api-docs/service/eSearch) and, at present time, KMC and KMCng's code do not make use of it so it isn't a critical component for Kaltura CE.
Thanks all, for your reports,
Bug report
*Please provide steps to reproduce, including errors from /opt/kaltura/log/kaltura_api_v3.log, /opt/kaltura/log/kaltura_apache_errorslog and /opt/kaltura/log/kaltura_prod.log:**
1) Start a new Amazon Lightsail instance with ubuntu 16.04 2) Modify hosts file for your domain 3) Install Percona as per the instructions https://github.com/kaltura/platform-install-packages/blob/Orion-15.11.0/doc/install-percona-deb.md 4) Follow the instructions here https://github.com/kaltura/platform-install-packages/blob/Orion-15.11.0/doc/install-kaltura-xenial.md
Expected outcome: Installed platform
Actual outcome: Failed on the installing kaltura-db step.
Cause: No databases are created
Root cause: /opt/kaltura/bin/db_actions.rc has variable OP_DBS, while script expects DBS
Is this an all in one instance [single server] or a cluster?