Re: [Dovecot] dovecot from debian lenny-backports does not accept connections
Joelly Alexander put forth on 5/15/2010 4:22 AM:
the server and the client are on the same layer2 network and there is no hard- or software or anything else installed on the server what prevents traffic between them; i just figured out that it has to do with the nfs portion; while incoming mails have no problems and are delivered correct into the maildir on the nfs, it does not work when the client want to connect to the maildir; when i copy content from nfs-storage to the local harddisk it works;
Read these below, and post back if that doesn't help. Please remember to reply to the list next time, not to individuals. I'm not an NFS guru, and those who are didn't see your reply.
http://wiki.dovecot.org/MailLocation/SharedDisk http://wiki.dovecot.org/NFS
-- Stan
storage are two debian lenny systems with rhcs, nfs-export configured: <nfsexport name="nfs-storage"/> <nfsclient name="nfs_fcamx1" allow_recover="1" path="/storage/fca-mailstore" target="fcamx1" options="rw,no_root_squash,no_all_squash"/> <nfsclient name="nfs_fcamx2" allow_recover="1" path="/storage/fca-mailstore" target="fcamx2" options="rw,no_root_squash,no_all_squash"/>
mountpoint on fcamx-servers: 192.168.100.20:/storage/fca-mailstore on /var/vmail type nfs (rw,rsize=8192,wsize=8192,timeo=14,intr,tcp,addr=192.168.100.20)
dovecot is configured with this parameters: fcamx1:/etc/dovecot# dovecot -n
1.2.11: /etc/dovecot/dovecot.conf
OS: Linux 2.6.32-bpo.4-686 i686 Debian 5.0.4 nfs
log_path: /var/log/dovecot/dovecot-errors.log info_log_path: /var/log/dovecot/dovecot-info.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/ssl/certs/dovecot-cert.pem ssl_key_file: /etc/ssl/private/dovecot-key.pem verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_greeting: hey dude, do you have an account? verbose_proctitle: yes first_valid_uid: 150 last_valid_uid: 150 mail_privileged_group: mail mail_location: maildir:/var/vmail/%d/%u mail_debug: yes mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes lock_method: fnctl mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh lda: postmaster_address: postmaster@mydomain.tld mail_plugins: sieve quota global_script_path: /var/vmail/globalsieverc log_path: /var/log/dovecot/dovecot-deliver.log info_log_path: /var/log/dovecot/dovecot-deliver-info.log auth default: mechanisms: plain login user: nobody verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: prefetch userdb: driver: passwd userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: mail master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: mail plugin: quota: maildir:storage=102400 sieve: ~/.dovecot.sieve sieve_dir: ~/sieve fcamx1:/etc/dovecot#
found the error - i had a typo in dovecot.conf
lock_method: fnctl should be lock_method: fcntl
dovecot reload does not show a problem, only a stop/start generated the entry in the logfile....
two days for a stupid typo....
thanks!
On 15.05.2010 11:58, Stan Hoeppner wrote:
Joelly Alexander put forth on 5/15/2010 4:22 AM:
the server and the client are on the same layer2 network and there is no hard- or software or anything else installed on the server what prevents traffic between them; i just figured out that it has to do with the nfs portion; while incoming mails have no problems and are delivered correct into the maildir on the nfs, it does not work when the client want to connect to the maildir; when i copy content from nfs-storage to the local harddisk it works;
Read these below, and post back if that doesn't help. Please remember to reply to the list next time, not to individuals. I'm not an NFS guru, and those who are didn't see your reply.
http://wiki.dovecot.org/MailLocation/SharedDisk http://wiki.dovecot.org/NFS
On 2010-05-15 2:54 PM, Joelly Alexander wrote:
found the error - i had a typo in dovecot.conf
lock_method: fnctl should be lock_method: fcntl
dovecot reload does not show a problem, only a stop/start generated the entry in the logfile....
two days for a stupid typo....
dovecot -n should also show the problem...
--
Best regards,
Charles
yes, it shows a summary what is configured, but not that there is a problem with one of the settings; only the 'restart' of the dovecot service generates a error in the logfile which point you to the problem, a 'reload' sets the configured value but does not generate a error; also not when clients want to connect via imap - you see in the logs only that the client trys to connect several times until it hits the 'mail_max_userip_connections' and the imap processes hang until you kill them hard manually;
On 15.05.2010 21:05, Charles Marcus wrote:
On 2010-05-15 2:54 PM, Joelly Alexander wrote:
found the error - i had a typo in dovecot.conf
lock_method: fnctl should be lock_method: fcntl
dovecot reload does not show a problem, only a stop/start generated the entry in the logfile....
two days for a stupid typo....
dovecot -n should also show the problem...
On 2010-05-16 5:34 AM, Joelly Alexander wrote:
On 15.05.2010 21:05, Charles Marcus wrote:
On 2010-05-15 2:54 PM, Joelly Alexander wrote:
two days for a stupid typo....
dovecot -n should also show the problem...
yes, it shows a summary what is configured, but not that there is a problem with one of the settings;
Hmmm... it was my understanding that, like postfix, dovecot -n would warn on *all* syntax errors, which I would classify a typo like this as...
But I just checked... if it is spelled properly, this setting doesn't show up in doveoct -n output at all, which suggests that lock_method = fcntl is the default - *but*, if it is spelled *improperly*, it *does* show up, and with the incorrect spelling...
A quick test with another setting does produce the desired warning/error
- I changed the protocols line to inaps, and:
myhost : Sun May 16, 13:49:16 : /etc
dovecot -n
1.2.11: /etc/dovecot/dovecot.conf
Error: Invalid protocols given in configuration file Fatal: Invalid configuration in /etc/dovecot/dovecot.conf myhost : Sun May 16, 13:49:18 : /etc
Timo? Shouldn't dovecot -n produce a similar warning/error for all invalid/typo'd settings?
I also think it would be a good idea to report the line# in the config file where the error resides (can make it much easier to find the setting in a large, heavily commented config file)...
--
Best regards,
Charles
On 16.5.2010, at 19.54, Charles Marcus wrote:
Timo? Shouldn't dovecot -n produce a similar warning/error for all invalid/typo'd settings?
v2.0 dovecot -n shows if lock_method was typoed. Also I find it strange that reloading a config wouldn't show the error.
I also think it would be a good idea to report the line# in the config file where the error resides (can make it much easier to find the setting in a large, heavily commented config file)...
This is unfortunately difficult. The config file is first parsed and only afterwards validated. It's even more problematic if the setting is overwritten in different places in config file..
On 2010-05-20 1:58 PM, Timo Sirainen wrote:
On 16.5.2010, at 19.54, Charles Marcus wrote: v2.0 dovecot -n shows if lock_method was typoed. Also I find it strange that reloading a config wouldn't show the error.
Cool...
I also think it would be a good idea to report the line# in the config file where the error resides (can make it much easier to find the setting in a large, heavily commented config file)...
This is unfortunately difficult. The config file is first parsed and only afterwards validated. It's even more problematic if the setting is overwritten in different places in config file..
Hmmm... postfix handles this by simply letting the last one 'win', which seems like a reasonable way to handle that.
Any chance 2.0 could work the same way? This way I could keep all of my settings in a separate file, and then include them in the main file, and I'd be sure that my custom settings overrode any of the defaults.
--
Best regards,
Charles
On 20.5.2010, at 21.59, Charles Marcus wrote:
I also think it would be a good idea to report the line# in the config file where the error resides (can make it much easier to find the setting in a large, heavily commented config file)...
This is unfortunately difficult. The config file is first parsed and only afterwards validated. It's even more problematic if the setting is overwritten in different places in config file..
Hmmm... postfix handles this by simply letting the last one 'win', which seems like a reasonable way to handle that.
Any chance 2.0 could work the same way? This way I could keep all of my settings in a separate file, and then include them in the main file, and I'd be sure that my custom settings overrode any of the defaults.
That's how Dovecot works too, but you could have for example:
foo = bar protocol imap { foo = foo }
The validation stage then tracks both imap and non-imap protocols and needs to give the line number for the right one. It probably wouldn't be too difficult to do, but not really something I want to spend time on right now.
On 2010-05-22 4:35 AM, Timo Sirainen wrote:
On 20.5.2010, at 21.59, Charles Marcus wrote:
Hmmm... postfix handles this by simply letting the last one 'win', which seems like a reasonable way to handle that.
Any chance 2.0 could work the same way? This way I could keep all of my settings in a separate file, and then include them in the main file, and I'd be sure that my custom settings overrode any of the defaults.
That's how Dovecot works too,
<sigh> I did test this real quick before posting, but I goofed - what I did was add 'protocols = pop' to the bottom, where above it was 'protocols = imaps' - and of course dovecot -n barfed since it should be pop3, not pop.
Sorry for the noise - I haven't used POP in many many years, so gloss over anything POP related - I'm glad to see it is indeed working like this... :)
--
Best regards,
Charles
Joelly Alexander put forth on 5/15/2010 1:54 PM:
found the error - i had a typo in dovecot.conf
lock_method: fnctl should be lock_method: fcntl
dovecot reload does not show a problem, only a stop/start generated the entry in the logfile....
two days for a stupid typo....
We all screw ourselves with a typo at one point or another. Don't fret over it. Isn't the first time and won't be the last, for any of us. :)
-- Stan
participants (4)
-
Charles Marcus
-
Joelly Alexander
-
Stan Hoeppner
-
Timo Sirainen