Results 1 to 6 of 6

Thread: Wrong Postfix Version - Post GA Upgrade

Hybrid View

  1. #1
    Join Date
    Dec 2005
    Location
    Denver, Colorado
    Posts
    8
    Rep Power
    9

    Default Wrong Postfix Version - Post GA Upgrade

    I have upgraded from M2 to GA on FC4. When attempting to start Postfix it appears that Zimbra is looking in the 2.2.3 version folders rather than 2.2.5 where smtpd resides.

    tail /var/log/zimbra.log
    Feb 8 04:11:36 zimbra zimbramon[8722]: 8722:info: 2006-02-08 04:11:07, STATUS: zimbra.XXX.local: antivirus: Running
    Feb 8 04:11:36 zimbra zimbramon[8722]: 8722:info: 2006-02-08 04:11:07, STATUS: zimbra.XXX.local: ldap: Running
    Feb 8 04:11:36 zimbra zimbramon[8722]: 8722:info: 2006-02-08 04:11:07, STATUS: zimbra.XXX.local: logger: Running
    Feb 8 04:11:37 zimbra zimbramon[8722]: 8722:info: 2006-02-08 04:11:07, STATUS: zimbra.XXX.local: mailbox: Running
    Feb 8 04:11:37 zimbra zimbramon[8722]: 8722:info: 2006-02-08 04:11:07, STATUS: zimbra.XXX.local: mta: Stopped
    Feb 8 04:11:37 zimbra zimbramon[8722]: 8722:info: 2006-02-08 04:11:07, STATUS: zimbra.XXX.local: snmp: Running
    Feb 8 04:11:37 zimbra zimbramon[8722]: 8722:info: 2006-02-08 04:11:07, STATUS: zimbra.XXX.local: spell: Running
    Feb 8 04:11:49 zimbra master[8998]: fatal: master_spawn: exec /opt/zimbra/postfix-2.2.3/libexec/smtpd: No such file or directory
    Feb 8 04:11:52 zimbra postfix/master[10380]: warning: process /opt/zimbra/postfix-2.2.3/libexec/smtpd pid 8998 exit status 1
    Feb 8 04:11:52 zimbra postfix/master[10380]: warning: /opt/zimbra/postfix-2.2.3/libexec/smtpd: bad command startup -- throttling

    /opt/zimbra/postfix-2.2.5/libexec/smtpd exist.

    Thanks for your help.
    Carl Richell | System76 | http://system76.com

  2. #2
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    19

    Default

    Have you tried shuting Zimbra all the way down? zmcontrol stop/start?
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  3. #3
    Join Date
    Dec 2005
    Location
    Denver, Colorado
    Posts
    8
    Rep Power
    9

    Default

    Quote Originally Posted by KevinH
    Have you tried shuting Zimbra all the way down? zmcontrol stop/start?
    Yeah I gave that a shot.

    [zimbra@zimbra root]$ zmcontrol stop
    Host zimbra.xxx.local
    Stopping antispam...Done
    Stopping antivirus...Done
    Stopping ldap...Done
    Stopping logger...Done
    Stopping mailbox...Done
    Stopping mta...Done
    Stopping snmp...Done
    Stopping spell...Done
    [zimbra@zimbra root]$ zmcontrol start
    Host zimbra.xxx.local
    Starting ldap...Done.
    Starting antispam...Done.
    Starting antivirus...Done.
    Starting logger...Done.
    Starting mailbox...Done.
    Starting mta...Done.
    Starting snmp...Done.
    Starting spell...Done.
    [zimbra@zimbra root]$ zmcontrol status
    Host zimbra.xxx.local
    antispam Running
    antivirus Running
    ldap Running
    logger Running
    mailbox Running
    mta Stopped
    snmp Running
    spell Running

    I received these two errors during the upgrade -

    port conflict detected: 10025 (zimbra-mta)
    port conflict detected: 25 (zimbra-mta)
    Last edited by crichell; 02-07-2006 at 10:21 PM.
    Carl Richell | System76 | http://system76.com

  4. #4
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    19

    Default

    Might want to just try editing the start scripts. grep for 2.2.3 and see which files are still refering to the old version.
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  5. #5
    Join Date
    Dec 2005
    Location
    Denver, Colorado
    Posts
    8
    Rep Power
    9

    Default

    Stopping the old postfix and starting the new one did the trick. Thanks.
    Carl Richell | System76 | http://system76.com

  6. #6
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default postfix upgrade

    Chances are that the problem is that the postfix-2.2.3 instance didn't shut down cleanly (thus the port conflicts). The current start/stop scripts reference 2.2.5, so won't kill the old version.

    ps auxww | grep postf
    kill -9 everything
    su - zimbra
    postfix start

Similar Threads

  1. Planning for Version 5 Upgrade...
    By LMStone in forum Installation
    Replies: 3
    Last Post: 07-07-2008, 08:21 AM
  2. Replies: 3
    Last Post: 11-03-2007, 10:55 PM
  3. .53 Will Not "Launch" in FF 2.0.0.6
    By jhoelz in forum Installation Help
    Replies: 4
    Last Post: 08-04-2007, 09:01 PM
  4. Replies: 6
    Last Post: 07-04-2007, 08:36 AM
  5. Admin windows shows GA version after 3.1 NE upgrade
    By sbjordal in forum Installation
    Replies: 1
    Last Post: 05-03-2006, 09:29 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •