In the hourly logs of the analytics I keep see "ERROR cant seize lock"
In the locks table I see only 2 records, daily & retention.
I think there should be more loc records, what do I do next?
In the hourly logs of the analytics I keep see "ERROR cant seize lock"
In the locks table I see only 2 records, daily & retention.
I think there should be more loc records, what do I do next?
Hi Ofer,
Typically should have:
| 1 | daily_lock | 2014-12-08 20:59:10 | 1 |
| 2 | retention_lock | 2014-12-20 12:31:14 | 0 |
| 3 | hourly_hostname | 2014-12-19 21:00:24 | 1 |
| 4 | update_dims_lock | 2014-12-08 20:00:30 | 0 |
Try to set lock_state to 0 for all and rerun all jobs under /etc/cron.d/kaltura-dwh
then look for errors in /opt/kaltura/dwh/logs
Hi Jess,
Even after creating the locks records (manually) I keep getting this errors in the log file:
ERROR 08-03 10:00:15,502 - Lock is already seized - Row nr 1 causing abort : [ip-172-31-0-138], [hourly_], [hourly_ip-172-31-0-138], [1], [0], [null]
ERROR 08-03 10:00:15,502 - Lock is already seized - Aborting after having seen 1 rows.
INFO 08-03 10:00:15,502 - Lock is already seized - Finished processing (I=0, O=0, R=1, W=1, U=0, E=1)
INFO 08-03 10:00:15,503 - seize_lock_by_name - seize_lock_by_name
INFO 08-03 10:00:15,503 - seize_lock_by_name - seize_lock_by_name
ERROR 08-03 10:00:15,503 - seize_lock_by_name - Errors detected!
ERROR 08-03 10:00:15,503 - seize_lock_by_name - Errors detected!
When into the locks table the lock_time was never updated, so no actual lock was done.
Ofer
I found the issue (at least seems so)
The kettle.properties contained reference to localhost db (the old one) instead to the remote mysql server (new one).