Kaltura mails and Red5 integration failing

Community Forums
1

Hi

I have installed Kaltura on CentOS.
I would like to get the following done:

  1. Change the mail id from which mails are being sent upon occasions like user registrations,password reset.
    How do I change the "From mail id so that my SMTP relay server can accept and forward these messages.
  2. I am unable to Configure Red5 server as in documentation. When I try to install the Ready made application, it fails with “Net status: NetConnection.Connect.Failed
    Trying to connect to war location”.

Appreciate any help in these two issues.

Thanks

2

Hi @bindurajesh,

RE #1: the relevant directives are in /opt/kaltura/app/configurations/local.ini:

default_email = customer_service@jessex
default_email_name = "Kaltura Video Platform" Automated Response
partner_registration_confirmation_email = registration_confirmation@jessex
partner_notification_email = customer_service@jessex
partner_change_email_email = customer_service@jessex
partner_change_email_name = "Kaltura Video Platform" Automated Response
purchase_package_email = customer_service@jessex
batch_download_video_sender_email = download_video@jessex
batch_flatten_video_sender_email = download_video@jessex
batch_notification_sender_email = notifications@jessex  
batch_alert_email = alert@jessex  
bulk_notification_sender_email = notifications@jessex  
live_report_sender_email = live_report@jessex

More info about on how the mail sending mechanism works can be found here:

RE #2: see my reply here: Error in installing kaltura-red5

Thanks,

3

Hi Jess

Thank you for the response and information on red5. Now, it is clear why red5 is not getting setup.This information has really helped me so much as I thought I was stuck with the part “**Configure red5 server” which I got referred from http://kaltura-install-packages.readthedocs.io/en/latest/install-kaltura-redhat-based/

I will check the solution what you have given for mailing and update the status.I believe I need to restart all the services once I modify the local.ini file.

Thanks again for the timely response.

Bindu

4

Hi @bindurajesh,

First of all - most welcome.
As for the documentation, always best to refer to https://github.com/kaltura/platform-install-packages/#documentation-and-guides

After changing the mail settings in local.ini, an Apache reload should suffice for them to take effect.

5

Hi Jess

Thanks for your mail. I still have an issue with the mails not getting received from the Kaltura server.
It is still using the mail ids like notifications@kaltura.com. Not sure how to change it.

I am facing another problem. I get internal error whenever I login to Management Console
However, I am able to login and see the various tabs and see the contents.

Can you please guide which log files to be checked.

Thanks

6

Hi @bindurajesh,

In relation to the FROM header, please post the values set for the directives I mentioned above in local.ini. In the event of a clustered ENV, of course make sure you updated the file on all relevant nodes and also that you have reloaded Apache after doing so.

As for your other issue, this is most likely related to a problem in communicating with the DWH MySQL DBs.
To know for sure, start by running:
# source /etc/profile.d/kaltura_bash.sh
# kaltlog
From a root shell on the server and then make a request for KMC’s index page.
This will output errors to STDOUT and you’ll be able to better understand what fails.
If you see something like:

2015-06-24 15:45:35 [0.001585] [::1] [991771667] [API] [KalturaFrontController->errorHandler] WARN: /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php line 1309 - mysqli_error() expects parameter 1 to be mysqli, boolean given
2015-06-24 15:45:35 [0.000160] [::1] [991771667] [API] [kCoreException->__construct] ERR: exception 'kCoreException' with message 'Can't use foo : ' in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1309

Then I am correct, in which case, refer to kCoreException in KMC
And for a general explanation about how DWH [Analytics] works see:
https://github.com/kaltura/platform-install-packages/blob/Lynx-12.20.0/doc/kaltura-packages-faq.md#analytics-issues

If it’s a different issue, please post the output of kaltlog here.

7

Hi Jess

I am getting the following message in kaltlog

Looks like different from the link what you have given.

Thanks

2017-07-06 14:20:32 [0.000319] [10.120.32.85] [1486446036] [48] [API] [KalturaFrontController->errorHandler] WARN: /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php line 1332 - mysqli_error() expects parameter 1 to be mysqli, boolean given
2017-07-06 14:20:32 [0.000256] [10.120.32.85] [1486446036] [49] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message 'Can’t use foo : ’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1332
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(884): myReportsMgr::executeQuery(‘SELECT COUNT(DI…’, false)

2017-07-06 14:20:32 [0.001484] [10.120.32.85] [1811617985] [11] [API] [KalturaStatement->execute] DEBUG: /* kaltura[1811617985][propel] */ SELECT invalid_session.ID, invalid_session.KS, invalid_session.KS_VALID_UNTIL, invalid_session.CREATED_AT, invalid_session.ACTIONS_LIMIT, invalid_session.TYPE FROM invalid_session WHERE (invalid_session.TYPE=‘0’ AND invalid_session.KS=‘caee669460d94470b128c4ffdda9c43e4d19bbf5’) LIMIT 1
2017-07-06 14:20:32 [0.006880] [10.120.32.85] [1486446036] [51] [API] [KalturaFrontController->getExceptionObject] CRIT: exception ‘kCoreException’ with message 'Can’t use foo : ’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1332
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(884): myReportsMgr::executeQuery(‘SELECT COUNT(DI…’, false)

2017-07-06 14:20:32 [0.000277] [10.120.32.85] [2120566107] [48] [API] [KalturaFrontController->errorHandler] WARN: /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php line 1332 - mysqli_error() expects parameter 1 to be mysqli, boolean given
2017-07-06 14:20:32 [0.000250] [10.120.32.85] [2120566107] [49] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message 'Can’t use foo : ’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1332
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(884): myReportsMgr::executeQuery(‘SELECT count(*)…’, false)

2017-07-06 14:20:32 [0.000461] [10.120.32.85] [2120566107] [50] [API] [myReportsMgr::executeQueryByType] NOTICE: Can’t use foo :
2017-07-06 14:20:32 [0.000365] [10.120.32.85] [2120566107] [51] [API] [KalturaFrontController->getExceptionObject] CRIT: exception ‘kCoreException’ with message 'Can’t use foo : ’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1332
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(884): myReportsMgr::executeQuery(‘SELECT count(*)…’, false)

2017-07-06 14:20:32 [0.000444] [10.120.32.85] [1811617985] [47] [API] [KalturaFrontController->errorHandler] WARN: /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php line 1332 - mysqli_error() expects parameter 1 to be mysqli, boolean given
2017-07-06 14:20:32 [0.000251] [10.120.32.85] [1811617985] [48] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message ‘Can’t use foo : ’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1332
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(884): myReportsMgr::executeQuery(’\nSELECT\n\tDATE(D…’, false)

2017-07-06 14:20:32 [0.000951] [10.120.32.85] [1818284523] [21] [API] [KalturaStatement->execute] DEBUG: /* kaltura[1818284523][propel] */ SELECT kuser_to_user_role.ID, kuser_to_user_role.KUSER_ID, kuser_to_user_role.USER_ROLE_ID, kuser_to_user_role.CREATED_AT, kuser_to_user_role.UPDATED_AT FROM kuser_to_user_role WHERE kuser_to_user_role.KUSER_ID=‘12’
2017-07-06 14:20:32 [0.000554] [10.120.32.85] [1811617985] [50] [API] [KalturaFrontController->getExceptionObject] CRIT: exception ‘kCoreException’ with message ‘Can’t use foo : ’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1332
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(884): myReportsMgr::executeQuery(’\nSELECT\n\tDATE(D…’, false)

2017-07-06 14:20:32 [0.000241] [10.120.32.85] [1818284523] [47] [API] [KalturaFrontController->errorHandler] WARN: /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php line 1332 - mysqli_error() expects parameter 1 to be mysqli, boolean given
2017-07-06 14:20:32 [0.000217] [10.120.32.85] [1818284523] [48] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message ‘Can’t use foo : ’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1332
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(884): myReportsMgr::executeQuery(’/* Plays | Uni…’, false)

2017-07-06 14:20:32 [0.000187] [10.120.32.85] [1818284523] [49] [API] [myReportsMgr::executeQueryByType] NOTICE: Can’t use foo :
2017-07-06 14:20:32 [0.000317] [10.120.32.85] [1818284523] [50] [API] [KalturaFrontController->getExceptionObject] CRIT: exception ‘kCoreException’ with message ‘Can’t use foo : ’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1332
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(884): myReportsMgr::executeQuery(’/* Plays | Uni…’, false)

2017-07-06 14:21:42 [0.000396] [::1] [2064340738] [66] [API] [KalturaObject->generateFromObjectClass] ALERT: exception ‘Exception’ with message ‘getter for property thumbHeight was not found on object kConvertProfileJobData’ in /opt/kaltura/app/infra/log/KalturaLog.php:65
Stack trace:
#0 /opt/kaltura/app/api_v3/lib/types/KalturaObject.php(153): KalturaLog::alert(‘getter for prop…’)

2017-07-06 14:21:42 [0.000341] [::1] [2064340738] [67] [API] [KalturaObject->generateFromObjectClass] ALERT: exception ‘Exception’ with message ‘getter for property thumbBitrate was not found on object kConvertProfileJobData’ in /opt/kaltura/app/infra/log/KalturaLog.php:65
Stack trace:
#0 /opt/kaltura/app/api_v3/lib/types/KalturaObject.php(153): KalturaLog::alert(‘getter for prop…’)
^C
[root@kaltura profile.d]# kaltlog
==> /opt/kaltura/log/kaltura_apache_errors.log <==
[Thu Jul 06 13:56:01 2017] [error] [client 10.120.32.85] File does not exist: /opt/kaltura/app/alpha/web/opt, referer: http://kaltura.sjri.res.in/admin_console/index.php/partner/list

–
2017-07-06 13:49:46 [221824578] [addPermissionsAndItems.php] [addItemToPermissions] ALERT: exception ‘Exception’ with message ‘ERROR - Permission name [] for partner [0] not found in database - skipping!’ in /opt/kaltura/app/infra/log/KalturaLog.php:65
Stack trace:
#0 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(284): KalturaLog::alert(‘ERROR - Permiss…’)

2017-07-06 14:27:15 [0.000275] [10.120.32.85] [1262547124] [48] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message ‘Can’t use foo : ’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1332
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(884): myReportsMgr::executeQuery(’/* Plays | Uni…’, false)

2017-07-06 14:27:15 [0.000229] [10.120.32.85] [1658617952] [48] [API] [KalturaFrontController->errorHandler] WARN: /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php line 1332 - mysqli_error() expects parameter 1 to be mysqli, boolean given
2017-07-06 14:27:15 [0.000532] [10.120.32.85] [1262547124] [50] [API] [KalturaFrontController->getExceptionObject] CRIT: exception ‘kCoreException’ with message ‘Can’t use foo : ’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1332
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(884): myReportsMgr::executeQuery(’/* Plays | Uni…’, false)

2017-07-06 14:27:15 [0.000151] [10.120.32.85] [1262547124] [54] [API] [global] DEBUG: <------------------------------------- api_v3 -------------------------------------
2017-07-06 14:27:15 [0.002521] [10.120.32.85] [1658617952] [49] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message 'Can’t use foo : ’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1332
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(884): myReportsMgr::executeQuery(‘SELECT COUNT(DI…’, false)

==> /opt/kaltura/log/kaltura_api_v3.log <==
2017-07-06 14:27:15 [0.000534] [10.120.32.85] [1658617952] [51] [API] [KalturaFrontController->getExceptionObject] CRIT: exception ‘kCoreException’ with message 'Can’t use foo : ’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1332
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(884): myReportsMgr::executeQuery(‘SELECT COUNT(DI…’, false)

2017-07-06 14:27:15 [0.000243] [10.120.32.85] [1303428214] [47] [API] [KalturaFrontController->errorHandler] WARN: /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php line 1332 - mysqli_error() expects parameter 1 to be mysqli, boolean given
2017-07-06 14:27:15 [0.000246] [10.120.32.85] [1303428214] [48] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message ‘Can’t use foo : ’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1332
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(884): myReportsMgr::executeQuery(’\nSELECT\n\tDATE(D…’, false)

2017-07-06 08:57:15 [0.000167] [10.120.32.85] [876762736] [33] [API] [KalturaFrontController->errorHandler] WARN: /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php line 1309 - mysqli_real_escape_string() expects parameter 1 to be mysqli, boolean given
2017-07-06 14:27:15 [0.000419] [10.120.32.85] [1303428214] [50] [API] [KalturaFrontController->getExceptionObject] CRIT: exception ‘kCoreException’ with message ‘Can’t use foo : ’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1332
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(884): myReportsMgr::executeQuery(’\nSELECT\n\tDATE(D…’, false)

2017-07-06 14:27:15 [0.000340] [10.120.32.85] [876762736] [48] [API] [KalturaFrontController->errorHandler] WARN: /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php line 1332 - mysqli_error() expects parameter 1 to be mysqli, boolean given
2017-07-06 14:27:15 [0.000254] [10.120.32.85] [876762736] [49] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message 'Can’t use foo : ’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1332
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(884): myReportsMgr::executeQuery(‘SELECT count(*)…’, false)

2017-07-06 14:27:15 [0.000193] [10.120.32.85] [876762736] [50] [API] [myReportsMgr::executeQueryByType] NOTICE: Can’t use foo :
2017-07-06 14:27:15 [0.000359] [10.120.32.85] [876762736] [51] [API] [KalturaFrontController->getExceptionObject] CRIT: exception ‘kCoreException’ with message 'Can’t use foo : ’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1332
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(884): myReportsMgr::executeQuery(‘SELECT count(*)…’, false)

8

Dashboard and Analytics links are only giving Internal server error. Rest of the tabs seem to be fine.
If I click on OK to the error, it goes and load the page.

9

Hi @bindurajesh,

It’s the same error… please see the links I referred you to.

10

Hi Jess

There was a correction for SQL host in db.ini and .kettler.properties related to DWH.
I changed these parameters. Still I am getting the internal error.
kaltlog gives me following error now.
While executing the config-all script, I had given my fully qualified hostname (which is the apache server name) for Media server details. Isn’t it that correct ?

[root@kaltura tmp]# kaltlog
==> /opt/kaltura/log/batch/clearcuepoints-0-2017-07-07.err.log <==
PHP Fatal error: Uncaught exception ‘KalturaException’ with message ‘Internal database error’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:894
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(4285): KalturaClientBase->throwExceptionIfError(Array)

==> /opt/kaltura/log/batch/validatelivemediaservers-0-2017-07-07.err.log <==
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘couldn’t connect to host’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:362
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(2315): KalturaClientBase->doQueue()

11

Hi @bindurajesh,

I am confused by your question:

Are you having other problems that do not relate to DWH? if not, I’m not sure why you’re doubting your choice in regards to the FQDN hostname you provided.

As for your DWH issue, after correcting the values in /opt/kaltura/dwh/.kettle/kettle.properties, specifically:

  78 # the DWH DB settinge
  79 DbHostName = localhost
  80 DbPort = 3306
  81 DbUser = etl
  82 DbPassword = 
  83 
  84 # the Read DWH connection
  85 DbReadHostName = localhost
  86 DbReadPort = 3306
  87 DbReadUser = etl
  88 DbReadPassword = 
  89 
  90 # the operational Db settings
  91 OpDbHostName = localhost
  92 OpDbPort = 3306
  93 OpDbUser = etl
  94 OpDbPassword = 
  95 
  96 # operational DB with write priviledge (for exporting plays/views)
  97 OpWritableDbHostName = localhost
  98 OpWritableDbPort = 3306
  99 OpWritableDbUser = etl
 100 OpWritableDbPassword =

and in /opt/kaltura/app/configurations/db.ini:

dwh.adapter = mysql
dwh.connection.classname = KalturaPDO
dwh.connection.phptype = mysql
dwh.connection.database = kalturadw
dwh.connection.hostspec = localhost
dwh.connection.port = 3306 
dwh.connection.user = kaltura
dwh.connection.password = 
dwh.connection.dsn = "mysql:host=localhost;port=3306;dbname=kalturadw;"

And reloading Apache, are you able to connect to the kalturadw DB using these credentials?
Note that you should not touch other MySQL DSN directives in this file, since, if I understood you correctly, the connection to the operational MySQL DB was fine and the only problem was with the DWH [Analytics].
If that is not so, please reiterate.

12

Hi Jess

Thanks a lot for the support.

Apparently, the problem was that etl user was unable to connect using the password in db.ini file.
I never suspected that because it is a default configuration. Got a reference to the problem after referring through the message you had given. Changed the password and now the internal database error is not appearing.

Thanks again.
Mail problem is still appearing. It is relaying to kaltura@localhost whereas my relay server is something different. I have configured the relayhost in/etc/postfix/main.cf. Still it gives problem.

Any hint will be really appreciated.

Thanks

13

Hi @bindurajesh,

Most welcome.
Configuring the MTA is beyond the scope of our support since it really isn’t specific to Kaltura.
That said, this thread:


includes a basic main.cf relay configuration which you can use as reference.
The sender’s addr, as I said, is controlled by the directives in local.ini.
In addition, PHP has a directive called sendmail_path. This can be set as following:

sendmail_path = "sendmail -t -i -F community@kaltura.com -f community@kaltura.com"

Setting this would mean that any PHP code run on this machine, unless specifying a different FROM header, will use community@kaltura.com as the sender’s addr. If you do use this, remember to also reload Apache.

14

Thanks Jess.

I will try this out.