Hello All,
I am running postfix (apple version) with MAC OSX10.4.11 client. I
found the following entries in the "console.log".
Mar 25 13:49:23 postfix/master[2077]: fatal: open lock file pid/
master.pid: unable to set exclusive lock: Resource temporarily
unavailable
Mar 25 13:57:44 postfix/master[2096]: fatal: open lock file pid/
master.pid: unable to set exclusive lock: Resource temporarily
unavailable
Mar 25 14:06:24 postfix/master[2113]: fatal: open lock file pid/
master.pid: unable to set exclusive lock: Resource temporarily
unavailable
Mar 25 14:10:09 postfix/master[2122]: fatal: open lock file pid/
master.pid: unable to set exclusive lock: Resource temporarily
unavailable
Mar 25 14:15:10 postfix/master[2130]: fatal: open lock file pid/
master.pid: unable to set exclusive lock: Resource temporarily
unavailable
Mar 25 14:18:52 postfix/master[2140]: fatal: open lock file pid/
master.pid: unable to set exclusive lock: Resource temporarily
unavailable
I did some research on the internet and I found:
Quote
Postfix on OSX: Fatal: Open Lock File pid/master.pid
You use OSX. You change the Postfix configuration, or maybe you
install your own. You get this error throughout your mail.log:
"fatal: open lock file pid/master.pid: unable to set exclusive lock:
Resource temporarily unavailable"
I know you do, because I've seen you asking about it all over the
Internets, and no one ever has an answer. Well, try this, because it
worked for me (click through)...
Macintosh OSX 10.4 uses something called "launchd" to control daemons
(among other things). This includes the default Postfix master
executable.
When mail is received, the running Postfix master wants to handle it.
But launchd wants to handle it, too. The result is that they both try
to lock the master.pid file at the same time.
Try this command, as root (or use sudo):
#launchctl list
If you see "org.postfix.master" in the list of launchd jobs, then
this is probably what is causing the lock errors in your logs.
To fix the problem, edit the org.postfix.master.plist file in /System/
Library/LaunchDaemons (as root or using sudo):
#nano -w /System/Library/LaunchDaemons/org.postfix.master.plist
Add the following two tags within the <dict> container:
<key>Disabled</key>
<true/>
Then Restart your Mac. Do not try to restart launchd by iteself, it
will most likely put your system into an unusable state (at least, it
buggered mine when I tried it).
After restart, try launchctl list again. There should be no
org.postfix.master record. Use postfix start to launch the mail
system, send yourself a test message, and check the logs. Good luck!
EndQuote
I would like some reassurance from this list that this is the problem
and the appropriate action to correct it.
Below is the output of postconf -n.
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
debug_peer_level = 2
html_directory = no
inet_interfaces = all
mail_owner = postfix
mailbox_size_limit = 0
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
mydestination = $myhostname, localhost.$mydomain, localhost,
$mydomain, mail.$mydomain, www.$mydomain, ftp.$mydomain, domain2.tld
mydomain_fallback = mail.domin1.tld
myhostname = mail.domain1.tld
mynetworks_style = host
myorigin = $mydomain
newaliases_path = /usr/bin/newaliases
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = postdrop
smtpd_tls_key_file =
unknown_local_recipient_reject_code = 550
virtual_alias_maps = hash:/etc/postfix/virtual_alias_maps
Thanks Rupert
