FILES NOT UPLOADING USING TEST CONSOLE APIs

*I am using centos 6.7 release

*mysql Ver Distrib 5.1.73

*Below are my kaltura packages-
kaltura-release-11.2.0-1.noarch
kaltura-lame-3.99.5-3.x86_64
kaltura-sshpass-1.05-1.x86_64
kaltura-html5lib-v2.37.1-2.noarch
kaltura-clipapp-1.3-2.noarch
kaltura-kclip-v1.1.2.1-2.noarch
kaltura-kdp3-v3.9.9-2.noarch
kaltura-libmemcached-1.0.16-2.x86_64
kaltura-segmenter-1.0-2.x86_64
kaltura-batch-11.2.0-1.noarch
kaltura-server-11.5.0-1.noarch
kaltura-x264-0.140-2.20140104.x86_64
kaltura-libass-0.9.11-2.x86_64
kaltura-a52dec-0.7.4-11.x86_64
kaltura-ffmpeg-aux-2.1.3-1.x86_64
kaltura-postinst-1.0.30-2.noarch
kaltura-base-11.2.0-12.noarch
kaltura-krecord-1.0.0-1.noarch
kaltura-sphinx-2.2.1-17.x86_64
kaltura-kdp3wrapper-v37.0-1.noarch
kaltura-flexwrapper-v1.2-1.noarch
kaltura-kupload-1.0.0-1.noarch
kaltura-kcw-1.0.0-6.noarch
kaltura-html5-studio-v2.0.1-1.noarch
kaltura-widgets-1.0.0-8.noarch
kaltura-librtmp-2.3-2.x86_64
kaltura-front-11.2.0-1.noarch
kaltura-mencoder-3.4.6-9.x86_64
kaltura-pentaho-4.2.1-2.x86_64
kaltura-libopencore-amr-0.1.2-2.x86_64
kaltura-ffmpeg-2.7.2-2.x86_64
kaltura-monit-5.13-1.x86_64
kaltura-kdp-v2.7.0-1.noarch
kaltura-kvpm-v1.0.6-1.noarch
kaltura-kdpwrapper-v11.0-1.noarch
kaltura-kmc-v5.39.11-3.noarch
kaltura-libfaac-1.26-1.x86_64
kaltura-nginx-1.8.0-9.x86_64
kaltura-dwh-9.5.0-2.noarch

i am facing following issues-

  1. when restarting mysqld service- it shows “internal database error” from publisher console and doesn’t allow any new uploads. to troubleshoot this i am taking all database backup and running kaltura-drop-db.sh, then runing kaltura-config-all.sh to Reconfigure it and generating a fresh database. and then updating the newly generated “Kaltura” database with my backup dump.

  2. I have tried fresh installation of kaltura-11.5 and 11.2, then everything works fine, but i am still unable to upload files using test console api uploads.

  3. After few days proper functioning, my video uploads get stuck at converting stage only.

Hi,

When a video is stuck at converting, it usually means the batch daemon is down.
You should check by:
# /etc/init.d/kaltura-batch status
if down, try:
# /etc/init.d/kaltura-batch start

if still down, look at /opt/kaltura/log/kaltura_batch.log for errors.

In general, to debug you should always run:
# kaltlog
while making requests from the UI and look at the errors. Then go to the actual log file under /opt/kaltura/log and look at the lines before the actual error to understand what happened.