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 Display Modes
  #1 (permalink)  
Old 02-10-2006, 07:02 PM
Intermediate Member
 
Posts: 15
Default Zimbra startup hangs after install CentOS 4.2

I had this same problem on Milestone 3. Just upgraded to the opensource binary install for RHEL 4 on CentOS 4. Upgrade was super smooth, actually very informative yet simple and easy.

After upgrading I still have 1 problem I had when using Milestone 3 plus a new problem.

When starting Zimbra it hangs for a very long time (sometimes hours) at this stage in the log file:

Code:
Feb 10 18:35:31 centos zimbramon[4553]: 4553:info: Starting mta
After waiting it out i finally get this in the log file after it (notice the first line has a future date?):

Code:
Feb 11 02:36:08 centos postfix/postqueue[8031]: fatal: Queue report unavailable - mail system is down
Feb 10 18:36:08 centos postfix/postfix-script: warning: not owned by root: /opt/zimbra/postfix-2.2.5/conf/main.cf
Feb 10 18:36:09 centos postfix/postfix-script: starting the Postfix mail system
Feb 10 18:36:09 centos postfix/master[8054]: daemon started -- version 2.2.5, configuration /opt/zimbra/postfix-2.2.5/conf
Feb 10 18:36:09 centos zimbramon[4553]: 4553:info: Starting snmp
Feb 10 18:36:09 centos zimbramon[4553]: 4553:info: Starting spell
Feb 10 18:36:10 centos zimbramon[7786]: 7786:info: 2006-02-10 18:36:02, STATUS: centos.h4xed.us: antispam: Running
Feb 10 18:36:10 centos zimbramon[7786]: 7786:info: 2006-02-10 18:36:02, STATUS: centos.h4xed.us: antivirus: Running
Feb 10 18:36:10 centos zimbramon[7786]: 7786:info: 2006-02-10 18:36:02, STATUS: centos.h4xed.us: ldap: Running
Feb 10 18:36:10 centos zimbramon[7786]: 7786:info: 2006-02-10 18:36:02, STATUS: centos.h4xed.us: logger: Running
Feb 10 18:36:10 centos zimbramon[7786]: 7786:info: 2006-02-10 18:36:02, STATUS: centos.h4xed.us: mailbox: Running
Feb 10 18:36:10 centos zimbramon[7786]: 7786:info: 2006-02-10 18:36:02, STATUS: centos.h4xed.us: mta: Stopped
Feb 10 18:36:10 centos zimbramon[7786]: 7786:info: 2006-02-10 18:36:02, STATUS: centos.h4xed.us: snmp: Running
Feb 10 18:36:10 centos zimbramon[7786]: 7786:info: 2006-02-10 18:36:02, STATUS: centos.h4xed.us: spell: Stopped
I'm not sure what it's hanging up on yet...

The next problem is that everything is only listening on a ipv6 socket and no ipv4. Here is what the netstat listening sockets look like:

Code:
[eger@centos ~]$ netstat -an |grep LISTEN
tcp        0      0 0.0.0.0:389                 0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:807                 0.0.0.0:*                   LISTEN
tcp        0      0 127.0.0.1:10024             0.0.0.0:*                   LISTEN
tcp        0      0 127.0.0.1:10025             0.0.0.0:*                   LISTEN
tcp        0      0 127.0.0.1:7306              0.0.0.0:*                   LISTEN
tcp        0      0 127.0.0.1:7307              0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:3310                0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:111                 0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:631                 0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:25                  0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:636                 0.0.0.0:*                   LISTEN
tcp        0      0 :::993                      :::*                        LISTEN
tcp        0      0 :::995                      :::*                        LISTEN
tcp        0      0 :::7780                     :::*                        LISTEN
tcp        0      0 ::ffff:127.0.0.1:8005       :::*                        LISTEN
tcp        0      0 :::110                      :::*                        LISTEN
tcp        0      0 :::143                      :::*                        LISTEN
tcp        0      0 :::80                       :::*                        LISTEN
tcp        0      0 :::7025                     :::*                        LISTEN
tcp        0      0 :::22                       :::*                        LISTEN
tcp        0      0 :::443                      :::*                        LISTEN
tcp        0      0 :::7071                     :::*                        LISTEN
This may be a server specific problem. I may try installing a fresh copy of CentOS 4 and starting a fresh Zimbra install.

Anyone have any ideas?
Reply With Quote
  #2 (permalink)  
Old 02-10-2006, 07:31 PM
Zimbra Employee
 
Posts: 4,784
Default

Are you running in a Virtual machine? Can you identify which process is taking a long time to start? How much CPU/RAM do you have?
__________________
Bugzilla - Wiki - Downloads - Offline Client
Reply With Quote
  #3 (permalink)  
Old 02-10-2006, 08:36 PM
Intermediate Member
 
Posts: 15
Default

I am running in a virtual machine with 384meg RAM (for the VM) and 2x2.8g xeon. I was thinking it might have something to do with the VM. I haven't identified which process it is that is taking a long time to load. I will add some stuff to the startup script so I can easily identify the part at which it is hanging.

EDIT:

If it helps at all this is what it hangs at:

Code:
root      2162  0.0  0.2  4840  668 ?        S    20:52   0:00 initlog -q -c /etc/rc3.d/S99zimbra start
root      2163  0.0  0.4  5636 1140 ?        S    20:52   0:00 /bin/bash /etc/rc3.d/S99zimbra start
root      2164  0.0  0.4  6164 1220 ?        S    20:52   0:00 su - zimbra -c zmcontrol startup
Wouldn't think that helps tho since it could be anything in zmcontrol. Is there a way I could get it to print out in the console from zmcontrol?

Last edited by eger : 02-10-2006 at 09:04 PM.
Reply With Quote
  #4 (permalink)  
Old 02-10-2006, 09:46 PM
Zimbra Employee
 
Posts: 4,784
Default

Kinda slim on the RAM... Take a look at this post... Lots of VM's hit this.

Post install : Zimbra start up is taking upwards of 10 minutes
__________________
Bugzilla - Wiki - Downloads - Offline Client
Reply With Quote
  #5 (permalink)  
Old 02-10-2006, 11:08 PM
Intermediate Member
 
Posts: 15
Default

Yea I had a similar problem my first try. Eventually everything worked after it finally finished starting.

I just did a reinstall of CentOS 4.2 and Zimbra on a new VM with 512RAM and now everything is starting up within 20 seconds. Guess the VM doesn't play well with java and needs a good amount of memory to play nice.

Now it looks like everything is working great. I can start playing with this wonderfeul open source app! Goodbye qmailrocks!!! =p
Reply With Quote
Reply


Thread Tools
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.

Zimbrablog.com




 

Search Engine Optimization by vBSEO 3.1.0