1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Upgrade 7.5.3->7.5.4 killed qmail

Discussion in 'Plesk for Linux - 8.x and Older' started by sermad, Nov 14, 2005.

  1. sermad

    sermad Guest

    0
     
    Hi guys.

    I updated from 7.5.3 to 7.5.4 today - I obviously never got the email saying the upgrade had completed because our pop server stopped during the upgrade and never came back.

    I have rebooted.

    any ideas what I should be looking at to fix this?

    ps I did this in the faq and it did nothing -

    http://faq.swsoft.com/article_22_956_en.html
     
  2. hardweb

    hardweb Guest

    0
     
    Ok, but have you checked the log files available at:

    /tmp/psa**_upgrade.log

    ? Are you sure that the upgrade completed sucesfully?

    You can try in command line to force a qmail RPM install, but I advise you to check the log files first.
     
  3. sermad

    sermad Guest

    0
     
    Hi there.

    yes I am sure the upgrade was successful.

    Ive been tinkering with the server for about 5 hours now! I somehow DID get emails to work.

    Then I rebooted it and now they dont.

    Also when I send emails to myself I get mailbox errors.

    Also for me - that courier technote is wrong.

    My mailpasswd is at - /var/qmail/users/poppasswd - ???
     
  4. sermad

    sermad Guest

    0
     
    More errors - Getting closer.

    Seems the courier-imap is running twice on start?

    If I also run - /etc/rc.d/init.d/courier-imap restart

    I get the courier-imap service starting twice! Please help guys. I feel Im so close.

    Nov 15 02:34:29 bowden4585 qmail: qmail-send shutdown succeeded
    Nov 15 02:34:33 bowden4585 qmail: Starting qmail: succeeded
    Nov 15 02:35:33 bowden4585 courier-imap: Stopping imap succeeded
    Nov 15 02:35:33 bowden4585 courier-imap: Stopping imap-ssl succeeded
    Nov 15 02:35:33 bowden4585 courier-imap: Stopping pop3 succeeded
    Nov 15 02:35:33 bowden4585 courier-imap: Stopping pop3-ssl succeeded
    Nov 15 02:35:36 bowden4585 imapd.rc: bind: Address already in use
    Nov 15 02:35:36 bowden4585 imapd.rc: ll_daemon_start: Resource temporarily unavailable
    Nov 15 02:35:36 bowden4585 courier-imap: Starting imapd succeeded
    Nov 15 02:35:36 bowden4585 imapd-ssl.rc: bind: Address already in use
    Nov 15 02:35:36 bowden4585 imapd-ssl.rc: ll_daemon_start: Resource temporarily unavailable
    Nov 15 02:35:36 bowden4585 courier-imap: Starting imap-ssl succeeded
    Nov 15 02:35:36 bowden4585 pop3d.rc: bind: Address already in use
    Nov 15 02:35:36 bowden4585 pop3d.rc: ll_daemon_start: Resource temporarily unavailable
    Nov 15 02:35:36 bowden4585 courier-imap: Starting pop3 succeeded
    Nov 15 02:35:36 bowden4585 pop3d-ssl.rc: bind: Address already in use
    Nov 15 02:35:36 bowden4585 pop3d-ssl.rc: ll_daemon_start: Resource temporarily unavailable
    Nov 15 02:35:36 bowden4585 courier-imap: Starting pop3-ssl succeeded
     
  5. cdavis

    cdavis Guest

    0
     
    Here is a possible temporary fix. Stop the xinetd, courier-imap, and qmail services. Then start them in this order:
    qmail, courier-imap, xinetd.
    This has worked in the past. It is a temporary fix though because when the server reboots it will probably fail again.
     
  6. hardweb

    hardweb Guest

    0
     
    You have a service running on imap port. Hard to tell which is this service without taking a look to the server. You can try to get the service name running:

    netstat -lp
     
Loading...