Kaltura-batch does not start

1

Hello,
I have 10.3.0 installed on an AWS EC2 instance. My current issue is that kaltura-batch does not start and gives an error similar to the one discussed in the post below.

However in my case the problem is not resolved when re-running:
/opt/kaltura/bin/kaltura-batch-config.sh

Any suggestions on the next steps for trouble-shooting would be appreciated.

My specific error in kaltura_batch.log is:
2015-02-04 13:19:33 [295703753] [KSchedulerConfig->load] NOTICE: loading configuration /opt/kaltura/app/configurations/batch at 1422942956
PHP Fatal error:  Uncaught exception ‘Zend_Config_Exception’ with message ‘Section ‘ip-172-31-33-203.us-west-2.compute.internal’ cannot be found in /opt/kaltura/app/cache//batch/config.ini’ in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Config/Ini.php:150
Stack trace:
#0 /opt/kaltura/app/batch/scheduler/KSchedulerConfig.class.php(59): Zend_Config_Ini->__construct(’/opt/kaltura/ap…’, ‘ip-172-31-33-20…’, true)
#1 /opt/kaltura/app/batch/scheduler/KSchedulerConfig.class.php(42): KSchedulerConfig->load()
#2 /opt/kaltura/app/batch/scheduler/KGenericScheduler.class.php(81): KSchedulerConfig->__construct(’/opt/kaltura/ap…’)
#3 /opt/kaltura/app/batch/scheduler/KGenericScheduler.class.php(63): KGenericScheduler->loadConfig(’/opt/kaltura/ap…’)
#4 /opt/kaltura/app/batch/KGenericBatchMgr.class.php(37): KGenericScheduler->__construct(’/usr/bin/php’, ‘/opt/kaltura/ap…’)
#5 {main}
  thrown in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Config/Ini.php on line 150

2

Hi,

What do you have in:
/opt/kaltura/app/configurations/batch/batch.ini, line 23?

[@INSTALLED_HOSNAME@ : mainTemplate]

‘@INSTALLED_HOSNAME@’ should be your actual hostname which the batch-config.sh script does as part of its job.
Also, try clearing /opt/kaltura/app/cache//batch dir and restart batch with:
# /etc/init.d/kaltura-batch restart

3

Thank you. I made the changes you suggested. Those changes alone did not solve the problem, however. The final culprit was the system “hostname” was pointing to the AWS default hostname. Once the system hostname was updated so that hostname returned my FQDN batch started fine.

Unfortunately my files are still getting stuck in the conversion process. The admin console reports status for "Extract Media (94) with Status = Pending with a Processing Start and End time of Dec. 31, 1969.

Is this normal? The dates seem odd. Also I can’t seem to find the entry id in any of the batch logs so not sure where this is failing in the batch process. Thanks for any additional hints.

4

Hello,

Please use kaltlog to check errors in the logs so we can understand what is failing.
Thanks,

5

It seems to another bad hostname. Where would these be configured? ip-172-31-42-45.us-west-2.compute.internal is not currently on this system.

2015-02-08 20:43:29 [0.000362] [54.148.255.126] [1429271386] [API] [KalturaStatement->execute] DEBUG: Sql took - 0.00024318695068359 seconds
2015-02-08 20:43:29 [0.000849] [54.148.255.126] [1429271386] [API] [KalturaFrontController->getExceptionObject] ERR: exception ‘KalturaAPIException’ with message ‘Scheduler id “47552” conflicts between hosts: “dev.awmedia.biz” and “ip-172-31-42-45.us-west-2.compute.internal”’ in /opt/kaltura/app/api_v3/services/BatchControlService.php:148
Stack trace:
#0 /opt/kaltura/app/api_v3/services/BatchControlService.php(48): BatchControlService->getOrCreateScheduler(Object(KalturaScheduler))

==> /opt/kaltura/log/batch/kschedulehelper-0-2015-02-08.err.log <==
PHP Fatal error:  Uncaught exception ‘KalturaException’ with message ‘Scheduler id “47552” conflicts between hosts: “dev.awmedia.biz” and “ip-172-31-42-45.us-west-2.compute.internal”’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:734
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(644): KalturaClientBase->throwExceptionIfError(Array)

6

Please run:
truncate all tables that start with scheduler in the kaltura DB.
Then restart the batch daemon and you should be OK.
Let me know,