Kaltura CE 13.0 Issue Creating New Players Studio

After completing the update to the recent version I am having issue with creating new players from scratch and duplicating existing players. If I duplicate the player from the KMC studio tab or via the admin console the player does not displays at all when I try to play back using the newly created player. If I create a new player from the KMC studio tab the new player only displays a black box when I try to playback with the new player. No, control buttons nor other options appear in any browser. I am not getting any errors in the web developers console of my browser.

After creating a new player I am getting the caption spinner when I attempt to edit the new player regardless if it is duplicated from any console or created from scratch from any console.

I am not seeing any errors in the ‘kaltlog’ when creating or attempting to edit the new players. After adding the custom UI configuration for iOS playback I got the caption error.

39 AM

Hi @hiphopservers,

My first guess would be permission issues preventing the UI conf JSON files from being written to the disk.
You should see that reflected in the logs but you can start by querying the kaltura.ui_conf table like so:
mysql> select * from ui_conf where id=$YOUR_PLAYER_ID;

Make sure that conf_file_path which is relative to /opt/kaltura/web/ exists and the dir is writeable by the apache user.

The caption command return the following error.

MariaDB [kaltura]> select * from ui_conf where id=$YOUR_PLAYER_ID;
ERROR 1054 (42S22): Unknown column '$YOUR_PLAYER_ID' in 'where clause'
MariaDB [kaltura]>

Hi @hiphopservers, I meant for you to replace $YOUR_PLAYER_ID with the actual ID you see in Studio/Admin Console.

@jess

What should the permission be for these folders? I am thinking owner and group should be reversed considering what your saying but I want to be sure before I swap ownership.

# ls -al /opt/kaltura/web/content/generatedUiConf
total 60
drwxrwx---. 15 kaltura kaltura 4096 Jul 24 23:48 .
drwxrwxr-x. 15 kaltura apache  4096 Jul 30 16:01 ..
drwxrwx---.  7 kaltura apache  4096 Jul 24 23:48 0
drwxrwx---. 19 kaltura apache  4096 Jul 24 23:48 1
drwxrwx---.  4 kaltura apache  4096 Jul 24 23:48 11
drwxrwx---.  6 kaltura apache  4096 Jul 24 23:48 14
drwxrwx---.  3 kaltura apache  4096 Jul 24 23:48 15
drwxrwx---.  6 kaltura apache  4096 Jul 24 23:48 2
drwxrwx---.  4 kaltura apache  4096 Jul 25 01:48 23
drwxrwx---.  8 kaltura apache  4096 Jul 24 23:48 4
drwxrwx---.  9 kaltura apache  4096 Jul 24 23:48 5
drwxrwx---.  7 kaltura apache  4096 Jul 24 23:48 6
drwxrwx---.  4 kaltura apache  4096 Jul 24 23:48 7
drwxrwx---.  6 kaltura apache  4096 Jul 24 23:48 8
drwxrwx---.  4 kaltura apache  4096 Jul 24 23:48 9

# ls -al /opt/kaltura/web/content/
total 60
drwxrwxr-x. 15 kaltura apache  4096 Jul 30 16:01 .
drwxrwxr-x.  9 root    root    4096 Jul 25 05:14 ..
drwxrwxr-x. 14 apache  kaltura 4096 Aug 10 12:08 batchfiles
drwxrwxr-x.  2 kaltura apache  4096 Jul 30 16:01 cacheswf
drwxr-xr-x. 11 kaltura apache  4096 Aug 10 12:02 clientlibs
drwxr-xr-x.  7 root    root    4096 Aug 10 12:08 docs
drwxrwxr-x.  5 apache  kaltura 4096 Jul 30 16:01 entry
drwxrwx---. 15 kaltura kaltura 4096 Jul 24 23:48 generatedUiConf
drwxrwx---.  3 kaltura apache  4096 Jul 24 23:48 metadata
drwxr-xr-x.  3 apache  kaltura 4096 Jul 25 01:53 notifications
drwxr-xr-x.  3 kaltura apache  4096 Jul 25 01:54 recorded
drwxrwxr-x.  4 kaltura apache  4096 Feb 11  2014 templates
drwxr-xr-x.  4 kaltura apache  4096 Jul 25 01:55 uiconf
drwxrwxr-x. 10 apache  kaltura 4096 Aug 10 12:08 uploads
drwxr-xr-x.  2 kaltura apache  4096 Jul 25 01:55 webcam

Hi @hiphopservers,

Since it should be 775 [for dirs] and 664 [for files], it doesn’t really matter whether it’s apache.kaltura or kaltura.apache as both user and group have write privileges with 775 and 664.

@jess

Is there a way you suggest to set all the permissions properly for all the files, directories and sub directory as required by the application and Apache? I tried to set them manually using wildcard options for setting folders and this appears to have resolved the issue. I was able to create new players without and issue.

Something like:

# chmod 775 /opt/kaltura/web/content/generatedUiConf/*
# chmod 775 /opt/kaltura/web/content/generatedUiConf/*/*/
# chmod 664 /opt/kaltura/web/content/generatedUiConf/*/*/*