Kaltura 11.14 to 11.16 PHP Notice: Use of undefined constant DEBUG_BACKTRACE_IGNORE_ARGS

angober · June 20, 2016, 12:06pm

I upgraded kaltura 11.14 to 11.16 and when I executed kaltlog I see a repetitive PHP Notice every few seconds and isn´t see others problems:

PHP Notice: Use of undefined constant DEBUG_BACKTRACE_IGNORE_ARGS - assumed ‘DEBUG_BACKTRACE_IGNORE_ARGS’ in /srv_apl/kaltura/app/infra/log/KalturaLog.php on line 192

jess · June 20, 2016, 2:32pm

Hello,

This is a known issue that is fixed here:

You can just merge the fix to your current version, it will be included in the 11.17.0 release which is due tomorrow.

Thanks,

angober · June 21, 2016, 7:01am

Ok, thanks…

jess · June 26, 2016, 2:01pm

Hi,

11.17.0 is now the latest stable, please upgrade and it should be resolved, along with some additional issues.

Thanks,

angober · June 27, 2016, 1:18pm

Hi,
I upgraded kaltura 11.17 and also I’ve changed ip server and I found the problem that in BBDD all Views and Stored Procedures and Funtions of databases with root user, doesn´t change a new ip

jess · June 28, 2016, 12:38pm

Hi,

When changing the SERVICE_URL or CDN_HOST, you should follow:

github.com

kaltura/platform-install-packages/blob/Kajam-11.18.0/doc/kaltura-packages-faq.md#changing-apache-configurations-post-install

# Frequently Asked Questions

### Before You Get Started Notes
* If you see a `#` at the beginning of a line, this line should be run as `root`.

### Commercial Editions and Paid Support

The Open Source Kaltura Platform is provided under the [AGPLv3 license](http://www.gnu.org/licenses/agpl-3.0.html) and with no commercial support or liability.  

[Kaltura Inc.](http://corp.kaltura.com) also provides commercial solutions and services including pro-active platform monitoring, applications, SLA, 24/7 support and professional services. If you're looking for a commercially supported video platform  with integrations to commercial encoders, streaming servers, eCDN, DRM and more - Start a [Free Trial of the Kaltura.com Hosted Platform](http://corp.kaltura.com/free-trial) or learn more about [Kaltura' Commercial OnPrem Edition™](http://corp.kaltura.com/Deployment-Options/Kaltura-On-Prem-Edition). For existing RPM based users, Kaltura offers commercial upgrade options.

### How to contribute
We value contributions from our CE user base very much. To make a contribution, follow the [See our CONTRIBUTERS doc](https://github.com/kaltura/platform-install-packages/blob/IX-9.19.0/doc/CONTRIBUTERS.md).


### Changing Apache configurations post install.

Sometimes, you may want to change deployment settings post installation, for example: replacing the domain, port or protocol, or changing the system to use SSL or stop using SSL.   
You can run `/opt/kaltura/bin/kaltura-front-config.sh` as many times as you'd like with different values. The script will re-configure the system accordingly.   
For instance, you may want to change the service URL, port or protocol.

This file has been truncated. show original

Which will change it in the relevant conf files under /opt/kaltura/app/configuration, you then only need to update the delivery_profile table as explained in this doc.

If you’ve done both and are still having issues, please detail exactly what you’re seeing and I’ll gladly assist.

angober · June 28, 2016, 1:33pm

In my case, I have one server with kaltura and other with MySQL. I doesn´t changes hostnames. The names of hostnames is equal. I only change the ip of servers and when I reconfigure all kaltura (kaltura-config-all.sh *.ans) I saw in MySQL that all Views and Stored Procedures and Funtions of databases with root user, doesn´t change a new ip.