Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 05-23-2011, 07:35 PM
Intermediate Member
 
Posts: 20
Default [SOLVED] Postfix will not start in Release 7.1.0_GA_3140.RHEL5_64

Fresh install. Everything starts except the mta/postfix.

Please advise

Thanks in advance


[zimbra@atl-storemail01 ~]$ postfix start
postfix/postfix-script: warning: not owned by root: /opt/zimbra/postfix-2.7.2.2z/conf/main.cf
postfix/postfix-script: warning: not owned by root: /opt/zimbra/postfix-2.7.2.2z/conf/master.cf
postfix/postfix-script: warning: not owned by root: /opt/zimbra/postfix-2.7.2.2z/conf/master.cf.in
postfix/postfix-script: warning: not owned by postfix: /opt/zimbra/data/postfix/data/./master.lock
postfix/postfix-script: starting the Postfix mail system


antispam Running
antivirus Running
ldap Running
logger Running
mailbox Running
mta Stopped
postfix is not running
snmp Running
spell Running
stats Running
zmconfigd Running
Reply With Quote
  #2 (permalink)  
Old 05-24-2011, 12:50 PM
Elite Member
 
Posts: 305
Default

What's your /var/log/zimbra.log show when you tried to start up zimbra?

Doug
__________________
Ben Franklin quote:

"Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety."
Reply With Quote
  #3 (permalink)  
Old 05-30-2011, 11:17 PM
Member
 
Posts: 12
Default

I have the same problem from time2time.

The backup script does a stop, LVM snapshot create, start and back-up using just created snapshot:
Code:
Fri May 27 04:00:01 MSD 2011 Stopping zimbra...
Host mx40
        Stopping stats...Done.
        Stopping mta...Done.
        Stopping spell...Done.
        Stopping snmp...Done.
        Stopping cbpolicyd...Done.
        Stopping archiving...Done.
        Stopping antivirus...Done.
        Stopping antispam...Done.
        Stopping imapproxy...Done.
        Stopping memcached...Done.
        Stopping mailbox...Done.
        Stopping logger...Done.
        Stopping zmconfigd...Done.
        Stopping ldap...Done.
Fri May 27 04:00:34 MSD 2011 Creating snapshot
  Logical volume "zmsnapshot" created
Fri May 27 04:00:36 MSD 2011 Starting zimbra...
Host mx40
        Starting ldap...Done.
        Starting zmconfigd...Done.
        Starting logger...Done.
        Starting mailbox...Done.
        Starting memcached...Done.
        Starting imapproxy...Done.
        Starting antispam...Done.
        Starting antivirus...Done.
        Starting snmp...Done.
        Starting spell...Done.
        Starting mta...Done.
        Starting stats...Done.
Fri May 27 04:01:42 MSD 2011 Mounting and backing up...
And that's what zimbra.log is stating about the 'service zimbra start' command:
Code:
May 27 04:01:40 mx40 zimbramon[24634]: 24634:info: Starting snmp via zmcontrol
May 27 04:01:40 mx40 zimbramon[24634]: 24634:info: Starting spell via zmcontrol
May 27 04:01:40 mx40 zimbramon[24634]: 24634:info: Starting mta via zmcontrol
May 27 04:01:41 mx40 sudo:   zimbra : TTY=unknown ; PWD=/data/zimbra ; USER=root ; COMMAND=/opt/zimbra/libexec/zmmtastatus
May 27 04:01:41 mx40 saslauthd[26046]: detach_tty      : master pid is: 26046
May 27 04:01:41 mx40 saslauthd[26046]: ipc_init        : listening on socket: /opt/zimbra/cyrus-sasl-2.1.23.3z/state/mux
May 27 04:01:41 mx40 zimbramon[24634]: 24634:info: Starting stats via zmcontrol
May 27 04:01:44 mx40 sudo:   zimbra : TTY=unknown ; PWD=/data/zimbra ; USER=root ; COMMAND=/opt/zimbra/libexec/zmstat-fd
May 27 04:01:59 mx40 clamd[25957]: Reading databases from /opt/zimbra/data/clamav/db
May 27 00:02:00 mx40 postfix/postqueue[26719]: fatal: Queue report unavailable - mail system is down
May 27 04:02:04 mx40 clamd[25957]: Database correctly reloaded (846254 signatures)
May 27 04:02:07 mx40 sudo:   zimbra : TTY=unknown ; PWD=/data/zimbra ; USER=root ; COMMAND=/opt/zimbra/libexec/zmmailboxdmgr status
May 27 04:02:07 mx40 zmmailboxdmgr[27075]: status requested
May 27 04:02:07 mx40 zmmailboxdmgr[27075]: status OK
May 27 04:02:07 mx40 sudo:   zimbra : TTY=unknown ; PWD=/data/zimbra ; USER=root ; COMMAND=/opt/zimbra/libexec/zmmtastatus
May 27 00:02:30 mx40 postfix/postqueue[27239]: fatal: Queue report unavailable - mail system is down
May 27 00:03:00 mx40 postfix/postqueue[27274]: fatal: Queue report unavailable - mail system is down
Reply With Quote
  #4 (permalink)  
Old 06-01-2011, 06:25 AM
New Member
 
Posts: 7
Default

i had the same problem, i tryed a lot stuff, then i had to reinstall the zimbra and its fixed.
Reply With Quote
  #5 (permalink)  
Old 06-02-2011, 08:13 PM
Zimbra Employee
 
Posts: 8
Default

Check the ownership of the master.lock and /opt/zimbra/data/postfix directory.
Reply With Quote
  #6 (permalink)  
Old 06-02-2011, 11:32 PM
Member
 
Posts: 12
Default

Quote:
Originally Posted by ssatam View Post
Check the ownership of the master.lock and /opt/zimbra/data/postfix directory.
Is this an answer to my case too?
Reply With Quote
  #7 (permalink)  
Old 06-03-2011, 06:20 AM
Intermediate Member
 
Posts: 20
Default

I discovered that sendmail was still running and sitting on the port that postfix watned.

Stopped sendmail and restarted Zimbra.

Solved.

Thanks guys!!!
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.