Admin console -> configuration throws error

Hello Community,

the configuration menu in the admin console throws an error:

An error occurred

(error code: Server:INTERNAL_DATABASE_ERROR)

In kaltlog i see:

2019-02-22 12:31:28 [0.000223] [172.31.37.11] [1994073200] [65] [API] [KalturaStatement->execute] DEBUG: /* ip-172-31-37-11[1994073200][propel] */ SELECT conf_maps.ID, conf_maps.MAP_NAME, conf_maps.HOST_NAME, conf_maps.STATUS, conf_maps.CREATED_AT, conf_maps.REMARKS, conf_maps.CONTENT, conf_maps.VERSION FROM conf_maps WHERE conf_maps.STATUS=‘1’ GROUP BY conf_maps.MAP_NAME
2019-02-22 12:31:28 [0.000249] [172.31.37.11] [1994073200] [66] [API] [BasePeer::doSelect] ERR: Exception: SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘kaltura.conf_maps’ doesn’t exist in /opt/kaltura/app/infra/log/KalturaLog.php:88
Stack trace:
#0 /opt/kaltura/app/vendor/propel/Propel.php(408): KalturaLog::err(‘SQLSTATE[42S02]…’)

2019-02-22 12:31:28 [0.000237] [172.31.37.11] [1994073200] [67] [API] [KalturaFrontController->getExceptionObject] ALERT: PropelException: [wrapped: SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘kaltura.conf_maps’ doesn’t exist] in /opt/kaltura/app/vendor/propel/util/BasePeer.php:467
Stack trace:
#0 /opt/kaltura/app/plugins/conf_maps/lib/model/om/BaseConfMapsPeer.php(353): BasePeer::doSelect(Object(Criteria), Object(KalturaPDO))

2019-02-22 12:31:28 [0.000041] [609116550] [11] [%context%] [Kaltura_Client_ClientBase->doQueue] DEBUG: execution time for [http://ec2-18-203-60-25.eu-west-1.compute.amazonaws.com/api_v3/service/confmaps_confmaps/action/getMapNames]: [0.077507972717285]
2019-02-22 12:31:28 [0.000454] [609116550] [12] [%context%] [ErrorController->errorAction] ERR: Kaltura_Client_Exception: Internal database error in /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php:937
Stack trace:
#0 /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php(953): Kaltura_Client_ClientBase->getKalturaAPIException(‘Internal databa…’, ‘INTERNAL_DATABA…’, Array)

There is a missing table kaltura.conf_maps.

Any idea why and how to repair it?

Thanks,
Werner

Hi @esnecca,

Based on your previous posts, it looks as though you have a half baked deployment that’s a mix and match between Kaltura CE 13 [codename Mercury] and 14 [codename Naos - current stable].
I just released 14.14.0. I strongly recommend you redeploy as per what I wrote to you here:

Before running install_kaltura_all_in_1.sh, please ensure that you have the latest version of it; for Ubuntu 14.04, that is:
http://installrepo.kaltura.org/repo/apt/debian/install_kaltura_all_in_1.sh
sha256sum: 5fb670cffdfe3e288dd24be48ca88f3ab5edde7160d4b2495158e0cc71fba0b6
For 16.04:
http://installrepo.kaltura.org/repo/apt/xenial/install_kaltura_all_in_1.sh
sha256sum: 8baf4813910661eeef5ce4be3b9c262bb118dbbe6d443e25492ecc3ce63618cf

Thanks,

Hello Jess, hello community,

i have installed kaltura again on a fresh
Ubuntu 16.04.6 LTS (GNU/Linux 4.4.0-1075-aws x86_64)
system.

I used:
wget -O - http://installrepo.kaltura.org/repo/apt/xenial/kaltura-deb-256.gpg.key|apt-key add -
echo “deb [arch=amd64] http://installrepo.kaltura.org/repo/apt/xenial naos main” > /etc/apt/sources.list.d/kaltura.list

wget http://installrepo.origin.kaltura.org/repo/apt/xenial/install_kaltura_all_in_1.sh
chmod +x install_kaltura_all_in_1.sh
./install_kaltura_all_in_1.sh

The installation process shows no errors.

Kaltura runs fine.

Only the configuration in the admin console throws errors.

/opt/kaltura/log/kaltura_admin.log:

2019-02-27 09:18:14 [0.000039] [943661612] [11] [%context%] [Kaltura_Client_ClientBase->doQueue] DEBUG: execution time for [http://ec2-52-213-25-93.eu-west-1.compute.amazonaws.com/api_v3/service/confmaps_confmaps/action/getMapNames]: [0.09263801574707]
2019-02-27 09:18:14 [0.000821] [943661612] [12] [%context%] [ErrorController->errorAction] ERR: Kaltura_Client_Exception: Internal database error in /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php:937
Stack trace:
#0 /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php(953): Kaltura_Client_ClientBase->getKalturaAPIException(‘Internal databa…’, ‘INTERNAL_DATABA…’, Array)

/opt/kaltura/log/kaltura_api_v3.log:

2019-02-27 09:18:14 [0.001752] [10.0.113.40] [320548560] [65] [API] [KalturaStatement->execute] DEBUG: /* ip-10-0-113-40[320548560][propel] */ SELECT conf_maps.ID, conf_maps.MAP_NAME, conf_maps.HOST_NAME, conf_maps.STATUS, conf_maps.CREATED_AT, conf_maps.REMARKS, conf_maps.CONTENT, conf_maps.VERSION FROM conf_maps WHERE conf_maps.STATUS=‘1’ GROUP BY conf_maps.MAP_NAME
2019-02-27 09:18:14 [0.000995] [10.0.113.40] [320548560] [66] [API] [BasePeer::doSelect] ERR: Exception: SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘kaltura.conf_maps’ doesn’t exist in /opt/kaltura/app/infra/log/KalturaLog.php:88
Stack trace:
#0 /opt/kaltura/app/vendor/propel/Propel.php(408): KalturaLog::err(‘SQLSTATE[42S02]…’)
#1 /opt/kaltura/app/vendor/propel/util/BasePeer.php(466): Propel::log(‘SQLSTATE[42S02]…’, 3)
#2 /opt/kaltura/app/plugins/conf_maps/lib/model/om/BaseConfMapsPeer.php(353): BasePeer::doSelect(Object(Criteria), Object(KalturaPDO))
#3 /opt/kaltura/app/plugins/conf_maps/lib/model/ConfMapsPeer.php(57): BaseConfMapsPeer::doSelect(Object(Criteria))
#4 /opt/kaltura/app/plugins/conf_maps/services/ConfMapsService.php(107): ConfMapsPeer::retrieveMapsNames()
#5 /opt/kaltura/app/api_v3/lib/reflection/KalturaActionReflector.php(233): ConfMapsService->getMapNamesAction()
#6 /opt/kaltura/app/api_v3/lib/KalturaDispatcher.php(130): KalturaActionReflector->invoke(Array)
#7 /opt/kaltura/app/api_v3/lib/KalturaFrontController.php(114): KalturaDispatcher->dispatch(‘confmaps_confma…’, ‘getmapnames’, Array)
#8 /opt/kaltura/app/api_v3/web/index.php(32): KalturaFrontController->run()
#9 {main}
2019-02-27 09:18:14 [0.000271] [10.0.113.40] [320548560] [67] [API] [KalturaFrontController->getExceptionObject] ALERT: PropelException: [wrapped: SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘kaltura.conf_maps’ doesn’t exist] in /opt/kaltura/app/vendor/propel/util/BasePeer.php:467
Stack trace:
#0 /opt/kaltura/app/plugins/conf_maps/lib/model/om/BaseConfMapsPeer.php(353): BasePeer::doSelect(Object(Criteria), Object(KalturaPDO))
#1 /opt/kaltura/app/plugins/conf_maps/lib/model/ConfMapsPeer.php(57): BaseConfMapsPeer::doSelect(Object(Criteria))
#2 /opt/kaltura/app/plugins/conf_maps/services/ConfMapsService.php(107): ConfMapsPeer::retrieveMapsNames()
#3 /opt/kaltura/app/api_v3/lib/reflection/KalturaActionReflector.php(233): ConfMapsService->getMapNamesAction()
#4 /opt/kaltura/app/api_v3/lib/KalturaDispatcher.php(130): KalturaActionReflector->invoke(Array)
#5 /opt/kaltura/app/api_v3/lib/KalturaFrontController.php(114): KalturaDispatcher->dispatch(‘confmaps_confma…’, ‘getmapnames’, Array)
#6 /opt/kaltura/app/api_v3/web/index.php(32): KalturaFrontController->run()
#7 {main}

So i have still have a missing table.
If anyone has an idea how this could happen and how to fix it, please let me know!
Thanks,
Werner

Hello @esnecca,

Please run:

# mysql -h $DB1_HOST -u $DB1_USER -p$DB1_PASS $DB1_NAME < /opt/kaltura/app/deployment/updates/sql/2018_08_19_create_config_maps_table.sql

That should fix it.

thx, yes, it did fix it.