The hostname should have been changed before the install, but it is possible that human error may have crept in right after the ISP setup the server, and configuring the server, during the preparation for Kaltura, and might have changed the hostname at inappropriate stage.
Just in case that was the case, should I re-run /opt/kaltura/bin/kaltura-config-all.sh ? Or do I need to wipe out Kaltura and DB, and reinstall Kaltura and DB fresh? Or is there a more elegant solution?
No need to drop the entire DB, you can simply re-run /opt/kaltura/bin/kaltura-config-all.sh providing the new hostname and SERVICE URL as inputs. It will correct both the batch and Sphinx configuration files and restart the daemons and you should then have a functional system.
In the DB, the only place where the hostname is stored that is of importance is the kaltura.delivery_profile table so do make sure that the host_name and url columns point to the correct hostname.
Okay, that went well. It also fixed a problem where the video uploads of new content from a publisher were stuck in “converting” mode. Now they just automatically work.
Many thanks again!
Our testing/learning continues.
Cheers!
The video ingestion is handled by the batch daemon, so indeed, if the daemon is not running, videos will not be converted:)
Glad to hear we’re good now.