1

Topic: Dovecot stops after upgrade of SuSE 11.3 to 11.4?

I have symptoms almost identical to Can't login to..., except that in my case the mail system had been working until I upgraded the SuSE OS from 11.3 to 11.4.

With debug options turned on in /etc/dovecot/dovecot.conf, this is the console output (nothing in /var/log/dovecot.log or /var/log/sieve.log):

console:~ # /etc/init.d/dovecot start
Starting dovecot ILoading modules from directory: /usr/lib64/dovecot/modules/imap
IModule loaded: /usr/lib64/dovecot/modules/imap/lib10_quota_plugin.so
IModule loaded: /usr/lib64/dovecot/modules/imap/lib11_imap_quota_plugin.so
IModule loaded: /usr/lib64/dovecot/modules/imap/lib20_autocreate_plugin.so
IEffective uid=65534, gid=65533, home=/tmp
IQuota root: name=user backend=dict args=:proxy::quotadict
IQuota rule: root=user mailbox=* bytes=0 messages=0
IQuota warning: bytes=0 (85%) messages=0 command=/usr/local/bin/dovecot-quota-warning.sh 85
IQuota warning: bytes=0 (90%) messages=0 command=/usr/local/bin/dovecot-quota-warning.sh 90
IQuota warning: bytes=0 (95%) messages=0 command=/usr/local/bin/dovecot-quota-warning.sh 95
Fatal: execv(/usr/lib/dovecot/managesieve) failed: Permission denied
Error: managesieve dump-capability process returned 84
Fatal: Invalid configuration in /etc/dovecot/dovecot.conf
startproc:  exit status of parent of /usr/sbin/dovecot: 89
                                                                                                                           failed
console:~ #

Can anyone suggest where to start? Is it the quota warnings, permission denied or the invalid dovecot.conf?

Permissions are:

console:~ # ls -dl /usr/lib/dovecot/managesieve
-rwxr-xr-x 1 root root 989496 May 25 12:22 /usr/lib/dovecot/managesieve
console:~ #

First section of dovecot.conf is:

#
# File generated by iRedMail (2011.02.12.10.25.01):
#
# Version:  0.7.0-beta2
# Project:  http://www.iredmail.org/
#
# Community: http://www.iredmail.org/forum/
#

# Provided services.
protocols =  pop3 pop3s imap imaps managesieve

# Listen addresses. for Dovecot-1.1.x.
# ipv4: *
# ipv6: [::]
#listen = *, [::]
listen = *

# mail uid/gid.
mail_uid = 303
mail_gid = 303
first_valid_uid = 303
last_valid_uid = 303

And user/group 303 is vmail.

Looking forward to any suggestions.

Regards, Martin

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Dovecot stops after upgrade of SuSE 11.3 to 11.4?

Does it work if you remove "managesieve" from "protocols =" in dovecot.conf? like below:

protocols =  pop3 pop3s imap imaps

3

Re: Dovecot stops after upgrade of SuSE 11.3 to 11.4?

Hi Zhang,

Unfortunately not. Different debug output though:

console:~ # /usr/sbin/dovecot -c /etc/dovecot/dovecot.conf
ILoading modules from directory: /usr/lib64/dovecot/modules/imap
IModule loaded: /usr/lib64/dovecot/modules/imap/lib10_quota_plugin.so
IModule loaded: /usr/lib64/dovecot/modules/imap/lib11_imap_quota_plugin.so
IModule loaded: /usr/lib64/dovecot/modules/imap/lib20_autocreate_plugin.so
IEffective uid=65534, gid=65533, home=/tmp
IQuota root: name=user backend=dict args=:proxy::quotadict
IQuota rule: root=user mailbox=* bytes=0 messages=0
IQuota warning: bytes=0 (85%) messages=0 command=/usr/local/bin/dovecot-quota-warning.sh 85
IQuota warning: bytes=0 (90%) messages=0 command=/usr/local/bin/dovecot-quota-warning.sh 90
IQuota warning: bytes=0 (95%) messages=0 command=/usr/local/bin/dovecot-quota-warning.sh 95
Can't open log file /var/log/dovecot.log: Permission denied
console:~ #

As root, in this console, I can access /var/log/dovecot.log?

Regards,

4

Re: Dovecot stops after upgrade of SuSE 11.3 to 11.4?

mprowe wrote:

Can't open log file /var/log/dovecot.log: Permission denied

/var/log/dovecot.log should be owned by user 'vmail', group 'vmail', file permission is 0600.
Also, /var/log/sieve.log should be owned by user 'vmail' and group 'vmail' too, file permission is 0666. (Yes, 0666 is not security enough, but it's required by dovecot-1.x.)

5

Re: Dovecot stops after upgrade of SuSE 11.3 to 11.4?

Hi again Zhang,

While chatting to you, I was also searching through the OpenSuSE forums.
Over there there are a couple of post that link these symptoms to AppArmor ( a Novel security tool). On checking, I find that during the upgrade it has got turned on!

Turn it back off - and all is okay now.

Thanks for your (very) prompt help and a great tool.

Regards, Martin

6

Re: Dovecot stops after upgrade of SuSE 11.3 to 11.4?

Spoke too soon!!!!!

Although I can now start Dovecot, it seems that all incoming smtp trafic is being rejected.
On investigation it looks like a problem with policyd?

console:~ # /etc/init.d/policyd start
Starting policyd
Message from syslogd@supermicro at Jun  9 11:02:27 ...
policyd: fatal: didn't find priority 'LOG_IFOO', exiting
startproc:  exit status of parent of /usr/sbin/policyd: 255
                                                                                                                                                         failed
console:~ #

So, after a search around your forum, I find Fatal error: Policyd and try your workaround. Now I get this:

console:~ # /etc/init.d/policyd start
Starting policyd
Message from syslogd@supermicro at Jun  9 11:04:06 ...
policyd: fatal: didn't find priority 'LOG_ER', exiting
startproc:  exit status of parent of /usr/sbin/policyd: 255
                                                                                                                                                         failed
console:~ #

Different but no clue (to me) on what to do next.....


Regards, Martin

7

Re: Dovecot stops after upgrade of SuSE 11.3 to 11.4?

mprowe wrote:

policyd: fatal: didn't find priority 'LOG_ER', exiting

Change "SYSLOG_FACILITY" in /etc/policyd.conf, like below:

FACILITY="LOG_MAIL|LOG_INFO"

8

Re: Dovecot stops after upgrade of SuSE 11.3 to 11.4?

Hi Zhang,

No that won’t work for me! As I said above, it changes the symptoms but policyd will still not start.

What I have done that seems to be working is to revert back the the 32bit version.
Using policyd 1.82-1.1-x86_64 fails ...
          policyd 1.82-1.1-i586 WORKS?

Regards, Martin

9

Re: Dovecot stops after upgrade of SuSE 11.3 to 11.4?

I had the same problem.
Tried to chmod 777 to all files that did not had priviledges
nothing happened

UNTIL i DISABLED AppArmor

http://www.iredmail.org/forum/topic2087 … o-114.html

Disable apparmor and then the dovecot will start

I have some more issues but te result of staring the service dovecot is :

Starting dovecot ILoading modules from directory: /usr/lib64/dovecot/modules/imap
IModule loaded: /usr/lib64/dovecot/modules/imap/lib10_quota_plugin.so
IModule loaded: /usr/lib64/dovecot/modules/imap/lib11_imap_quota_plugin.so
IModule loaded: /usr/lib64/dovecot/modules/imap/lib20_autocreate_plugin.so
IEffective uid=65534, gid=65533, home=/tmp
IQuota root: name=user backend=dict args=:proxy::quotadict
IQuota rule: root=user mailbox=* bytes=0 messages=0
IQuota warning: bytes=0 (85%) messages=0 command=/usr/local/bin/dovecot-quota-warning.sh 85
IQuota warning: bytes=0 (90%) messages=0 command=/usr/local/bin/dovecot-quota-warning.sh 90
IQuota warning: bytes=0 (95%) messages=0 command=/usr/local/bin/dovecot-quota-warning.sh 95
                                                                     done

10

Re: Dovecot stops after upgrade of SuSE 11.3 to 11.4?

chasapis christos wrote:

I have some more issues but te result of staring the service dovecot is :
Starting dovecot ILoading modules from directory: /usr/lib64/dovecot/modules/imap
IModule loaded: /usr/lib64/dovecot/modules/imap/lib10_quota_plugin.so

You turn on debug mode in Dovecot, so there're so many debug message.

mail_debug = no

11

Re: Dovecot stops after upgrade of SuSE 11.3 to 11.4?

chasapis christos wrote:

I had the same problem.
Tried to chmod 777 to all files that did not had priviledges
nothing happened

UNTIL i DISABLED AppArmor

Thank you!!!! I tried to fix this problem several weeks and nobody  knew what to do, until i find your message here. I edited AppArmor config by adding "/var/log/*" with "rw" permissions in all profiles with "dovecot" in names and dovecot successfully started.
P.S. Sorry for my english - i'm russian smile