Kaltura-db-config.sh FAILED with: 255 on line 194


#1

For new install display error. i enabled https.
Output for /opt/kaltura/app/deployment/base/scripts/insertContent.php being logged into /opt/kaltura/log/insertContent.log

kaltura-db-config.sh FAILED with: 255 on line 194

Archving logs to /opt/kaltura/log/log_14_10_18_11_34.tar.gz…
ERROR: we failed on something else…

[root@kaltura log]# php /opt/kaltura/app/deployment/base/scripts/insertContent.php
Queuing action [userRole.add]
Queuing action [user.add]
Executing multirequest
service url: [http://kaltura]
curl: http://kaltura/api_v3/service/multirequest
post: {“format”:“3”,“ignoreNull”:true,“clientTag”:“php5:18-09-28”,“apiVersion”:“14.5.0”,“0”:{“service”:“userrole”,“action”:“add”,“userRole”:{“objectType”:“KalturaUserRole”,“name”:“System Administrator”,“systemName”:“System Administrator”,“description”:“System Administrator”,“status”:“1”,“permissionNames”:"",“tags”:“admin_console”},“ks”:“NjQwYWZlYjQ0NWUwOGMzOGRiZjNkMDlhNTVmNGEyZjMxM2MxNmYwMXwtMjstMjsxNTM5NTc1NDYwOzI7MTg3MzI7Ow==”},“1”:{“service”:“user”,“action”:“add”,“user”:{“objectType”:“KalturaUser”,“id”:“zhujianfeng@test.com”,“screenName”:“zhujianfeng@test.com”,“fullName”:“Kaltura Administrator",“email”:"zhujianfeng@test.com”,“status”:“1”,“password”:“12345678”,“isAdmin”:“1”,“roleIds”:"{1:result:id}",“allowedPartnerIds”:""},“ks”:“NjQwYWZlYjQ0NWUwOGMzOGRiZjNkMDlhNTVmNGEyZjMxM2MxNmYwMXwtMjstMjsxNTM5NTc1NDYwOzI7MTg3MzI7Ow==”},“kalsig”:“e959cde5d6257e9db77cd22a6ae9c9e0”}
result (serialized):

400 Bad Request

Bad Request

Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.

Hint: https://kaltura/

Apache/2.2.15 (CentOS) Server at kaltura Port 443

PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message 'failed to unserialize server result

400 Bad Request

Bad Request

Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.

Hint: https://kaltura/

Apache/2.2.15 (CentOS) Server at kaltura Port 443 ' in /opt/kaltura/app/tests/lib/KalturaClientBase.php:401 Stack trace: #0 /opt/kaltura/app/tests/lib/KalturaClientBase.php(953): KalturaClientBase->doQueue() #1 /opt/kaltura/app/tests/standAloneClient/exec.php(345): KalturaClientBase->doMultiRequest() #2 {main} thrown in /opt/kaltura/app/tests/lib/KalturaClientBase.php on line 401

#2

Hi @jianfzhu,

The DB population phase makes API requests to the Kaltura Server [an Apache Vhost]. Since these requests return HTTP 400, the deployment fails.

From the above output, it appears as though you’ve configured the Apache Kaltura Vhost to run over SSL on port 443, which is good but, when prompted about the Kaltura base endpoint [AKA Kaltura service URL], you’ve used http://kaltura instead of https://kaltura. That’s why Apache returns HTTP 400 with:

Your browser sent a request that this server could not understand.
Reason: You’re speaking plain HTTP to an SSL-enabled server port.

Rerun /opt/kaltura/bin/kaltura-config-all.sh and input https://kaltura when prompted for the service URL. kaltura-db-config.sh will inform you that you already have a kaltura DB in place. Since it is half baked, you should opt to drop it and recreate it. You should be good to go after that.

Note that the hostname used for the Kaltura endpoint [service URL] must be resolvable from both inside the server and from any machine you intend to perform playback from or access the management web I/Fs.


#3

Thanks, @jess now it can pass insertConten. but new error appears.
i manual run service httpd reload.
[root@kaltura batch]# service httpd reload
Reloading httpd: not reloading due to configuration syntax error
[FAILED]
[root@kaltura batch]# service httpd start
Starting httpd: httpd: Syntax error on line 220 of /etc/httpd/conf/httpd.conf: Syntax error on line 7 of /etc/httpd/conf.d/zzzkaltura.conf: Include directory ‘/etc/httpd/@APP_DIR@/configurations/apache/conf.d’ not found
[FAILED]


Output for /opt/kaltura/app/deployment/base/scripts/insertContent.php being logged into /opt/kaltura/log/insertContent.log
Generating UI confs…
Shutting down monit: [FAILED]
Starting monit: Starting Monit 5.23.0 daemon with http interface at [127.0.0.1]:2812
[ OK ]
Running Batch config…

kaltura-batch-14.5.0-1.noarch
base-config completed successfully, if you ever want to re-configure your system (e.g. change DB hostname) run the following script:

rm /opt/kaltura/app/base-config.lock

/opt/kaltura/bin/kaltura-base-config.sh

Reloading httpd: not reloading due to configuration syntax error
[FAILED]

kaltura-batch-config.sh FAILED with: 6 on line 100

Archving logs to /opt/kaltura/log/log_16_10_18_15_26.tar.gz…
ERROR: /opt/kaltura/bin/kaltura-batch-config.sh failed:( You can re-run it when the issue is fixed.


#4

Hi @jianfzhu,

I believe you’re encountering an issue that was fixed here:

This fix was included in the kaltura-postinst package released to the new stable repo [14.6.0]. You can either upgrade or patch /opt/kaltura/bin/kaltura-batch-config.sh manually and rerun kaltura-config-all.sh.


#5

@jess now i can install success. but can’t login https://kaltura/admin_console/index.php/partner/list
image

install log

Output for /opt/kaltura/app/deployment/base/scripts/insertContent.php being logged into /opt/kaltura/log/insertContent.log
Generating UI confs…
Shutting down monit: [FAILED]
Starting monit: Starting Monit 5.23.0 daemon with http interface at [127.0.0.1]:2812
[ OK ]
Running Batch config…

kaltura-batch-14.5.0-1.noarch
base-config completed successfully, if you ever want to re-configure your system (e.g. change DB hostname) run the following script:

rm /opt/kaltura/app/base-config.lock

/opt/kaltura/bin/kaltura-base-config.sh

Reloading httpd:
Stopping memcached: [ OK ]
Starting memcached: [ OK ]
Starting monit: Starting Monit 5.23.0 daemon with http interface at [127.0.0.1]:2812
[ OK ]
kaltura-nginx-1.14.0-4.x86_64
Kaltura API host and port (without the protocol) [kaltura:80]:

Nginx server name [kaltura]:

Nginx port to listen on [88]:
RTMP port to listen on [1935]:
Would you like to configure Nginx with SSL?[Y/n]n
Reloading nginx: [ OK ]
Running DWH config…

kaltura-dwh-12.14.0-1.noarch
base-config completed successfully, if you ever want to re-configure your system (e.g. change DB hostname) run the following script:

rm /opt/kaltura/app/base-config.lock

/opt/kaltura/bin/kaltura-base-config.sh

Deploying analytics warehouse DB, please be patient as this may take a while…
Output is logged to /opt/kaltura/dwh/logs/dwh_setup.log.

sending incremental file list
MySQLInserter/

sent 133 bytes received 25 bytes 316.00 bytes/sec
total size is 2646419 speedup is 16749.49
sending incremental file list
MappingFieldRunner/

sent 147 bytes received 25 bytes 344.00 bytes/sec
total size is 90670 speedup is 527.15
sending incremental file list
GetFTPFileNames/

sent 137 bytes received 25 bytes 324.00 bytes/sec
total size is 7308893 speedup is 45116.62
sending incremental file list
FetchFTPFile/

sent 131 bytes received 25 bytes 312.00 bytes/sec
total size is 5783119 speedup is 37071.28
sending incremental file list
DimLookup/

sent 122 bytes received 25 bytes 294.00 bytes/sec
total size is 3687964 speedup is 25088.19
sending incremental file list

sent 80 bytes received 12 bytes 184.00 bytes/sec
total size is 34770 speedup is 377.93
current version 5999

DWH configured.

====================================================================================================================

Setup completed successfully!

To access your Kaltura tools visit:
https://kaltura

To verify the integrity of your deployment and that all components are fully configured and installed,
you can run the sanity tests using the following command:
/opt/kaltura/bin/kaltura-sanity.sh

To begin, access the Admin Console using the Admin email and password you’ve entered while installing.
When logged in to the KAC, create a new publisher account to being using Kaltura.
Visit http://www.kaltura.org to join the community and get help!
Visit https://forum.kaltura.org to post issues and help others with theirs.
Visit https://www.kaltura.com/tiny/u08ud to submit our community survey.
Visit https://knowledge.kaltura.com to read documentation and learn more.

Thank you for running Kaltura! To keep Kaltura viable, stable and tested, please join the community and help by contributing sanity tests that verify overall platform stability: http://bit.ly/kaltura-ci , and by contributing to the project roadmap by solving simple tasks and challenges: http://bit.ly/kaltura-tasks.

[root@kaltura bin]#


#6

Hi @jianfzhu,

Please clear your browser’s cache and try again. Should be fine.


#7

@jess thanks, now i can login and upload movies, but can’t play it, always display converting…
wait 2 hours… try re-login, restart the server. no change.


#8

Hi @jianfzhu,

Is the kaltura-batch daemon running?

# /etc/init.d/kaltura-batch status

My guess is that it is not… if so:
What’s is in the of at /opt/kaltura/log/kaltura_batch.log?
Does the hostname, in /opt/kaltura/app/configurations/batch/batch.ini look OK? i.e:
[YOURHOST : mainTemplate]
Do the serviceUrl and secret directives hold the correct values? for the secret, should be the value of:

mysql> select admin_secret from kaltura.partner where id=-1;

#9

@jess kaltura-batch is running. and secret id is correct. below is kaltura-batch log and piece of ini file

i find below error in kschedulehelper log

[BATCH] [KScheduleHelper->run] ERR: exception ‘Exception’ with message ‘System is not yet ready - ping failed’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/batch/batches/KScheduleHelper.class.php(42): KalturaLog::err(‘System is not y…’)
#1 /opt/kaltura/app/batch/batches/KScheduleHelperExe.php(10): KScheduleHelper->run()

[root@kaltura init.d]# ./kaltura-batch status
Batch Manager running with PID 1530 [ OK ]

[root@kaltura init.d]# less /opt/kaltura/app/configurations/batch/batch.ini | grep secret
secret = d4b37d0ca3c2d282ef12ef6e065e829f
mysql> select admin_secret from kaltura.partner where id=-1;
±---------------------------------+
| admin_secret |
±---------------------------------+
| d4b37d0ca3c2d282ef12ef6e065e829f |
±---------------------------------+

kaltura_batch.log

2018-10-23 09:23:16 [0.000473] [1027757070] [461] [BATCH] [KProcessWrapper->init] DEBUG: Now executing [setsid /usr/bin/php /opt/kaltura/app/batch/batches/ValidateLiveMediaServers/KAsyncValidateLiveMediaServersExe.php eJzFVVtP2zAU3k9BeZw0cuk9fQG6ojGgRUvZpL1UbnzaWnXszHGgBfHfd+zYowK2oWnTHlon5+bvfOeSaZpEaXCe5WugNSdqRqrNSIolWwVpnKT3lfkP3rx9862GGjJ2B8GQpdEQ5T0rnwuodAYlUURLFRhFGhya0wQ2BhXkmknx1Ca1Z8fZbFg53moQtAqGCxs/ae6dE87l7aWkbMlyYgJZixgtBo0BExS2HpWT5bIW2siSLgr7jZASTYIhQZnJy8AryJYVdTHeQl6b0DNWgIHVSoNWFJmnbhoY2AVeOk1jhP0VMc49Q30b6O8AfQGnpR9p1lCU75lCHqXaXRG9ttQhtFCWOtwQrmtFQl2UntKCiZEC8iSlOMGUHhBw/Ej6BLb6TIOytsFwsldYLgkFmjXVcyrnCb5UJI3S+4fHWhufU8ZhrJRUmVbGDdUx3g5ixQRMS8fMv2Uzfs5mbNlE0khVYr4z5PRUcgq2H1vRczLDxnBelyar/8XcwHbpR7mYyaua85kcEZxVX9GmSQ2sigOUJ6BvAUSmZZlporRVml52D4w6x05sRWa2l4ohIr6bkKZREkziM+EMeYODC3YDB5dAGTnIQN2AqoxJG1tyV4In7vy42onc+xgX67HnEKNVlStWat+9PZQsiMZUqvBnnuGvA+PUHpbr0gESDv4rASWW1jNRaSJyqNxOioOml3DktQB1Rh1v72K3C3CXKbC0tlBM24tWj0Y5aeUJTfoJLGP8dSHqdqCfDJaBK3xeK27mUNbaF64feWXVrF5/G05vqxvHA6tu7al9fbA8rkl/MIt5sRyuFffzv9a6rNIw3DNEN3q79vQn7Sf9zuUqRP0hnjYI6qnfOKN1IX3j9HodhzLfk3a7bQ8Gg4wFWXCgjlObKM6iRgLupACf2HHFSJitiVitCXM2TDA9FXznvwEmFwWF1NDUzqeIYY9OjmejD/PrTxdHXmQKSjk0G2/SVFLj9+zscVP88Qzb/dHsmtd02MOLE28X+isbFAtwBYrhAsy/SLVp1tTLUuxL//K7hfIdRYd9XA== ‘[1299740743]’ >> /opt/kaltura/log/batch//validatelivemediaservers-0-2018-10-23.log 2>> /opt/kaltura/log/batch//validatelivemediaservers-0-2018-10-23.err.log]
2018-10-23 09:23:24 [8.446693] [1027757070] [462] [BATCH] [KGenericScheduler->spawn] INFO: Executing KScheduleHelper [0]
2018-10-23 09:23:24 [0.001121] [1027757070] [463] [BATCH] [KProcessWrapper->init] DEBUG: Now executing [setsid /usr/bin/php /opt/kaltura/app/batch/batches/KScheduleHelperExe.php eJzFVVtv2jAU3k+Z8jhpzQ0ohJe2jKrsAtVCNWkvyMQHsHDszHFWaNX/vmPHLqjtNmma1AcInJu/853zObMsibLgU15sgDacqDmptyMpVmwdZHGS3dfmO3jz7s2PBhrI2R0EQ5ZFQ7SfWvtCQK1zqIgiWqrAOLLgxDxNYRNQQ6GZFE9jMvvsupgtq8Y7DYLWwXBp6yftuQvCubz9IilbsYKYQjYixohBG8AEhZ1H5WyFbIQ2tqSHxn5rpESTYEjQZvoy8EqyY2VTjndQNKb0nJVgYKVZkEaR+dXLAgO7xENnWYywvyPGhWeobwv9F6Dxc5yxpR9p1lBWH5hCHqXaXxO9sdQhtFBWOtwSrhtFQl1WwfAB8cQHTqew0xMNyuIJhtOjuXFJKNC8HY5zuUzwkyBZlN0/HEZpci4Zh7FSUuVamTR0x8gXiDUTMKtc469EFnJC6gr7nSNll5JTsOuWRs+5CtvARVOZrl6LuYFdwo9yOZfXDedzOSIoRbeDcbuDBlbNAaoL0LcAIteyyjVR2joxrOt+MOoTOzbRSHelGCLi+ylpV9sozqkd3l4Br1qGOrhl++oxwl8IcIiIsZO6UKzSfgMNq0uiMbIOnySgok6qTeUqi6OzX6qcWBImotZEFFC7CyIO2smj/rQANaGuy/exEyZeLAosCSmaaWeZntKoIGmR0KSfwCrGTw+iXhf6yWAVuDEVjeJG57LRnq1+5J21A+dOQ7xpL44H1p0euT2buBFupR4pAvWTFXCjuO94o3VVZ2F4FIhp9HbjeUw6T7aTy3WI/hN82iLop17+o00p/ZhPT7sOZXFk7fU6HgwWGQuy5EAdp7ZRVI5GAu6kAN/Yec1ImG+IWG8IczFMMD0TfO8vZNOLglJqyLFHUL5FLHt2cT4fXS1uvn4+8yYzUMqhvVGn7SQ1vlwmB13/s+Ks2tkjqGcr9fCiINu32W9WECm+BsXwQiq+SbX9kxU3z//5m8B/AcUzR64= ‘[1352375983]’ >> /opt/kaltura/log/batch//kschedulehelper-0-2018-10-23.log 2>> /opt/kaltura/log/batch//kschedulehelper-0-2018-10-23.err.log]

batch.ini file

[template]
logDir = /opt/kaltura/log/batch/
pidFileDir = /opt/kaltura/var/run/
statusInterval = 300
serviceUrl = https://kaltura
remoteServerUrl = @BATCH_URL@
partnerId = -1
secret = d4b37d0ca3c2d282ef12ef6e065e829f
curlTimeout = 180
dwhPath = /opt/kaltura/log/dwh.log


#10

Hi @jianfzhu,

Seeing how the batch daemon is running, start by going to Admin Console->Batch Process Control and inputting an entry ID in the search box.
This will show the entire ingestion and export flow, including all the batch jobs that were attempted, their output and final status.