Sep 19 03:06:03 penguin postfix/postsuper[11224]: fatal: scan_dir_push: open directory hold: No such file or directory Sep 19 03:06:04 penguin postfix/postfix-script: fatal: Postfix integrity check failed! This ebuild should be remasked. 1.1.11-r5 works fine
postfix-1.1.11.20020822.ebuild has been removed from portage. postfix-1.1.11.20020917.ebuild has been added. Please test this new vesion and let me know if the problem is fixed for you. NOTES: There is a bugfix related to postsuper in postfix-1.1.11-20020918 as well. When the ipv6 and tls patches catch up to this version I may release an upgrade to that if it fixes the related problem These are the comments regarding postsuper in the ChangeLog for 20020918. #1: Documentation: postsuper(1) did not document the -c option. #2: Bugfix: pickup should not preserve INSPECT or FILTER records from "postsuper -r". File: pickup/pickup.c.
Still the same... [20:50 root@penguin: ~] # postfix reload postfix/postfix-script: refreshing the Postfix mail system [20:50 root@penguin: ~] # postsuper: fatal: scan_dir_push: open directory hold: No such file or directory postfix check postsuper: fatal: scan_dir_push: open directory hold: No such file or directory [20:50 root@penguin: ~] # postfix stop postfix/postfix-script: stopping the Postfix mail system [20:50 root@penguin: ~] # postfix start postsuper: fatal: scan_dir_push: open directory hold: No such file or directory postfix/postfix-script: fatal: Postfix integrity check failed! [20:50 root@penguin: ~] # emerge -s postfix Searching... [ Results for search key : postfix ] [ Applications found : 1 ] * net-mail/postfix Latest version available: 1.1.11.20020917 Latest version installed: 1.1.11.20020917 Homepage: http://www.postfix.org/ Description: A fast and secure drop-in replacement for sendmail
I just emerged the latest postfix-1.1.11.20020917 on a freshly installed system. I modified /etc/mail/aliases, ran newaliases, which consequently told me to edit "myhostname" in /etc/postfix/main.cf After that I started postfix without any problems. Are you upgrading a previous installation? Have you copied configuration files from another installation? Why aren't you using the /etc/init.d/postfix start stop script? I look forward to hearing more about this issue as I have a fully functional installation working presently
Are you upgrading a previous installation? Yes Have you copied configuration files from another installation? No Why aren't you using the /etc/init.d/postfix start stop script? Because it only offers "start" and "stop"
I've just upgraded to 1.1.11.20020917 (from an existing, working installation) and I have precisely the same problem. I DO use '/etc/init.d/postfix start' to start postfix. Keith
I think this might be the fix required... Created /var/spool/postfix/hold and then try to start postfix. I will most likely be updating the ebuild this evening with this change in the source. Let me know if things work for you.
That didn't fix it for me (BUT...): root@gsgenlsb001 usr # touch /var/spool/postfix/hold root@gsgenlsb001 usr # /etc/init.d/postfix start * Starting postfix... [ !! ] root@gsgenlsb001 usr # tail /var/log/mail.log [SNIP] Sep 23 09:24:08 gsgenlsb001 postfix/postsuper[5855]: fatal: scan_dir_push: open directory hold: Not a directory Sep 23 09:24:09 gsgenlsb001 postfix/postfix-script: fatal: Postfix integrity check failed! BUT... root@gsgenlsb001 usr # rm /var/spool/postfix/hold root@gsgenlsb001 usr # mkdir /var/spool/postfix/hold root@gsgenlsb001 usr # /etc/init.d/postfix start * Starting postfix... [ ok ] DID fix it...
The ebuild has been modified. /var/spool/postfix/hold is now created manually with the ebuild. Thanks for the report.
