Yesterday:
-- cut --
User sversr has been backed up. <1:23:31>
Unable to lock the 'tba' account actions:
User's System Quotas set
Error locking the User 'tba' actions lock file due to existing lock created on Dec 1 01:23:27 2024. Some other process may be doing work on this account.
<1:23:33>
Cannot find /home/tmp/admin.3125813.8xfQM0dOPXCcgsJnxtmvwlPlcUQ01wB9/EmEIFtZcdnC5RwyZRpCnFyhWi1vkoda1/user.admin.tba.tar.zst.enc for upload.
User tdorst has been backed up. <1:23:34>
-- cut --
today:
-- cut --
User tba has been backed up. <1:23:55>
User tvandis has been backed up. <1:24:11>
Unable to lock the 'tdde' account actions:
User's System Quotas set
Error locking the User 'tdde' actions lock file due to existing lock created on Dec 2 01:24:05 2024. Some other process may be doing work on this account.
<1:24:13>
Cannot find /home/tmp/admin.3322660.8QUDkRDsVlPfF7VXSRTbwYGzoZVVXgPd/c4iUPwB83JJcr60hm6RyunJT6XBycScD/reseller.admin.tdde.tar.zst.enc for upload.
-- cut --
Since yesterday there are 'lock' problems.
I tried
cd /usr/local/directadmin/data/users/
find . -type f -name "user.action.lock"
and
find . -type f -name "*lock"
But found nothing.
In errortask.log I am seeing daily these messages:
2024:12:02-01:25:51: sys::remove_tracked_temporary_files: removed temporary file './data/users/n541592/user.action.lock'
2024:12:02-01:25:51: sys::remove_tracked_temporary_files: removed temporary file './data/users/n541596/user.action.lock'
2024:12:02-01:25:51: sys::remove_tracked_temporary_files: removed temporary file './data/users/n541668/user.action.lock'
2024:12:02-01:25:51: sys::remove_tracked_temporary_files: removed temporary file './data/users/n541734/user.action.lock'
2024:12:02-01:25:51: sys::remove_tracked_temporary_files: removed temporary file './data/users/n541739/user.action.lock'
There is a message for every user in this system. Very annoying lines, what does it tell us? That D.A. is not cleaning up lock files?
(I have seen this for a very long time and never thought anything of it, but it is of course an indication of something going wrong).
In any case, the backup is now failing daily, one user at a day for now. Can this be stopped?
I expect this is some sort of bug.
If you look very close, you will see the lock file is created merely seconds before the backup starts.
yesterday:
existing lock created on Dec 1 01:23:27 2024
The line above this says: User tvandis has been backed up. <1:24:11>
This means that the backup of a user starts while the backup of the previous user has not finished yet. Indicating parallelism. This is why I think this is a bug, it looks to me the backup for a user MAY be started twice.
-- cut --
User sversr has been backed up. <1:23:31>
Unable to lock the 'tba' account actions:
User's System Quotas set
Error locking the User 'tba' actions lock file due to existing lock created on Dec 1 01:23:27 2024. Some other process may be doing work on this account.
<1:23:33>
Cannot find /home/tmp/admin.3125813.8xfQM0dOPXCcgsJnxtmvwlPlcUQ01wB9/EmEIFtZcdnC5RwyZRpCnFyhWi1vkoda1/user.admin.tba.tar.zst.enc for upload.
User tdorst has been backed up. <1:23:34>
-- cut --
today:
-- cut --
User tba has been backed up. <1:23:55>
User tvandis has been backed up. <1:24:11>
Unable to lock the 'tdde' account actions:
User's System Quotas set
Error locking the User 'tdde' actions lock file due to existing lock created on Dec 2 01:24:05 2024. Some other process may be doing work on this account.
<1:24:13>
Cannot find /home/tmp/admin.3322660.8QUDkRDsVlPfF7VXSRTbwYGzoZVVXgPd/c4iUPwB83JJcr60hm6RyunJT6XBycScD/reseller.admin.tdde.tar.zst.enc for upload.
-- cut --
Since yesterday there are 'lock' problems.
I tried
cd /usr/local/directadmin/data/users/
find . -type f -name "user.action.lock"
and
find . -type f -name "*lock"
But found nothing.
In errortask.log I am seeing daily these messages:
2024:12:02-01:25:51: sys::remove_tracked_temporary_files: removed temporary file './data/users/n541592/user.action.lock'
2024:12:02-01:25:51: sys::remove_tracked_temporary_files: removed temporary file './data/users/n541596/user.action.lock'
2024:12:02-01:25:51: sys::remove_tracked_temporary_files: removed temporary file './data/users/n541668/user.action.lock'
2024:12:02-01:25:51: sys::remove_tracked_temporary_files: removed temporary file './data/users/n541734/user.action.lock'
2024:12:02-01:25:51: sys::remove_tracked_temporary_files: removed temporary file './data/users/n541739/user.action.lock'
There is a message for every user in this system. Very annoying lines, what does it tell us? That D.A. is not cleaning up lock files?
(I have seen this for a very long time and never thought anything of it, but it is of course an indication of something going wrong).
In any case, the backup is now failing daily, one user at a day for now. Can this be stopped?
I expect this is some sort of bug.
If you look very close, you will see the lock file is created merely seconds before the backup starts.
yesterday:
existing lock created on Dec 1 01:23:27 2024
The line above this says: User tvandis has been backed up. <1:24:11>
This means that the backup of a user starts while the backup of the previous user has not finished yet. Indicating parallelism. This is why I think this is a bug, it looks to me the backup for a user MAY be started twice.