Hi @petruzzo79,
Glad to hear we’re good.
If you’re asking whether it was something you did wrong or not, I honestly can’t say for certain but as I mentioned before, it is possible that you had a defunct searchd proc which would account for the observed behaviour. After you killed it, kaltura-monit automatically started a new one which loaded the up to date configuration from /opt/kaltura/app/configurations/sphinx/kaltura.conf, thus solving your issue.