[CLOSED] Postfix "fatal error" query

[trossachs]

Have just reinstalled Postfix due to a mail server prob. Emerge it as usual, but now it won't start siting the following error:

[Rob1n]

Presumably it's done some checks on the install, found existing files and decided you were reinstalling/upgrading so there was no need to create directories (especially as you might have changed them from the defaults). You could try unmerging it first to clear up the old files/directories.

[trossachs]

Have emerge -C postfix and emerge postfix some 3 times now. When I had probs earlier I removed the /var/spool/postfix directory in error and am wondering if this is the cause of the prob.

But then I would have thought that an emerge --sync then emerge postfix would have sorted the prob. Is there anyway to force creation of directories?

[Rob1n]

Not all of them, no - from the looks of things you can rerun the post-install script which will create the queue directories but not the daemon directory. The only thing I can think of is to do the "emerge -C postfix" again, check what files/directories it's not removed (these'll be indicated in the list and will probably include /etc/postfix) and delete/rename/move these before installing postfix again.

[Rob1n]

Okay, to decode the info there:

• <<< => deleted
  
• >>> => installed
  
• --- => skipped, reasons being:
  
  
  !mtime => different modification time (i.e. it's been edited since install)
  !md5 => different md5 (again, edited since install)
  !empty => the directory is not empty (either a shared directory or contains files left for the above reasons)
  
  
  

So, from the list there you can see that /etc/postfix and /var/spool/postfix are being left. These should be moved/renamed before reinstalling if you want to be sure of getting a clean install.

[trossachs]

SORTED! Have downloaded the source files from postfix.org installed the package, then emerged PF which has now found the relevant files and directories needed. All ok!

[trossachs]

Just an update for you guys, had the same prob again today some 5 months after my last post. If after downloading a fresh copy from postfix.org the problem still occurs, look into directory

[neofutur]

I just had the same problem after upgrading postfix.

files are now in libexec, I hadto update my postfix main.cf , replacing :

daemon_directory = //usr/lib/postfix

with

daemon_directory = /usr/libexec/postfix

and fixed !
_________________
http://bitcoin.gw.gd-http://ww7.pe-http://waisse.org

[cach0rr0]