Please look at the pictures.
The problem is some users can not convert their uploaded video. When I check from batch management from admin_console, it’s show me the tasks pedding forever.
Any help?
Thank you very much.
Thank you very much.
The errors showed from log when I uploaded new video.
Anyway, The problem pending converting just happened with some accounts in kaltura.
tail -f /opt/kaltura/log/batch/*`date +%Y-%m-%d`*.log /opt/kaltura/log/kaltura_batch.log | grep -A 1 -B 1 --color "ERR:\|trace\|CRIT\|\[error\]"
' in /opt/kaltura/app/batch/client/KalturaClientBase.php:401
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1122): KalturaClientBase->doQueue()
--
' in /opt/kaltura/app/batch/client/KalturaClientBase.php:401
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1122): KalturaClientBase->doQueue()
You need to open the relevant log file and look at the lines leading to the final error.
Then paste the lines leading to it plus the full stack trace so I can help you further.
Thank you very much.
I rechecked again by log schedulerId and workerId but all of both return NULL.
I think this is the reason to make this->getJobs() method from KJobHandlerWorker.class.php return NULL.
Could yo help me know what happened? I’m very confusing this case
I just see only error from /opt/kaltura/log/batch/partnerloadcleanup-0-2016-08-18.err.log
PHP Fatal error: Uncaught exception 'KalturaClientException' with message 'failed to unserialize server result
' in /opt/kaltura/app/batch/client/KalturaClientBase.php:401
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1122): KalturaClientBase->doQueue()
#1 /opt/kaltura/app/batch/batches/Cleanup/KAsyncPartnerLoadCleanup.class.php(28): KalturaBatchService->updatePartnerLoadTable()
#2 /opt/kaltura/app/batch/batches/Cleanup/KAsyncPartnerLoadCleanupExe.php(11): KAsyncPartnerLoadCleanup->run()
#3 {main}
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 401
And I also check /opt/kaltura/log/batch//convert-0-2016-08-18.log But it alway returned 0 sent to scheduler
tail -f /opt/kaltura/log/kaltura_apache_errors_ssl.log
[Wed Aug 24 17:21:06 2016] [error] [client 52.196.26.215] PHP Fatal error: Call to a member function getJobTypeQuota() on a non-object in /opt/kaltura/app/alpha/lib/model/PartnerLoadPeer.php on line 180
[Wed Aug 24 17:22:07 2016] [error] [client 52.196.26.215] PHP Fatal error: Call to a member function getJobTypeQuota() on a non-object in /opt/kaltura/app/alpha/lib/model/PartnerLoadPeer.php on line 180
[Wed Aug 24 17:23:08 2016] [error] [client 52.196.26.215] PHP Fatal error: Call to a member function getJobTypeQuota() on a non-object in /opt/kaltura/app/alpha/lib/model/PartnerLoadPeer.php on line 180
[Wed Aug 24 17:24:10 2016] [error] [client 52.196.26.215] PHP Fatal error: Call to a member function getJobTypeQuota() on a non-object in /opt/kaltura/app/alpha/lib/model/PartnerLoadPeer.php on line 180
[Wed Aug 24 17:25:10 2016] [error] [client 52.196.26.215] PHP Fatal error: Call to a member function getJobTypeQuota() on a non-object in /opt/kaltura/app/alpha/lib/model/PartnerLoadPeer.php on line 180
[Wed Aug 24 17:26:12 2016] [error] [client 52.196.26.215] PHP Fatal error: Call to a member function getJobTypeQuota() on a non-object in /opt/kaltura/app/alpha/lib/model/PartnerLoadPeer.php on line 180
That I found on Kaltura document but I dont understand clearly
Job Quota - A quota can be configured to limit the number of concurrently running jobs in the Kaltura deployment. There is a system-wide default as well as defaults for specific job types. It is also possible to configure the quota differently per each account. https://knowledge.kaltura.com/kaltura-media-transcoding-services-and-technology