Urgent: Most of backups are getting error

thunn

Verified User
Joined
Mar 13, 2012
Messages
166
Hello,
I'm doing a full backup, and most of user, I got the following error (I have chown admin.admin /home/admin/admin_backups/, and chmod 755 /home/admin/admin_backups/)

I'm using csf firewall, but I guess there is no problem with process kill, because I checked in /var/log/lfd.log and /var/log/message there is no info about killing backup process.

Code:
Unable to write /home/admin/admin_backups/user01/backup/domain1.com/email/passwd : Unable to get Lock on file:
open error for /home/admin/admin_backups/user01/backup/domain1.com/email/passwd.lock: No such file or directory
/home/admin/admin_backups/user01/backup/domain1.com/email: No such file or directory

Unable to write /home/admin/admin_backups/user01/backup/domainabc.com/email/passwd : Unable to get Lock on file:
open error for /home/admin/admin_backups/user01/backup/domainabc.com/email/passwd.lock: No such file or directory
/home/admin/admin_backups/user01/backup/domainabc.com/email: No such file or directory

Unable to write /home/admin/admin_backups/user01/backup/domaindef.com/email/passwd : Unable to get Lock on file:
open error for /home/admin/admin_backups/user01/backup/domaindef.com/email/passwd.lock: No such file or directory
/home/admin/admin_backups/user01/backup/domaindef.com/email: No such file or directory


Some other user's backup are created successfully:
Code:
User user02 has been backed up. <19:44:11>
User user03 has been backed up. <19:46:13>
User user04 has been backed up. <19:46:26>
User user05 has been backed up. <19:46:32>
User user06 has been backed up. <19:47:32>
User user07 has been backed up. <19:56:49>
User user08 has been backed up. <19:56:52>


And one of backup, I got the following message:
Code:
User userxxx has been backed up.
<1:30:16>
Backup Halted


For admin and folder's permission, it's correct:
Code:
 7471105 drwxrwxrwt.   2 root       root        4096 Jun  1 04:21 tmp
34996225 drwx--x---    9 user01     access      4096 Mar  4 15:26 user01
13369345 drwx--x---    7 user02     access      4096 Apr 17 20:50 user02
28704774 drwx--x---    8 user03     access      4096 Nov 18  2013 user03
12320797 drwx--x---    7 user04     access      4096 May 31 14:17 user04
31719425 drwx--x---    8 user05     access      4096 Dec  9 14:31 user05
22151169 drwx--x--x    9 reseller01 reseller01  4096 Aug 29  2013 reseller01



Please help me, it's urgent.
Thank you very much!
 
Have you checked if that user indeed has email adresses?
Because you could get this error also if the email is not used. In that case no /email/passwd file will exist so it logically can't be found and/or locked.

I don't know about the "halted" notice.
 
Hello,

1) The only way to ever see "Backup Halted" would be if the dataskq received a USR2 signal.

That can be sent from directadmin via:
Admin Level -> Admin Backup/Transfer -> Backup Montior: kill

where the Backup Monitor will only show up if a backup is running, and it hidden all other times. (table shows up at the top of the page)

Or.. if some other root process sends a USR2 to the dataskq process while it's running the backup.

It's related to this:
http://www.directadmin.com/features.php?id=1509

---------

2) Another aspect of the backups is that you must not have 2 backups for the same creator running at the same time.
So if you have an Admin Backup/Transfer creating backups (via "admin") in /home/admin/admin_backups, you're not going to want to run a 2nd instance at the same time.
What happens is if you wait one minute, then the 2nd backup request goes into a fresh task.queue, and gets picked up by a brand new dataskq process.
This is bad because the 2nd process always cleans house before starting, which would wipe out any work that the 1st process is doing.. which can cause the missing passwd files, etc (I've added better checks and messages for the next release to let you know if the path goes missing)

However, the "Backup Halted" message is it's own thing, separate from the missing passwd files, meaning it was actually told to stop by someone.

Hope that helps clarify things.

John
 
Back
Top