Quantcast
Channel: Kaltura - Latest posts
Viewing all articles
Browse latest Browse all 7410

Dpkg: error processing package kaltura-db (--configure):

$
0
0

Hi @jlotito,

According to your output, /var/lib/dpkg/info/kaltura-db.postinst exited with RC 7, this only happens if:
check_mysql_settings() [defined in /opt/kaltura/bin/kaltura-functions.rc] did not return true AND the MySQL host you provided is NOT the same as the machine you deployed the kaltura-db package on.
See /var/lib/dpkg/info/kaltura-db.postinst lines 135-148.

Since /opt/kaltura/bin/kaltura-mysql-settings.sh needs to change values in the my.cnf file, it has to run from a root shell on the machine where the DB resides. If you ran it on a different machine, it will do nothing.

On the machine where you deployed the percona-server-server-5.5 you should have /etc/mysql/my.cnf but by default, it is empty, other than the line:

!includedir /etc/mysql/conf.d/

and /etc/mysql/conf.d/ only includes mysql.cnf which is also empty.

With this default config, running /opt/kaltura/bin/kaltura-mysql-settings.sh will do nothing, this script is only meant to correct things in case these directives are set to the wrong values, it doesn’t handle the case where these directives are not set at all.

You should simply add the following lines to /etc/mysql/my.cnf manually:

[mysqld]
lower_case_table_names = 1
innodb_file_per_table
innodb_log_file_size=32M
open_files_limit = 20000
max_allowed_packet = 16M

then:

# rm /var/lib/mysql/ib_logfile*

And restart the MySQL daemon.

To make sure the values are now correct, you can run this commands from the MySQL console:

mysql> select @@open_files_limit;
+--------------------+
| @@open_files_limit |
+--------------------+
|              20000 |
+--------------------+
1 row in set (0.00 sec)

mysql> select @@lower_case_table_names;
+--------------------------+
| @@lower_case_table_names |
+--------------------------+
|                        1 |
+--------------------------+
1 row in set (0.00 sec)

mysql> select @@innodb_log_file_size;
+------------------------+
| @@innodb_log_file_size |
+------------------------+
|               33554432 |
+------------------------+
1 row in set (0.00 sec)

mysql> select @@max_allowed_packet;
+----------------------+
| @@max_allowed_packet |
+----------------------+
|             16777216 |
+----------------------+
1 row in set (0.00 sec)

Note that the values I mentioned here are the min values the Kaltura Server can work with, depending on your resources and needs you may want to set higher values.

After that’s done, from the machine you’ve installed the kaltura-db package on, simply run:

# apt install -f

this should trigger the re-execution of /var/lib/dpkg/info/kaltura-db.postinst and this time, check_mysql_settings() will return true and the post install script will continue to run and populate your DB.


Viewing all articles
Browse latest Browse all 7410

Trending Articles