It’s time to upgrade my Kaltura CE Installation to it’s newest Release 13.0.0.
Last time I did upgrade, I did run in some problems:
After fixing my broken Kaltura I was a bit careful to upgrade again, like “Never touch a running System”
But now I’t time to go over to a new release and before I do I’d like to ask if I can simply folow the upgrade steps that are descibed below or if I have to consider something else before?
What are your experiences with Upgrading Kaltura to a newer release?
The upgrade howto you referenced includes all the steps you need to perform when upgrading.
As with any complex server side product, upgrades can get complicated, we do our very best to simplify and test the process continuously but there are always edge cases. My best recommendation to avoid downtime is to first do so on a staging ENV. If you’ll have issues post upgrading, do post them and I’ll gladly help you solve them.
In general, I recommend performing upgrades at small intervals, you don’t have to upgrade every other week, but the longer you wait between upgrades, the bigger the delta and risk.
Hi jess,
Thanks for the suggestion. Today I’ve tried the upgrade and it seems that it worked almost fine.
Previously I did create some Publisher Users and they’re all here if I log in to the admin console. For each Publisher I did also create some subusers (KMC Users) who work together with the same media content pool. It seems that all of the subusers are gone. The list is empty --> See Screenshot .Is there a way to restore them? Where are they stored and is it needed to save them before the upgrade?
if so, try running:
# php /opt/kaltura/app/deployment/base/scripts/populateSphinxKusers.php
and make sure it finishes w/o errors, if there are errors, please paste them here.
@jess
Thank you so much. With a query of that SQL statement, I could see all the users that were missing.
The php command worked fine without any errors and now I can see them again
It seems that I have a similar issue described in the topic here:
If there is a recommendation how to set the permissions on /content/generatedUiConf, I’ll correct them.
Creating a new player in the universal studio worked fine.
I did run the sanity check. Looks mostly fine as passed, but there are three errors:
[kaltura_logo_animated_blue.flv - 0_v7r0kq4p status] [FAILED, RC: 1] - [-.417988825]
Napping 30 seconds to allow mail to be sent out…
[Found an email sending entry for mb-agsstr01.gib.bs@kaltura.com[PID is 115] in /var/log/maillog] [PASSED, RC: 0] - [30.050433933]
Testing analytics, be patient…
Hi Jess, I did set the permissions as described, Thank you so much for your help
If I run the kaltlog command, I can see two other errors and one of them is constantly repeating:
==> /opt/kaltura/log/kaltura_apache_errors.log <==
[Fri Aug 11 14:28:32 2017] [error] [client 127.0.0.1] File does not exist: /opt/kaltura/app/alpha/web/localthumb
[Fri Aug 11 14:34:20 2017] [error] [client 127.0.0.1] File does not exist: /opt/kaltura/app/alpha/web/localthumb
And that’s the error that is constantly repeating:
–
2017-08-11 16:21:52 [0.000545] [127.0.0.1] [377205948] [28] [API] [KalturaStatement->execute] DEBUG: Sql took - 0.00031208992004395 seconds
2017-08-11 16:21:52 [0.000427] [127.0.0.1] [377205948] [29] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message ‘Dynamic enum not found [scheduleBulkUpload.SCHEDULE_EVENT] for type [BulkUploadObjectType]’ in /opt/kaltura/app/alpha/lib/kPluginableEnumsManager.php:167
Any ideas how i can fix them too?
Another issue was send to me by a user. He did work with categories, but as you can see on the screenshot on the left there are no more categories displayed:
@jess and @aquileasfx1
Thanks, that’s firstclass community work!
After running the kaltura-sphinx-reindex script, all the categories got restored and are available now!
For the other issue I’ve followed the suggestions from the other thread! It seems that the generate.php script went trough.
If I run again the kaltlog I can see some permission errors with the batch process job. A video that was uploaded is still queued and did not go over to the converting process. I’ll post a screenshot (For some reason copy/past from my terminal session don’t work…)
I’m confident that we’ll also resolve this issue.
Thanks in advance
@jess
Hi Jess, I did recheck and set the permission command over /opt/kaltura/app/cache again as you’ve described.
Now it seems that the permission error is gone, but if I rerun the kaltlog command, I got a bunch of new errors that I havn’t seen before. Im slightly confused
==> /opt/kaltura/log/kaltura_apache_errors.log <==
[Mon Aug 14 09:47:30 2017] [error] [client 127.0.0.1] File does not exist: /opt/kaltura/app/alpha/web/localthumb
[Mon Aug 14 09:47:30 2017] [error] [client 127.0.0.1] File does not exist: /opt/kaltura/app/alpha/web/localthumb
[Mon Aug 14 09:47:30 2017] [error] [client 127.0.0.1] File does not exist: /opt/kaltura/app/alpha/web/localthumb
[Mon Aug 14 10:19:39 2017] [error] [client 127.0.0.1] File does not exist: /opt/kaltura/app/alpha/web/localthumb
[Mon Aug 14 10:19:39 2017] [error] [client 127.0.0.1] File does not exist: /opt/kaltura/app/alpha/web/localthumb
[Mon Aug 14 10:19:39 2017] [error] [client 127.0.0.1] File does not exist: /opt/kaltura/app/alpha/web/localthumb
/opt/kaltura/log/batch/bulkuploadcloser-0-2017-08-13.err.log
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘Empty reply from server’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:362
Stack trace:
/opt/kaltura/app/batch/client/KalturaClient.php(1364): KalturaClientBase->doQueue()
==> /opt/kaltura/log/batch/extractmedia-0-2017-08-14.err.log <==
PHP Warning: Division by zero in /opt/kaltura/app/infra/media/mediaInfoParser/KMediaFileComplexity.php on line 281
PHP Notice: Trying to get property of non-object in /opt/kaltura/app/infra/media/mediaInfoParser/KMediaFileComplexity.php on line 282
PHP Notice: Trying to get property of non-object in /opt/kaltura/app/infra/media/mediaInfoParser/KMediaFileComplexity.php on line 282
PHP Notice: Trying to get property of non-object in /opt/kaltura/app/infra/media/mediaInfoParser/KMediaFileComplexity.php on line 282
PHP Notice: Trying to get property of non-object in /opt/kaltura/app/infra/media/mediaInfoParser/KMediaFileComplexity.php on line 282
PHP Notice: Trying to get property of non-object in /opt/kaltura/app/infra/media/mediaInfoParser/KMediaFileComplexity.php on line 282
PHP Notice: Trying to get property of non-object in /opt/kaltura/app/infra/media/mediaInfoParser/KMediaFileComplexity.php on line 282
PHP Notice: Trying to get property of non-object in /opt/kaltura/app/infra/media/mediaInfoParser/KMediaFileComplexity.php on line 282
PHP Notice: Trying to get property of non-object in /opt/kaltura/app/infra/media/mediaInfoParser/KMediaFileComplexity.php on line 282
PHP Warning: Division by zero in /opt/kaltura/app/infra/media/mediaInfoParser/KMediaFileComplexity.php on line 282
In order to understand why you’re getting a fatal error in /opt/kaltura/log/batch/bulkuploadcloser-0-2017-08-13.err.log, you need to open that log file and look at the lines leading to the final error but… do you even use dropfolders? if not, then it’s not that critical to debug.
As for the notices in /opt/kaltura/log/batch/extractmedia-0-2017-08-14.err.log, same thing. Need to open the log file and locate the root cause.
However, is the batch daemon now up and running? are you able to transcode new videos successfully? are there any other apparent issues at the moment?
Yesterday I did upgrade from Kaltura 13.0.0 to the newest release 13.13.0
This time mostly everything went through fine.
I’ve still have a question.
According to the “kaltlog” output I got the following error:
==> /opt/kaltura/log/batch/extractmedia-0-2018-02-20.err.log <==
PHP Warning: Division by zero in /opt/kaltura/app/infra/media/mediaInfoParser/KMediaFileComplexity.php on line 281
PHP Notice: Trying to get property of non-object in /opt/kaltura/app/infra/media/mediaInfoParser/KMediaFileComplexity.php on line 282
PHP Notice: Trying to get property of non-object in /opt/kaltura/app/infra/media/mediaInfoParser/KMediaFileComplexity.php on line 282
PHP Notice: Trying to get property of non-object in /opt/kaltura/app/infra/media/mediaInfoParser/KMediaFileComplexity.php on line 282
PHP Notice: Trying to get property of non-object in /opt/kaltura/app/infra/media/mediaInfoParser/KMediaFileComplexity.php on line 282
PHP Notice: Trying to get property of non-object in /opt/kaltura/app/infra/media/mediaInfoParser/KMediaFileComplexity.php on line 282
PHP Notice: Trying to get property of non-object in /opt/kaltura/app/infra/media/mediaInfoParser/KMediaFileComplexity.php on line 282
PHP Notice: Trying to get property of non-object in /opt/kaltura/app/infra/media/mediaInfoParser/KMediaFileComplexity.php on line 282
PHP Notice: Trying to get property of non-object in /opt/kaltura/app/infra/media/mediaInfoParser/KMediaFileComplexity.php on line 282
PHP Warning: Division by zero in /opt/kaltura/app/infra/media/mediaInfoParser/KMediaFileComplexity.php on line 282
What does this Division by zero error mean?
I’m also interessted to setup kmc-ng. In which release of Kaltura CE is it planed to implent it instead of a Flash based KMC?
Sorry for the delayed response.
The issues you posted above were due to a missing directive in /opt/kaltura/app/configurations/batch/batch.ini.
I’ve just fixed this and it will be included in the next release [13.16.0].
However, you can already manually patch the config file, simply add:
params.ffmpegCmd = /opt/kaltura/bin/ffmpeg
Right after:
209 [KAsyncExtractMedia : JobHandlerWorker]
210 id = 60
211 friendlyName = Extract Media
212 type = KAsyncExtractMedia
213 scriptPath = batches/ExtractMedia/KAsyncExtractMediaExe.php
214 params.mediaInfoCmd=/opt/kaltura/bin/mediainfo
215 params.ffprobeCmd = /opt/kaltura/bin/ffprobe
in /opt/kaltura/app/configurations/batch/batch.ini
No need to restart the kaltura-batch daemon after doing so.
In regards to KMCng, no ETA yet I’m afraid. That said, you’re welcome to manually deploy it and start testing.
See the repo’s README for instructions and in particular: