Batch Server failed conversion after update to 13.0

Community Forums Backend Server Support
1

After the upgrade to 13.0 my Batchservers fail to convert entries
the kaltlog of the batchserver is :

--
==> /opt/kaltura/log/batch/convert-0-2017-08-15.err.log <==
PHP Warning:  file_put_contents(/opt/kaltura/tmp/convert/convert_0_6c80rlql_8bd5c.log): failed to open stream: Permission denied in /opt/kaltura/app/batch/batches/Conve on line 254

--
==> /opt/kaltura/log/batch/convert-0-2017-08-15.err.log <==
PHP Warning:  file_put_contents(/opt/kaltura/tmp/convert/convert_0_6c80rlql_8bd5c.log): failed to open stream: Permission denied in /opt/kaltura/app/batch/batches/Conve on line 254

--
==> /opt/kaltura/log/batch/convert-0-2017-08-15.err.log <==
PHP Warning:  file_put_contents(/opt/kaltura/tmp/convert/convert_0_6c80rlql_8bd5c.log): failed to open stream: Permission denied in /opt/kaltura/app/batch/batches/Conve on line 254

--
==> /opt/kaltura/log/batch/convert-0-2017-08-15.err.log <==
PHP Warning:  file_put_contents(/opt/kaltura/tmp/convert/convert_0_6c80rlql_8bd5c.log): failed to open stream: Permission denied in /opt/kaltura/app/batch/batches/Conve on line 254
PHP Warning:  file_get_contents(/opt/kaltura/tmp/convert/convert_0_6c80rlql_8bd5c.log): failed to open stream: No such file or directory in /opt/kaltura/app/batch/batchlass.php on line 105

==> /opt/kaltura/log/batch/convert-0-2017-08-15.log <==
2017-08-15 15:25:28 [0.000323] [1801714421] [39] [BATCH] [KJobHandlerWorker->closeJob] ERR: exception 'Exception' with message 'engine [KOperationEngineOldVersionWrappe' in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/batch/batches/KJobHandlerWorker.class.php(364): KalturaLog::err('engine [KOperat...')
--
==> /opt/kaltura/log/batch/convert-0-2017-08-15.err.log <==
PHP Warning:  file_put_contents(/opt/kaltura/tmp/convert/convert_0_6c80rlql_83ee1.log): failed to open stream: Permission denied in /opt/kaltura/app/batch/batches/Conve on line 254

--
==> /opt/kaltura/log/batch/convert-0-2017-08-15.err.log <==
PHP Warning:  file_put_contents(/opt/kaltura/tmp/convert/convert_0_6c80rlql_83ee1.log): failed to open stream: Permission denied in /opt/kaltura/app/batch/batches/Conve on line 254

--
==> /opt/kaltura/log/batch/convert-0-2017-08-15.err.log <==
PHP Warning:  file_put_contents(/opt/kaltura/tmp/convert/convert_0_6c80rlql_83ee1.log): failed to open stream: Permission denied in /opt/kaltura/app/batch/batches/Conve on line 254

--
==> /opt/kaltura/log/batch/convert-0-2017-08-15.err.log <==
PHP Warning:  file_put_contents(/opt/kaltura/tmp/convert/convert_0_6c80rlql_83ee1.log): failed to open stream: Permission denied in /opt/kaltura/app/batch/batches/Conve on line 254
PHP Warning:  file_get_contents(/opt/kaltura/tmp/convert/convert_0_6c80rlql_83ee1.log): failed to open stream: No such file or directory in /opt/kaltura/app/batch/batchlass.php on line 105

==> /opt/kaltura/log/batch/convert-0-2017-08-15.log <==
2017-08-15 15:25:30 [0.000315] [182331397] [38] [BATCH] [KJobHandlerWorker->closeJob] ERR: exception 'Exception' with message 'engine [KOperationEngineOldVersionWrapper]' in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/batch/batches/KJobHandlerWorker.class.php(364): KalturaLog::err('engine [KOperat...')

I cannot figure out wich permission is missing www-data and kaltura have got permissions on these directories.

Kind Regards
Roger Barras

2

Hi Roger,

What’s the output for:
# ls -ald /opt/kaltura/tmp/*
?

3

Hello I had the same problem converting after upgrading,

I solved it by:

yum reinstall “kaltura” do a backup before.

hope this helps

Bryan

4

the output is:

drwxr-xr-x 2 www-data kaltura 4096 Aug 11 05:43 /opt/kaltura/tmp/convert
drwxr-xr-x 2 www-data kaltura 4096 Aug 11 05:43 /opt/kaltura/tmp/thumb
5

Hi @roger78,

Run:
# find /opt/kaltura/tmp -type d -exec chmod 775 {} ;
The user and group are correct but group [‘kaltura’] does not have write permissions, which is wrong.

6

Thank you, this change solved the issue.

I just wondering, why these permissions are beeing set wrong during the setup. ( I had the same issue on my 2nd Batch Server)

Is currently somethig broken in the debian Repository?
I try to install another server and I got the following error, when I try to intall kaltura-base:

Err http://installrepo.kaltura.org/repo/apt/debian/ mercury/main kaltura-base all 13.0.0-2
  404  Not Found [IP: 54.192.93.39 80]
0% [Working]E: Failed to fetch http://installrepo.kaltura.org/repo/apt/debian/pool/main/k/kaltura-base/kaltura-base_13.0.0-2_all.deb: 404  Not Found [IP: 54.192.93.39 80]

Greetings

7

Hi @roger78,

http://installrepo.kaltura.org is a CDN endpoint. It’s possible the edge you are hitting is not fully up to date, you can edit /etc/apt/sources.list.d/kaltura.list and change ‘http://installrepo.kaltura.org’ to read ‘http://installrepo.origin.kaltura.org’. Then make sure aptitude update passes with no errors or warnings.

Let me know if that fixes it for you.

8

Thank you it works. but I dont get the desired version.

Is it right that I could not load the version 13.0.0-2 from any repository?

9

Hi @roger78,

http://installrepo.origin.kaltura.org/repo/apt/debian currently points to http://installrepo.origin.kaltura.org/repo/apt/debian-13.1.0/ which is the latest stable.

If you want 13.0.0, you can use:

deb [arch=amd64] http://installrepo.origin.kaltura.org/repo/apt/debian-13.0.0 mercury main

or, if using Ubuntu 16.{4,10}:

deb [arch=amd64] http://installrepo.origin.kaltura.org/repo/apt/xenial-13.0.0 mercury main
10

Thank you nice to know :slight_smile:

11

Surething:)

Just to explain the release scheme: we release a new stable version every other week. New versions are announced here:

The stable repos are always:
http://installrepo.origin.kaltura.org/repo/apt/debian
Which is compatible with Ubuntu 14 and Debian Wheezy and Jessie

and http://installrepo.origin.kaltura.org/repo/apt/xenial
For Ubuntu Xenial [16].

the dist/codename changes every once in a while… right now it’s ‘mercury’.

However, we always keep the repos with the older versions and so, debian-$VERSION $CODENAME is always available.

1 Like