When attempting to restart httpd after having trouble connecting to the kmc and admin console, I got the following error.
[error] (EAI 2)Name or service not known: Could not resolve host name *:@KALTURA_VIRTUAL_HOST_PORT@ -- ignoring!
This error appeared after I was unable to load the admin pages for Kaltura. Any ideas what causes such and error or how to fix it. I am not sure if it is related to my recent update but it started after few hours after the update was completed. Currently, none of the Kaltura admin pages are not loading.
I followed the the instruction from a post I read about a php error to clear the Kaltura cache and it got the admin consoles working again.
service httpd stop
service kaltura-monit stop
rm -rf /opt/kaltura/app/cache/*
php /opt/kaltura/app/deployment/base/scripts/installPlugins.php
I had to change the permission on the follow file to run the command.
/opt/kaltura/app/generator/generate.php
After running the command I got the following message
/opt/kaltura/app/generator/generate.php: line 1: ?php: No such file or directory
/opt/kaltura/app/generator/generate.php: line 2: /bin: is a directory
/opt/kaltura/app/generator/generate.php: line 3: anaconda-ks.cfg: command not found
/opt/kaltura/app/generator/generate.php: line 4: anaconda-ks.cfg: command not found
/opt/kaltura/app/generator/generate.php: line 5: anaconda-ks.cfg: command not found
/opt/kaltura/app/generator/generate.php: line 6: syntax error near unexpected token(' /opt/kaltura/app/generator/generate.php: line 6:
* 1. Copying one of the existing client generators (*ClientGenerator.php) and name it accordingly.’
I am not sure what caused the issue and I am still getting the caption error when reloading ‘httpd’. This error does not appear to cause any issue with Kaltura running at this time but I still have not idea what cause it to stop running in the first place.