127.0.0.1 Connection refused

For some reason, I am unable to send or receive messages. The senders and receivers get no error messages, but the messages get stuck in the mail queue with the error "delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]: Connection refused"
It has worked perfectly in the past. I recently began using DNS service (I wasn't previously), but now it won't work with the DNS on or off.
Correction: When I turn DNS off, I get this error: The error that the other server returned was: 550 550 #5.1.0 Address rejected [email protected] (state 14).
Message was edited by: vidgpersonrsw

The 'delivery temporarily suspended' message is coming from postfix trying to pass the message through some kind of filter process that isn't running.
For example, the anti-virus scanner runs in this manner - messages come into the server, postfix passes the message to the scanner via a custom port on 127.0.0.1 and the scanner passes it back to postfix.
You should check that all your mail components are working correctly.

Similar Messages

  • Delivery temporarly suspended : [127.0.0.1]: connection refused

    Hello everyone,
    I have some troubles getting email services up on my server.
    The plan is to run an SMTP server, POP and IMAP.
    So far, POP and IMAP seem to be working, as I can log in with different users.
    But there are no mail messages there.
    When I check my mail queue, I find many messages.
    Mostly from [email protected] or [email protected]
    when I check the message details I get this :
    Message ID: 5654199DFB
    Date: Tue Feb 14 08:30:41
    Size: 350
    Sender: [email protected]
    Recipient(s) & Status:
    [email protected]:
    delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:
    Connection refused
    When I check my smtp log I get this :
    Feb 14 09:07:31 billie postfix/cleanup[10385]: 9EB2799E96: message-id=<[email protected]>
    Feb 14 09:07:31 billie postfix/qmgr[10387]: 9EB2799E96: from=<[email protected]>, size=636, nrcpt=1 (queue active)
    Feb 14 09:07:31 billie postfix/qmgr[10387]: 2813898166: from=<[email protected]>, size=842, nrcpt=1 (queue active)
    Feb 14 09:07:31 billie postfix/qmgr[10387]: 4EBB897327: from=<[email protected]>, size=705, nrcpt=1 (queue active)
    Feb 14 09:07:31 billie postfix/qmgr[10387]: 5654199DFB: from=<[email protected]>, size=350, nrcpt=1 (queue active)
    Feb 14 09:07:31 billie postfix/qmgr[10387]: 59AE199DE6: from=<[email protected]>, size=294, nrcpt=1 (queue active)
    Feb 14 09:07:31 billie postfix/qmgr[10387]: 5C59C99DE7: from=<[email protected]>, size=1246, nrcpt=1 (queue active)
    Feb 14 09:07:31 billie postfix/qmgr[10387]: 5D3DE95689: from=<[email protected]>, size=788, nrcpt=1 (queue active)
    Feb 14 09:07:31 billie postfix/qmgr[10387]: 6F78D994E9: from=<[email protected]>, size=1748, nrcpt=1 (queue active)
    Feb 14 09:07:31 billie postfix/qmgr[10387]: A4EC699DEC from=<[email protected]>, size=45296, nrcpt=1 (queue active)
    Feb 14 09:07:31 billie postfix/qmgr[10387]: A60B0942D2: from=<[email protected]>, size=688, nrcpt=1 (queue active)
    Feb 14 09:07:31 billie postfix/smtp[10388]: connect to 127.0.0.1[127.0.0.1]: Connection refused (port 10024)
    Feb 14 09:07:31 billie postfix/qmgr[10387]: AB63D99DF4: from=<[email protected]>, size=1352, nrcpt=1 (queue active)
    Feb 14 09:07:31 billie postfix/smtp[10388]: 9EB2799E96: to=<[email protected]>, relay=none, delay=1, status=deferred (connect to 127.0.0.1[127.0.0.1]: Connection refused)
    Feb 14 09:07:31 billie postfix/qmgr[10387]: AB74995B99: from=<[email protected]>, size=658, nrcpt=1 (queue active)
    Feb 14 09:07:31 billie postfix/smtp[10389]: connect to 127.0.0.1[127.0.0.1]: Connection refused (port 10024)
    Feb 14 09:07:31 billie postfix/smtp[10389]: 2813898166: to=<[email protected]>, relay=none, delay=130692, status=deferred (connect to 127.0.0.1[127.0.0.1]: Connection refused)
    Feb 14 09:07:31 billie postfix/smtp[10388]: connect to 127.0.0.1[127.0.0.1]: Connection refused (port 10024)
    Feb 14 09:07:31 billie postfix/smtp[10388]: 4EBB897327: to=<[email protected]>, relay=none, delay=198147, status=deferred (connect to 127.0.0.1[127.0.0.1]: Connection refused)
    Feb 14 09:07:31 billie postfix/smtp[10389]: connect to 127.0.0.1[127.0.0.1]: Connection refused (port 10024)
    Feb 14 09:07:31 billie postfix/smtp[10389]: 5654199DFB: to=<[email protected]>, relay=none, delay=2210, status=deferred (connect to 127.0.0.1[127.0.0.1]: Connection refused)
    And to top the cake, here is my postconf -n :
    postconf -n
    command_directory = /usr/sbin
    config_directory = /etc/postfix
    content_filter = smtp-amavis:[127.0.0.1]:10024
    daemon_directory = /usr/libexec/postfix
    debugpeerlevel = 2
    enableserveroptions = yes
    html_directory = no
    inet_interfaces = localhost
    localrecipientmaps = proxy:unix:passwd.byname $alias_maps
    luser_relay =
    mail_owner = postfix
    mailboxsizelimit = 0
    mailbox_transport = cyrus
    mailq_path = /usr/bin/mailq
    manpage_directory = /usr/share/man
    mapsrbldomains =
    messagesizelimit = 15728640
    mydestination = $myhostname,localhost.$mydomain,localhost,domainname.be
    mydomain = domainname.be
    mydomain_fallback = localhost
    myhostname = mail.domainname.be
    mynetworks = 127.0.0.1/32,83.217.76.0/24
    mynetworks_style = host
    newaliases_path = /usr/bin/newaliases
    queue_directory = /private/var/spool/postfix
    readme_directory = /usr/share/doc/postfix
    relayhost =
    sample_directory = /usr/share/doc/postfix/examples
    sendmail_path = /usr/sbin/sendmail
    setgid_group = postdrop
    smtpdclientrestrictions = permit_mynetworks permit
    smtpdenforcetls = no
    smtpdpw_server_securityoptions = cram-md5,login,plain
    smtpdrecipientrestrictions =
    permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
    smtpdsasl_authenable = yes
    smtpdtls_certfile = /etc/certificates/Default.crt
    smtpdtls_keyfile = /etc/certificates/Default.key
    smtpduse_pwserver = yes
    smtpdusetls = no
    unknownlocal_recipient_rejectcode = 550
    virtualmailboxdomains = hash:/etc/postfix/virtual_domains
    virtual_transport = lmtp:unix:/var/imap/socket/lmtp
    Anyone an idea to fix this? I think it is just something minor, but I don't seem to find it. Maybe something involving junk-mail scanning ?
    Many many thanks for all your time.
    If there are any other questions, I'll try to answer them as soon as possible.

    This is my output
    ps -U clamav
    PID TT STAT TIME COMMAND
    58 ?? Ss 0:00.01 freshclam -d -D -pfreshclam.pid -c 1
    Tried restarts and bin/usr/amavisd start and still nothing. Also looked in the logs and found this:
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: starting. /usr/bin/amavisd at www.funsunstudio.com ama
    visd-new-2.2.0 (20041102), Unicode aware
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: user=, EUID: 0 (0); group=, EGID: 0 80 5 29 4 20 3 2 1
    0 (0 80 5 29 4 20 3 2 1 0)
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Perl version 5.008006
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Net::Server: 2006/02/15-13:19:35 Amavis (type Net::Serv
    er::PreForkSimple) starting! pid(1611)
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Net::Server: Binding to UNIX socket file /var/amavis/am
    avisd.sock using SOCK_STREAM
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Net::Server: Binding to TCP port 10024 on host 127.0.0.
    1
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Net::Server: Setting gid to "82 82"
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Net::Server: Setting uid to "82"
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Module Amavis::Conf 2.033
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Module Archive::Tar 1.22
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Module Archive::Zip 1.14
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Module Compress::Zlib 1.33
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Module Convert::TNEF 0.17
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Module Convert::UUlib 1.03
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Module DB_File 1.810
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Module MIME::Entity 5.416
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Module MIME::Parser 5.416
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Module MIME::Tools 5.416
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Module Mail::Header 1.65
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Module Mail::Internet 1.65
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Module Mail::SpamAssassin 3.000001
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Module Net::Cmd 2.26
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Module Net::SMTP 2.29
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Module Net::Server 0.87
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Module Time::HiRes 1.65
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Module Unix::Syslog 0.99
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Amavis::DB code NOT loaded
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Amavis::Cache code NOT loaded
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Lookup::SQL code NOT loaded
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Lookup::LDAP code NOT loaded
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: AMCL-in protocol code loaded
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: SMTP-in protocol code loaded
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: ANTI-VIRUS code loaded
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: ANTI-SPAM code loaded
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Unpackers code loaded
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Found $file at /usr/bin/file
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: No $arc, not using it
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Found $gzip at /usr/bin/gzip
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Found $bzip2 at /usr/bin/bzip2
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: No $lzop, not using it
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: No $lha, not using it
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: No $unarj, not using it
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Found $uncompress at /usr/bin/uncompress
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: No $unfreeze, not using it
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: No $unrar, not using it
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: No $zoo, not using it
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Found $cpio at /usr/bin/cpio
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: No $ar, not using it
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: No $rpm2cpio, not using it
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: No $cabextract, not using it
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: No $dspam, not using it
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: Found secondary av scanner Clam Antivirus - clamscan at
    /usr/bin/clamscan
    Feb 15 13:19:35 www.funsunstudio.com /usr/bin/amavisd[1611]: SpamControl: initializing Mail::SpamAssassin
    Feb 15 13:19:36 www.funsunstudio.com /usr/bin/amavisd[1611]: SpamControl: done
    Feb 15 13:20:39 www.funsunstudio.com /usr/bin/amavisd[1611]: Net::Server: 2006/02/15-13:20:39 Server closing!

  • Delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]: Connection

    All in mail in or out is sitting in the queue. I have restarted the mail server and also the entire xserve box.
    Hardware Overview:
    Machine Name: Xserve G5
    Machine Model: RackMac3,1
    CPU Type: PowerPC G5 (3.1)
    Number Of CPUs: 2
    CPU Speed: 2.3 GHz
    L2 Cache (per CPU): 512 KB
    Memory: 1 GB
    Bus Speed: 1.15 GHz
    Boot ROM Version: 5.1.7f2
    Server Version: Mac OS X Server 10.4.10 (Build 8R218)
    No matter who sends or is going to receive the email I get the following message in the queue:
    delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]: Connection refused
    here is the config
    ns1:~ administrator$ postconf -n
    command_directory = /usr/sbin
    config_directory = /etc/postfix
    content_filter = smtp-amavis:[127.0.0.1]:10024
    daemon_directory = /usr/libexec/postfix
    debugpeerlevel = 2
    enableserveroptions = yes
    html_directory = no
    inet_interfaces = all
    localrecipientmaps = proxy:unix:passwd.byname $alias_maps
    luser_relay =
    mail_owner = postfix
    mailboxsizelimit = 0
    mailbox_transport = cyrus
    mailq_path = /usr/bin/mailq
    manpage_directory = /usr/share/man
    messagesizelimit = 52428800
    mydestination = $myhostname,localhost.$mydomain,ms1.rigginsconst.com,ms1.rigginsconstruction.co m,rigginsconst.com,rigginsconstructions.com,mail.rigginsconst.com
    mydomain = rigginsconst.com
    mydomain_fallback = localhost
    myhostname = rigginsconst.com
    mynetworks = 67.94.43.194,64.208.56.97,216.237.12.146,66.162.217.99,66.162.217.100,66.162.21 7.101,66.92.226.25,208.254.27.248,194.133.15.69,66.249.2.114,64.34.161.7,74.7.73 .178,74.7.73.179,74.7.73.180,69.162.84.11,216.237.12.147,66.92.226.26,66.92.226. 27,66.92.226.28,66.92.226.29,66.92.226.30,208.254.27.249,208.254.27.250,208.254. 27.251,66.249.2.115,66.249.2.116,66.249.2.117,66.249.2.118,74.7.73.181,74.7.73.1 82,74.7.73.183,74.7.73.184,127.0.0.1,74.7.73.189,74.7.73.190
    mynetworks_style = host
    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
    smtpdpw_server_securityoptions = login,plain,gssapi,cram-md5
    smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
    smtpdsasl_authenable = yes
    smtpdtls_keyfile =
    smtpduse_pwserver = yes
    unknownlocal_recipient_rejectcode = 550
    virtualmailboxdomains =
    virtual_transport = virtual
    ns1:~ administrator$
    if I try
    sudo launchctl load -w /System/Library/LaunchDaemons/org.amavis.amavisd.plist
    as was pointed out in another post, the mail log shows:
    Oct 19 14:46:20 ns1 sudo: administrator : TTY=ttyp1 ; PWD=/Users/administrator ; USER=root ; COMMAND=/bin/launchctl load -w /System/Library/LaunchDaemons/org.amavis.amavisd.plist
    Oct 19 14:46:21 ns1 launchd: org.amavis.amavisd: exited with exit code: 255
    Oct 19 14:46:21 ns1 launchd: org.amavis.amavisd: respawning too quickly! throttling
    Oct 19 14:46:21 ns1 launchd: org.amavis.amavisd: 9 more failures without living at least 60 seconds will cause job removal
    Oct 19 14:46:21 ns1 launchd: org.amavis.amavisd: will restart in 10 seconds
    Oct 19 14:46:29 ns1 sudo: root : TTY=unknown ; PWD=/ ; USER=cyrusimap ; COMMAND=/usr/bin/cyrus/bin/cyrus-quota -r
    Oct 19 14:46:31 ns1 launchd: org.amavis.amavisd: exited with exit code: 255
    Oct 19 14:46:31 ns1 launchd: org.amavis.amavisd: respawning too quickly! throttling
    Oct 19 14:46:31 ns1 launchd: org.amavis.amavisd: 8 more failures without living at least 60 seconds will cause job removal
    Oct 19 14:46:31 ns1 launchd: org.amavis.amavisd: will restart in 10 seconds
    Oct 19 14:46:41 ns1 launchd: org.amavis.amavisd: exited with exit code: 255
    Oct 19 14:46:41 ns1 launchd: org.amavis.amavisd: respawning too quickly! throttling
    Oct 19 14:46:41 ns1 launchd: org.amavis.amavisd: 7 more failures without living at least 60 seconds will cause job removal
    Oct 19 14:46:41 ns1 launchd: org.amavis.amavisd: will restart in 10 seconds
    Oct 19 14:46:50 ns1 pop3[3528]: login: [74.7.73.178] info APOP User logged in
    Oct 19 14:46:50 ns1 pop3[3527]: login: [74.7.73.178] kimiko APOP User logged in
    Oct 19 14:46:52 ns1 launchd: org.amavis.amavisd: exited with exit code: 255
    Oct 19 14:46:52 ns1 launchd: org.amavis.amavisd: respawning too quickly! throttling
    Oct 19 14:46:52 ns1 launchd: org.amavis.amavisd: 6 more failures without living at least 60 seconds will cause job removal
    Oct 19 14:46:52 ns1 launchd: org.amavis.amavisd: will restart in 10 seconds
    Oct 19 14:47:02 ns1 launchd: org.amavis.amavisd: exited with exit code: 255
    Oct 19 14:47:02 ns1 launchd: org.amavis.amavisd: respawning too quickly! throttling
    Oct 19 14:47:02 ns1 launchd: org.amavis.amavisd: 5 more failures without living at least 60 seconds will cause job removal
    Oct 19 14:47:02 ns1 launchd: org.amavis.amavisd: will restart in 10 seconds
    Oct 19 14:47:13 ns1 launchd: org.amavis.amavisd: exited with exit code: 255
    Oct 19 14:47:13 ns1 launchd: org.amavis.amavisd: respawning too quickly! throttling
    Oct 19 14:47:13 ns1 launchd: org.amavis.amavisd: 4 more failures without living at least 60 seconds will cause job removal
    Oct 19 14:47:13 ns1 launchd: org.amavis.amavisd: will restart in 10 seconds
    Oct 19 14:47:23 ns1 launchd: org.amavis.amavisd: exited with exit code: 255
    Oct 19 14:47:23 ns1 launchd: org.amavis.amavisd: respawning too quickly! throttling
    Oct 19 14:47:23 ns1 launchd: org.amavis.amavisd: 3 more failures without living at least 60 seconds will cause job removal
    Oct 19 14:47:23 ns1 launchd: org.amavis.amavisd: will restart in 10 seconds
    Oct 19 14:47:32 ns1 sudo: root : TTY=unknown ; PWD=/ ; USER=cyrusimap ; COMMAND=/usr/bin/cyrus/bin/cyrus-quota -r
    Oct 19 14:47:34 ns1 launchd: org.amavis.amavisd: exited with exit code: 255
    Oct 19 14:47:34 ns1 launchd: org.amavis.amavisd: respawning too quickly! throttling
    Oct 19 14:47:34 ns1 launchd: org.amavis.amavisd: 2 more failures without living at least 60 seconds will cause job removal
    Oct 19 14:47:34 ns1 launchd: org.amavis.amavisd: will restart in 10 seconds
    Oct 19 14:47:44 ns1 launchd: org.amavis.amavisd: exited with exit code: 255
    Oct 19 14:47:44 ns1 launchd: org.amavis.amavisd: respawning too quickly! throttling
    Oct 19 14:47:44 ns1 launchd: org.amavis.amavisd: 1 more failure without living at least 60 seconds will cause job removal
    Oct 19 14:47:44 ns1 launchd: org.amavis.amavisd: will restart in 10 seconds
    Oct 19 14:47:50 ns1 pop3[3528]: login: [74.7.73.178] info APOP User logged in
    Oct 19 14:47:50 ns1 pop3[3528]: login: [74.7.73.178] kimiko APOP User logged in
    Oct 19 14:47:54 ns1 launchd: org.amavis.amavisd: exited with exit code: 255
    Oct 19 14:47:54 ns1 launchd: org.amavis.amavisd: respawning too quickly! throttling
    Oct 19 14:47:54 ns1 launchd: org.amavis.amavisd: too many failures in succession
    Oct 19 14:48:01 ns1 postfix/smtpd[3591]: auxpropfunc error no mechanism available\n
    Where to go from here?

    you can clear your queue by temporarily disabling the content filter.
    once you catch your breath, take a look at amavisd.log when you issue:
    sudo launchctl load -w /System/Library/LaunchDaemons/org.amavis.amavisd.plist
    The problem may be revealed down to the line#.
    -or-
    revert to a previous version of amavisd.conf
    Jeff

  • Mail queue filling up - Delivery Temporarily Suspended Connection Refused

    About 2 hours ago we stopped getting any email from our server. The mail queue is filling up. If I click on one of the messages in queue, it gives me a message of "delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]: connection refused".
    What happened????
    Thanks,
    Robert

    My configuration was running fine for months but suddenly every night amavisd stops running (I suppose after mailbfr ran). I have to launch amavisd manually with +sudo /bin/launchctl load -w /System/Library/LaunchDaemons/org.amavis.amavisd.plist+ every day.
    Maybe something is wrong with my org.amavis.amavisd.plist? Here is it:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
    <key>Label</key>
    <string>org.amavis.amavisd</string>
    <key>OnDemand</key>
    <false/>
    <key>Program</key>
    <string>/usr/bin/amavisd</string>
    <key>ProgramArguments</key>
    <array>
    <string>amavisd</string>
    <string>foreground</string>
    </array>
    <key>ServiceIPC</key>
    <false/>
    <key>UserName</key>
    <string>_amavisd</string>
    </dict>
    </plist>

  • Connection refused by host in Nagios NRPE

    Hi Experts
    I had configured Nagios in Redhat linux everthing is working smoothly
    My problem is i have Solaris 8,9,10 now i am installing NRPE plugings and NRPE in Solaris 10 to get the details of swap space & Machine load information all the compilation went smoothly.
    When i run the given below command i am getting connection refused by host.
    bash-2.05# /usr/local/nagios/libexec/check_nrpe -H 127.0.0.1
    Connection refused by host
    One more query how to start xinetd in solaris10 and other solaris platform.I saw in nagios NRPE document it says to run "make install-xinetd" if it is there how to start it i think most probly xinet is not running
    Could any please help me on this
    Thanks
    kr

    Describe your setup and what internet realated applications you've installed and i'm sure someone will be able to help you.
    - How are you connecting - via a swtich, usb or ethernet modem somehow?
    - What other apps are installed - any download managers or things that integrate with your web browser?

  • Amavisd died? - Connection refused.

    Hi!
    Suddenly my junk mail filtering (I suppose amavisd) died. When I turn it off via server admin my mail gets delivered fine. When it is turned on I read in the logs: connect to 127.0.0.1[127.0.0.1]: Connection refused
    Here is the output of my postconf -n:
    command_directory = /usr/sbin
    config_directory = /etc/postfix
    content_filter = smtp-amavis:[127.0.0.1]:10024
    daemon_directory = /usr/libexec/postfix
    debugpeerlevel = 2
    disablevrfycommand = yes
    enableserveroptions = yes
    html_directory = no
    inet_interfaces = all
    localrecipientmaps = proxy:unix:passwd.byname $alias_maps
    mail_owner = _postfix
    mailboxsizelimit = 0
    mailbox_transport = cyrus
    mailq_path = /usr/bin/mailq
    manpage_directory = /usr/share/man
    messagesizelimit = 15728640
    mydestination = $myhostname,localhost.$mydomain,localhost,kosmatschof.com,veech-vma.com
    mydomain = veech-vma.com
    mydomain_fallback = localhost
    myhostname = server.veech-vma.com
    newaliases_path = /usr/bin/newaliases
    queue_directory = /private/var/spool/postfix
    readme_directory = /usr/share/doc/postfix
    relayhost = smtp.inode.at
    sample_directory = /usr/share/doc/postfix/examples
    sendmail_path = /usr/sbin/sendmail
    setgid_group = _postdrop
    smtpsasl_passwordmaps =
    smtpdclientrestrictions = permitsaslauthenticated, permit_mynetworks, rejectrblclient zen.spamhaus.org, permit
    smtpddatarestrictions = permit_mynetworks, rejectunauthpipelining, permit
    smtpdenforcetls = no
    smtpdhelorequired = yes
    smtpdhelorestrictions = permitsaslauthenticated, permit_mynetworks, checkheloaccess hash:/etc/postfix/helo_access, rejectnon_fqdnhostname, rejectinvalidhostname, permit
    smtpdpw_server_securityoptions = plain,login,gssapi,cram-md5
    smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
    smtpdsasl_authenable = yes
    smtpdsenderrestrictions = permitsaslauthenticated, permit_mynetworks, rejectnon_fqdnsender, permit
    smtpdtls_certfile = /etc/certificates/Default.crt
    smtpdtls_keyfile = /etc/certificates/Default.key
    smtpdtlsloglevel = 0
    smtpduse_pwserver = yes
    smtpdusetls = no
    unknownlocal_recipient_rejectcode = 550
    When I issue ps U clamav I see:
    83022 ?? Ss 0:00.01 freshclam -d -c 4
    Please help and thanks so much in advance for helping me out, as I am really stuck right now.
    Chris

    Thanks for the hint, but I think my master.cf is fine:
    # Postfix master process configuration file. For details on the format
    # of the file, see the master(5) manual page (command: "man 5 master").
    # ==========================================================================
    # service type private unpriv chroot wakeup maxproc command + args
    # (yes) (yes) (yes) (never) (100)
    # ==========================================================================
    smtp inet n - n - - smtpd
    #submission inet n - n - - smtpd
    # -o smtpdenforcetls=yes
    # -o smtpdsasl_authenable=yes
    # -o smtpdclient_restrictions=permit_saslauthenticated,reject
    #smtps inet n - n - - smtpd
    # -o smtpdtlswrappermode=yes
    # -o smtpdsasl_authenable=yes
    # -o smtpdclient_restrictions=permit_saslauthenticated,reject
    #628 inet n - n - - qmqpd
    pickup fifo n - n 60 1 pickup
    -o content_filter=
    cleanup unix n - n - 0 cleanup
    qmgr fifo n - n 300 1 qmgr
    #qmgr fifo n - n 300 1 oqmgr
    tlsmgr unix - - n 1000? 1 tlsmgr
    rewrite unix - - n - - trivial-rewrite
    bounce unix - - n - 0 bounce
    defer unix - - n - 0 bounce
    trace unix - - n - 0 bounce
    verify unix - - n - 1 verify
    flush unix n - n 1000? 0 flush
    proxymap unix - - n - - proxymap
    smtp unix - - n - - smtp
    # When relaying mail as backup MX, disable fallback_relay to avoid MX loops
    relay unix - - n - - smtp
    -o fallback_relay=
    # -o smtphelotimeout=5 -o smtpconnecttimeout=5
    showq unix n - n - - showq
    error unix - - n - - error
    retry unix - - n - - error
    discard unix - - n - - discard
    local unix - n n - - local
    virtual unix - n n - - virtual
    lmtp unix - - n - - lmtp
    anvil unix - - n - 1 anvil
    scache unix - - n - 1 scache
    # ====================================================================
    # Interfaces to non-Postfix software. Be sure to examine the manual
    # pages of the non-Postfix software to find out what options it wants.
    # Many of the following services use the Postfix pipe(8) delivery
    # agent. See the pipe(8) man page for information about ${recipient}
    # and other message envelope options.
    # ====================================================================
    # maildrop. See the Postfix MAILDROP_README file for details.
    # Also specify in main.cf: maildropdestination_recipientlimit=1
    #maildrop unix - n n - - pipe
    # flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${recipient}
    # ====================================================================
    # The Cyrus deliver program has changed incompatibly, multiple times.
    #old-cyrus unix - n n - - pipe
    # flags=R user=cyrus argv=/cyrus/bin/deliver -e -m ${extension} ${user}
    # ====================================================================
    # Cyrus 2.1.5 (Amos Gouaux)
    # Also specify in main.cf: cyrusdestination_recipientlimit=1
    cyrus unix - n n - - pipe
    user=_cyrus argv=/usr/bin/cyrus/bin/deliver -e -r ${sender} -m ${extension} ${user}
    # ====================================================================
    # See the Postfix UUCP_README file for configuration details.
    #uucp unix - n n - - pipe
    # flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
    # ====================================================================
    # Other external delivery methods.
    #ifmail unix - n n - - pipe
    # flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient)
    #bsmtp unix - n n - - pipe
    # flags=Fq. user=bsmtp argv=/usr/local/sbin/bsmtp -f $sender $nexthop $recipient
    #scalemail-backend unix - n n - 2 pipe
    # flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store
    # ${nexthop} ${user} ${extension}
    #mailman unix - n n - - pipe
    # flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
    # ${nexthop} ${user}

  • I am set up mac mini and when I test the mail server by sending a mail from administrator to administrator I get the error message 'Diagnostic-Code: X-Postfix; connect to 127.0.0.1[127.0.0.1]:10024: Connection    refused'. Can any one suggest a solution

    I set up mac mini and when I test the mail server by sending a mail from administrator to administrator I get the error message 'Diagnostic-Code: X-Postfix; connect to 127.0.0.1[127.0.0.1]:10024: Connection    refused'. Can any one suggest a solution

    Thanks. Where could I possibly look for a firewall rule. I knowingly did not creat any. My system has internet coming to a Modem which then is connected to a wireless router. I have computers connecting to the router through cable as well as wireless. One of these computers has been our  mailserver using Mercury and Pegasus and that computer has a static IP address. The Mac Mini also has been assigned a different srtatic IP address. I have only set up user account, none of them an email account as I initially expect them to receive only internal mails. Is it necessary that I must set up an email id for each user while setting up the user account. My server id is server.local. So would the email id for local users be [email protected]?

  • Connection refused to host 127.0.0.1  (Lookup  windows -- Linux)

    Hi Folks,
    Buddies I am facing a problem. My server is running at specified port on a linux machine but when I try to connect it from a windows machine i got error massage "Connection refused to host 127.0.0.1 " but it's very inscrutable message.
    I made some changes in /etc/hosts file and /etc/xinetd.d/services and everything worked fine.
    But now there is a question come in my mind that , Is there any alternative so we don't need to make any change in above mentioned two files.
    My Changes;
    /etc/host
    I've added system ip and name in the first line.
    /etc/xinetd.d/services
    Modified services files and enabled protocol and permitted to all system who are under class three network.
    Could anybody have a better idead to avoid these changes because of security issues?
    --Manoj                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    Hi,,,Thanks
    When I refer to random it is when the pc in windows in his configuration of net it has " obtain ip automatic " when the ip are fixed in the configuration of net I do not have problems of (connection refused to host:name_machine) what I need is to know that I must do to solve the problem (connection refused to host:name_machine) when in the pc they have a configuration of net of obtaining ip automaticamennte,
    I dont understand when you say that..."you should always set java.rmi.server.hostname at server JVMs to the FQDN of the host, not the IP address." Where I do this ??, where I put it??, I dont understand
    you can help me to know if this could solve my problem when the ip is obtained automatically
    this it is my code...
    public static UserPreferences systemPrefs;
    static
    try
    Configuration cfgServer = (Configuration) Registry.lookupServer(Configuration.class);
    systemPrefs = cfgServer.getSystemPreferences();
    catch (Exception e)
    Logger log = LoggerFactory.getLogger(AlertManagerServer.class);
    log.error("Error obteniendo las preferencias para Alert Manager Client", e);
    /** Puerto **/
    public static final String SERVER_PORT = systemPrefs.getString(SystemModuleDescriptor.Settings.ALERTMANAGER_SERVER_PORT, "1198");
    /** Server Name **/
    public static final String SERVER_NAME = NotificationConstants.ALERTSERVER_NAME;
    /** Client Separator **/
    public static final String ALERTCLIENT_SEPARATOR = NotificationConstants.ALERTCLIENT_SEPARATOR;
    * Constructor
    public AbstractAlertManagerClient()
    * Constructor
    * @param clientName Nombre del cliente
    * @throws Exception Problemas
    public AbstractAlertManagerClient(String clientName)
    throws Exception
    launchClient(clientName);
    * Subiendo el Cliente de Mensajeria
    * @param clientName Nombre
    * @throws ProvisioningException Problemas
    public void launchClient(String clientName)
    throws ProvisioningException
    try
    NotificationInterface notification = (NotificationInterface)Registry.lookupServer(NotificationInterface.class);
    String serverIPAddress = notification.getServerIPAddress();
    String serverInfo = "//" + serverIPAddress + ":" + SERVER_PORT + "/" + SERVER_NAME;
    AlertManagerServerInterface server = (AlertManagerServerInterface) TransparentItemProxy.getItem( serverInfo,new Class[] { AlertManagerServerInterface.class });
    AlertManagerClient client = new AlertManagerClient();
    this.server = server;
    this.name = setClientName(clientName);
    client.server = server;
    client.name = setClientName(clientName);
    Object oclient1 = new Remote(this);
    oclient = oclient1;
    Remote.invoke(server, "registerClient", oclient1);
    catch(Exception ex)
    String msg = "";
    msg += "[ERROR] trying com.iptotal.notification.bo.AbstractAlertManagerClient.AbstractAlertManagerClient()...subiendo Client ";
    ProvisioningException pex = new ProvisioningException(ProvisioningException.ErrorCatalog.NOTIFICATION_DISPATCHING_ERROR, ex);
    Logger log = LoggerFactory.getLogger(AbstractAlertManagerClient.class);
    log.error(msg, pex);
    throw pex;
    * Registrar un Cliente
    * @param client Cliente
    public void registerClient(Object client)
    try
    String name = (String)Remote.invoke(client,"getClientName",null);
    if( ! clients.containsKey(name) )
    clients.put( name, client);
    catch(Exception ex)
    String msg = "";
    msg += "[ERROR] trying com.iptotal.notification.bo.AlertManagerServer.registerClient(1) ";
    Logger log = LoggerFactory.getLogger(AlertManagerServer.class);
    log.error(msg + " " + ex.getMessage()); // VA: para que no salgan en el log los stacktrace del CAJO no route to host
    Really Thank you for the help that you can offer me

  • SMTP not working-- connect to 127.0.0.1:10023: Connection refused

    A couple of days ago, after turning off and on spam filtering using Server Admin, mail stopped being received for all users on the OS X Server 10.4.8 machine. I have tried stopping and restarting the mail service, restarting the server, restoring lots of files in /etc/ to how they were last week, with no change. All new mail is refused, and there are hunderds of mails in the queue that can't be delivered.
    - how can I get it working again?
    - how can I recover the mail in the queue? Where is the queue stored?
    The SMTP log has entries like:
    Feb 11 21:13:47 Woomera-Xserve postfix/qmgr[130]: F3AB8D44CB8: to=<[email protected]>, orig_to=<[email protected]>, relay=none, delay=177778, status=deferred (delivery temporarily suspended: transport is unavailable)
    Feb 11 21:14:56 Woomera-Xserve postfix/smtpd[254]: warning: problem talking to server 127.0.0.1:10023: Connection refused
    and amavisd.log has entries like the following, which I think mean it is not running:
    Feb 11 20:47:56 Woomera-Xserve.local /usr/bin/amavisd[943]: SpamControl: initializing Mail::SpamAssassin
    Feb 11 20:47:57 Woomera-Xserve.local /usr/bin/amavisd[943]: SpamControl: done
    Feb 11 20:49:24 Woomera-Xserve.local /usr/bin/amavisd[943]: Net::Server: 2007/02/11-20:49:24 Server closing!
    Any ideas would be very welcome! I have no command-line experience with mail, having done almost all previous admin using Server Admin.

    Based on what you are saying, it looks like Amavis is failing for some reason. So the good news is that your server is still receiving mail. It's trying to pass that mail to Amavis for processing, but then it's finding Amavis shut down. So, it's sticking mail in the queue and waiting until you get Amavis back up and running. Don't worry about that mail queue. It's doing what it's supposed to -- storing the mail until you can get your system back up.
    Let's first verify that Amavis is or is not running.
    Make sure that your content filter is turned on. Verify that "Scan email for junk mail" and "Scan email for viruses" are checked in Server Admin --> Mail --> Settings --> Filters and then save those settings.
    Then, do the following:
    Quit Server Admin
    Open Terminal and issue the following ...
    sudo serveradmin stop mail
    [give it half a minute to shut down]
    sudo serveradmin start mail
    [give it a half minute to start up]
    Then issue ...
    ps -U clamav
    You should have several processes running under the "PID TT STAT TIME COMMAND" header (post the results here on the forum). If you do have processes running, everything is probably alright. If not, issue ...
    postconf -n
    and post the results here.

  • Problems with SSH: Connection Refused

    Greetings fellow Arch users,
    I have hit a bit of a snag that I could really use some extra help getting around. I've tried everything I can think of (and everything that Google thought might work) and I have my back rather against a wall, so I thought I'd come here to see if anyone can offer some advice.
    To make a long story short, I am a college student and am attempting to set up an ssh server on a desktop at my house so I can access it remotely from the college. I have the computer set up and the server running, however I am having difficulty making connections to it from my laptop. I know that the server is running, because I can log into it both from the server itself (sshing into local host) and from my laptop when I use the internal IP address.
    The server is on a static IP address within the network(192.168.0.75), and my router is configured to forward TCP port 1500 to it (I'm using 1500 as the port for my ssh server). However, when I attempt to log into the ssh server using my network's external IP address, the connection is refused. I used nmap to scan my network and found that, even though the proper ports are forwarded to the proper place as far as my Router's configuration interface is concerned, port 1500 is not listed as one of the open TCP ports. I also, to test it, temporarily disabled the firewalls on both the server and the client. That didn't help. The command that I am running is:
    ssh -p 1500 douglas@[external ip address
    As I am really not sure what is causing this problem, I don't know what information to provide. So here is everything that my inexperienced mind sees as likely being important. If you need anything more, let me know and I will do my best to provide it.
    Here is the sshd_config file from my server.
    # This is the sshd server system-wide configuration file. See
    # sshd_config(5) for more information.
    # This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin
    # The strategy used for options in the default sshd_config shipped with
    # OpenSSH is to specify options with their default value where
    # possible, but leave them commented. Uncommented options override the
    # default value.
    Port 1500
    #AddressFamily any
    #ListenAddress 0.0.0.0
    #ListenAddress ::
    # The default requires explicit activation of protocol 1
    #Protocol 2
    # HostKey for protocol version 1
    #HostKey /etc/ssh/ssh_host_key
    # HostKeys for protocol version 2
    #HostKey /etc/ssh/ssh_host_rsa_key
    #HostKey /etc/ssh/ssh_host_dsa_key
    #HostKey /etc/ssh/ssh_host_ecdsa_key
    # Lifetime and size of ephemeral version 1 server key
    #KeyRegenerationInterval 1h
    #ServerKeyBits 1024
    # Ciphers and keying
    #RekeyLimit default none
    # Logging
    # obsoletes QuietMode and FascistLogging
    #SyslogFacility AUTH
    #LogLevel INFO
    # Authentication:
    #LoginGraceTime 2m
    PermitRootLogin no
    #StrictModes yes
    #MaxAuthTries 6
    #MaxSessions 10
    #RSAAuthentication yes
    #PubkeyAuthentication yes
    # The default is to check both .ssh/authorized_keys and .ssh/authorized_keys2
    # but this is overridden so installations will only check .ssh/authorized_keys
    AuthorizedKeysFile .ssh/authorized_keys
    #AuthorizedPrincipalsFile none
    #AuthorizedKeysCommand none
    #AuthorizedKeysCommandUser nobody
    # For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
    #RhostsRSAAuthentication no
    # similar for protocol version 2
    #HostbasedAuthentication no
    # Change to yes if you don't trust ~/.ssh/known_hosts for
    # RhostsRSAAuthentication and HostbasedAuthentication
    #IgnoreUserKnownHosts no
    # Don't read the user's ~/.rhosts and ~/.shosts files
    #IgnoreRhosts yes
    # To disable tunneled clear text passwords, change to no here!
    #PasswordAuthentication yes
    #PermitEmptyPasswords no
    # Change to no to disable s/key passwords
    ChallengeResponseAuthentication no
    # Kerberos options
    #KerberosAuthentication no
    #KerberosOrLocalPasswd yes
    #KerberosTicketCleanup yes
    #KerberosGetAFSToken no
    # GSSAPI options
    #GSSAPIAuthentication no
    #GSSAPICleanupCredentials yes
    # Set this to 'yes' to enable PAM authentication, account processing,
    # and session processing. If this is enabled, PAM authentication will
    # be allowed through the ChallengeResponseAuthentication and
    # PasswordAuthentication. Depending on your PAM configuration,
    # PAM authentication via ChallengeResponseAuthentication may bypass
    # the setting of "PermitRootLogin without-password".
    # If you just want the PAM account and session checks to run without
    # PAM authentication, then enable this but set PasswordAuthentication
    # and ChallengeResponseAuthentication to 'no'.
    UsePAM yes
    #AllowAgentForwarding yes
    #AllowTcpForwarding yes
    #GatewayPorts no
    #X11Forwarding no
    #X11DisplayOffset 10
    #X11UseLocalhost yes
    PrintMotd no # pam does that
    #PrintLastLog yes
    #TCPKeepAlive yes
    #UseLogin no
    UsePrivilegeSeparation sandbox # Default for new installations.
    #PermitUserEnvironment no
    #Compression delayed
    #ClientAliveInterval 0
    #ClientAliveCountMax 3
    #UseDNS yes
    #PidFile /run/sshd.pid
    #MaxStartups 10:30:100
    #PermitTunnel no
    #ChrootDirectory none
    #VersionAddendum none
    # no default banner path
    #Banner none
    # override default of no subsystems
    Subsystem sftp /usr/lib/ssh/sftp-server
    # Example of overriding settings on a per-user basis
    #Match User anoncvs
    # X11Forwarding no
    # AllowTcpForwarding no
    # ForceCommand cvs server
    The ouptut of ip addr when run on the server:
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
    valid_lft forever preferred_lft forever
    2: enp8s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:21:9b:3a:be:94 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.75/24 brd 192.168.255.0 scope global enp8s0
    valid_lft forever preferred_lft forever
    inet6 fe80::221:9bff:fe3a:be94/64 scope link
    valid_lft forever preferred_lft forever
    Here is the output from running nmap on the network:
    Starting Nmap 6.40 ( http://nmap.org ) at 2013-09-28 21:05 EDT
    Initiating Ping Scan at 21:05
    Scanning address [2 ports]
    Completed Ping Scan at 21:05, 0.01s elapsed (1 total hosts)
    Initiating Parallel DNS resolution of 1 host. at 21:05
    Completed Parallel DNS resolution of 1 host. at 21:05, 0.05s elapsed
    Initiating Connect Scan at 21:05
    Scanning pa-addresss.dhcp.embarqhsd.net (address) [1000 ports]
    Discovered open port 80/tcp on address
    Discovered open port 443/tcp on address
    Discovered open port 23/tcp on address
    Discovered open port 21/tcp on address
    Completed Connect Scan at 21:05, 4.08s elapsed (1000 total ports)
    Nmap scan report for pa-address.dhcp.embarqhsd.net (address)
    Host is up (0.036s latency).
    Not shown: 995 closed ports
    PORT STATE SERVICE
    21/tcp open ftp
    23/tcp open telnet
    80/tcp open http
    443/tcp open https
    8080/tcp filtered http-proxy
    Read data files from: /usr/bin/../share/nmap
    Nmap done: 1 IP address (1 host up) scanned in 4.19 seconds
    Here is the ssh_config client-side:
    # $OpenBSD: ssh_config,v 1.27 2013/05/16 02:00:34 dtucker Exp $
    # This is the ssh client system-wide configuration file. See
    # ssh_config(5) for more information. This file provides defaults for
    # users, and the values can be changed in per-user configuration files
    # or on the command line.
    # Configuration data is parsed as follows:
    # 1. command line options
    # 2. user-specific file
    # 3. system-wide file
    # Any configuration value is only changed the first time it is set.
    # Thus, host-specific definitions should be at the beginning of the
    # configuration file, and defaults at the end.
    # Site-wide defaults for some commonly used options. For a comprehensive
    # list of available options, their meanings and defaults, please see the
    # ssh_config(5) man page.
    # Host *
    # ForwardAgent no
    # ForwardX11 no
    # RhostsRSAAuthentication no
    # RSAAuthentication yes
    # PasswordAuthentication yes
    # HostbasedAuthentication no
    # GSSAPIAuthentication no
    # GSSAPIDelegateCredentials no
    # BatchMode no
    # CheckHostIP yes
    # AddressFamily any
    # ConnectTimeout 0
    # StrictHostKeyChecking ask
    # IdentityFile ~/.ssh/identity
    # IdentityFile ~/.ssh/id_rsa
    # IdentityFile ~/.ssh/id_dsa
    # Port 22
    Protocol 2
    # Cipher 3des
    # Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc
    # MACs hmac-md5,hmac-sha1,[email protected],hmac-ripemd160
    # EscapeChar ~
    # Tunnel no
    # TunnelDevice any:any
    # PermitLocalCommand no
    # VisualHostKey no
    # ProxyCommand ssh -q -W %h:%p gateway.example.com
    # RekeyLimit 1G 1h
    Output of ssh -v during connection attempt:
    OpenSSH_6.3, OpenSSL 1.0.1e 11 Feb 2013
    debug1: Reading configuration data /home/douglas/.ssh/config
    debug1: Reading configuration data /etc/ssh/ssh_config
    debug2: ssh_connect: needpriv 0
    debug1: Connecting to address [address] port 1500.
    debug1: connect to address address port 1500: Connection refused
    ssh: connect to host address port 1500: Connection refused
    Thank you guys ahead of time. Getting this server operational is hardly critical, it is just a side project of mine, but I would really like to see it working.
    Douglas Bahr Rumbaugh
    Last edited by douglasr (2013-09-29 02:58:56)

    Okay, so I finally have the opportunity to try and log in from a remote network. And. . .  it doesn't work. Which is just my luck because I now need to wait an entire week, at least, before I can touch the server again. Anyway, running ssh with the maximum verbosity I get this output:
    douglas ~ $ ssh -vvv -p 2000 address
    OpenSSH_6.3, OpenSSL 1.0.1e 11 Feb 2013
    debug1: Reading configuration data /home/douglas/.ssh/config
    debug1: Reading configuration data /etc/ssh/ssh_config
    debug2: ssh_connect: needpriv 0
    debug1: Connecting to address [address] port 2000.
    debug1: connect to address address port 2000: Connection timed out
    ssh: connect to host address port 2000: Connection timed out
    It takes a minute or two for the command to finish with the connection timeout, as one would expect. And yes, I am reasonably sure that the address that I am using is my home network's external IP. It is dynamic, but I checked it before I left which was just over an hour ago. I guess that it may have changed. I'll know that for sure in the morning, when my server sends me an automatic email with the network's current address. In the meantime I am operating under the assumption that the address I am using is correct. What else could be the problem?

  • Lion Server postfix mail not being delivered to mailboxes. "SMTP restriction `reject_invalid_helo_hostname' after `permit' is ignored" and "connect to private/policy: Connection refused" errors.

    All, Im stumped. In fact I have been on the phone with Apple Support and this has been escalated to the top engineers, as I think its got them too..
    Anyway, here is my problem..
    I'm running an Mac Mini with OS X 10.7.4 Server. I have had mail running on it for 2 months or so, without any issues. The mail was actually migrated from 10.6 in March, and It actually went smoothly. I have 3 domains which all recieve mail and they all work (or did up until 2 weeks ago)..
    So the story is this.. I can send mail from my domains, without issue.  imap and dovecot must be working.. cause all the stored mail, can be read with the mail IMAP client.. I can even transfer mail messages from one mailbox to another with Mail client. Sending mail is a breeze, it still works and the recipients still recieve their mail. But I noticed I wasnt getting any mail at all from those mailboxes... no mail, no spam, nothing.. which is unusal. I fired up Server admin and checked out the SMTP log, and this is what it showed for every email recieved: (xxxxxx is just me hiding sensitive info)
    Jul 21 14:25:20 xxxxxxxx postfix/postscreen[65857]: CONNECT from [17.158.233.225]:41909
    Jul 21 14:25:26 xxxxxxxx postfix/postscreen[65857]: PASS OLD [17.158.233.225]:41909
    Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: connect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
    Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: warning: restriction `reject_invalid_helo_hostname' after `permit' is ignored
    Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
    Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
    Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
    Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
    Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: NOQUEUE: reject: RCPT from nk11p03mm-asmtp994.mac.com[17.158.233.225]: 451 4.3.5 Server configuration problem; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<nk11p99mm-asmtpout004.mac.com>
    Jul 21 14:25:28 azathoth postfix/smtpd[65858]: disconnect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
    Ok, now what is odd, is these rejected messages are not even appearing in the mail queue in Server Admin. I have no idea why there are not being delivered
    Ive checked my postfix main.cf file and master.cf files they both look ok.. Ive even replaced them with the main.cf.defualt.10.7 and master.cf.default.10.7 files and to no avail... same problem..
    So in summary
    I can send mail out
    IMAP is working on the client end (thus dovecot is) exsisting stored emails can be accessed, read, moved unread etc..
    mail is coming into the sever, but its being rejected. there is NO rejection email sent back to the sender.
    mail is recieved by postfix, but cyrus isnt doing anything with it.. I have no idea where it goes...
    Could anyone shed light on this...
    my main.cf file:
    # Global Postfix configuration file. This file lists only a subset
    # of all 300+ parameters. See the postconf(5) manual page for a
    # complete list.
    # The general format of each line is: parameter = value. Lines
    # that begin with whitespace continue the previous line. A value can
    # contain references to other $names or ${name}s.
    # NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
    # POSTFIX STILL WORKS AFTER EVERY CHANGE.
    # SOFT BOUNCE
    # The soft_bounce parameter provides a limited safety net for
    # testing.  When soft_bounce is enabled, mail will remain queued that
    # would otherwise bounce. This parameter disables locally-generated
    # bounces, and prevents the SMTP server from rejecting mail permanently
    # (by changing 5xx replies into 4xx replies). However, soft_bounce
    # is no cure for address rewriting mistakes or mail routing mistakes.
    # soft_bounce = no
    # LOCAL PATHNAME INFORMATION
    # The queue_directory specifies the location of the Postfix queue.
    # This is also the root directory of Postfix daemons that run chrooted.
    # See the files in examples/chroot-setup for setting up Postfix chroot
    # environments on different UNIX systems.
    queue_directory = /private/var/spool/postfix
    # The command_directory parameter specifies the location of all
    # postXXX commands.
    command_directory = /usr/sbin
    # The daemon_directory parameter specifies the location of all Postfix
    # daemon programs (i.e. programs listed in the master.cf file). This
    # directory must be owned by root.
    daemon_directory = /usr/libexec/postfix
    # QUEUE AND PROCESS OWNERSHIP
    # The mail_owner parameter specifies the owner of the Postfix queue
    # and of most Postfix daemon processes.  Specify the name of a user
    # account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
    # AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM.  In
    # particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
    # USER.
    mail_owner = _postfix
    # The default_privs parameter specifies the default rights used by
    # the local delivery agent for delivery to external file or command.
    # These rights are used in the absence of a recipient user context.
    # DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
    #default_privs = nobody
    # INTERNET HOST AND DOMAIN NAMES
    # The myhostname parameter specifies the internet hostname of this
    # mail system. The default is to use the fully-qualified domain name
    # from gethostname(). $myhostname is used as a default value for many
    # other configuration parameters.
    #myhostname = host.domain.tld
    #myhostname = virtual.domain.tld
    # The mydomain parameter specifies the local internet domain name.
    # The default is to use $myhostname minus the first component.
    # $mydomain is used as a default value for many other configuration
    # parameters.
    #mydomain = domain.tld
    # SENDING MAIL
    # The myorigin parameter specifies the domain that locally-posted
    # mail appears to come from. The default is to append $myhostname,
    # which is fine for small sites.  If you run a domain with multiple
    # machines, you should (1) change this to $mydomain and (2) set up
    # a domain-wide alias database that aliases each user to
    # [email protected].
    # For the sake of consistency between sender and recipient addresses,
    # myorigin also specifies the default domain name that is appended
    # to recipient addresses that have no @domain part.
    #myorigin = $myhostname
    #myorigin = $mydomain
    # RECEIVING MAIL
    # The inet_interfaces parameter specifies the network interface
    # addresses that this mail system receives mail on.  By default,
    azathoth:postfix root#
    azathoth:postfix root# less main.cf
    azathoth:postfix root# more main.cf
    # Global Postfix configuration file. This file lists only a subset
    # of all 300+ parameters. See the postconf(5) manual page for a
    # complete list.
    # The general format of each line is: parameter = value. Lines
    # that begin with whitespace continue the previous line. A value can
    # contain references to other $names or ${name}s.
    # NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
    # POSTFIX STILL WORKS AFTER EVERY CHANGE.
    # SOFT BOUNCE
    # The soft_bounce parameter provides a limited safety net for
    # testing.  When soft_bounce is enabled, mail will remain queued that
    # would otherwise bounce. This parameter disables locally-generated
    # bounces, and prevents the SMTP server from rejecting mail permanently
    # (by changing 5xx replies into 4xx replies). However, soft_bounce
    # is no cure for address rewriting mistakes or mail routing mistakes.
    # soft_bounce = no
    # LOCAL PATHNAME INFORMATION
    # The queue_directory specifies the location of the Postfix queue.
    # This is also the root directory of Postfix daemons that run chrooted.
    # See the files in examples/chroot-setup for setting up Postfix chroot
    # environments on different UNIX systems.
    queue_directory = /private/var/spool/postfix
    # The command_directory parameter specifies the location of all
    # postXXX commands.
    command_directory = /usr/sbin
    # The daemon_directory parameter specifies the location of all Postfix
    # daemon programs (i.e. programs listed in the master.cf file). This
    # directory must be owned by root.
    daemon_directory = /usr/libexec/postfix
    # QUEUE AND PROCESS OWNERSHIP
    # The mail_owner parameter specifies the owner of the Postfix queue
    # and of most Postfix daemon processes.  Specify the name of a user
    # account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
    # AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM.  In
    # particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
    # USER.
    mail_owner = _postfix
    # The default_privs parameter specifies the default rights used by
    # the local delivery agent for delivery to external file or command.
    # These rights are used in the absence of a recipient user context.
    # DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
    #default_privs = nobody
    # INTERNET HOST AND DOMAIN NAMES
    # The myhostname parameter specifies the internet hostname of this
    # mail system. The default is to use the fully-qualified domain name
    # from gethostname(). $myhostname is used as a default value for many
    # other configuration parameters.
    #myhostname = host.domain.tld
    #myhostname = virtual.domain.tld
    # The mydomain parameter specifies the local internet domain name.
    # The default is to use $myhostname minus the first component.
    # $mydomain is used as a default value for many other configuration
    # parameters.
    #mydomain = domain.tld
    # SENDING MAIL
    # The myorigin parameter specifies the domain that locally-posted
    # mail appears to come from. The default is to append $myhostname,
    # which is fine for small sites.  If you run a domain with multiple
    # machines, you should (1) change this to $mydomain and (2) set up
    # a domain-wide alias database that aliases each user to
    # [email protected].
    # For the sake of consistency between sender and recipient addresses,
    # myorigin also specifies the default domain name that is appended
    # to recipient addresses that have no @domain part.
    #myorigin = $myhostname
    #myorigin = $mydomain
    # RECEIVING MAIL
    # The inet_interfaces parameter specifies the network interface
    # addresses that this mail system receives mail on.  By default,
    # the software claims all active interfaces on the machine. The
    # parameter also controls delivery of mail to user@[ip.address].
    # See also the proxy_interfaces parameter, for network addresses that
    # are forwarded to us via a proxy or network address translator.
    # Note: you need to stop/start Postfix when this parameter changes.
    #inet_interfaces = all
    #inet_interfaces = $myhostname
    #inet_interfaces = $myhostname, localhost
    # The proxy_interfaces parameter specifies the network interface
    # addresses that this mail system receives mail on by way of a
    # proxy or network address translation unit. This setting extends
    # the address list specified with the inet_interfaces parameter.
    # You must specify your proxy/NAT addresses when your system is a
    # backup MX host for other domains, otherwise mail delivery loops
    # will happen when the primary MX host is down.
    #proxy_interfaces =
    #proxy_interfaces = 1.2.3.4
    # The mydestination parameter specifies the list of domains that this
    # machine considers itself the final destination for.
    # These domains are routed to the delivery agent specified with the
    # local_transport parameter setting. By default, that is the UNIX
    # compatible delivery agent that lookups all recipients in /etc/passwd
    # and /etc/aliases or their equivalent.
    # The default is $myhostname + localhost.$mydomain.  On a mail domain
    # gateway, you should also include $mydomain.
    # Do not specify the names of virtual domains - those domains are
    # specified elsewhere (see VIRTUAL_README).
    # Do not specify the names of domains that this machine is backup MX
    # host for. Specify those names via the relay_domains settings for
    # the SMTP server, or use permit_mx_backup if you are lazy (see
    # STANDARD_CONFIGURATION_README).
    # The local machine is always the final destination for mail addressed
    # to user@[the.net.work.address] of an interface that the mail system
    # receives mail on (see the inet_interfaces parameter).
    # Specify a list of host or domain names, /file/name or type:table
    # patterns, separated by commas and/or whitespace. A /file/name
    # pattern is replaced by its contents; a type:table is matched when
    # a name matches a lookup key (the right-hand side is ignored).
    # Continue long lines by starting the next line with whitespace.
    # See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
    #mydestination = $myhostname, localhost.$mydomain, localhost
    #mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
    #mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,
    #       mail.$mydomain, www.$mydomain, ftp.$mydomain
    # REJECTING MAIL FOR UNKNOWN LOCAL USERS
    # The local_recipient_maps parameter specifies optional lookup tables
    # with all names or addresses of users that are local with respect
    # to $mydestination, $inet_interfaces or $proxy_interfaces.
    # If this parameter is defined, then the SMTP server will reject
    # mail for unknown local users. This parameter is defined by default.
    # To turn off local recipient checking in the SMTP server, specify
    # local_recipient_maps = (i.e. empty).
    # The default setting assumes that you use the default Postfix local
    # delivery agent for local delivery. You need to update the
    # local_recipient_maps setting if:
    # - You define $mydestination domain recipients in files other than
    #   /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
    #   For example, you define $mydestination domain recipients in   
    #   the $virtual_mailbox_maps files.
    # - You redefine the local delivery agent in master.cf.
    # - You redefine the "local_transport" setting in main.cf.
    # - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
    #   feature of the Postfix local delivery agent (see local(8)).
    # Details are described in the LOCAL_RECIPIENT_README file.
    # Beware: if the Postfix SMTP server runs chrooted, you probably have
    # to access the passwd file via the proxymap service, in order to
    # overcome chroot restrictions. The alternative, having a copy of
    # the system passwd file in the chroot jail is just not practical.
    # The right-hand side of the lookup tables is conveniently ignored.
    # In the left-hand side, specify a bare username, an @domain.tld
    # wild-card, or specify a [email protected] address.
    #local_recipient_maps = unix:passwd.byname $alias_maps
    #local_recipient_maps = proxy:unix:passwd.byname $alias_maps
    #local_recipient_maps =
    # The unknown_local_recipient_reject_code specifies the SMTP server
    # response code when a recipient domain matches $mydestination or
    # ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
    # and the recipient address or address local-part is not found.
    # The default setting is 550 (reject mail) but it is safer to start
    # with 450 (try again later) until you are certain that your
    # local_recipient_maps settings are OK.
    unknown_local_recipient_reject_code = 550
    # TRUST AND RELAY CONTROL
    # The mynetworks parameter specifies the list of "trusted" SMTP
    # clients that have more privileges than "strangers".
    # In particular, "trusted" SMTP clients are allowed to relay mail
    # through Postfix.  See the smtpd_recipient_restrictions parameter
    # in postconf(5).
    # You can specify the list of "trusted" network addresses by hand
    # or you can let Postfix do it for you (which is the default).
    # By default (mynetworks_style = subnet), Postfix "trusts" SMTP
    # clients in the same IP subnetworks as the local machine.
    # On Linux, this does works correctly only with interfaces specified
    # with the "ifconfig" command.
    # Specify "mynetworks_style = class" when Postfix should "trust" SMTP
    # clients in the same IP class A/B/C networks as the local machine.
    # Don't do this with a dialup site - it would cause Postfix to "trust"
    # your entire provider's network.  Instead, specify an explicit
    # mynetworks list by hand, as described below.
    # Specify "mynetworks_style = host" when Postfix should "trust"
    # only the local machine.
    #mynetworks_style = class
    #mynetworks_style = subnet
    #mynetworks_style = host
    # Alternatively, you can specify the mynetworks list by hand, in
    # which case Postfix ignores the mynetworks_style setting.
    # Specify an explicit list of network/netmask patterns, where the
    # mask specifies the number of bits in the network part of a host
    # address.
    # You can also specify the absolute pathname of a pattern file instead
    # of listing the patterns here. Specify type:table for table-based lookups
    # (the value on the table right-hand side is not used).
    #mynetworks = 168.100.189.0/28, 127.0.0.0/8
    #mynetworks = $config_directory/mynetworks
    #mynetworks = hash:/etc/postfix/network_table
    # The relay_domains parameter restricts what destinations this system will
    # relay mail to.  See the smtpd_recipient_restrictions description in
    # postconf(5) for detailed information.
    # By default, Postfix relays mail
    # - from "trusted" clients (IP address matches $mynetworks) to any destination,
    # - from "untrusted" clients to destinations that match $relay_domains or
    #   subdomains thereof, except addresses with sender-specified routing.
    # The default relay_domains value is $mydestination.
    # In addition to the above, the Postfix SMTP server by default accepts mail
    # that Postfix is final destination for:
    # - destinations that match $inet_interfaces or $proxy_interfaces,
    # - destinations that match $mydestination
    # - destinations that match $virtual_alias_domains,
    # - destinations that match $virtual_mailbox_domains.
    # These destinations do not need to be listed in $relay_domains.
    # Specify a list of hosts or domains, /file/name patterns or type:name
    # lookup tables, separated by commas and/or whitespace.  Continue
    # long lines by starting the next line with whitespace. A file name
    # is replaced by its contents; a type:name table is matched when a
    # (parent) domain appears as lookup key.
    # NOTE: Postfix will not automatically forward mail for domains that
    # list this system as their primary or backup MX host. See the
    # permit_mx_backup restriction description in postconf(5).
    #relay_domains = $mydestination
    # INTERNET OR INTRANET
    # The relayhost parameter specifies the default host to send mail to
    # when no entry is matched in the optional transport(5) table. When
    # no relayhost is given, mail is routed directly to the destination.
    # On an intranet, specify the organizational domain name. If your
    # internal DNS uses no MX records, specify the name of the intranet
    # gateway host instead.
    # In the case of SMTP, specify a domain, host, host:port, [host]:port,
    # [address] or [address]:port; the form [host] turns off MX lookups.
    # If you're connected via UUCP, see also the default_transport parameter.
    #relayhost = $mydomain
    #relayhost = [gateway.my.domain]
    #relayhost = [mailserver.isp.tld]
    #relayhost = uucphost
    #relayhost = [an.ip.add.ress]
    # REJECTING UNKNOWN RELAY USERS
    # The relay_recipient_maps parameter specifies optional lookup tables
    # with all addresses in the domains that match $relay_domains.
    # If this parameter is defined, then the SMTP server will reject
    # mail for unknown relay users. This feature is off by default.
    # The right-hand side of the lookup tables is conveniently ignored.
    # In the left-hand side, specify an @domain.tld wild-card, or specify
    # a [email protected] address.
    #relay_recipient_maps = hash:/etc/postfix/relay_recipients
    # INPUT RATE CONTROL
    # The in_flow_delay configuration parameter implements mail input
    # flow control. This feature is turned on by default, although it
    # still needs further development (it's disabled on SCO UNIX due
    # to an SCO bug).
    # A Postfix process will pause for $in_flow_delay seconds before
    # accepting a new message, when the message arrival rate exceeds the
    # message delivery rate. With the default 100 SMTP server process
    # limit, this limits the mail inflow to 100 messages a second more
    # than the number of messages delivered per second.
    # Specify 0 to disable the feature. Valid delays are 0..10.
    #in_flow_delay = 1s
    # ADDRESS REWRITING
    # The ADDRESS_REWRITING_README document gives information about
    # address masquerading or other forms of address rewriting including
    # username->Firstname.Lastname mapping.
    # ADDRESS REDIRECTION (VIRTUAL DOMAIN)
    # The VIRTUAL_README document gives information about the many forms
    # of domain hosting that Postfix supports.
    # "USER HAS MOVED" BOUNCE MESSAGES
    # See the discussion in the ADDRESS_REWRITING_README document.
    # TRANSPORT MAP
    # See the discussion in the ADDRESS_REWRITING_README document.
    # ALIAS DATABASE
    # The alias_maps parameter specifies the list of alias databases used
    # by the local delivery agent. The default list is system dependent.
    # On systems with NIS, the default is to search the local alias
    # database, then the NIS alias database. See aliases(5) for syntax
    # details.
    # If you change the alias database, run "postalias /etc/aliases" (or
    # wherever your system stores the mail alias file), or simply run
    # "newaliases" to build the necessary DBM or DB file.
    # It will take a minute or so before changes become visible.  Use
    # "postfix reload" to eliminate the delay.
    #alias_maps = dbm:/etc/aliases
    #alias_maps = hash:/etc/aliases
    #alias_maps = hash:/etc/aliases, nis:mail.aliases
    #alias_maps = netinfo:/aliases
    # The alias_database parameter specifies the alias database(s) that
    # are built with "newaliases" or "sendmail -bi".  This is a separate
    # configuration parameter, because alias_maps (see above) may specify
    # tables that are not necessarily all under control by Postfix.
    #alias_database = dbm:/etc/aliases
    #alias_database = dbm:/etc/mail/aliases
    #alias_database = hash:/etc/aliases
    #alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
    # ADDRESS EXTENSIONS (e.g., user+foo)
    # The recipient_delimiter parameter specifies the separator between
    # user names and address extensions (user+foo). See canonical(5),
    # local(8), relocated(5) and virtual(5

    Ok 1st one. The warning restriction message relates to this line in main.cf:
    smtpd_helo_restrictions = permit_sasl_authenticated  permit_mynetworks  check_helo_access hash:/etc/postfix/helo_access  reject_non_fqdn_hostname  reject_invalid_hostname  permit reject_invalid_helo_hostname
    The last reject occurs after the single word "permit" and is ignored.
    However, that's not the problem.
    I'm not exactly sure what's happening, but this might be a clue.
    It would appear that either postfix is not being able to create the socket for private/policy or it's somehow created with the wrong permissions.  You might need to ramp up the debug level to get a better idea.
    You could check if it's being created by "netstat -a | grep private/policy" in terminal.
    My guess is that it's not being created because there is no setup statement in your master.cf file, but I don't understand why postfix would be looking for it if it isn't set up.  Private/policy I think relates to grey listing.  Maybe gives you a hint.

  • Sccheck fails with connection refused

    I have a 2 node cluster that was just upgraded from SC3.0 to SC3.1u4 (8/05). sccheck passes on node aemhrsDV1 and fails with the following message on aemhrsDV2:
    root@aemhrsDV2 # sccheck -b -v2 -h aemhrsDV2
    sccheck: Requesting explorer data and node report from aemhrsDV2.
    sccheck: aemhrsDV2 error: Connection refused
    sccheck: Unable to run checks on: aemhrsDV2All SC3.1 patches have been applied. All availble agents were updated using 'scinstall -u update -s all' and re-registered. Test ip addresses were supplied during 'scinstall -u update -S interact'.
    Both nodes come up fine individually in cluster (through step 10) but together the log /var/cluster/ucmm/ucmm_reconf.log shows:
    Thu Aug  9 21:47:04 EST 2007 SUNWscucm.ucmm_reconf udlm started in cmmstep2
    Thu Aug  9 21:48:44 EST 2007 SUNWscucm.ucmm_reconf udlm completed successfully in cmmstep2
    Thu Aug  9 21:48:44 EST 2007 SUNWscucm.ucmm_reconf cvm started in cmmstep2
    Thu Aug  9 21:48:45 EST 2007 SUNWscucm.ucmm_reconf cvm completed successfully in cmmstep2
    Thu Aug  9 21:48:45 EST 2007 SUNWscucm.ucmm_reconf ucmm reconfiguration step 2 completed
    Thu Aug  9 21:48:45 EST 2007 SUNWscucm.ucmm_reconf Step: cmmreturn CURRNODES=0 1Running scstat -i hangs forever at IPMP Groups with both nodes in cluster but separately displays the adapters and status.
    Node 1
    root@aemhrsDV1 # ifconfig -a
    lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
            inet 127.0.0.1 netmask ff000000
    ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
            inet 192.168.100.30 netmask ffffff00 broadcast 192.168.100.255
            ether 0:3:ba:39:f5:62
    ce0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
            inet 192.168.101.30 netmask ffffff00 broadcast 192.168.101.255
    ce1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
            inet 192.168.251.30 netmask ffffff00 broadcast 192.168.251.255
            ether 0:3:ba:39:f5:ef
    ge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
            inet 10.10.3.30 netmask ffffff00 broadcast 10.10.3.255
            groupname nafo0
            ether 0:3:ba:b:e:8
    ge0:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 4
            inet 10.10.3.31 netmask ffffff00 broadcast 10.10.3.255
    qfe0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 5
            inet 10.10.3.33 netmask ffffff00 broadcast 10.10.3.255
            groupname nafo0
            ether 0:3:ba:17:97:d5
    qfe0:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 5
            inet 10.10.3.32 netmask ffffff00 broadcast 10.10.3.255
    qfe2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 6
            inet 192.168.2.112 netmask ffffff00 broadcast 192.168.2.255
            ether 0:3:ba:17:97:d7
    qfe7: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 index 7
            inet 172.16.1.1 netmask ffffff80 broadcast 172.16.1.127
            ether 0:3:ba:17:98:68
    qfe3: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 index 8
            inet 172.16.0.129 netmask ffffff80 broadcast 172.16.0.255
            ether 0:3:ba:17:97:d8
    clprivnet0: flags=1009843<UP,BROADCAST,RUNNING,MULTICAST,MULTI_BCAST,PRIVATE,IPv4> mtu 1486 index 9
            inet 172.16.193.1 netmask ffffff00 broadcast 172.16.193.255
            ether 0:0:0:0:0:1Node 2
    root@aemhrsDV2 # ifconfig -a
    lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
            inet 127.0.0.1 netmask ff000000
    ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
            inet 192.168.100.40 netmask ffffff00 broadcast 192.168.100.255
            ether 0:3:ba:39:f5:50
    ce0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
            inet 192.168.101.40 netmask ffffff00 broadcast 192.168.101.255
    ce1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
            inet 192.168.251.40 netmask ffffff00 broadcast 192.168.251.255
            ether 0:3:ba:39:f5:20
    ge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
            inet 10.10.3.40 netmask ffffff00 broadcast 10.10.3.255
            groupname nafo0
            ether 0:3:ba:b:41:22
    ge0:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 4
            inet 10.10.3.41 netmask ffffff00 broadcast 10.10.3.255
    qfe0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 5
            inet 10.10.3.43 netmask ffffff00 broadcast 10.10.3.255
            groupname nafo0
            ether 0:3:ba:17:96:2d
    qfe0:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 5
            inet 10.10.3.42 netmask ffffff00 broadcast 10.10.3.255
    qfe0:2: flags=1040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4> mtu 1500 index 5
            inet 10.10.3.35 netmask ffffff00 broadcast 10.10.3.255
    qfe7: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 index 6
            inet 172.16.1.2 netmask ffffff80 broadcast 172.16.1.127
            ether 0:3:ba:17:97:18
    qfe3: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 index 7
            inet 172.16.0.130 netmask ffffff80 broadcast 172.16.0.255
            ether 0:3:ba:17:96:30
    clprivnet0: flags=1009843<UP,BROADCAST,RUNNING,MULTICAST,MULTI_BCAST,PRIVATE,IPv4> mtu 1486 index 8
            inet 172.16.193.2 netmask ffffff00 broadcast 172.16.193.255
            ether 0:0:0:0:0:2
    root@aemhrsDV1 # scstat
    -- Cluster Nodes --
                        Node name           Status
      Cluster node:     aemhrsDV1           Online
      Cluster node:     aemhrsDV2           Online
    -- Cluster Transport Paths --
                        Endpoint               Endpoint               Status
      Transport path:   aemhrsDV1:qfe7         aemhrsDV2:qfe7         Path online
      Transport path:   aemhrsDV1:qfe3         aemhrsDV2:qfe3         Path online
    -- Quorum Summary --
      Quorum votes possible:      3
      Quorum votes needed:        2
      Quorum votes present:       3
    -- Quorum Votes by Node --
                        Node Name           Present Possible Status
      Node votes:       aemhrsDV1           1        1       Online
      Node votes:       aemhrsDV2           1        1       Online
    -- Quorum Votes by Device --
                        Device Name         Present Possible Status
      Device votes:     /dev/did/rdsk/d3s2  1        1       Online
    -- Device Group Servers --
                             Device Group        Primary             Secondary
      Device group servers:  rmt/1               -                   -
      Device group servers:  rmt/2               -                   -
    -- Device Group Status --
                                  Device Group        Status
      Device group status:        rmt/1               Offline
      Device group status:        rmt/2               Offline
    -- Multi-owner Device Groups --
                                  Device Group        Online Status
    -- Resource Groups and Resources --
                Group Name          Resources
    Resources: nfs-test            aemhrsDVlh
    Resources: hastp-aemhrsDV1-rg  -
    Resources: hastp-aemhrsDV2-rg  -
    Resources: rac-framework-rg    rac_framework rac_udlm rac_cvm
    -- Resource Groups --
                Group Name          Node Name           State
         Group: nfs-test            aemhrsDV1           Offline
         Group: nfs-test            aemhrsDV2           Online
         Group: hastp-aemhrsDV1-rg  aemhrsDV1           Online
         Group: hastp-aemhrsDV2-rg  aemhrsDV2           Online
         Group: rac-framework-rg    aemhrsDV1           Pending online
         Group: rac-framework-rg    aemhrsDV2           Online
    -- Resources --
                Resource Name       Node Name           State     Status Message
      Resource: aemhrsDVlh          aemhrsDV1           Offline   Offline
      Resource: aemhrsDVlh          aemhrsDV2           Online    Online - LogicalHostname online.
      Resource: rac_framework       aemhrsDV1           Starting  Degraded - reconfiguration in progress
      Resource: rac_framework       aemhrsDV2           Online    Online
      Resource: rac_udlm            aemhrsDV1           Offline   Offline
      Resource: rac_udlm            aemhrsDV2           Online    Online
      Resource: rac_cvm             aemhrsDV1           Offline   Offline
      Resource: rac_cvm             aemhrsDV2           Online    Online
    -- IPMP Groups --
                  Node Name           Group   Status         Adapter   Status
                  ---------           -----   ------         -------   ------I believe the reconfig is coming from aemhrsDV2 since sccheck will not run.
    Suggestions?

    Also the output from the sccheck commad using 'ksh -x' shows where the error is occurring and exiting with a status of 107.
    The line executed is 765 of the script.
    # echo "CLASSPATH: ${CLASSPATH}"
    ${JAVA} -classpath ${CLASSPATH} ${JDEFINES_LIST} ${JAVA_CLIENT} &
    JVM_PID=$!
    + JVM_PID=13881
    # now wait for java to exit
    wait $JVM_PID
    + wait 13881
    + /usr/java/bin/java -classpath /usr/cluster/lib/sccheck:/usr/cluster/lib/sccheck/sccheck.jar:/usr/cluster/lib/sccheck/k
    ae/kae.jar:/usr/cluster/lib/sccheck/kae/kae-libs.jar:/usr/cluster/lib/sccheck/kae/eras-common.jar:/usr/cluster/lib/scche
    ck/kae/common-libs.jar:/usr/cluster/lib/sccheck/kae/eras-parsers.jar:/usr/cluster/lib/sccheck/kae/explorer-input-source.
    jar:/usr/cluster/lib/sccheck/kae/resources:/var/cluster/sccheck/tmp/client.0 -Dcom.sun.eras.common.logging4.config.file=
    /usr/cluster/lib/sccheck/sccheck.logging4.properties -Dke.client.log=/var/cluster/logs/sccheck/ke-client.log.0 -Dke.clie
    nt.xsldir=/var/cluster/sccheck/tmp/client.0 -Dsccheck.clustername=aemhrsDV -Dsccheck.clustermode=true -Dsccheck.localnam
    e=aemhrsDV2 -Dsccheck.privatelocalname=clusternode2-priv -Dsccheck.publicnodenames=aemhrsDV1,aemhrsDV2 -Dsccheck.private
    nodenames=clusternode1-priv,clusternode2-priv -Dsccheck.clientnumber=0 -Dsccheck.explorersgzDir=/var/cluster/sccheck/exp
    lorers-gz -Dsccheck.explorersUnpackDir=/var/cluster/sccheck/explorers.0 -Dsccheck.gunzip=/usr/bin/gunzip -Dsccheck.tar=/
    usr/bin/tar -Dsccheck.brief=true -Dsccheck.vverbose=true -Dsccheck.hostlist=aemhrsDV2 -Dsccheck.outputDir=/var/cluster/s
    ccheck/reports.2007-08-10.09:19:37 com.sun.cluster.sccheck.SccheckClient
    sccheck: Requesting explorer data and node report from aemhrsDV2.
    sccheck: aemhrsDV2 error: Connection refused
    sccheck: Unable to run checks on: aemhrsDV2
    typeset -i exitstatus=$?
    + typeset -i exitstatus=107
    # constuct closing message if reports were created
    if ((${exitstatus} > 0)) && ((${exitstatus} < 100)); then
        typeset severity=""
        printf ""
        case "${exitstatus}" in
            1)      severity=$(gettext '1 (LOW)');;
            2)      severity=$(gettext '2 (MODERATE)');;
            3)      severity=$(gettext '3 (HIGH)');;
            4)      severity=$(gettext '4 (CRITICAL)');;
        esac
        printf "$(gettext '%s: One or more checks failed.')\n" ${PROG}
        printf "$(gettext '%s: The greatest severity of all check failures was %s.')\n" ${PROG} "${severity}"
        printf "$(gettext '%s: Reports are in %s.')\n" ${PROG} ${OUTPUTDIR}
    fi
    + (( 107 > 0 ))
    + (( 107 < 100 ))
    cleanup
    + cleanup
    exit ${exitstatus}
    + exit 107

  • Management console connection refused

    When I tried to use the management console to connect to JRockit on another
    machine, I got the error at the end of this email. I downloaded a
    license, the application is definitely running and listening on 7091. Could
    someone provide some insight into this error?
    Thanks
    ava.rmi.ConnectException: Connection refused to host: 127.0.0.2; nested
    exception is:
    java.net.ConnectException: Connection refused
    at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574)
    at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
    at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
    at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:94)
    at
    javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Ljava.lang.Object;)Ljavax.management.remote.rmi.RMIConnection;(Unknown
    Source)
    at
    javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2229)
    at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:271)
    at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:229)
    at
    com.jrockit.console.rjmx.RJMXConnection.setupServer(RJMXConnection.java:617)
    at com.jrockit.console.rjmx.RJMXConnection.connect(RJMXConnection.java:175)
    at
    com.jrockit.console.rjmx.RJMXConnectorModel.connect(RJMXConnectorModel.java:387)
    at
    com.jrockit.console.browser.BrowserAbstractNode.connectNode(BrowserAbstractNode.java:102)
    at
    com.jrockit.console.application.AllUIOperations$4.doAction(AllUIOperations.java:127)
    at
    com.jrockit.console.application.AllUIOperations.executeAction(AllUIOperations.java:664)
    at
    com.jrockit.console.application.UIOperation.actionPerformed(UIOperation.java:311)
    at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
    at
    javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
    at
    javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
    at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
    at javax.swing.AbstractButton.doClick(AbstractButton.java:302)
    at
    javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1000)
    at workshop.core.plaf.JbMenuItemUI.doClick(JbMenuItemUI.java:640)
    at
    javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1041)
    at
    javax.swing.plaf.basic.BasicMenuItemUI$MouseInputHandler.mouseReleased(BasicMenuItemUI.java:942)
    at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231)
    at java.awt.Component.processMouseEvent(Component.java:5488)
    at javax.swing.JComponent.processMouseEvent(JComponent.java:3093)
    at java.awt.Component.processEvent(Component.java:5253)
    at java.awt.Container.processEvent(Container.java:1966)
    at java.awt.Component.dispatchEventImpl(Component.java:3955)
    at java.awt.Container.dispatchEventImpl(Container.java:2024)
    at java.awt.Component.dispatchEvent(Component.java:3803)
    Caused by: java.net.ConnectException: Connection refused
    at
    jrockit.net.SocketNativeIO.connect(Ljava.io.FileDescriptor;Ljava.net.InetAddress;III)I(Unknown
    Source)
    at java.net.AbstractSocketImpl.doConnect(Ljava.net.InetAddress;II)V(Unknown
    Source)
    at java.net.PlainSocketImpl.doConnect(Ljava.net.InetAddress;II)V(Unknown
    Source)
    at
    java.net.PlainSocketImpl.connectToAddress(Ljava.net.InetAddress;II)V(Unknown
    Source)
    at java.net.PlainSocketImpl.connect(Ljava.net.SocketAddress;I)V(Unknown
    Source)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:364)
    at java.net.Socket.connect(Socket.java:507)
    at java.net.Socket.connect(Socket.java:457)
    at java.net.Socket.<init>(Socket.java:365)
    at java.net.Socket.<init>(Socket.java:178)
    at
    sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
    at
    sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
    at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
    at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
    at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
    at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:94)
    at
    javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Ljava.lang.Object;)Ljavax.management.remote.rmi.RMIConnection;(Unknown
    Source)
    at
    javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2229)
    at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:271)
    at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:229)
    at
    com.jrockit.console.rjmx.RJMXConnection.setupServer(RJMXConnection.java:617)
    at com.jrockit.console.rjmx.RJMXConnection.connect(RJMXConnection.java:175)
    at
    com.jrockit.console.rjmx.RJMXConnectorModel.connect(RJMXConnectorModel.java:387)
    at
    com.jrockit.console.browser.BrowserAbstractNode.connectNode(BrowserAbstractNode.java:102)
    at
    com.jrockit.console.application.AllUIOperations$4.doAction(AllUIOperations.java:127)
    at
    com.jrockit.console.application.AllUIOperations.executeAction(AllUIOperations.java:664)
    at
    com.jrockit.console.application.UIOperation.actionPerformed(UIOperation.java:311)
    at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
    at
    javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
    at
    javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
    at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
    at javax.swing.AbstractButton.doClick(AbstractButton.java:302)
    Jeff

    I did that as well, but it doesn't change the error message beyond the IP address which is refusing the connection:
    Could not open Management Console for testfix.dhcp.isgenesis.com.
    java.rmi.ConnectException: Connection refused to host: 10.0.129.82; nested exception is:
         java.net.ConnectException: Connection refused: connect
    at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574)
    at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
    at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
    at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:94)
    at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown Source)
    at javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2239)
    at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:271)
    at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:229)
    at com.jrockit.console.rjmx.RJMXConnection.setupServer(RJMXConnection.java:616)
    at com.jrockit.console.rjmx.RJMXConnection.connect(RJMXConnection.java:194)
    at com.jrockit.console.rjmx.RJMXConnectorModel.connect(RJMXConnectorModel.java:209)
    at com.jrockit.mc.browser.views.JRockitBrowserToolkit.connect(JRockitBrowserToolkit.java:372)
    at com.jrockit.mc.console.ui.actions.StartConsole$1.preConnect(StartConsole.java:35)
    at com.jrockit.mc.browser.utils.PreConnectJob.run(PreConnectJob.java:56)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
    -- Caused by --
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
    at java.net.Socket.connect(Socket.java:516)
    at java.net.Socket.connect(Socket.java:466)
    at java.net.Socket.<init>(Socket.java:366)
    at java.net.Socket.<init>(Socket.java:179)
    at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
    at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
    at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
    at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
    at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
    at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:94)
    at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown Source)
    at javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2239)
    at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:271)
    at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:229)
    at com.jrockit.console.rjmx.RJMXConnection.setupServer(RJMXConnection.java:616)
    at com.jrockit.console.rjmx.RJMXConnection.connect(RJMXConnection.java:194)
    at com.jrockit.console.rjmx.RJMXConnectorModel.connect(RJMXConnectorModel.java:209)
    at com.jrockit.mc.browser.views.JRockitBrowserToolkit.connect(JRockitBrowserToolkit.java:372)
    at com.jrockit.mc.console.ui.actions.StartConsole$1.preConnect(StartConsole.java:35)

  • RMI Callback Connection Refused Problem

    we are running Red Hat Linux 9, we previously had a problem connecting a server and client running in 2 different PC's. we had the following error
    Exception in mainjava.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
    java.net.ConnectException: Connection refused
    we used the -Djava.rmi.server.hostname= <hostname> option to make it run. Now, were trying to make use of call backs this time we ran into another problem having the error:
    Exception in mainjava.rmi.ConnectException: Connection refused to host: 172.16.100.24; nested exception is:
    java.net.ConnectException: Connection refused
    what are we doing wrong?

    We already included a security manager. but the error is still there.

  • Rmi client throws Connection Refused exception

    My Rmi client throws a Connection Refused exception when i try to run it on remote machine (in this case i run it on my virtualbox macine).
    The virtualbox machine network is in NAT mode (host machine ip should be 10.0.2.2).
    When rmi client starts get registry instance and print in standar output:
    RegistryImpl_Stub[UnicastRef2 [liveRef: [endpoint:[//10.0.2.2/:1099,util,RmiInstances$1@1275d39](remote),objId:[0:0:0, 0]]]]But when rmi client trys to use any of remote methods it throws Connection Refused, but it's to strange because the Connection Refused has 127.0.1.1 as ip.
    java.rmi.ConnectException: Connection refused to host: 127.0.1.1; ....In client RmiInstances code (this class contains all remote implementations) is:
    public class RmiInstances {
        private static RmiInstances instance;
        private IUserManage userManage;
        private IAnalysis analysis;
        private IPacientManage pacientManage;
        private IInsuranceManage insuranceManage;
        private Config config;
        private RmiInstances()
                throws RemoteException, NotBoundException, IOException {
            this.config = Config.getInstance();
            Registry registry = LocateRegistry.getRegistry(config.getServerUrl()+"/",
                    1099, new RMIClientSocketFactory() {
                @Override
                public Socket createSocket(String host, int port) throws IOException {
                    try {
                        URI uri = new URI(config.getServerUrl()+
                                ":"+config.getServerPort());
                        return new Socket(uri.getHost(), uri.getPort());
                    } catch (URISyntaxException ex) {
                        ex.printStackTrace();
                        return null;
            System.out.println(registry);
            userManage = (IUserManage)registry.lookup("RUserManage");
            analysis = (IAnalysis)registry.lookup("RAnalysis");
            pacientManage = (IPacientManage)registry.lookup("RPacientManage");
            insuranceManage = (IInsuranceManage)registry.lookup("RInsuranceManage");
    ...And server code is the next:
    public static void main(String[] args) {
         System.out.println("GNULab Server " + VERSION + " starting...");
         System.setProperty("java.rmi.server.codebase",
              "file:/home/zarovich/workspace/labserver/bin");
         try {
             // Loading config
             System.out.println("Loading config...");
             Config config = Config.getInstance();
             // inicializando rmi registry
             Registry registry;
             if (config.isSsl()) {
              registry = LocateRegistry.createRegistry(
                   config.getServerPort(), new RmiSSLClient(),
                   new RmiSSLServer());
             } else
              registry = LocateRegistry
                   .createRegistry(config.getServerPort());
             // instanciando implementaciones
             RAnalysis rAnalysis = new RAnalysis();
             RInsuranceManage rInsuranceManage = new RInsuranceManage();
             RPacientManage rPacientManage = new RPacientManage();
             RUserManage rUserManage = new RUserManage();
             // registrando interfaz rmi
             registry.rebind("RAnalysis", (IAnalysis) UnicastRemoteObject.exportObject(rAnalysis, 0));
             registry.rebind("RInsuranceManage", (IInsuranceManage) UnicastRemoteObject.exportObject(rInsuranceManage, 0));
             registry.rebind("RPacientManage", (IPacientManage) UnicastRemoteObject.exportObject(rPacientManage, 0));
             registry.rebind("RUserManage", (IUserManage) UnicastRemoteObject.exportObject(rUserManage, 0));
             System.out.println("GNULab Server " + VERSION + " listening ...");
             System.out.println("Registry instance: " + registry.toString());
         } catch (RemoteException e) {
             e.printStackTrace();
            * catch (MalformedURLException e) { e.printStackTrace(); }
            */catch (IOException e) {
             // TODO Auto-generated catch block
             e.printStackTrace();
         } catch (JDOMException e) {
             // TODO Auto-generated catch block
             e.printStackTrace();
    ...

    I'm solved my problem.
    I just need run my server with -Djava.rmi.serverhost=10.0.2.2 and my client running on my virtualbox machine works!

Maybe you are looking for

  • Help needed in upload command

    Can anyone please help me in finding out the meaning of the field values of second APDU What I try to say is how the value " C4 82 03 81" is calculated. I am able to figure out rest of the values of the upload command. cm> upload -b 250 "C:\....\app\

  • PO error in process

    Hi Experts, Need your inputs on issue below: we have some cases where PO errors out due to below backend application error: -enter quantity,percentage or value for account assignment -enter g/l account I have checked with the account assignment detai

  • Adding ssd to an iMac early 2008

    I have an iMac early 2008 with a hd by sata. I have also SuperDrive by pata/IDE. If I change the hd by a ssd by sata and a 1 tb hd by pata, I will increase the speed of my iMac? Another option is to install osx on a ext. FireWire 800 ssd with a box,

  • Archivelink u2013 System refresh

    We are planning to refresh our SAP R/3 QA system with a copy of our PRD. For both systems we have a content server installed which are used for HR pictures etc but the links a created as archivelinks in R/3. Do we need to do some kind of post activit

  • IT 0024 enhancement

    Hello gurus, ive searched various threads and postings in Google, marketplace, SCN, hoe to add custom columns into IT 0024. But with no luck. I managed to add columns in TC: PM01 in List screen. Im also able to see the fields in the screen layout whe