Hi @Jess,
I already check that.
The Access Log rotate every day from both Servern.
They also Include a lot of this kind of Records.
The kaltura User dont have own rights. But the Kaltura User can Read them.
-rw-r--r-- 1 root root 5133490 Jan 26 03:24 xxx-xxx-xxx-kaltura_apache_access_ssl.log-20170126-03.gz
[changed@changed logs]$ cat * | grep ERROR
ERROR 25-01 12:30:07,222 - Lock is already seized - Row nr 1 causing abort : [retention_lock], [1], [0], [null]
ERROR 25-01 12:30:07,223 - Lock is already seized - Aborting after having seen 1 rows.
ERROR 25-01 12:30:07,223 - seize_lock_by_name - Errors detected!
ERROR 25-01 12:30:07,223 - seize_lock_by_name - Errors detected!
ERROR 26-01 12:30:07,301 - Lock is already seized - Row nr 1 causing abort : [retention_lock], [1], [0], [null]
ERROR 26-01 12:30:07,301 - Lock is already seized - Aborting after having seen 1 rows.
ERROR 26-01 12:30:07,302 - seize_lock_by_name - Errors detected!
ERROR 26-01 12:30:07,302 - seize_lock_by_name - Errors detected!
ERROR 24-01 14:00:07,805 - Lock is already seized - Row nr 1 causing abort : [update_dims_lock], [1], [0], [null]
ERROR 24-01 14:00:07,805 - Lock is already seized - Aborting after having seen 1 rows.
ERROR 24-01 14:00:07,807 - seize_lock_by_name - Errors detected!
ERROR 24-01 14:00:07,807 - seize_lock_by_name - Errors detected!
ERROR 24-01 16:00:06,751 - Lock is already seized - Row nr 1 causing abort : [update_dims_lock], [1], [0], [null]
ERROR 24-01 16:00:06,752 - Lock is already seized - Aborting after having seen 1 rows.
ERROR 24-01 16:00:06,753 - seize_lock_by_name - Errors detected!
ERROR 24-01 16:00:06,753 - seize_lock_by_name - Errors detected!
ERROR 26-01 12:00:07,102 - Lock is already seized - Row nr 1 causing abort : [update_dims_lock], [1], [0], [null]
ERROR 26-01 12:00:07,102 - Lock is already seized - Aborting after having seen 1 rows.
ERROR 26-01 12:00:07,104 - seize_lock_by_name - Errors detected!
ERROR 26-01 12:00:07,104 - seize_lock_by_name - Errors detected!