Hi Jess
I Think I have found the solution to my problem… The problem was to use the .ans file in the upgrade proccess. Beacuse of that I have earned from the previuos version the configuration of the SECOND sphinx server as “127.0.0.1” The problem i found in the doc is that when you deploy a new RPM cluster system you have the ability to introduce a second sphinks server if you want. But in the help notice which came along this step it is said… “Leave empty if you do not have”. That was I made I left empty… but automatically it fills in the configuration section the second sphinks index as “127.0.0.1” which for a front is an error because in a front there is no index. Because of that I Made the .ans file according to my previos version and that configuration was carried.
That was the mistake in this version… In my front configuration it is configured the second index as “127.0.0.1” an error in a cluster deployment. So I have edit the file /opt/kaltura/app/configurations/db.ini, replace the second sphinks with the same url as the first. Reload the apache. And until now IS WORKING!!!
So many thanks for your guide, it was very helpful. I only recomend to erase the notice tip in the index step when you are deploy the RPM cluster, or redesing the script in order to avoid the second index WHEN YOU LEAVE THE FIELD EMPTY. Or make required the second index configuration. That would be erase the optional thing…
Thanks for all