1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice

qmail - Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)

Discussion in 'Plesk for Linux - 8.x and Older' started by JC_SON, Sep 22, 2005.

  1. JC_SON

    JC_SON Guest

    0
     
    I have been having serious problems with qmail on Plesk 7.5.4 (again)

    Problem:

    Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)

    I have :

    1. Removed DrWeb
    2. Re installed qmail
    3. Tested a telnet connection from inside and outside - both refused
    4. Checked that qmHandle can read the queue's
    5. Checked smpt.psa in xinetd.d
    6. Check that qmail is running - ps aux..
    7. /etc/init.d/qmail status - reports status as stopped !!!!!
    8. Munched a banana
    9. Smelled my sneakers

    Anybody have any ideas!
    Thanks
     
  2. sieb@

    sieb@ Guest

    0
     
    What do the logs say?
     
  3. JC_SON

    JC_SON Guest

    0
     
    Sieb

    Logs with a restart:

    Sep 22 10:20:58 vps537 qmail: 1127377258.231024 delivery 3: deferral: Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/
    Sep 22 10:20:58 vps537 qmail: 1127377258.231066 status: local 0/10 remote 1/20
    Sep 22 10:20:58 vps537 qmail: 1127377258.240135 delivery 1: deferral: Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/
    Sep 22 10:20:58 vps537 qmail: 1127377258.240181 status: local 0/10 remote 0/20
    Sep 22 10:23:25 vps537 qmail: 1127377405.165559 status: exiting
    Sep 22 10:23:25 vps537 spamd[1284]: server killed by SIGTERM, shutting down
    Sep 22 10:23:25 vps537 spamd[1271]: server killed by SIGTERM, shutting down
    Sep 22 10:23:25 vps537 spamd[1282]: server killed by SIGTERM, shutting down
    Sep 22 10:27:17 vps537 qmail: 1127377637.653367 status: local 0/10 remote 0/20
    Sep 22 10:27:20 vps537 spamd[3353]: server started on port 783/tcp (running version 2.63)
    Sep 22 10:27:21 vps537 spamd[3365]: server started on UNIX domain socket /tmp/spamd_full.sock (running version 2.63)
    Sep 22 10:27:22 vps537 spamd[3367]: server started on UNIX domain socket /tmp/spamd_light.sock (running version 2.63)
    Sep 22 10:28:30 vps537 qmail: 1127377710.650156 starting delivery 1: msg 12861813 to remote anonymous@vps201.sonarola.com
    Sep 22 10:28:30 vps537 qmail: 1127377710.650214 status: local 0/10 remote 1/20
    Sep 22 10:28:30 vps537 qmail: 1127377710.650384 starting delivery 2: msg 12861815 to remote anonymous@vps201.sonarola.com
    Sep 22 10:28:30 vps537 qmail: 1127377710.650411 status: local 0/10 remote 2/20
    Sep 22 10:28:30 vps537 qmail: 1127377710.659449 delivery 2: deferral: Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/
    Sep 22 10:28:30 vps537 qmail: 1127377710.659502 status: local 0/10 remote 1/20
    Sep 22 10:28:30 vps537 qmail: 1127377710.659640 delivery 1: deferral: Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/
    Sep 22 10:28:30 vps537 qmail: 1127377710.659677 status: local 0/10 remote 0/20
    Sep 22 10:31:30 vps537 qmail: 1127377890.650136 starting delivery 3: msg 12861814 to remote anonymous@vps201.sonarola.com
    Sep 22 10:31:30 vps537 qmail: 1127377890.650197 status: local 0/10 remote 1/20
    Sep 22 10:31:30 vps537 qmail: 1127377890.650371 starting delivery 4: msg 12861817 to remote anonymous@vps201.sonarola.com
    Sep 22 10:31:30 vps537 qmail: 1127377890.650400 status: local 0/10 remote 2/20
    Sep 22 10:31:30 vps537 qmail: 1127377890.661379 delivery 3: deferral: Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/
    Sep 22 10:31:30 vps537 qmail: 1127377890.661434 status: local 0/10 remote 1/20
    Sep 22 10:31:30 vps537 qmail: 1127377890.662094 delivery 4: deferral: Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/
    Sep 22 10:31:30 vps537 qmail: 1127377890.662138 status: local 0/10 remote 0/20
     
  4. jamesyeeoc

    jamesyeeoc Guest

    0
     
     
  5. JC_SON

    JC_SON Guest

    0
     
    2. used Force
    3.1 used telnet localhost 25 - connection refused
    3.2 used telnet locahost 110 - connected ok
    5. no
    6. ps waux | grep qmail - as required for qmail to operate

    Code:
    qmails    8710  0.0  0.0  1452  356 pts/1    S    11:07   0:00 qmail-send
    qmaill    8712  0.0  0.0  1412  412 pts/1    S    11:07   0:00 splogger qmail
    root      8713  0.0  0.0  1412  312 pts/1    S    11:07   0:00 qmail-lspawn ./Maildir/
    qmailr    8714  0.0  0.0  1408  340 pts/1    S    11:07   0:00 qmail-rspawn
    qmailq    8715  0.0  0.0  1400  296 pts/1    S    11:07   0:00 qmail-clean
    root      9397  0.0  0.0  1504  448 pts/1    S    11:16   0:00 grep qmail
    
    Also
    1. did a netstat - no SMTP ports
    2. webmail can be accessed by cannot send - pear socket error reported (thats where I noticed it first)
    3. checked chmod u_s state for qmail-queue as DrWeb/Plesk does not set this flag correclty
    4. sacrificed a rubber chicken
    5. Firewall shoud not be an issue - but will check

    Further:
    1. It is a VPS
    2. Nothing was changed on this system
     
  6. jamesyeeoc

    jamesyeeoc Guest

    0
     
  7. JC_SON

    JC_SON Guest

    0
     
    1. theres a cron job to check mail every 10 mins - qmail_check - nothing odd there

    - took it out in any case

    2. Watchdog is not installed
    3. Found the dummy
     
  8. jamesyeeoc

    jamesyeeoc Guest

    0
     
    Read the other thread about the a1dummy, I don't remember if there was anything else to do other than disabling the cronjob.
     
  9. JC_SON

    JC_SON Guest

    0
     
    Removed the cron and rpm -e the files a1dummy package

    I see there is a also a 0adummy package
     
  10. jamesyeeoc

    jamesyeeoc Guest

    0
     
    I have no clue what the 0adummy package is....
     
  11. JC_SON

    JC_SON Guest

    0
     
    Still at a loss for mail

    Checked iptables -L - nor rules found
     
  12. JC_SON

    JC_SON Guest

    0
     
    Problem solved:

    Seems that xinted expected a file call smtp_psa while smtp.psa in the dir.
     
  13. jamesyeeoc

    jamesyeeoc Guest

    0
     
    Funny how the eyes play tricks on us. When I just re-read your post, in number 5 I didn't even notice you had typed 'smtp.psa' and what my eyes saw was 'smtp_psa' which is the correct filename, else I would have commented on that much earlier...
     
  14. JC_SON

    JC_SON Guest

    0
     
    The 64 000 banana question is how did that happen?
     
  15. jamesyeeoc

    jamesyeeoc Guest

    0
     
    My crystal ball is offline at the moment, but it may have been when you were uninstalling/reinstalling packages, or maybe even a typo when modifying/copying/moving the smtp_psa file when you were trying to solve the problem. If you're like me, and work too many hours until you can't see straight, it becomes quite easy to make simple typos and such.

    Have you found out what the 0adummy package is? Maybe related to the a1dummy?
     
  16. JC_SON

    JC_SON Guest

    0
     
    No - but I decided it would be wise to leave the 0dummy alone (for now).

    And on the copying of the smtp_psa file - not me - so somewhere in the upgrade/re-install process from 7.1.x to 7.4.x it happended.
     
  17. sadara

    sadara New Pleskian

    22
    73%
    Joined:
    Sep 24, 2004
    Messages:
    19
    Likes Received:
    0
    thanks a lot, people. you've just solved a problem for me.

    two questions:

    1. do you have any idea how smtp_psa gets to be renamed to smtp.psa?
    2. i'm assuming that smtps.psa should be renamed to smtps_psa, too. is this right?

    again, thanks a bunch.
     
  18. spot

    spot Guest

    0
     
    i don't know what was the name before, but today it was smtp.psa. I enabled Watchdog last night and since then qmail would not start, even when i stopped watchdog, even when I uninstalled it !!!! Qmail refused to start.
    I checked to see if these 2 files where renamed, and yes, they were .psa and not _psa.
    I changed them back, reboot, works ok, and I think right now its is sending to my mailbox mail that where received those "dead" hours - I am not sure about this yet, but surely I can send and receive mail now.
    Dimitris
     
  19. jamesyeeoc

    jamesyeeoc Guest

    0
     
    Yes, both files should have the "_" instead of the period "." in the filename. I believe it is a bug in one of their updates, but never spent the time to track it down totally. As a precaution, I put a script in cron to check/rename the files, just in case... it may not be needed, but didn't want to find out the hard way :)
     
  20. sadara

    sadara New Pleskian

    22
    73%
    Joined:
    Sep 24, 2004
    Messages:
    19
    Likes Received:
    0
    looking back through my support notes, i've come to the conclusion that it was the/a plesk 7.5.4 installer which was responsible. the problem with mail began just after a problem with the plesk cp was fixed. not exactly conclusive proof, i admit, but none of the other explanations / theories i've come across explain the phenomena better.
     
Loading...