Hi Mathieu,
Not sure I understand the current state of the file:)
Only line I think should be changed is 298. What that done?
Thanks,
Hi Jess,
Only the line 298 has been changed.
I have the same error:
Format.parseObject(String) failed (script#30)
It was only a proposition for the second. 
Mathieu
Hm… interesting issue indeed:)
What do you have set for DataTimeZone in /opt/kaltura/dwh/.kettle/kettle.properties?
Hi Jess,
Sorry for my response in late …
In keetle.properties I’ve this
DataTimeZone = @TIME_ZONE@
I don’t find where the TIME_ZONE is defined …
For information : /etc/timezone on my Ubuntu : Europe/Paris
Thanks
Mathieu
Hi Mathieu,
This is obviously one problem:)
You need to edit it and have it read:
DataTimeZone = ‘Europe/Paris’
I would recommend rerunning:
# dpkg-reconfigure kaltura-base
# dpkg-reconfigure kaltura-front
# dpkg-reconfigure kaltura-batch
as the ‘@.*@’ placeholders are replaced during the postinst scripts
I am suggesting this because if the @TIME_ZONE@ token was not replaced, it is quite possible others were not as well.
Hi Jess,
So I replace the good time zone on kettle.properties for my configuration:
DataTimeZone = 'Europe/Paris'
I do a dpk-reconfigure of the three package:base;front and batch
root@kaltest:/opt/kaltura/dwh/logs# grep -R ERROR
Give me this now
etl_hourly-20150825-15.log:ERROR 25-08 15:44:01,733 - parse bandwidth lines - Unexpected error
etl_hourly-20150825-15.log:ERROR 25-08 15:44:01,734 - parse bandwidth lines - org.pentaho.di.core.exception.KettleValueException:
etl_hourly-20150825-15.log:ERROR 25-08 15:44:01,735 - process file - Errors detected!
etl_hourly-20150825-15.log:ERROR 25-08 15:44:01,735 - process file - Errors detected!
For information, it’s not better on display analytics.
Thanks for your help
Mathieu
I have this one too:
etl_perform_retention_policy-20150825.log:ERROR 25-08 15:57:57,234 - Lock is already seized - Row nr 1 causing abort : [retention_lock], [1], [0], [null]
etl_perform_retention_policy-20150825.log:ERROR 25-08 15:57:57,234 - Lock is already seized - Aborting after having seen 1 rows.
etl_perform_retention_policy-20150825.log:ERROR 25-08 15:57:57,235 - seize_lock_by_name - Errors detected!
etl_perform_retention_policy-20150825.log:ERROR 25-08 15:57:57,235 - seize_lock_by_name - Errors detected!
with
mysql> select * from kalturadw_ds.locks;
+---------+------------------+---------------------+------------+
| lock_id | lock_name | lock_time | lock_state |
+---------+------------------+---------------------+------------+
| 1 | daily_lock | 2015-08-25 16:03:28 | 0 |
| 2 | retention_lock | 2015-08-13 11:26:21 | 1 |
| 3 | hourly_kaltest | 2015-08-25 16:03:15 | 0 |
| 4 | update_dims_lock | 2015-08-25 16:03:22 | 0 |
+---------+------------------+---------------------+------------+
I put the lock state to 0 and run the cron.
etl_perform_retention_policy-20150825.log:ERROR 25-08 16:21:12,578 - Move old partitions to archive - An error occurred executing this job entry :
etl_perform_retention_policy-20150825.log:ERROR 25-08 16:21:12,593 - Kitchen - Finished with errors
The lock state is again put on 1 on retention lock.
It displays nothing more.
Hi Mathieu,
Please check the log and paste the errors around that line so its easier to understand the problem.
Hello Mathieu, I read your problem and I’ve found your problem.
“Couldn’t execute SQL: call register_file(‘kaltest-kaltura_apache_access.log-20150722-06’, 1, 328,9, ‘gz’, ‘’)”
The parameter “328,9” is the size of apache log file in kbytes. I’m from Spain and my language server is LANG=es_ES.UTF-8 (Spanish) and I imagine in your server was French.
If you change the language to English (LANG=en_US.UTF-8) your problem is solved because the size of apache log file was “328.9” and you had 5 parameters and not 6 parameters.
i like it sir … goodjob.