I at one time installed bind with chroot but decided to remove the bind-chroot package but it did not clean up and remove chroot mounts so I manually removed the chroot mounts, reconfgured bind, restarted named, with no apparent errors.
But now, dovecot complains in maillog, the following errors:
dovecot: master: Warning: /var/named/chroot/etc/named.root.key is no longer mounted. See http://wiki2.dovecot.org/Mountpoints dovecot: master: Warning: /var/named/chroot/etc/named.conf is no longer mounted. See http://wiki2.dovecot.org/Mountpoints dovecot: master: Warning: /var/named/chroot/etc/named.rfc1912.zones is no longer mounted. See http://wiki2.dovecot.org/Mountpoints dovecot: master: Warning: /var/named/chroot/etc/rndc.key is no longer mounted. See http://wiki2.dovecot.org/Mountpoints dovecot: master: Warning: /var/named/chroot/usr/lib/bind is no longer mounted. See http://wiki2.dovecot.org/Mountpoints dovecot: master: Warning: /var/named/chroot/etc/named.iscdlv.key is no longer mounted. See http://wiki2.dovecot.org/Mountpoints dovecot: master: Warning: /var/named/chroot/var/named is no longer mounted. See http://wiki2.dovecot.org/Mountpoints
I tried some of the examples pointed out in wiki2 but I am unable to remove the warnings...
What do I need to do?
On 10/22/2013 11:00 AM, Dan Thurman wrote:
I at one time installed bind with chroot but decided to remove the bind-chroot package but it did not clean up and remove chroot mounts so I manually removed the chroot mounts, reconfgured bind, restarted named, with no apparent errors.
But now, dovecot complains in maillog, the following errors:
dovecot: master: Warning: /var/named/chroot/etc/named.root.key is no longer mounted. See http://wiki2.dovecot.org/Mountpoints dovecot: master: Warning: /var/named/chroot/etc/named.conf is no longer mounted. See http://wiki2.dovecot.org/Mountpoints dovecot: master: Warning: /var/named/chroot/etc/named.rfc1912.zones is no longer mounted. See http://wiki2.dovecot.org/Mountpoints dovecot: master: Warning: /var/named/chroot/etc/rndc.key is no longer mounted. See http://wiki2.dovecot.org/Mountpoints dovecot: master: Warning: /var/named/chroot/usr/lib/bind is no longer mounted. See http://wiki2.dovecot.org/Mountpoints dovecot: master: Warning: /var/named/chroot/etc/named.iscdlv.key is no longer mounted. See http://wiki2.dovecot.org/Mountpoints dovecot: master: Warning: /var/named/chroot/var/named is no longer mounted. See http://wiki2.dovecot.org/Mountpoints
I tried some of the examples pointed out in wiki2 but I am unable to remove the warnings...
What do I need to do?
I think I solved it... was wiki2 says:
As root: # doveadm mount remove /var/named/chroot/etc/named.root.key # doveadm mount remove /var/named/chroot/etc/named.conf # doveadm mount remove /var/named/chroot/etc/named.rfc1912.zones # doveadm mount remove /var/named/chroot/etc/rndc.key # doveadm mount remove /var/named/chroot/usr/lib/bind # doveadm mount remove /var/named/chroot/etc/named.iscdlv.key # doveadm mount remove /var/named/chroot/var/named
On Tue, 2013-10-22 at 11:00 -0700, Dan Thurman wrote:
dovecot complains in maillog, the following errors:
dovecot: master: Warning: /var/named/chroot/etc/named.root.key is no longer mounted. See http://wiki2.dovecot.org/Mountpoints
I notice you've resolved this, but I find the information Dovecot provides on that link, "Dovecot wants to keep track of mountpoints that might contain emails," to be quite disturbing. I don't think a mail program should be behaving like that, at all. Imagine the mess we'd be in all sorts of programs started ploughing through the directory tree, without being told to, just because they thought it was a good idea.
Since Fedora likes to put removeable media into /var/run/username/media you might encounter that problem again, unless you put /var/run into its ignore database.
On Wed, 23 Oct 2013 16:30:19 +1030 Tim wrote:
Since Fedora likes to put removeable media into /var/run/username/media you might encounter that problem again, unless you put /var/run into its ignore database.
It is worse than that. It apparently doesn't store the ignored info anywhere, because if a mountpoint appears again then disappears again, it will warn you again no matter what you might have told it previously.
This appears to be another case of butt-headed developers since lots of users have asked for a way to eradicate this "feature" but the requests are always rejected as "user is wrong".
I think I put in a syslog rule to just filter out all the messages since there is no practical way to make them stop.
Tim:
Since Fedora likes to put removeable media into /var/run/username/media you might encounter that problem again, unless you put /var/run into its ignore database.
Tom Horsley:
It is worse than that. It apparently doesn't store the ignored info anywhere, because if a mountpoint appears again then disappears again, it will warn you again no matter what you might have told it previously.
This appears to be another case of butt-headed developers since lots of users have asked for a way to eradicate this "feature" but the requests are always rejected as "user is wrong".
Gawd, what were they thinking?! And I wonder what their response will be to a blunt, "no, YOU, are wrong"?
Why should an email server program go looking for places that you might have mail? Surely where mail is stored is something that the admin person ought to be configuring.
If it were an occasional removable drive change, then I could possibly live with just ensuring that a start script was used somewhere to add in the parameters. But I'll just have to make sure than either the next server I set up doesn't get things plugging into it (though I suppose inserting a DVD-ROM into a drive is going to send it bananas, too), or I use another IMAP server program.
Well done Dovecot programmers, what a fucking stupid thing to do.
On 10/22/2013 11:00 PM, Tim wrote:
On Tue, 2013-10-22 at 11:00 -0700, Dan Thurman wrote:
dovecot complains in maillog, the following errors:
dovecot: master: Warning: /var/named/chroot/etc/named.root.key is no longer mounted. See http://wiki2.dovecot.org/Mountpoints
I notice you've resolved this, but I find the information Dovecot provides on that link, "Dovecot wants to keep track of mountpoints that might contain emails," to be quite disturbing. I don't think a mail program should be behaving like that, at all. Imagine the mess we'd be in all sorts of programs started ploughing through the directory tree, without being told to, just because they thought it was a good idea.
Since Fedora likes to put removeable media into /var/run/username/media you might encounter that problem again, unless you put /var/run into its ignore database.
(and sub-thread replies to Tim)
After dovecot restarts and a reboot, (lazarus's) bind-chroot mountpoints warnings has not risen from the grave. ;)
Do you think the dovecot programmers read "Fedora Community" mailing list? I don't think so, but I could be wrong...
Why not ask dovecot.org?
I read their site and it appears that dovecot supports clustered filesytems, *dsync, and a myriad of different things. Then I found this:
* http://blog.dovecot.org/2012/02/dovecot-clustering-with-dsync-based.html (Could replication/clustering/dsync have something to do with detecting disk changes?)
Since I mentioned that I installed bind-chroot, installed dovecot, then uninstalled bind-chroot, perhaps triggering dovecot to notice a disk change (dsync) and thus generated bind-chroot mountpoint warnings, repeatedly? I do recall that when I installed bind-root, dovecot did not complain and I had this running for a week or so. The dovecot warning came after I removed bind-root.
Just something to consider...
Dan
Am 23.10.2013 17:28, schrieb Dan Thurman:
Why not ask dovecot.org?
because Timo was asked often enough the remove this stupid behavior as default
I read their site and it appears that dovecot supports clustered filesytems, *dsync, and a myriad of different things. Then I found this:
(Could replication/clustering/dsync have something to do with detecting disk changes?)
even if - you have the same behavior while dovecot is running as proxy only
Since I mentioned that I installed bind-chroot, installed dovecot, then uninstalled bind-chroot, perhaps triggering dovecot to notice a disk change (dsync) and thus generated bind-chroot mountpoint warnings, repeatedly? I do recall that when I installed bind-root, dovecot did not complain and I had this running for a week or so. The dovecot warning came after I removed bind-root
yes because it complains *always* if any mountpoint got removed no user-space application on this planet needs to scan mountpoints at least not as default behavior in any setup
Am 22.10.2013 20:00, schrieb Dan Thurman:
I at one time installed bind with chroot but decided to remove the bind-chroot package but it did not clean up and remove chroot mounts so I manually removed the chroot mounts, reconfgured bind, restarted named, with no apparent errors.
But now, dovecot complains in maillog, the following errors:
dovecot: master: Warning: /var/named/chroot/etc/named.root.key is no longer mounted. See http://wiki2.dovecot.org/Mountpoints dovecot: master: Warning: /var/named/chroot/etc/named.conf is no longer mounted. See http://wiki2.dovecot.org/Mountpoints dovecot: master: Warning: /var/named/chroot/etc/named.rfc1912.zones is no longer mounted. See http://wiki2.dovecot.org/Mountpoints dovecot: master: Warning: /var/named/chroot/etc/rndc.key is no longer mounted. See http://wiki2.dovecot.org/Mountpoints dovecot: master: Warning: /var/named/chroot/usr/lib/bind is no longer mounted. See http://wiki2.dovecot.org/Mountpoints dovecot: master: Warning: /var/named/chroot/etc/named.iscdlv.key is no longer mounted. See http://wiki2.dovecot.org/Mountpoints dovecot: master: Warning: /var/named/chroot/var/named is no longer mounted. See http://wiki2.dovecot.org/Mountpoints
I tried some of the examples pointed out in wiki2 but I am unable to remove the warnings...
What do I need to do?
seems the Fedora dovecot is broken because these are no mountpoints at all anyways, removed them and tell dovecot to ignore the complete tree
http://wiki2.dovecot.org/Mountpoints
doveadm mount remove /var/named/chroot/etc/named.root.key doveadm mount remove /var/named/chroot/etc/named.conf doveadm mount remove /var/named/chroot/etc/named.rfc1912.zones doveadm mount remove /var/named/chroot/etc/rndc.key doveadm mount remove /var/named/chroot/usr/lib/bind doveadm mount remove /var/named/chroot/var/named
and *finally*
doveadm mount add '/var/named/*' ignore
-
Dan Thurman -
Reindl Harald -
Tim -
Tom Horsley