Hi,
Running /opt/kaltura/bin/kaltura-db-update.sh is no longer needed.
I updated the documentation just now.
Dropping the DB means you lost all the data.. unless it is what you intended, I suggest you reimport it.
As for your actual problem, it starts with bad permissions on /opt/kaltura/app/cache.
It should be:
# ls -ald /opt/kaltura/app/cache/
drwxrwxr-x 7 kaltura apache 4096 Aug 3 10:00 /opt/kaltura/app/cache
so, directory is 775 and both the kaltura and apache user should be able to write to it.
Start by removing all cached files [be sure NOT to remove directories] by using:
find /opt/kaltura/app/cache/ -type f -exec rm {} \;
then, set permissions correctly with:
# chmod -R 775 /opt/kaltura/app/cache
# chown -R kaltura.apache /opt/kaltura/app/cache
Then remove the lock files:
# rm /opt/kaltura/app/base-config.lock
# rm /opt/kaltura/app/base-config-generator.lock
and rerun /opt/kaltura/bin/kaltura-config-all.sh and let's see.