cant make any admin backup anymore

kanary

Verified User
Joined
Jun 8, 2007
Messages
113
Location
Holland - Het westland
Hi,

I just upgraded DA to the last versions but now i cant backup anymore it will break after this.

The following hard links have been found under User admin:

How can i remove this very anoying feature ?

Thanks
 
i will set that.

It's my own server and im the only one thats using it.

What the DA backup found are only imap folder i don't care about that

Since I got the same error and all of them are in either IMAP folder and Maildir folder. I'm wondering what cause that in IMAP/Maildir though and what should be done to fix it?
 
Last edited:
I've just received a New Message from Directadmin, entitled as "Backup Abort: A hard link was found under User username's path". And I see a lot of:

The following hard links have been found under User username:

/home/username/imap/domain.com/monitoring/Maildir/.INBOX.Logwatch/cur/1356974589.H978159P3137.server.domain.com:2,
/home/username/imap/domain.com/monitoring/Maildir/.INBOX.Logwatch/cur/1356974596.H151714P3142.server.domain.com:2,
/home/username/imap/domain.com/monitoring/Maildir/.INBOX.Logwatch/cur/1356977417.H461054P11822.server.domain.com:2,S
/home/username/imap/domain.com/monitoring/Maildir/.INBOX.Logwatch/cur/1356981795.H721894P24630.server.domain.com:2,

I'll check it and update you with my findings soon. If it's not a bug in the latest Directadmin, then it's probably Dovecot with its recent update which causes it.
 
That's related to dovecot:

maildir_copy_with_hardlinks=yes (default): When copying a message, do it with hard links whenever possible. This makes the performance much better, and it's unlikely to have any side effects. Only reason to disable this is if you're using a filesystem where hard links are slow (e.g. HFS+).

See this: http://wiki2.dovecot.org/MailLocation/Maildir

So you should either disable the check:

Code:
backup_hard_link_check=0

or disable using hard links with dovecot:

Code:
maildir_copy_with_hardlinks=no
 
Hello John,

Files found by Directadmin check are hardlinks in imap folders, but they are existing emails, not deleted. Yes, they have been moved by me to a folder. Roundcube shows neither deleted, nor marked as deleted in the folder. So that relates to maildir_copy_with_hardlinks option in dovecot.conf I guess. Anyway your fix:

The checks are relaxed slightly, in that a hardlink can exist, as long as it's chowned to the user.

should solve it.
 
Hello,

It was an overly aggressive check on hardlinks.
I'm about to release 1.43.3 with this change:
http://www.directadmin.com/features.php?id=1471

as Dovecot does have hardlinks if a message is deleted, but not purged (something that our tests didn't catch)

John

I've upgraded to 1.43.3, but I'm still getting lots and lots of "Backup Abort: A hard link was found under User ..." errors, all complaining about hardlinks to "imap/.../mail/spam" folders.
 
Hello,

Is this an older system that has since been updated to Dovecot?

If so, the mail/spam is likely old, from the old vm-pop3d/wu-imap days.


1) Confirm that you're actually running dovecot. If not, then don't continue.

2) If you are running dovecot, then the mbox files wont be needed.
For that case, type:
Code:
echo "action=delete&value=mbox" >> /usr/local/directadmin/data/task.queue

3) Beyond that, paste us the permissions and ownership of the link, an of the spam folder it points to.

John
 
Hello John, thanks for replying.

Yes, this system is running Dovecot and has been from the start. However, many users on this server came from an older system that had been running mbox and was converted to Dovecot later. So maybe the mbox folders were recreated during the restore process on this server?

I will run the delete mbox task and see if that solves the problem.

Thanks!
 
I agree.
After running the 'delete mbox task', the problem appears to have gone.
Thanks!
 
Hello,

Is this an older system that has since been updated to Dovecot?

If so, the mail/spam is likely old, from the old vm-pop3d/wu-imap days.


1) Confirm that you're actually running dovecot. If not, then don't continue.

2) If you are running dovecot, then the mbox files wont be needed.
For that case, type:
Code:
echo "action=delete&value=mbox" >> /usr/local/directadmin/data/task.queue

3) Beyond that, paste us the permissions and ownership of the link, an of the spam folder it points to.

John

I have upgraded DA 2 days ago (from v1.43.0 to v1.43.3), and since then my backups seems to fail "Backup Abort: A hard link was found under User xuser's path" (and this happens for all existing users in DA).
Everytime the reason is (example for xuser):
The following hard links have been found under User xuser:

/home/xuser/mail/spam

Now I'm wondering how I can solve this as the solution above only seems useful if you no longer use vm-pop3d (which is still in use on the server). And I would like to keep the security backup_hard_link_check=1 on. I only think it's a bit strange that I experience this now since 1.43.3 and not before. According to the changelog it should now be less aggressive.

Any help would be appreciated. Thanks.
 
Ok. I'll do the conversion, since Dovecot means major improvement. And hoping the backup problem disappears with it.
 
Same Backup Error

Hi everyone,

I recognize that this is a very old thread - but it describes exactly what I am currently experiencing. Recently I installed Drupal (v8.5.6) to do some testing. For the past few nights I have been receiving backup error notifications for the account this was installed under:

Code:
Subject: Backup Abort (4): A hard link was found under User USERNAME's path

The following hard links have been found under User USERNAME:

/home/USERNAME/domains/DOMAIN.COM/public_html/d8/vendor/zendframework/zend-escaper/README.md
/home/USERNAME/domains/DOMAIN.COM/public_html/d8/vendor/zendframework/zend-escaper/doc/book/index.md
/home/USERNAME/domains/DOMAIN.COM/public_html/d8/vendor/zendframework/zend-feed/README.md
/home/USERNAME/domains/DOMAIN.COM/public_html/d8/vendor/zendframework/zend-feed/doc/book/index.md
/home/USERNAME/domains/DOMAIN.COM/public_html/d8/vendor/zendframework/zend-stdlib/README.md
/home/USERNAME/domains/DOMAIN.COM/public_html/d8/vendor/zendframework/zend-stdlib/doc/book/index.md

The site was installed by uploading the Drupal tar.gz file through DirectAdmin then extracted using the File Manager. None of these files should be hard links so I am not certain why this error occurs.

Could the file contents be triggering this error?

I am unable to attach one of the files to my post as I believe the .md extension is not permitted. Here is what the first file I listed contains (.../zend-escaper/README.md):

Code:
# zend-escaper

[![Build Status](https://secure.travis-ci.org/zendframework/zend-escaper.svg?branch=master)](https://secure.travis-ci.org/zendframework/zend-escaper)
[![Coverage Status](https://coveralls.io/repos/zendframework/zend-escaper/badge.svg?branch=master)](https://coveralls.io/r/zendframework/zend-escaper?branch=master)

The OWASP Top 10 web security risks study lists Cross-Site Scripting (XSS) in
second place. PHP’s sole functionality against XSS is limited to two functions
of which one is commonly misapplied. Thus, the zend-escaper component was written.
It offers developers a way to escape output and defend from XSS and related
vulnerabilities by introducing contextual escaping based on peer-reviewed rules.

- File issues at https://github.com/zendframework/zend-escaper/issues
- Documentation is at https://zendframework.github.io/zend-escaper/

Has anyone else experienced this issue with Drupal 8?

Thank you for any insight that may resolve this issue!
 
Thank you Richard G - I completely missed the help page that you provided. My apology for not starting a new thread! I'll go ahead and do that if I am unable to find a resolution.

Take care!
 
Back
Top