Hi,
Can you please guide me as how i can change the hostname (subdomain.domain.com) of my already installed and running Kaltura with new hostname (new-subdomain.domain.com)?
Thanks in Advance
Hello,
Are you using the RPM or Deb install?
Am using RPM installation for Community Edition 10.8.0.
Simple re-run the config script and select a different host.
If this is an all in one server, you can run kaltura-config-all.sh, if not, you will need to run each config script[s] separately depending on the specific server role.
Hi Jess,
Thanks for the solution.
Yes, everything is running on one server.
Am worried about my data, running kaltura-config-all.sh will lead to any data loss or DB drop?
Hi,
No, it will skip DB creation since it will see the DB is already there.
However, never hurts to create a backup first. Which you can do with:
kaltura-export-db.sh
You will need to export:
| kaltura |
| kaltura_sphinx_log |
| kalturadw |
| kalturadw_bisources |
| kalturadw_ds |
| kalturalog |
But again, this is just a precaution measure.
Thanks,
DO we need to take backup of Kaltura Folder (File system) as well?
No, the configs are backed up automatically.
Hi Jess,
Thanks a lot for your kind help and suggestions.
Most welcome of course.
Will it work same for domain name (subdomain.domain.com) of my already installed and running Kaltura with new domain (new-subdomain.domain.com)?
Hi Jess,
We have ran the kaltura-config-all.sh file to reconfigure hostname but it seems that nothing has changed in the config files.
We are getting below response on sanity checking:
[Check kaltura-batch daemon is started by Monit] [PASSED, RC: 0] - [59.769556221]
[check daemon kaltura-batch init status] [PASSED, RC: 0] - [.007143554]
[Check kaltura-monit daemon status] [PASSED, RC: 0] - [.024757098]
[check daemon kaltura-monit init status] [PASSED, RC: 0] - [.008173744]
[Check memcached daemon status] [PASSED, RC: 0] - [.022992276]
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it…
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it…
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it…
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it…
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it…
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it…
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it…
[Check memcached daemon is started by Monit] [PASSED, RC: 0] - [7.344958259]
[check daemon memcached init status] [PASSED, RC: 0] - [.007123418]
[kaltura-html5lib ver in KMC config.ini] [PASSED, RC: 0] - [.140936741]
[kaltura-kdp3 ver in KDP3 config.ini] [PASSED, RC: 0] - [.032780269]
[kaltura-kmc ver in KMC config.ini] [PASSED, RC: 0] - [.066047359]
PHP Warning: file_get_contents(http://www..com:80/kmc): failed to open stream: HTTP request failed! HTTP/1.0 404 Not Found
in /opt/kaltura/bin/get_kmc_swfs.php on line 9
[Get KMC SWFs] [FAILED, RC: 255] - [.442245693]
curl: no URL specified!
curl: try ‘curl --help’ or ‘curl --manual’ for more information
[check_testme_page] [FAILED, RC: 1] - [.121263030]
[check_kmc_index_page] [FAILED, RC: 1] - [.112204942]
curl: no URL specified!
curl: try ‘curl --help’ or ‘curl --manual’ for more information
[check_admin_console_index_page] [FAILED, RC: 1] - [.119634849]
[check_studio_index_page] [FAILED, RC: 1] - [.475759929]
[check_clipapp_index_page] [FAILED, RC: 1] - [.478078045]
[Create Partner] [FAILED, RC: 255] - [.218939576]
Partner creation failed. I will skip all tests that require it.
[Red5 file upload] [SKIPPED as OflaDemo isn’t configured]
see: https://github.com/kaltura/platform-install-packages/blob/master/doc/install-kaltura-redhat-based.md#configure-red5-server
Thank you for running Kaltura! To keep Kaltura viable, stable and well tested, please join the community and help by contributing sanity tests that verify overall platform stability: http://bit.ly/kaltura-ci , and by contributing to the project roadmap by solving simple tasks and challenges: http://bit.ly/kaltura-tasks.
Please suggest.
Did you make sure to remove the /opt/kaltura/app/base-config.lock file before reconfiguring?
Hi Jess,
No we didn’t. But will try again by removing base-config.lock file.
Thanks for your suggestion.
Will let you know if we still get any issue.