Please share your /opt/kaltura/app/configurations/batch/batch.ini, masking the ‘secret’ directive value and your /etc/init.d/kaltura-batch as well as the output for:
# rpm -q kaltura-batch
Wow, whatever that repo was seems to have corrected a lot of issues even before running the scripts again. Email notifications and other process started working immediately after installing that repo. I will update you on all open issues separately in each thread after I re-run the scripts.
I will drop all datebases and run the configuration scripts from scratch and see if this fixes my issues.
I still have not been able to get remote drop folders to work but I was able to get local drop folders to work without issue. Basically, if I try to access a drop folder using non SSL FTP I get an error saying the host cannot be reached. This is even after Kaltura has already connected once and got a list of the files to be imported from the FTP connection. My review shows the information passed on the second pass is malformed.
However, I am getting the following error when trying to configure the local folder to skip a file type.
The question is how to file this error and the malformed connection information passed by Kaltura on the second pass during the batch process when connecting with a basic FTP connection.