warning: connect #1 to subsystem private/proxymap: Connection refused
Patrick - South Valley Internet
I'm building a load balanced e-mail server using two Dell Opterons
running CentOS with Postfix/Dovecot that attach to an NFS point. I have
both Opterons mounting /vol/vol0/spool-mail and /vol/vol0/spool-mqueue
via /etc/fstab, and that's working fine.
I am however, getting some errors in the logfile:
Jul 6 11:10:09 pearl postfix/master[2784]: daemon started -- version
2.2.10, configuration /etc/postfix
Jul 6 11:11:08 pearl postfix/master[2784]: warning:
master_wakeup_timer_event: service public/pickup: No such device or address
Jul 6 11:12:03 pearl postfix/smtpd[3521]: warning: connect #1 to
subsystem private/proxymap: Connection refused
Jul 6 11:12:08 pearl postfix/master[2784]: warning:
master_wakeup_timer_event: service public/pickup: No such device or address
Jul 6 11:12:13 pearl postfix/smtpd[3521]: warning: connect #2 to
subsystem private/proxymap: Connection refused
Jul 6 11:12:23 pearl postfix/smtpd[3521]: warning: connect #3 to
subsystem private/proxymap: Connection refused
Jul 6 11:12:33 pearl postfix/smtpd[3521]: warning: connect #4 to
subsystem private/proxymap: Connection refused
Jul 6 11:12:43 pearl postfix/smtpd[3521]: warning: connect #5 to
subsystem priv ate/proxymap: Connection refused
Jul 6 11:12:53 pearl postfix/smtpd[3521]: warning: connect #6 to
subsystem private/proxymap: Connection refused
Jul 6 11:13:03 pearl postfix/smtpd[3521]: warning: connect #7 to
subsystem private/proxymap: Connection refused
Jul 6 11:13:08 pearl postfix/master[2784]: warning:
master_wakeup_timer_event: service public/pickup: No such device or address
Jul 6 11:13:13 pearl postfix/smtpd[3521]: warning: connect #8 to
subsystem private/proxymap: Connection refused
Jul 6 11:13:23 pearl postfix/smtpd[3521]: warning: connect #9 to
subsystem private/proxymap: Connection refused
Jul 6 11:13:33 pearl postfix/smtpd[3521]: warning: connect #10 to
subsystem private/proxymap: Connection refused
Jul 6 11:13:43 pearl postfix/smtpd[3521]: fatal: connect #11 to
subsystem private/proxymap: Connection refused
Jul 6 11:13:44 pearl postfix/master[2784]: warning: process
/usr/libexec/postfix/smtpd pid 3521 exit status 1
Jul 6 11:13:44 pearl postfix/master[2784]: warning:
/usr/libexec/postfix/smtpd: bad command startup -- throttling
Jul 6 11:14:08 pearl postfix/master[2784]: warning:
master_wakeup_timer_event: service public/pickup: No such device or address
Jul 6 11:14:44 pearl postfix/smtpd[3523]: warning: connect #1 to
subsystem private/proxymap: Connection refused
Jul 6 11:14:54 pearl postfix/smtpd[3523]: warning: connect #2 to
subsystem private/proxymap: Connection refused
Jul 6 11:15:04 pearl postfix/smtpd[3523]: warning: connect #3 to
subsystem private/proxymap: Connection refused
Jul 6 11:15:08 pearl postfix/master[2784]: warning:
master_wakeup_timer_event: service public/qmgr: No such device or address
Jul 6 11:15:08 pearl postfix/master[2784]: warning:
master_wakeup_timer_event: service public/pickup: No such device or address
Jul 6 11:15:14 pearl postfix/smtpd[3523]: warning: connect #4 to
subsystem private/proxymap: Connection refused
Jul 6 11:15:24 pearl postfix/smtpd[3523]: warning: connect #5 to
subsystem private/proxymap: Connection refused
I did a Google, and every post I found mentions something to me about
upgrading, but I'm not upgrading - this is a fresh install, and the only
items I changed in the /etc/postfix/main.cf is mail_spool_directory and
the queue_directory.
Anyone have any ideas as to what I'm doing wrong?
Thanks in advance.
Patrick
Noel Jones
>Hi all,
>
>I'm building a load balanced e-mail server using two Dell Opterons
>running CentOS with Postfix/Dovecot that attach to an NFS point. I
>have both Opterons mounting /vol/vol0/spool-mail and
>/vol/vol0/spool-mqueue via /etc/fstab, and that's working fine.
Each postfix instance must have its own queue_directory.
>Jul 6 11:10:09 pearl postfix/master[2784]: daemon started --
>version 2.2.10, configuration /etc/postfix
Hmm, postfix 2.2 appeared over 2 years ago. Last patch is 2.2.11,
released about a year ago.
The current stable version is 2.4.4, any reason to not use current
software on a new server?
Note the further behind you get, the harder it will be to get expert help here.
>Jul 6 11:11:08 pearl postfix/master[2784]: warning:
>master_wakeup_timer_event: service public/pickup: No such device or address
>Jul 6 11:12:03 pearl postfix/smtpd[3521]: warning: connect #1 to
>subsystem private/proxymap: Connection refused
"postfix set-permissions" or "postfix upgrade-configuration" may help.
Did I mention that each postfix instance must have its own queue
directory? It appears you are trying to share the queue among your
two machines - that won't work.
--
Noel Jones
Victor Duchovni
> The current stable version is 2.4.4, any reason to not use current
> software on a new server?
Minor correction, 2.4.3 is the latest stable release. The 2.4.4 release
is expected shortly (2.4.4-RC1 is available), but is not released yet.
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majo...@postfix.org?body=unsubscribe%20postfix-users>
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
Patrick - South Valley Internet
This is all good information. I honestly don't know why I don't have
the latest Postfix - I did a yum install postfix from CentOS - I'll look
into that.
I'll make sure each postfix instance has its own queue directory - this
might help a lot.
Thanks again for the help, I really appreciate it!
I will update shortly!
Patrick
Patrick - South Valley Internet
started working.
Thank you very much!
Patrick
mouss
no, you won't see latest postfix on centos. use simon mudd rpms (or
rebuild his src rpms).