I have V1.1 running on a test server that NFS mounts mbox-formatted inbox and
home folder dirs. I have eliminated the profile listing for connection to the
V1.0 production servers so that can't start up and corrupt the synch of the test
servers indices
I am seeing posix_fallocate and file_set_size errmsgs in the mail syslog, but
see a pattern:
1) They only happen with the /var/spool/mail inbox NOT with any of the /home
folders and appear to be happening every 10 minutes from the time I started DC
(9AM, 10/1/98) until 11AM, 10/2...and then ceased
The every ten minute message sets looked like this:
> Oct 1 22:30:31 egg mail:err|error dovecot: IMAP(sdean): posix_fallocate()
failed: Resource temporarily unavailable
> Oct 1 22:30:31 egg mail:err|error dovecot: IMAP(sdean): file_set_size()
failed with mbox file /var/spool/mail/sdean: Resource temporarily unavailable
> Oct 1 22:40:31 egg mail:err|error dovecot: IMAP(sdean): posix_fallocate()
failed: Resource temporarily unavailable
> Oct 1 22:40:31 egg mail:err|error dovecot: IMAP(sdean): file_set_size()
failed with mbox file /var/spool/mail/sdean: Resource temporarily unavailable
> Oct 1 22:50:31 egg mail:err|error dovecot: IMAP(sdean): posix_fallocate()
failed: Resource temporarily unavailable
2) My Thunderbird client's server settings are set to check for mail every 10
minutes AND I don't access the mail overnight, so it this must be causing it!
I did check the crontabs on both my test and production servers and they had
nothing with this time periodicity
3) However, then there was the following:
a) If I used webmail, which accessed the production server and got the indices
on my test server out of sync, I got this error message from in the mail syslog
on my test server:
Oct 3 12:20:23 egg mail:err|error dovecot: IMAP(sdean): mbox sync: UID inserted
in the middle of mailbox /var/spool/mail/sdean (648818 > 648046, seq=1153, idx_
msgs=1187)
Which is what one would expect...once the V1.1 code is on production server that
won't happen anymore, so that's OK and can be ignored
b) I seem to end up having leftover imap session on the test server. Around 1PM
today, I was unable to get mail and saw these messages in the test server's mail
syslog:
Oct 3 12:44:58 egg mail:info dovecot: imap-login: Maximum number of connections
from user+IP exceeded: user=<sdean>, method=PLAIN, rip=10.20.10.169, lip=192.24
6.229.31
Turns out I had 10+ sessions, one back from yesterday, so I killed them all and
could get mail, but...about six minutes later, I had the two posix_fallocate and
file_set_size errmsgs again after not having any for a day. So something about
new connections maybe causes this?
Any ideas why:
a) I am having leftover IMAP sessions on my test server? This doesn't happen on
my production DC V1.0 server
b) Ditto on the the posix_fallocate and file_set_size errmsgs which also aren't
found on my production server's mail syslog.
?
I do realize that these seem to be related to Tbird, but they don't happen with
V1.0....
I have attached my original note with its copies of the dovecot -n
output for both machines
--- Begin Message ---
My production DC machine owns the mail filesystems and is running DC
V1.0.15 and mbox folder format.
I am looking to test V1.1.3 on another machine, which NFS mounts the
mail filesystems, but has its own local index FS.
I have made this test environment my default connection in TBird, and it
seems to work just fine. Also, I have made sure that my TBird client
isn't connecting to the production server (it has multiple accounts but
I have turned off the cehck for mail when starting and check for new
mail every N minutes functions, and then check the ps table to make sure
there are no imap connections)
However, I'm seeing two errmsgs in the maillog on the test machine:
Sep 22 11:54:13 egg mail:err|error dovecot: IMAP(sdean): posix_fallocate() faile
d: Protocol not available
Sep 22 11:54:13 egg mail:err|error dovecot: IMAP(sdean): file_set_size() failed
with mbox file /var/spool/mail/sdean: Protocol not available
which appear to happen AFTER mail arrives at the production server....it
seems to happen on my test server the next time my client goes to access
mail AFTER mail has arrived at the production server. Subsequent client
requests of the test server execute without error until AFTER the next
time mail arrives at and my inbox is updated with it.
Again, if I hadn't looked at the logs, I wouldn't know there was a
problem...I can see my new mail just fine from the test server.
The questions: Is this anything I should be concerned about? Is this a
bug or a legit problem coming from my improper use of two servers
against the same data.
FWIW, I am using fcntl for both mbox read and write locks. procmail in
the MDA on the production server, and its locking hierarchy
<dotlock,fcntl>, which Timo previously approved.
Thanks!
Production dovecot -n output:
# 1.0.15: /usr/local/etc/dovecot.conf
listen: *:143
ssl_listen: *:993
disable_plaintext_auth: no
verbose_ssl: yes
login_dir: /var/run/dovecot/login
login_executable: /usr/local/libexec/dovecot/imap-login
login_processes_count: 12
login_max_processes_count: 774
verbose_proctitle: yes
first_valid_uid: 200
mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u:INDEX=/var/dcindx/%u
mbox_write_locks: fcntl
mbox_dirty_syncs: no
auth default:
passdb:
driver: pam
userdb:
driver: passwd
Test dovecot -n output:
# 1.1.3: /usr/local/etc/dovecot.conf
listen: *:143
ssl_listen: *:993
disable_plaintext_auth: no
verbose_ssl: yes
login_dir: /var/run/dovecot/login
login_executable: /usr/local/libexec/dovecot/imap-login
login_processes_count: 12
login_max_processes_count: 774
max_mail_processes: 1024
verbose_proctitle: yes
first_valid_uid: 200
mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u:INDEX=/var/dcindx/%u
mbox_write_locks: fcntl
mbox_dirty_syncs: no
auth default:
passdb:
driver: pam
userdb:
driver: passwd
--- End Message ---
