Hello everyone,
I cannot get the Postfix service to start on my pristine copy of CentOS 6.2 (installed straight from a DVD, and 6.2 directly, not 6.0 with upgrades...not thatit should matter).
Anyway, I copied over /var/spool/mail to this system by using tar, as well as /etc/services and /etc/passwd, etc. Now, it doesn't want to start. I get permission errors like:
postfix/master: warning: /usr/libexec/postfix/pickup pid 2006 exit 1 postfix/master:warning /usr/libexec/postfix/pickup: bad command startup -- throttling postfix/pickup: fatal: scan_dir_push: open directory maildrop: permission denied
warning: the postfix sendmail command has set-uid root file permissions warning: or the command is run from a set-uid root process warning: the Postfix sendmail command must be installed without set-uid root file permissions
Now, I Googled these errors, and didn't see any good specific help for CentOS. So, I did a yum erase postfix, which also erased dependencies. After I did that, I erased the /etc/postfix directory. I then reinstalled postfix with all the dependencies...and got the same errors.
Then I googled the CentOS mailing list for help...nothing that applied to me turned up that I saw.
I'm stumped. Does anyone have any ideas what the issue could be?
Gilbert
******************************************************************************* Gilbert Sebenste ******** (My opinions only!) ****** *******************************************************************************
On Wed, 16 May 2012, Gilbert Sebenste wrote:
I'm stumped. Does anyone have any ideas what the issue could be?
Yes, you overwrote /etc/passwd and who knows what else, so it is no wonder that it is completely broken. Start again.
Steve
On Wed, 16 May 2012, Steve Thompson wrote:
On Wed, 16 May 2012, Gilbert Sebenste wrote:
I'm stumped. Does anyone have any ideas what the issue could be?
Yes, you overwrote /etc/passwd and who knows what else, so it is no wonder that it is completely broken. Start again.
Steve
No, it was the same reason I couldn't get Apache to work:
Selinux was enabled.
I disabled Selinux. Now, both work fine.
******************************************************************************* Gilbert Sebenste ******** (My opinions only!) ****** *******************************************************************************
On Wed, May 16, 2012 at 02:57:03PM -0500, Gilbert Sebenste wrote:
No, it was the same reason I couldn't get Apache to work:
Selinux was enabled.
I disabled Selinux. Now, both work fine.
Um, both work out of the box with selinux set to enforcing. There are other issues at play.
Disabling selinux is never a fix.
John
On Wed, 16 May 2012, John R. Dennison wrote:
Um, both work out of the box with selinux set to enforcing. There are other issues at play.
Disabling selinux is never a fix.
What other issues should I look for? I used apache out of the box with the default config, changed it to my server name...and it denied access. Turned off Selinux, bingo. No different than any other Apache server out there with default configs.
******************************************************************************* Gilbert Sebenste ******** (My opinions only!) ****** *******************************************************************************
On Wed, 16 May 2012, Gilbert Sebenste wrote:
On Wed, 16 May 2012, John R. Dennison wrote:
Um, both work out of the box with selinux set to enforcing. There are other issues at play.
Disabling selinux is never a fix.
Found the issue. /var/spool/mail permission wasn't set correctly. That fixed it.
******************************************************************************* Gilbert Sebenste ******** (My opinions only!) ****** *******************************************************************************
on 5/16/2012 1:03 PM John R. Dennison spake the following:
On Wed, May 16, 2012 at 02:57:03PM -0500, Gilbert Sebenste wrote:
No, it was the same reason I couldn't get Apache to work:
Selinux was enabled.
I disabled Selinux. Now, both work fine.
Um, both work out of the box with selinux set to enforcing. There are other issues at play.
Disabling selinux is never a fix.
Selinux tanked because of the mass file copies he did... The backup
files didn't have the extended attributes...
On Wed, May 16, 2012 at 2:50 PM, Gilbert Sebenste sebenste@weather.admin.niu.edu wrote:
Hello everyone,
I cannot get the Postfix service to start on my pristine copy of CentOS 6.2 (installed straight from a DVD, and 6.2 directly, not 6.0 with upgrades...not thatit should matter).
Anyway, I copied over /var/spool/mail to this system by using tar, as well as /etc/services and /etc/passwd, etc. Now, it doesn't want to start. I get permission errors like:
Did you relabel after copying? I believe you want to look at restorecon (or just relabel the whole filesystem).
http://wiki.centos.org/HowTos/SELinux
On Wed, 16 May 2012, William Hooper wrote:
Did you relabel after copying? I believe you want to look at restorecon (or just relabel the whole filesystem).
No, I didn't. And that's where the problem lies. :-) Bingo. Thanks!
Gilbert
******************************************************************************* Gilbert Sebenste ******** (My opinions only!) ****** *******************************************************************************