Internal database error while clicking analytics and dashboard

[rahul_bhargava]

Hello All,

While logging in KMC, I am facing issue of internal database error in analytics and dashboard.
I have created a new fresh self hosted Kaltura cluster 10.19 and I have mounted my old database to my new database andmy

mysql version is:

mysql-libs-5.1.73-5.el6_6.x86_64
mysql-5.1.73-5.el6_6.x86_64
mysql-server-5.1.73-5.el6_6.x86_64

and kaltura version is:

kaltura-base-10.19.0-10.noarch
kaltura-lame-3.99.5-3.x86_64
kaltura-x264-0.140-2.20140104.x86_64
kaltura-kupload-1.0.0-1.noarch
kaltura-libmemcached-1.0.16-2.x86_64
kaltura-ffmpeg-aux-0.6-3.x86_64
kaltura-kmc-v5.39.8-2.noarch
kaltura-front-10.19.0-1.noarch
kaltura-mencoder-3.4.6-9.x86_64
kaltura-release-10.19.0-1.noarch
kaltura-monit-5.13-1.x86_64
kaltura-sphinx-2.2.1-16.x86_64
kaltura-a52dec-0.7.4-11.x86_64
kaltura-kdp3-v3.9.9-2.noarch
kaltura-kdpwrapper-v11.0-1.noarch
kaltura-kclip-v1.1.2.1-2.noarch
kaltura-kvpm-v1.0.6-1.noarch
kaltura-clipapp-1.3-2.noarch
kaltura-librtmp-2.3-2.x86_64
kaltura-segmenter-1.0-1.x86_64
kaltura-html5-studio-v2.0.0-1.noarch
kaltura-krecord-1.0.0-1.noarch
kaltura-ffmpeg-2.1.3-9.x86_64
kaltura-widgets-1.0.0-8.noarch
kaltura-libfaac-1.26-1.x86_64
kaltura-batch-10.19.0-1.noarch
kaltura-libopencore-amr-0.1.2-2.x86_64
kaltura-sshpass-1.05-1.x86_64
kaltura-kcw-1.0.0-6.noarch
kaltura-flexwrapper-v1.2-1.noarch
kaltura-kdp3wrapper-v37.0-1.noarch
kaltura-kdp-v2.7.0-1.noarch
kaltura-html5lib-v2.34-1.noarch
kaltura-libass-0.9.11-2.x86_64
kaltura-nginx-1.8.0-4.x86_64

and while i am restarting all the kaltura services it shows :

[root@videocms ~]# /etc/init.d/httpd restart
Stopping httpd: [ OK ]
Starting httpd: [ OK ]
[root@videocms ~]# /etc/init.d/kaltura-monit restart
Shutting down monit: [ OK ]
Starting monit: Starting Monit 5.13 daemon with http interface at [*]:2812
[ OK ]
[root@videocms ~]# /etc/init.d/kaltura-batch restart
Shutting down:Killing batchMgr and workers
[ OK ]
Starting:[FAILED]
Service batch isn’t running but stale lock file exists
Removing stale lock file at /opt/kaltura/log/batch/batch.pid
/usr/bin/php KGenericBatchMgr.class.php /usr/bin/php /opt/kaltura/app/configurations/batch >> /opt/kaltura/log/kaltura_batch.log 2>&1 &
[ OK ]
[root@videocms ~]# /etc/init.d/kaltura-nginx restart
Stopping nginx: [ OK ]
Starting nginx: [ OK ]
[root@videocms ~]# /etc/init.d/kaltura-populate restart
Tue Oct 6 13:46:36 IST 2015
Shutting down:
Service populate isn’t currently running.
Starting:
Service populate isn’t running but stale lock file exists
Removing stale lock file at /opt/kaltura/log/populate.pid
/usr/bin/php populateFromLog.php >> /opt/kaltura/log/kaltura_populate.log 2>&1 &
[ OK ]

KALTLOG OUTPUT:

2015-10-06 14:59:12 [0.000220] [122.184.129.18] [129898300] [29] [API] [KalturaFrontController->errorHandler] WARN: /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php line 1325 - mysqli_error() expects parameter 1 to be mysqli, boolean given
2015-10-06 14:59:12 [0.000179] [122.184.129.18] [129898300] [30] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message 'Can’t use foo : ’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1325
Stack trace:

#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(879): myReportsMgr::executeQuery(’?SELECT??DATE(D…’)

2015-10-06 14:59:12 [0.000191] [122.184.129.18] [129898300] [31] [API] [myReportsMgr::executeQueryByType] NOTICE: Can’t use foo :
2015-10-06 14:59:12 [0.000301] [122.184.129.18] [129898300] [32] [API] [KalturaFrontController->getExceptionObject] CRIT: exception ‘kCoreException’ with message 'Can’t use foo : ’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1325
Stack trace:

#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(879): myReportsMgr::executeQuery(’?SELECT??DATE(D…’)

2015-10-06 14:59:12 [0.000166] [122.184.129.18] [129898300] [45] [API] [KalturaFrontController->errorHandler] WARN: /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php line 1325 - mysqli_error() expects parameter 1 to be mysqli, boolean given
2015-10-06 14:59:12 [0.000169] [122.184.129.18] [129898300] [46] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message 'Can’t use foo : ’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1325
Stack trace:

#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(879): myReportsMgr::executeQuery(’# return count_…’)

2015-10-06 14:59:12 [0.000320] [122.184.129.18] [129898300] [47] [API] [myReportsMgr::executeQueryByType] NOTICE: Can’t use foo :
2015-10-06 14:59:12 [0.000177] [122.184.129.18] [129898300] [48] [API] [KalturaFrontController->getExceptionObject] CRIT: exception ‘kCoreException’ with message ‘Can’t use foo : ’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1325
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(879): myReportsMgr::executeQuery(’# return count_…’)

[oferc1]

Try one of the following:

kCoreException in KMC

Hello everyone, Met with server internal error dialog when logging into KMC and click Analytics Tab, and extracted detailed log, any hints what is wrong? And what to check next step? Thanks. 2015-06-24 15:45:35 [0.001585] [::1] [991771667] [API] [KalturaFrontController->errorHandler] WARN: /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php line 1309 - mysqli_error() expects parameter 1 to be mysqli, boolean given 2015-06-24 15:45:35 [0.000160] [::1] [991771667] [API] [kC…

Unable to Upload Video using KMC CE-10.0.0 (DWH cycle FAILED issue)

Thanks for the replay and help. Yes sanity test is passed for upload and mock play, please refer sanity test logs. Kaltlog while login to KMC: [0.001247] [xx.xx.xx.xx] [1478801584] [PS2] [sfView->initialize] INFO: {sfView} initialize view for "kmc/kmc4"  [0.003462] [xx.xx.xx.xx] [1478801584] [PS2] [sfPHPView->renderFile] INFO: {sfView} render "/opt/kaltura/app/alpha/apps/kaltura/modules/kmc/templates/kmc4Success.php" [0.003271] [xx.xx.xx.xx] [1478801584] [PS2] [sfPHPView->decorate] INFO:…

[rahul_bhargava]

Hi oferc1,
We have a fresh Kaltura Cluster 10.19 CE set up and we have imported old database to our database.
Will my database be dropped if I re run the DWH config file???
Below is the output of sanity test. DWH Cycle test is skipped and kaltura-batch test is failed.
Please provide some suggestion.

[root@abc ~]# /opt/kaltura/bin/kaltura-sanity.sh
[Space on /] [PASSED, RC: 0] - [.008553528]
[Space on /opt/kaltura/web] [PASSED, RC: 0] - [.003325438]
[Check httpd daemon status] [PASSED, RC: 0] - [.017561386]
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it…
Napping 2 seconds to allow the daemon httpd to finish its init after monit restarted it…
Napping 3 seconds to allow the daemon httpd to finish its init after monit restarted it…
Napping 4 seconds to allow the daemon httpd to finish its init after monit restarted it…
Napping 5 seconds to allow the daemon httpd to finish its init after monit restarted it…
Napping 6 seconds to allow the daemon httpd to finish its init after monit restarted it…
Napping 7 seconds to allow the daemon httpd to finish its init after monit restarted it…
Napping 8 seconds to allow the daemon httpd to finish its init after monit restarted it…
Napping 9 seconds to allow the daemon httpd to finish its init after monit restarted it…
Napping 10 seconds to allow the daemon httpd to finish its init after monit restarted it…
Napping 11 seconds to allow the daemon httpd to finish its init after monit restarted it…
Napping 12 seconds to allow the daemon httpd to finish its init after monit restarted it…
Napping 13 seconds to allow the daemon httpd to finish its init after monit restarted it…
Napping 14 seconds to allow the daemon httpd to finish its init after monit restarted it…
Napping 15 seconds to allow the daemon httpd to finish its init after monit restarted it…
Napping 16 seconds to allow the daemon httpd to finish its init after monit restarted it…
Napping 17 seconds to allow the daemon httpd to finish its init after monit restarted it…
Napping 18 seconds to allow the daemon httpd to finish its init after monit restarted it…
Napping 19 seconds to allow the daemon httpd to finish its init after monit restarted it…
Napping 20 seconds to allow the daemon httpd to finish its init after monit restarted it…
[Check httpd daemon is started by Monit] [PASSED, RC: 0] - [21.377930218]
[check daemon httpd init status] [PASSED, RC: 0] - [.014886806]
[Check kaltura-sphinx daemon status] [PASSED, RC: 0] - [.019063856]
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it…
Napping 2 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it…
Napping 3 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it…
Napping 4 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it…
Napping 5 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it…
Napping 6 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it…
Napping 7 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it…
Napping 8 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it…
Napping 9 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it…
Napping 10 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it…
Napping 11 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it…
Napping 12 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it…
Napping 13 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it…
Napping 14 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it…
Napping 15 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it…
Napping 16 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it…
Napping 17 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it…
Napping 18 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it…
[Check kaltura-sphinx daemon is started by Monit] [PASSED, RC: 0] - [68.909875466]
[check daemon kaltura-sphinx init status] [PASSED, RC: 0] - [.004247793]
[Check kaltura-batch daemon status] [FAILED, RC: 1] - [.040091285]
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 2 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 3 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 4 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 5 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 6 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 7 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 8 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 9 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 10 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 11 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 12 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 13 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 14 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 15 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 16 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 17 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 18 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 19 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 20 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 21 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 22 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 23 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 24 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 25 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 26 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 27 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 28 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 29 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
[Check kaltura-batch daemon is started by Monit] [FAILED, RC: 1] - [122.231270794]
[check daemon kaltura-batch init status] [PASSED, RC: 0] - [.002733497]
[Check kaltura-monit daemon status] [PASSED, RC: 0] - [.012713730]
[check daemon kaltura-monit init status] [PASSED, RC: 0] - [.002639191]
[Check memcached daemon status] [PASSED, RC: 0] - [.013395394]
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it…
Napping 2 seconds to allow the daemon memcached to finish its init after monit restarted it…
Napping 3 seconds to allow the daemon memcached to finish its init after monit restarted it…
Napping 4 seconds to allow the daemon memcached to finish its init after monit restarted it…
Napping 5 seconds to allow the daemon memcached to finish its init after monit restarted it…
Napping 6 seconds to allow the daemon memcached to finish its init after monit restarted it…
Napping 7 seconds to allow the daemon memcached to finish its init after monit restarted it…
Napping 8 seconds to allow the daemon memcached to finish its init after monit restarted it…
Napping 9 seconds to allow the daemon memcached to finish its init after monit restarted it…
Napping 10 seconds to allow the daemon memcached to finish its init after monit restarted it…
Napping 11 seconds to allow the daemon memcached to finish its init after monit restarted it…
Napping 12 seconds to allow the daemon memcached to finish its init after monit restarted it…
Napping 13 seconds to allow the daemon memcached to finish its init after monit restarted it…
Napping 14 seconds to allow the daemon memcached to finish its init after monit restarted it…
Napping 15 seconds to allow the daemon memcached to finish its init after monit restarted it…
[Check memcached daemon is started by Monit] [PASSED, RC: 0] - [15.320109395]
[check daemon memcached init status] [PASSED, RC: 0] - [.009198888]
[kaltura-html5lib ver in KMC config.ini] [PASSED, RC: 0] - [.115883385]
[kaltura-kdp3 ver in KDP3 config.ini] [PASSED, RC: 0] - [.030037615]
[kaltura-kmc ver in KMC config.ini] [PASSED, RC: 0] - [.015450652]
[Get KMC SWFs] [PASSED, RC: 0] - [.189274250]
[check_testme_page] [PASSED, RC: 0] - [12.885710650]
[check_kmc_index_page] [PASSED, RC: 0] - [.014996189]
[check_admin_console_index_page] [PASSED, RC: 0] - [.245460691]
[check_studio_index_page] [PASSED, RC: 0] - [.009695784]
[check_clipapp_index_page] [PASSED, RC: 0] - [.394208926]
[Create Partner] [PASSED, RC: 0] - [3.252253142]
[Local dropfolder creation] [PASSED, RC: 0] - [.367899199]
[Create flavor param] [PASSED, RC: 0] - [.372336055]
[Delete flavor param] [PASSED, RC: 0] - [.157064424]
[HTTP notification:
No HTTP templates exist.
Try running:
php /opt/kaltura/app/tests/standAloneClient/exec.php /opt/kaltura/app/tests/standAloneClient/httpNotificationsTemplate.xml /tmp/out.xml
Passing -2 as partner ID] [PASSED, RC: 0] - [.372336055]
[Mail notification: ID: 20, Subject: Your video is ready to be played!, Mail body: Hello world:)] [PASSED, RC: 0] - [.372336055]
[Upload content kaltura_logo_animated_blue.flv] [PASSED, RC: 0] - [.691913542]
Napping 10 seconds to allow entry 0_s5g53krm to digest…
Napping 10 seconds to allow entry 0_s5g53krm to digest…
Napping 10 seconds to allow entry 0_s5g53krm to digest…
Napping 10 seconds to allow entry 0_s5g53krm to digest…
Napping 10 seconds to allow entry 0_s5g53krm to digest…
Napping 10 seconds to allow entry 0_s5g53krm to digest…
Napping 10 seconds to allow entry 0_s5g53krm to digest…
Napping 10 seconds to allow entry 0_s5g53krm to digest…
Napping 10 seconds to allow entry 0_s5g53krm to digest…
[kaltura_logo_animated_blue.flv - 0_s5g53krm status] [FAILED, RC: 1] - [-.380381707]
Napping 30 seconds to allow mail to be sent out…
send-mail: Cannot open mail:25
[Could not find an email sending entry for mb-videocms.webdunia.com@kaltura.com [PID is 111] in /var/log/maillog] [FAILED, RC: 1] - [30.012645102]
[Upload content kaltura_logo_animated_green.flv] [PASSED, RC: 0] - [.431452362]
[Upload bulk using CSV] [PASSED, RC: 0] - [.311133137]
[Upload bulk using XML] [PASSED, RC: 0] - [.270383554]
[Create player] [PASSED, RC: 0] - [.163253894]
[Generate thumb] [FAILED, RC: 255] - [.134272368]
[Delete partner] [PASSED, RC: 0] - [.116947519]