Problems with KMC after upgrade


#1

Hi!
After upgrade Kaltura Server to 14.2, the login in KMC is working, but not open the panel, like this:

33

In the server, running commands:

rpm -q kaltura-base

kaltura-base-14.2.0-14.noarch

kaltlog

==> /opt/kaltura/log/kaltura_apache_errors.log <==
[Tue Jul 24 15:24:17 2018] [error] [client 177.8.160.34] PHP Notice: Undefined offset: 0 in /opt/kaltura/app/alpha/apps/kaltura/modules/kmc/templates/kmc1Success.php on line 927
[Tue Jul 24 15:24:17 2018] [error] [client 177.8.160.34] PHP Fatal error: Call to a member function getId() on a non-object in /opt/kaltura/app/alpha/apps/kaltura/modules/kmc/templates/kmc1Success.php on line 927
[Tue Jul 24 15:40:00 2018] [error] [client 177.8.160.34] PHP Notice: Undefined offset: 0 in /opt/kaltura/app/alpha/apps/kaltura/modules/kmc/templates/kmc1Success.php on line 927, referer: http://192.99.19.65/start/index.php
[Tue Jul 24 15:40:00 2018] [error] [client 177.8.160.34] PHP Fatal error: Call to a member function getId() on a non-object in /opt/kaltura/app/alpha/apps/kaltura/modules/kmc/templates/kmc1Success.php on line 927, referer: http://192.99.19.65/start/index.php
[Tue Jul 24 15:44:29 2018] [error] [client 177.8.160.34] PHP Notice: Undefined offset: 0 in /opt/kaltura/app/alpha/apps/kaltura/modules/kmc/templates/kmc1Success.php on line 927, referer: http://192.99.19.65/kmc
[Tue Jul 24 15:44:29 2018] [error] [client 177.8.160.34] PHP Fatal error: Call to a member function getId() on a non-object in /opt/kaltura/app/alpha/apps/kaltura/modules/kmc/templates/kmc1Success.php on line 927, referer: http://192.99.19.65/kmc
[Tue Jul 24 16:13:05 2018] [error] [client 177.8.160.34] PHP Notice: Undefined offset: 0 in /opt/kaltura/app/alpha/apps/kaltura/modules/kmc/templates/kmc1Success.php on line 927, referer: http://192.99.19.65/start/index.php
[Tue Jul 24 16:13:05 2018] [error] [client 177.8.160.34] PHP Fatal error: Call to a member function getId() on a non-object in /opt/kaltura/app/alpha/apps/kaltura/modules/kmc/templates/kmc1Success.php on line 927, referer: http://192.99.19.65/start/index.php
[Tue Jul 24 16:18:31 2018] [error] [client 177.8.160.34] PHP Notice: Undefined offset: 0 in /opt/kaltura/app/alpha/apps/kaltura/modules/kmc/templates/kmc1Success.php on line 927, referer: http://192.99.19.65/start/index.php
[Tue Jul 24 16:18:31 2018] [error] [client 177.8.160.34] PHP Fatal error: Call to a member function getId() on a non-object in /opt/kaltura/app/alpha/apps/kaltura/modules/kmc/templates/kmc1Success.php on line 927, referer: http://192.99.19.65/start/index.php


==> /opt/kaltura/log/batch/clearcuepoints-0-2018-07-24.err.log <==
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘couldn’t connect to host’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:362

Sanity test:

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

[Space on /opt/kaltura] [PASSED, RC: 0] - [.001867137]
[Space on /opt/kaltura/web] [PASSED, RC: 0] - [.001819800]

INFO: Downloading ready-made schema from: /opt/kaltura/web/content/clientlibs/KalturaClient.xml
INFO: Generating from api version: 14.2.0, generated at: 24-07-2018
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: set tests path /opt/kaltura/clients-generator/tests/ovp
INFO: Copy sources from [/opt/kaltura/clients-generator/sources/php5]
INFO: Copy tests from [/opt/kaltura/clients-generator/tests/ovp/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_24-07-2018.tar.gz” …/php5full
tar: Removing leading `…/’ from member names
INFO: Package created successfully: …/php5full_24-07-2018.tar.gz
DEBUG: Restoring dir to [/opt/kaltura/clients-generator]
INFO: php5full generated successfully
[Check httpd daemon status] [PASSED, RC: 0] - [.014869764]
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.273100470]
[check daemon httpd init status] [PASSED, RC: 0] - [.002806018]
[Check kaltura-sphinx daemon status] [PASSED, RC: 0] - [.016565704]
[Check kaltura-sphinx daemon is started by Monit] [PASSED, RC: 0] - [10.538672106]
[check daemon kaltura-sphinx init status] [PASSED, RC: 0] - [.002783301]
[Check kaltura-batch daemon status] [PASSED, RC: 0] - [.015659057]
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…
[Check kaltura-batch daemon is started by Monit] [PASSED, RC: 0] - [10.189359945]
[check daemon kaltura-batch init status] [PASSED, RC: 0] - [.002846474]
[Check kaltura-monit daemon status] [PASSED, RC: 0] - [.014770030]
[check daemon kaltura-monit init status] [PASSED, RC: 0] - [.002646792]
[Check memcached daemon status] [PASSED, RC: 0] - [.014513208]
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.281866597]
[check daemon memcached init status] [PASSED, RC: 0] - [.002759061]
[kaltura-html5lib ver in KMC config.ini] [PASSED, RC: 0] - [.043971222]
[kaltura-kdp3 ver in KDP3 config.ini] [PASSED, RC: 0] - [.025301156]
[kaltura-kmc ver in KMC config.ini] [PASSED, RC: 0] - [.028536020]
[Get KMC SWFs] [PASSED, RC: 0] - [.090320786]
[check_start_page] [PASSED, RC: 0] - [.007027780]
[check_testme_page] [PASSED, RC: 0] - [.006161462]
[check_kmc_index_page] [PASSED, RC: 0] - [.011101233]
[check_admin_console_index_page] [PASSED, RC: 0] - [.102699945]
[check_studio_index_page] [PASSED, RC: 0] - [.006689334]
[check_clipapp_index_page] [PASSED, RC: 0] - [.245931979]
[Create Partner] [PASSED, RC: 0] - [2.414735987]
[Local dropfolder creation] [PASSED, RC: 0] - [.261614037]
[Create flavor param] [PASSED, RC: 0] - [.456550423]
[Delete flavor param] [PASSED, RC: 0] - [.107729371]
[HTTP notification: ID: 36, URL: http://localhost/1.php] [PASSED, RC: 0] - [.456550423]
] [PASSED, RC: 0] - [.456550423]ect: Your video is ready to be played!, Mail body: Hello world:)
[Upload content kaltura_logo_animated_blue.flv] [PASSED, RC: 0] - [.520802226]
Napping 10 seconds to allow entry 0_mnutxox6 to digest…
Napping 10 seconds to allow entry 0_mnutxox6 to digest…
Napping 10 seconds to allow entry 0_mnutxox6 to digest…
Napping 10 seconds to allow entry 0_mnutxox6 to digest…
Napping 10 seconds to allow entry 0_mnutxox6 to digest…
Napping 10 seconds to allow entry 0_mnutxox6 to digest…
Napping 10 seconds to allow entry 0_mnutxox6 to digest…
Napping 10 seconds to allow entry 0_mnutxox6 to digest…
Napping 10 seconds to allow entry 0_mnutxox6 to digest…
[kaltura_logo_animated_blue.flv - 0_mnutxox6 status] [FAILED, RC: 1] - [-.229236367]
Napping 30 seconds to allow mail to be sent out…
[Found an email sending entry for mb-Artsystem@kaltura.com[PID is 116] in /var/log/maillog] [PASSED, RC: 0] - [30.003719801]
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] - [433.310651780]
[Upload content kaltura_logo_animated_green.flv] [PASSED, RC: 0] - [.661059688]
[Upload bulk using CSV] [PASSED, RC: 0] - [.284063082]
[Upload bulk using XML] [PASSED, RC: 0] - [.268943660]
[Create player] [PASSED, RC: 0] - [.165450067]
[Generate thumb] [PASSED, RC: 0] - [.237986262]
[Delete all entries] [PASSED, RC: 0] - [.279549915]
[Delete partner] [PASSED, RC: 0] - [.344387099]
[Red5 file upload] [SKIPPED as OflaDemo isn’t configured]
see: https://github.com/kaltura/platform-install-packages/blob/master/doc/install-kaltura-redhat-based.md#configure-red5-server

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.

Any idea??


#2

Hi @claudinei_senger,

Did you run the kaltura-config.*.sh scripts after upgrading the RPMs?
If you have not, please do, if you have, please run them again and post the full output here.

Thanks,


#3

I running again to export the output for you. Is there another file or only Kaltura-config-all.sh?

kaltura-config-all.sh

Running base config…

kaltura-base-14.2.0-14.noarch

Welcome to Kaltura Server 14.2.0 post install setup.

In order to finalize the system configuration, please input the following:

CDN hostname [Artsystem]:

The host will be accessed over http(s). In case your CDN operates on a non-default port, please input CDNHOST:PORT.
192.99.19.65
Apache virtual hostname [Artsystem]
(Must be accessible from both inside the machine and from any clients / browsers that will use Kaltura):

192.99.19.65
Vhost port to listen on [80]:
range of ip addresses belonging to internal kaltura servers [0.0.0.0-255.255.255.255]:
The range is used when checking service actions permissions and allowing to access certain services without KS from the internal servers.
The default is only good for testing, on a production ENV you should adjust according to your network.

DB port [3306]:
MySQL super user [only for install, default root]:
Analytics DB hostname [127.0.0.1]:
Analytics DB port [3306]:
Sphinx hostname [127.0.0.1]:
Media Streaming Server secondary host [Artsystem]: 192.99.19.65
Secondary Sphinx hostname [leave empty if none]:
Your Kaltura Service URL [http://192.99.19.65]
(Base URL where the Kaltura API and Apps will be accessed from - this would be your Load Balancer URL on a cluster or same as your virtual host in an all-in-one Kaltura server - Must be accessible from both inside the machine and from any clients / browsers that will use Kaltura):

http://192.99.19.65
VOD packager hostname [Artsystem]: 192.99.19.65
VOD packager port to listen on [88]:
Admin user login password (must be minimum 8 chars and include at least one of each: upper-case, lower-case, number and a special character):
Confirm passwd:
Your time zone [see http://php.net/date.timezone], or press enter for [America/Toronto]: America/Sao_Paulo
Your Kaltura install name (this name will show as the From field in emails sent by the system) [Kaltura Video Platform]:
Your website Contact Us URL [http://corp.kaltura.com/company/contact-us]:
Your ‘Contact us’ phone number [+1 800 871 5224]:
Checking MySQL version…
Ver 5.1.73 found compatible

========================================================================================================================
Kaltura install answer file written to /tmp/kaltura_25_07_11_49.ans - Please save it!
This answers file can be used to silently-install re-install this machine or deploy other hosts in your cluster.

Configuration of 14.2.0 finished successfully!

Running FrontEnd config…

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

kaltura-front-14.2.0-1.noarch

Which port will this Vhost listen on? [80]

Please select one of the following options [0]:
0. All web interfaces

  1. Kaltura Management Console [KMC], Hosted Apps, HTML5 lib and ClipApp
  2. KAC - Kaltura Admin Console
    0
    Enabling Apache config - apps.conf
    Enabling Apache config - var.conf
    Enabling Apache config - admin.conf

========================================================================================================================
Kaltura install answer file written to /tmp/kaltura_25_07_11_49.ans - Please save it!
This answers file can be used to silently-install re-install this machine or deploy other hosts in your cluster.

Stopping httpd: [ OK ]
Starting httpd: [Wed Jul 25 11:49:50 2018] [warn] The Alias directive in /opt/kaltura/app/configurations/apache/conf.d/enabled.apps.conf at line 38 will probably never match because it overlaps an earlier Alias.
httpd: Could not reliably determine the server’s fully qualified domain name, using 192.99.19.65 for ServerName
[ OK ]
Stopping memcached: [ OK ]
Starting memcached: [ OK ]
Shutting down monit: [ OK ]
Starting monit: Starting Monit 5.23.0 daemon with http interface at [127.0.0.1]:2812
[ OK ]

Running Sphinx config…

kaltura-sphinx-2.2.1-23.x86_64
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

Starting monit: Starting Monit 5.23.0 daemon with http interface at [127.0.0.1]:2812
[ OK ]

Running Batch config…

kaltura-batch-14.2.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-1.x86_64
Kaltura API host and port (without the protocol) [Artsystem:80]:
192.99.19.65:80
Nginx server name [Artsystem]:
192.99.19.65
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

The Kaltura DWH DB seems to already be installed.
DB creation will be skipped.
DWH configured.

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

Setup completed successfully!

To access your Kaltura tools visit:
http://192.99.19.65

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.


#4

Hi @claudinei_senger,

Nothing wrong with the output you posted.
Are you sure you’re not trying to log in to KMC with the Admin Console credentials instead of with those of your partner[s]?

You can see a full listing of your partners [and reset the passwds if need be] by going to Admin Console->Publishers. From the “Actions” select box, you can also choose the “Manage” option [or “Manage - new” if you’d like to use the HTML5 KMC] which will automatically log that partner into KMC without you having to provide its password.


#5

Hi @jess,

I excluded partner[s] and recreated, and now the access its ok. I can choose the “Manage” option [or ‘Manage - new’] in the Kaltura Admin Console, I really did not know the html5 version, it is fantastic, much faster than the flash version.

Tks for you attention!!!


#6

Most welcome, @claudinei_senger.
Glad to hear we’re good:)