TAC
September 15, 2015, 3:49am
1
I had a very similar base-level problem in repeated installs to what was reported in the Nothing In Top Content Analytics thread. It was immediately apparent because two lines in /etc/cron.d/kaltura-dwh failed every hour and sent me mail about it:
Cron kaltura@kalturafloor /opt/kaltura/dwh -k /opt/kaltura/pentaho/pdi/kitchen.sh/etlsource/execute/etl_hourly.sh -p /opt/kaltura/dwh -k /opt/kaltura/pentaho/pdi/kitchen.sh -k @KETTLE_SH @
-------------and----------------
Cron kaltura@kalturafloor /opt/kaltura/dwh -k /opt/kaltura/pentaho/pdi/kitchen.sh/etlsource/execute/etl_update_dims.sh -p /opt/kaltura/dwh -k /opt/kaltura/pentaho/pdi/kitchen.sh -k @KETTLE_SH @
This post referred to at the bottom of this one pointed me to how to fix it, which I did by hand. At least the hourly cron executes are no longer failing.
Since I’m not sharp enough yet with Kaltura, I don’t know which module sets these up to enable me to find the install script and figure out why it is installing this way,. My mangled crontab entries weren’t exactly like jule’s but were quite similar.
I’m guessing I’m not the only one with this problem so figured I’d document it as its own issue.
Continuing the discussion from Nothing in Top Content Analytics :
Hi Jess,
I was find an error in /etc/cron.d:
[root@kaltest2 cron]# cat dwh
00 * * * * kaltura /opt/kaltura/dwh -k /opt/kaltura/pentaho/pdi/kitchen.sh/etlsource/execute/etl_hourly.sh -p /opt/kaltura/dwh -k /opt/kaltura/pentaho/pdi/kitchen.sh
00 * * * * kaltura /opt/kaltura/dwh -k /opt/kaltura/pentaho/pdi/kitchen.sh/etlsource/execute/etl_update_dims.sh -p /opt/kaltura/dwh -k /opt/kaltura/pentaho/pdi/kitchen.sh
59 0,4,8,12,16,20 * * * kaltura /opt/kaltura/dwh -k /opt/kaltura/pentaho/pdi/kitchen.sh/etlsource/execute/etl_daily.sh -p /opt/kaltura/dwh -k /opt/kaltura/pentaho/pdi/kitchen.sh
30 12 * * * kaltura /opt/kaltura/dwh -k /opt/kaltura/pentaho/pdi/kitchen.sh/etlsource/execute/etl_perform_retention_policy.sh -p /opt/kaltura/dwh -k /opt/kaltura/pentaho/pdi/kitchen.sh
0 10 * * * kaltura /opt/kaltura/app/alpha/scripts/dwh/dwh_plays_views_sync.sh >> /opt/kaltura/log/cron.log
I correct based on /opt/kaltura/app/configurations/cron/dwh.template
[root@kaltest2 cron.d]# cat kaltura-dwh
00 * * * * kaltura /opt/kaltura/dwh/etlsource/execute/etl_hourly.sh -p /opt/kaltura/dwh -k /opt/kaltura/pentaho/pdi/kitchen.sh
00 * * * * kaltura /opt/kaltura/dwh/etlsource/execute/etl_update_dims.sh -p /opt/kaltura/dwh -k /opt/kaltura/pentaho/pdi/kitchen.sh
59 0,4,8,12,16,20 * * * kaltura /opt/kaltura/dwh/etlsource/execute/etl_daily.sh -p /opt/kaltura/dwh -k /opt/kaltura/pentaho/pdi/kitchen.sh
30 12 * * * kaltura /opt/kaltura/dwh/etlsource/execute/etl_perform_retention_policy.sh -p /opt/kaltura/dwh -k /opt/kaltura/pentaho/pdi/kitchen.sh
0 10 * * * kaltura /opt/kaltura/app/alpha/scripts/dwh/dwh_plays_views_sync.sh >> /opt/kaltura/log/cron.log
It’s not correct the problem but etl was not working alone. There is an issue if you reinstall or reconfigure kaltura
jess
September 15, 2015, 8:58am
2
Hello,
The @KETTLE_SH @ is replaced as part of the kaltura-base.postinst.
If it does and there are still issues, please look at:
# 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.
show original
and lets see what the exact problem is.