both of my other servers its owned by exim, the permissions in the other two servers are 644, and dovecot starts just fine on those, I don't know what happened I updated my server from opensuse 12.1 to 13.2 and now dovecot is refusing to start.> From: alvin.sm@Mail.Linux-Consulting.com> Subject: Re: help, permissions issues> To: dovecot@dovecot.org> Date: Mon, 27 Jul 2015 14:47:14 -0700> CC: alvin.sm@Mail.Linux-Consulting.com> > > hi> > > Hey everyone I've tried changing the permissions with the file it is telling me is giving me the issue, restarted exim and the computer, but still can't get dovecot to start.> > > > 2.2.13> > > dovecot -F> > doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 14: ssl_cert: Can't open file /etc/exim/openssl/exim.crt: Permission denied> > wag ...> > chown root.root /etc/exim/openssl> chmod 750 /etc/exim/openssl> > chown root.root /etc/exim/openssl/exim.*> chmod 400 /etc/exim/openssl/exim.*> > OpenSSL certs should always be read only by root> > you might want to check the docs regarding uid/gid running dovecot > and uid/gid of dovenull> and permissions for the dovecot dir tree /etc/dovecot*> > wag ... i think it should not be owned by exim> > ...> > > ssl_cert = > ssl_key = > pixie dust> alvin> - http://NetworkNightmare.net/OpenSSL> - http://DDos-Mitigator.net
Try turning off Apparmor. When I did the same OpenSuSE upgrade, Apparmor messed up my dovecot installation with similar errors. I disabled Apparmor and the permissions issues disappeared. BTW, I gave up trying to re-configure Apparmor and have left it disabled with no issues.
On 27/07/2015 9:32 PM, josh schooler wrote:
both of my other servers its owned by exim, the permissions in the other two servers are 644, and dovecot starts just fine on those, I don't know what happened I updated my server from opensuse 12.1 to 13.2 and now dovecot is refusing to start.> From: alvin.sm@Mail.Linux-Consulting.com> Subject: Re: help, permissions issues> To: dovecot@dovecot.org> Date: Mon, 27 Jul 2015 14:47:14 -0700> CC: alvin.sm@Mail.Linux-Consulting.com> > > hi> > > Hey everyone I've tried changing the permissions with the file it is telling me is giving me the issue, restarted exim and the computer, but still can't get dovecot to start.> > > > 2.2.13> > > dovecot -F> > doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 14: ssl_cert: Can't open file /etc/exim/openssl/exim.crt: Permission denied> > wag ...> > chown root.root /etc/exim/openssl> chmod 750 /etc/exim/openssl> > chown root.root /etc/exim/openssl/exim.*> chmod 400 /etc/exim/openssl/exim.*> > OpenSSL certs should always be read only by root> > you might want to check the docs regarding uid/gid running dovecot > and uid/gid of dovenull> and permissions for the dovecot dir tree /etc/dovecot*> > wag ... i think it should not be owned by exim> > ...> > > ssl_cert = > ssl_key = > pixie dust> alvin> - http://NetworkNightmare.net/OpenSSL> - http://DDos-Mitigator.net
Tried disabling apparmor still a no go.
Date: Mon, 27 Jul 2015 22:23:42 -0400 From: tmorehen@ajmconsulting.ca To: dovecot@dovecot.org Subject: Re: \ help, permissions issues
Try turning off Apparmor. When I did the same OpenSuSE upgrade, Apparmor messed up my dovecot installation with similar errors. I disabled Apparmor and the permissions issues disappeared. BTW, I gave up trying to re-configure Apparmor and have left it disabled with no issues.
On 27/07/2015 9:32 PM, josh schooler wrote:
both of my other servers its owned by exim, the permissions in the other two servers are 644, and dovecot starts just fine on those, I don't know what happened I updated my server from opensuse 12.1 to 13.2 and now dovecot is refusing to start.> From: alvin.sm@Mail.Linux-Consulting.com> Subject: Re: help, permissions issues> To: dovecot@dovecot.org> Date: Mon, 27 Jul 2015 14:47:14 -0700> CC: alvin.sm@Mail.Linux-Consulting.com> > > hi> > > Hey everyone I've tried changing the permissions with the file it is telling me is giving me the issue, restarted exim and the computer, but still can't get dovecot to start.> > > > 2.2.13> > > dovecot -F> > doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 14: ssl_cert: Can't open file /etc/exim/openssl/exim.crt: Permission denied> > wag ...> > chown root.root /etc/exim/openssl> chmod 750 /etc/exim/openssl> > chown root.root /etc/exim/openssl/exim.*> chmod 400 /etc/exim/openssl/exim.*> > OpenSSL certs should always be read only by root> > you might want to check the docs regarding uid/gid running dovecot > and uid/gid of dovenull> and permissions for the dovecot dir tree /etc/dovecot*> > wag ... i think it should not be owned by exim> > ...> > > ssl_cert = > ssl_key = > pixie dust> alvin> - http://NetworkNightmare.net/OpenSSL> - http://DDos-Mitigator.net
hi josh
Try turning off Apparmor. When I did the same OpenSuSE upgrade, Apparmor messed up my dovecot installation with similar errors. I disabled Apparmor and the permissions issues disappeared. BTW, I gave up trying to re-configure Apparmor and have left it disabled with no issues.
i also do periodic rolling updates from suse-11.x to 12.x to 13.x on the same server and now just run suse-factory and need to tweek some apps/settings
in your case, i'd also check suse iptables rules and also maybe it's an issue with /etc/init.d vs systemctl
systemctl enable dovecot && systemctl restart dovecot
---> what is the output of systemctl status doveoct
pixie dust alvin
On 27/07/2015 9:32 PM, josh schooler wrote:
both of my other servers its owned by exim, the permissions in the other two servers are 644, and dovecot starts just fine on those, I don't know what happened I updated my server from opensuse 12.1 to 13.2 and now dovecot is refusing to start.
Alright I've finally gotten passed the permission issues, apparmor was the issue, I guess I wasn't fully killing the stupid thing, but now I'm having another issue trying to start dovecot
writing the configuration failed: Could not enable dovecot. Dovecot.service dovecot IMAP server Loaded: loaded (lib/systemd/system/dovecot.service; enabled) Activate: inactive (dead) since Wed 2015-07-28- 09:45:16 PDT: 39min ago Main PID 570 (code=exited status=0/SUCCESS)
July 29 9:45:15 hosting dovecot[611]: master: dovecot v2.2.12 starting up for pop3 (core dumps disabled) July 29 10:22:33 hosting systemd[1] [/lib/systemd/system/dovecot.service:6] executable path is not absolute, ignoring kill ‘cat /car/run/dovecot/Master.pid’
On Jul 28, 2015, at 2:28 PM, alvin alvin.sm@Mail.Linux-Consulting.com wrote:
hi josh
Try turning off Apparmor. When I did the same OpenSuSE upgrade, Apparmor messed up my dovecot installation with similar errors. I disabled Apparmor and the permissions issues disappeared. BTW, I gave up trying to re-configure Apparmor and have left it disabled with no issues.
i also do periodic rolling updates from suse-11.x to 12.x to 13.x on the same server and now just run suse-factory and need to tweek some apps/settings
in your case, i'd also check suse iptables rules and also maybe it's an issue with /etc/init.d vs systemctl
systemctl enable dovecot && systemctl restart dovecot
---> what is the output of systemctl status doveoct
pixie dust alvin
On 27/07/2015 9:32 PM, josh schooler wrote: both of my other servers its owned by exim, the permissions in the other two servers are 644, and dovecot starts just fine on those, I don't know what happened I updated my server from opensuse 12.1 to 13.2 and now dovecot is refusing to start.
participants (3)
-
alvin
-
josh schooler
-
Tony Morehen