Kaltura-db-config.sh failed with: 255 on line 188

I took a look at the insertContent log and here is the bottom section of that

> result (serialized): 
> PHP Fatal error:  Uncaught exception 'KalturaClientException' with message 'failed to unserialize server result
> ' 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

here is the kaltura apache ssl log

[Sat Sep 17 00:27:28 2016] [error] [client xxx.xxx.xxx.130] PHP Fatal error: Uncaught exception 'Zend_Log_Exception' with message '"/opt/kaltura/log/kaltura_api_v3.log" cannot be opened with mode "a"' in /opt/kaltura/app/infra/log/KalturaSerializableStream.php:59\nStack trace:\n#0 /opt/kaltura/app/infra/log/KalturaSerializableStream.php(31): KalturaSerializableStream->initStream()\n#1 /opt/kaltura/app/infra/log/KalturaLogFactory.php(59): KalturaSerializableStream->__construct('/opt/kaltura/lo...', 'a')\n#2 /opt/kaltura/app/infra/log/KalturaLogFactory.php(18): KalturaLogFactory::getWriter(Object(Zend_Config))\n#3 /opt/kaltura/app/infra/log/KalturaLog.php(40): KalturaLogFactory::getLogger(Object(Zend_Config))\n#4 /opt/kaltura/app/alpha/apps/kaltura/lib/cache/kLoggerCache.php(39): KalturaLog::initLog(Object(Zend_Config))\n#5 /opt/kaltura/app/api_v3/bootstrap.php(30): kLoggerCache::InitLogger('api_v3')\n#6 /opt/kaltura/app/api_v3/web/index.php(17): require_once('/opt/kaltura/ap...')\n#7 {main}\n thrown in /opt/kaltura/app/infra/log/KalturaSerializableStream.php on line 59

any ideas :slight_smile: thanks

permission issue you think?

i also ran

bash -x /opt/kaltura/bin/kaltura-db-config.sh

and all info looks good

@jess

Today i went thru the whole thing again and found some stuff in my php ini that i needed to fix. And now im confident my php ini is done and in good shape.

So now at least i am getting more input into the insertContent log than i did before and its creating the api logs now, but now i dont see any errors in any of the logs that i have looked at, but yet it still fails

255 on line 188

I have installed alot of software in my days and yes i have had issues with some of them and some of them have litterally been a pain. However i been working on trying to get kaltura installed for about a week now and thats way too long to try to install any software. I am really gettting to the point that it might be better for me to just abandon this effort, install ffmpeg and be done with it. I was really hoping i could get this installed because i know in days to come it will be usefull but its not usefull if i cant get it installed.

Now that there is no error message i can find i dont know why its failing. I am really discouraged at this point. I will poke around a bit more to see what i can find.

even though it failed i do get the admin_console signin page and also the start/index.php page. So im wondering if i should try to discover the issues using the console rather than trying to rerun the configall all the time.

so i went ahead and checked a few things out and wanted to share it with you jess.

ls -al /etc/kaltura.d/system.ini

lrwxrwxrwx. 1 root root 42 Sep 13 20:27 /etc/kaltura.d/system.ini -> /opt/kaltura/app/configurations/system.ini

/opt/kaltura/bin/kaltura-sanity.sh

[Space on /] [PASSED, RC: 0] - [.004084624]
[Space on /opt/kaltura/web] [PASSED, RC: 0] - [.003851889]

INFO: Downloading ready-made schema from: /opt/kaltura/web/content/clientlibs/KalturaClient.xml
INFO: Generating from api version: 3.3.0, generated at: 17-09-2016
INFO: Now generating: php5full using Php5ClientGenerator
INFO: Delete old files [/opt/kaltura/web/content/clientlibs/php5full, /opt/kaltura/app/clients/php5]
INFO: Generate client library [php5full]
INFO: Copy sources from [/opt/kaltura/clients-generator/sources/php5]
INFO: Copy tests from [/opt/kaltura/clients-generator/sources/php5]
INFO: Saving client library to [/opt/kaltura/web/content/clientlibs/php5full]
INFO: Trying to package
DEBUG: Changing dir to [/opt/kaltura/web/content/clientlibs/php5full]
INFO: Executing: tar -czf “…/php5full_17-09-2016.tar.gz” …/php5full
tar: Removing leading `…/’ from member names
INFO: Package created successfully: …/php5full_17-09-2016.tar.gz
DEBUG: Restoring dir to [/opt/kaltura/clients-generator]
INFO: php5full generated successfully
[Check httpd daemon status] [PASSED, RC: 0] - [.057132119]
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…
[Check httpd daemon is started by Monit] [PASSED, RC: 0] - [10.502081715]
[check daemon httpd init status] [PASSED, RC: 0] - [.005529962]
[Check kaltura-sphinx daemon status] [PASSED, RC: 0] - [.049542117]
[Check kaltura-sphinx daemon is started by Monit] [PASSED, RC: 0] - [10.599907790]
[check daemon kaltura-sphinx init status] [PASSED, RC: 0] - [.004653263]
[Check kaltura-batch daemon status] [FAILED, RC: 1] - [.040318462]
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…

time lapse

Napping 119 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 120 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] - [124.326539201]
[check daemon kaltura-batch init status] [PASSED, RC: 0] - [.008903617]
[Check kaltura-monit daemon status] [PASSED, RC: 0] - [.033832180]
[check daemon kaltura-monit init status] [PASSED, RC: 0] - [.005886711]
[Check memcached daemon status] [PASSED, RC: 0] - [.034111567]
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…
[Check memcached daemon is started by Monit] [PASSED, RC: 0] - [10.508336309]
[check daemon memcached init status] [PASSED, RC: 0] - [.003630873]
[kaltura-html5lib ver in KMC config.ini] [PASSED, RC: 0] - [.058459214]
[kaltura-kdp3 ver in KDP3 config.ini] [PASSED, RC: 0] - [.040111728]
[kaltura-kmc ver in KMC config.ini] [PASSED, RC: 0] - [.037100784]
[Get KMC SWFs] [FAILED, RC: 255] - [.068954732]
[check_testme_page] [PASSED, RC: 0] - [.148267208]
[check_kmc_index_page] [PASSED, RC: 0] - [1.144251614]
[check_admin_console_index_page] [PASSED, RC: 0] - [.254309131]
[check_studio_index_page] [PASSED, RC: 0] - [.082685458]
[check_clipapp_index_page] [PASSED, RC: 0] - [.456418459]
mysql: [Warning] Using a password on the command line interface can be insecure.
[Create Partner] [PASSED, RC: 0] - [7.971846351]
[Local dropfolder creation] [PASSED, RC: 0] - [.898745757]
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
[Create flavor param] [PASSED, RC: 0] - [.723146149]
[Delete flavor param] [PASSED, RC: 0] - [.410661080]
[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] - [.723146149]
[Mail notification: ] [PASSED, RC: 0] - [.723146149]
[Upload content kaltura_logo_animated_blue.flv] [FAILED, RC: 255] - [.581979823]
Napping 10 seconds to allow entry to digest…
Napping 10 seconds to allow entry to digest…
Napping 10 seconds to allow entry to digest…
Napping 10 seconds to allow entry to digest…
Napping 10 seconds to allow entry to digest…
Napping 10 seconds to allow entry to digest…
Napping 10 seconds to allow entry to digest…
Napping 10 seconds to allow entry to digest…
Napping 10 seconds to allow entry to digest…
[kaltura_logo_animated_blue.flv - status] [FAILED, RC: 1] - [-.387388528]
Napping 30 seconds to allow mail to be sent out…
[Found an email sending entry for mb-titan.xxxxxxxxxxxxxxxxxxx.com@kaltura.com[PID is 101] in /var/log/maillog] [PASSED, RC: 0] - [30.110312582]
Testing analytics, be patient…

Please note: if you are running this test on a clustered ENV, it will fail but this does not mean there is an actual problem.
The tech information as to why is available here:

[DWH cycle] [FAILED, RC: 255] - [.469751779]
[Upload content kaltura_logo_animated_green.flv] [FAILED, RC: 255] - [.462518398]
[Upload bulk using CSV] [FAILED, RC: 255] - [.352375246]
[Upload bulk using XML] [FAILED, RC: 255] - [.337142959]
[Create player] [PASSED, RC: 0] - [.495328518]
[Generate thumb] [FAILED, RC: 255] - [.202014234]
[Delete partner] [PASSED, RC: 0] - [.246508493]
[Red5 file upload] [SKIPPED as OflaDemo isn’t configured]

Thank you for running Kaltura! To keep Kaltura viable, stable and well 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.

You have mail in /var/spool/mail/xxxxxxxx

php /opt/kaltura/app/tests/standAloneClient/exec.php /opt/kaltura/app/tests/standAloneClient/httpNotificationsTemplate.xml /tmp/out.xml

Host name: titan.xxxxxxxxxxxxxxxxxx.com
Partner email address: xxxxxxxx@xxxxxx.com
Partner password: xxxxxxx
Partner ID: dave
service url: [http://titan.xxxxxxxxxxxxx.com/]
curl: http://titan.xxxxxxxxxxx.com//api_v3/service/user/action/loginByLoginId
post: {"format":"3","ignoreNull":true,"clientTag":"php5:16-09-14","apiVersion":"3.3.0","loginId":"xxxxxxx@xxxx.com","password":"xxxxx","partnerId":"dave","expiry":"86400","privileges":"*","kalsig":"43a36bcc08e37a4579b5cfa94404aa41"}
result (serialized): <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /api_v3/service/user/action/loginByLoginId was not found on this server.</p>
<hr>
<address>Apache/2.2.15 (CentOS) Server at titan.xxxxxxxxxxxxxxxx.com Port 80</address>
</body></html>

when i try to login to the admin console it says An error occured error code: API:-1

please advise

The solution for me was to update php from 5.3 to 5.5, then i was able to get past the insertContent log

Output for /opt/kaltura/app/deployment/base/scripts/insertContent.php being logged into /opt/kaltura/log/insertContent.log
Generating UI confs..

and then it failed again down the line. Ill make a new post grrrrr