At 06:09 AM 11/19/2010, you wrote: >Len Conrad: >> >> Had a power failure on a linux RHEL and postfix. disk got messed up a >> little bit but linux seemed to fix it up. all apps and services are running >> except postfix. >> >> I've had this problem before on another machine, and it was permissions. >> >> postfix set-permissions >> >> ... doesn't solve it >> >> postfix -vvv start >> >> ... gives a ton of stuff in maillog and ends with >> >> Nov 18 20:57:00 xxx.xxx.xxx postfix/postfix-script: starting the Postfix >> mail system >> >> but of course postfix is not running, no master, no postfix processes >> >> ... nothing looks different from "postfix -vvv start" maillog on machine >> where postfix does run. >> >> nothing in dmesg, nothing in system log, nothing more I can think of to coax >> postfix to tell why it won't start. >> >> suggestions? > >Yes. Does the problem change when you turn off SELINUX, APPARMOR >and similar crap?
No, can't find any of that. When the power came back up and postfix started it complained for 2000+ msgs and for every time we start/stop postfix: Nov 18 19:29:56 ms1.xxx postfix/postfix-script: warning: not owned by postfix: /mail/spool/postfix/private/scan Nov 18 19:29:56 ms1.xxx postfix/postfix-script: warning: not owned by postfix: /mail/spool/postfix/private/scan/1288699247.Vfd08I344d461M505034.ms1.xxx:2,S and postfix would just not start. I moved the 2176 msgs to a tmp directory. The scan dir ownership was fixed by running postfix-install. not sure how another guy detected that scan was bad ownership, since that finding was not logged after I moved the scan/* msgs out. I've moved the 2176 msgs back to scan and set them to postfix:wheel, but there they sit. What now? Len
