[Dovecot] Initial status notification not received
Hello,
We have SLES-11 SP2 Xen VMs running dovecot as IMAP proxies. At VMs startup, dovecot almost always shows these errors:
Nov 16 14:29:19 server dovecot: master: Dovecot v2.1.10 starting up (core dumps disabled) Nov 16 14:29:55 server dovecot: master: Error: service(anvil): Initial status notification not received in 30 seconds, killing the process Nov 16 14:29:55 server dovecot: master: Error: service(log): Initial status notification not received in 30 seconds, killing the process Nov 16 14:29:55 server dovecot: master: Error: service(ssl-params): Initial status notification not received in 30 seconds, killing the process Nov 16 14:29:55 server dovecot: master: Error: service(log): child 3591 killed with signal 9
As the last line tells, dovecot stops logging information. We have to restart the dovecot processes to get back normal behaviour. I also tried to set idle_kill values to services definitions, without success.
Is there a way to prevent these errors?
Here is the dovecot -n output:
# 2.1.10: /etc/dovecot/dovecot.conf # OS: Linux 3.0.42-0.7-xen x86_64 SUSE Linux Enterprise Server 11 (x86_64) default_client_limit = 4096 default_idle_kill = 5 mins default_process_limit = 16384 listen = 10.254.251.18 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap sieve service anvil { client_limit = 65536 idle_kill = 0 } service auth { client_limit = 32768 } service imap-login { inet_listener imap { port = 0 } } service imap { process_limit = 0 } service log { idle_kill = 0 } service managesieve { process_limit = 0 } service ssl-params { idle_kill = 0 } ssl_ca =
Thanks,
Nicolas
Hello,
Has anybody some suggestions about the problem below?
I see in the archives (http://thread.gmane.org/gmane.mail.imap.dovecot/67077) that someone also has (had?) this problem; a cronjob workaround was used, but no dovecot solution was given.
Thanks, Nicolas
On Fri, Nov 16, 2012 at 03:12:59PM +0100, Nicolas KOWALSKI wrote:
Hello,
We have SLES-11 SP2 Xen VMs running dovecot as IMAP proxies. At VMs startup, dovecot almost always shows these errors:
Nov 16 14:29:19 server dovecot: master: Dovecot v2.1.10 starting up (core dumps disabled) Nov 16 14:29:55 server dovecot: master: Error: service(anvil): Initial status notification not received in 30 seconds, killing the process Nov 16 14:29:55 server dovecot: master: Error: service(log): Initial status notification not received in 30 seconds, killing the process Nov 16 14:29:55 server dovecot: master: Error: service(ssl-params): Initial status notification not received in 30 seconds, killing the process Nov 16 14:29:55 server dovecot: master: Error: service(log): child 3591 killed with signal 9
As the last line tells, dovecot stops logging information. We have to restart the dovecot processes to get back normal behaviour. I also tried to set idle_kill values to services definitions, without success.
Is there a way to prevent these errors?
Here is the dovecot -n output:
# 2.1.10: /etc/dovecot/dovecot.conf # OS: Linux 3.0.42-0.7-xen x86_64 SUSE Linux Enterprise Server 11 (x86_64) default_client_limit = 4096 default_idle_kill = 5 mins default_process_limit = 16384 listen = 10.254.251.18 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap sieve service anvil { client_limit = 65536 idle_kill = 0 } service auth { client_limit = 32768 } service imap-login { inet_listener imap { port = 0 } } service imap { process_limit = 0 } service log { idle_kill = 0 } service managesieve { process_limit = 0 } service ssl-params { idle_kill = 0 } ssl_ca =
Thanks,
Nicolas
-- Nicolas
On 16.11.2012, at 16.12, Nicolas KOWALSKI wrote:
We have SLES-11 SP2 Xen VMs running dovecot as IMAP proxies. At VMs startup, dovecot almost always shows these errors:
Nov 16 14:29:19 server dovecot: master: Dovecot v2.1.10 starting up (core dumps disabled) Nov 16 14:29:55 server dovecot: master: Error: service(anvil): Initial status notification not received in 30 seconds, killing the process Nov 16 14:29:55 server dovecot: master: Error: service(log): Initial status notification not received in 30 seconds, killing the process Nov 16 14:29:55 server dovecot: master: Error: service(ssl-params): Initial status notification not received in 30 seconds, killing the process Nov 16 14:29:55 server dovecot: master: Error: service(log): child 3591 killed with signal 9
As the last line tells, dovecot stops logging information. We have to restart the dovecot processes to get back normal behaviour. I also tried to set idle_kill values to services definitions, without success.
You mean this happens when the VM starts up, but if you manually restart it later they don't happen?
Is there a way to prevent these errors?
I wonder if it's because of SLES or something else.
On Fri, Nov 23, 2012 at 08:18:32AM +0200, Timo Sirainen wrote:
On 16.11.2012, at 16.12, Nicolas KOWALSKI wrote:
We have SLES-11 SP2 Xen VMs running dovecot as IMAP proxies. At VMs startup, dovecot almost always shows these errors:
Nov 16 14:29:19 server dovecot: master: Dovecot v2.1.10 starting up (core dumps disabled) Nov 16 14:29:55 server dovecot: master: Error: service(anvil): Initial status notification not received in 30 seconds, killing the process Nov 16 14:29:55 server dovecot: master: Error: service(log): Initial status notification not received in 30 seconds, killing the process Nov 16 14:29:55 server dovecot: master: Error: service(ssl-params): Initial status notification not received in 30 seconds, killing the process Nov 16 14:29:55 server dovecot: master: Error: service(log): child 3591 killed with signal 9
As the last line tells, dovecot stops logging information. We have to restart the dovecot processes to get back normal behaviour. I also tried to set idle_kill values to services definitions, without success.
You mean this happens when the VM starts up, but if you manually restart it later they don't happen?
Yes.
Is there a way to prevent these errors?
I wonder if it's because of SLES or something else.
We narrowed the problem to another process, started before dovecot, which takes a lot of CPU and disk resources; since we delayed its launch, dovecot starts up happily.
However, I am still confused about why dovecot kills itself. Maybe the master process could restart its runaway processes, or the initial status notification delay could be customized?
-- Nicolas
participants (2)
-
Nicolas KOWALSKI
-
Timo Sirainen