Re: bad command startup -- throttling

From: Robert Fitzpatrick (no email)
Date: Sat Jul 02 2005 - 11:08:44 EDT

  • Next message: Wietse Venema: "Re: bad command startup -- throttling"

    On Fri, 2005-07-01 at 20:53 -0400, Wietse Venema wrote:
    > Look for obvious signs of trouble
    >
    > Postfix logs all failed and successful deliveries to a logfile.
    > The file is usually called /var/log/maillog or /var/log/mail; the
    > exact pathname is defined in the /etc/syslog.conf file.
    >
    > When Postfix does not receive or deliver mail, the first order of
    > business is to look for errors that prevent Postfix from working
    > properly:
    >
    > % egrep '(warning|error|fatal|panic):' /some/log/file | more
    >
    > Note: the most important message is near the BEGINNING of the
    > output.
    >
    Thanks, it seems a problem with the local delivery only, this is why I
    didn't notice because the machine is generally a transport and that
    works fine. I noticed when I was not getting messages in the admin cyrus
    mailbox where root messages are aliased. This is what I'm getting:

    Jul 2 00:00:16 esmtp postfix/local[40911]: warning: connect #2 to
    subsystem private/cyrus: Connection refused
    Jul 2 00:00:18 esmtp postfix/pipe[40926]: fatal: invalid option: ?
    Jul 2 00:00:19 esmtp postfix/master[1566]: warning:
    process /usr/local/libexec/postfix/pipe pid 40926 exit status
     1
    Jul 2 00:00:19 esmtp postfix/master[1566]:
    warning: /usr/local/libexec/postfix/pipe: bad command startup -- throt
    tling

    Cyrus stops and restarts fine and I can login to the mailboxes. What can
    I look for to tell me why that connection is being refused to cyrus?

    -- 
    Robert
    

  • Next message: Wietse Venema: "Re: bad command startup -- throttling"





    Hosted Email Solutions

    Invaluement Anti-Spam DNSBLs



    Powered By FreeBSD   Powered By FreeBSD