Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
 
Go Back   Zimbra - Forums > Zimbra Collaboration Suite > Installation
Reload this Page [SOLVED] 5.0.11 to 5.0.12 Upgrade Fails (Stop failed)

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
Page 1 of 2 1 2
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 01-29-2009, 07:17 PM
Active Member
  
Posts: 49
Default [SOLVED] 5.0.11 to 5.0.12 Upgrade Fails (Stop failed)
Hey,

Whenever I try to upgrade my 5.0.11 OSS Zimbra installation (Ubuntu 8.04) the upgrade fails at:

Code:
Stopping zimbra services
Stop failed - exiting
UPGRADE FAILED - exiting
There's nothing much more to see in the install logs. One thing I did notice is that after stopping and starting my server using zmcontrol (the server stops fine...?) the logger process uses so much CPU my load climbs from .55 to 5.05. I have to kill the logger to run zimbra. I'm guessing the problem must be with the logger during upgrade, can I remove and re-install it later or will that not fix the problem?

Any input is appreciated!
Reply With Quote
  #2 (permalink)  
Old 01-30-2009, 01:47 AM
Moderator
  
Posts: 5,806
Default
Stop all the services before actually running install.sh. Once they are down run a
Code:
ps aux | grep zimbra
and kill of any remaining processes. Then try running the install.sh again and hopefully it will go through fine and fix the logger issue that was in 5.0.11.
__________________
SplatNIX IT Services :: Innovation through Collaboration™


http://www.messagefortress.com
Reply With Quote
  #3 (permalink)  
Old 01-30-2009, 03:56 PM
Active Member
  
Posts: 49
Default
Quote:
Originally Posted by uxbod View Post
Stop all the services before actually running install.sh. Once they are down run a
Code:
ps aux | grep zimbra
and kill of any remaining processes. Then try running the install.sh again and hopefully it will go through fine and fix the logger issue that was in 5.0.11.
Thanks for responding. I stopped my server beforehand, and did notice some strange things. There were about 10 processes left over, and I could only kill 9 of them at first. The last one would hang around even though I was killing it. It eventually ended after about 3 minutes. Could that be the problem?
The upgrade still fails with zimbra stopped from the beginning.

Code:
Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...done
Operations logged to /tmp/zmsetup.01302009-164627.log
Starting ldap...done.
Setting defaults...done.
Upgrading from 5.0.11_GA_2695 to 5.0.12_GA_2789
Stopping zimbra services
Stop failed - exiting
UPGRADE FAILED - exiting
Reply With Quote
  #4 (permalink)  
Old 01-31-2009, 01:32 AM
Moderator
  
Posts: 5,806
Default
Ok, so lets try the following
Code:
su - zimbra
logmysql
use zimbra_logger;
show tables;
check table mta;
Repeat for all tables.
__________________
SplatNIX IT Services :: Innovation through Collaboration™


http://www.messagefortress.com
Reply With Quote
  #5 (permalink)  
Old 01-31-2009, 09:50 AM
Active Member
  
Posts: 49
Default
Quote:
Originally Posted by uxbod View Post
Ok, so lets try the following
Code:
su - zimbra
logmysql
use zimbra_logger;
show tables;
check table mta;
Repeat for all tables.
Code:
+----------------------+-------+----------+----------+
| Table                | Op    | Msg_type | Msg_text |
+----------------------+-------+----------+----------+
| zimbra_logger.amavis | check | status   | OK       |
+----------------------+-------+----------+----------+
+--------------------------------+-------+----------+----------+
| Table                          | Op    | Msg_type | Msg_text |
+--------------------------------+-------+----------+----------+
| zimbra_logger.amavis_aggregate | check | status   | OK       |
+--------------------------------+-------+----------+----------+
+----------------------+-------+----------+----------+
| Table                | Op    | Msg_type | Msg_text |
+----------------------+-------+----------+----------+
| zimbra_logger.config | check | status   | OK       |
+----------------------+-------+----------+----------+
+------------------------------+-------+----------+----------+
| Table                        | Op    | Msg_type | Msg_text |
+------------------------------+-------+----------+----------+
| zimbra_logger.disk_aggregate | check | status   | OK       |
+------------------------------+-------+----------+----------+
+-------------------+-------+----------+----------+
| Table             | Op    | Msg_type | Msg_text |
+-------------------+-------+----------+----------+
| zimbra_logger.mta | check | status   | OK       |
+-------------------+-------+----------+----------+
+-----------------------------+-------+----------+----------+
| Table                       | Op    | Msg_type | Msg_text |
+-----------------------------+-------+----------+----------+
| zimbra_logger.mta_aggregate | check | status   | OK       |
+-----------------------------+-------+----------+----------+
+----------------------------------+-------+----------+----------------------------------------------------------+
| Table                            | Op    | Msg_type | Msg_text                                                 |
+----------------------------------+-------+----------+----------------------------------------------------------+
| zimbra_logger.processing_history | check | warning  | 2 clients are using or haven't closed the table properly |
| zimbra_logger.processing_history | check | status   | OK                                                       |
+----------------------------------+-------+----------+----------------------------------------------------------+
+------------------------+-------+----------+----------+
| Table                  | Op    | Msg_type | Msg_text |
+------------------------+-------+----------+----------+
| zimbra_logger.raw_logs | check | status   | OK       |
+------------------------+-------+----------+----------+
+------------------------------+-------+----------+----------------------------------------------------------+
| Table                        | Op    | Msg_type | Msg_text                                                 |
+------------------------------+-------+----------+----------------------------------------------------------+
| zimbra_logger.service_status | check | warning  | 3 clients are using or haven't closed the table properly |
| zimbra_logger.service_status | check | status   | OK                                                       |
+------------------------------+-------+----------+----------------------------------------------------------+
Thanks for all the help. If worse comes to worse, I guess I could wait until the installation gets to the stopping services point and just kill the processes manually in another session.

EDIT: I just tried to stop my server. The logger using all of the CPU doesn't seem to be related to the setup problem, because now when I stop my server:

Code:
        Stopping stats...Done
        Stopping mta...Done
        Stopping spell...Done
        Stopping snmp...Done
        Stopping archiving...Done
        Stopping antivirus...Done
        Stopping antispam...Done
        Stopping imapproxy...Done
        Stopping mailbox...FAILED
Stopping zmmtaconfig...failed.
Stopping mailboxd...done.
Stopping mysqld... done.
        Stopping logger...Done
        Stopping ldap...Done
So it's not the logger? And then I run a ps and these are the processes left over:

Code:
zimbra    3489  0.2  0.0   7144  4920 ?        S    Jan10  76:46 /usr/bin/perl /opt/zimbra/libexec/zmmtaconfig
zimbra   13690  0.0  0.0   7136  1916 pts/1    S    10:48   0:00 su - zimbra
zimbra   13691  0.0  0.0   4640  2044 pts/1    S    10:48   0:00 -su
zimbra   15685  0.0  0.0   2960   744 ?        Ss   10:50   0:00 /opt/zimbra/clamav/bin/freshclam --config-file=/opt/zimbra/conf/freshclam.conf -d --checks=12
zimbra   15692  0.0  1.3 113208 110428 ?       Ss   10:51   0:00 /opt/zimbra/clamav/sbin/clamd --config-file=/opt/zimbra/conf/clamd.conf
zimbra   17618 63.0  0.2 478476 17020 ?        Sl   10:54   0:00 /opt/zimbra/java/bin/java -client -Xmx256m -Dzimbra.home=/opt/zimbra -Djava.library.path=/opt/zimbra/lib -Djava.ext.dirs=/opt/zimbra/java/jre/lib/ext:/opt/zimbra/lib/jars:/opt/zimbra/lib/ext-common:/opt/zimbra/lib/ext/clamscanner com.zimbra.cs.account.ProvUtil -l garpu
And the process 3489 won't die, I kill it and nothing happens
Last edited by Mccreations : 01-31-2009 at 09:57 AM.
Reply With Quote
  #6 (permalink)  
Old 02-01-2009, 09:17 AM
Active Member
  
Posts: 49
Default
After a little bit of digging, I believe I've found the problem, I just don't know how to fix it. When I stop my server, it reports this:

Code:
        Stopping stats...Done
        Stopping mta...Done
        Stopping spell...Done
        Stopping snmp...Done
        Stopping archiving...Done
        Stopping antivirus...Done
        Stopping antispam...Done
        Stopping imapproxy...Done
        Stopping mailbox...FAILED
Stopping zmmtaconfig...failed.
Stopping mailboxd...done.
Stopping mysqld... done.
        Stopping logger...Done
        Stopping ldap...Done
The reason zmmtaconfig won't stop is because clam(/freshclam) won't stop, and I don't know why.

In the clam log it says it stops, but then starts again while the shutdown is still going...?

Code:
Sun Feb  1 10:09:28 2009 -> Pid file removed.
Sun Feb  1 10:09:28 2009 -> --- Stopped at Sun Feb  1 10:09:28 2009
Sun Feb  1 10:10:49 2009 -> +++ Started at Sun Feb  1 10:10:49 2009
Sun Feb  1 10:10:49 2009 -> clamd daemon 0.94.1-broken-compiler (OS: linux-gnu, ARCH: i386, CPU: i686)
Sun Feb  1 10:10:49 2009 -> Log file size limited to 20971520 bytes.
And here's what zmmtaconfig.log reads:


Code:
Sun Feb  1 10:10:15 2009  Watchdog: adding antivirus to restart list
Sun Feb  1 10:10:15 2009  CONTROL ANTIVIRUS: /opt/zimbra/bin/zmclamdctl restart 
Sun Feb  1 10:12:14 2009  Skipping Global system configuration update.
Sun Feb  1 10:12:14 2009  gacf ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException myserver:389) 
Sun Feb  1 10:12:16 2009  Skipping All Reverse Proxy URLs update.
Sun Feb  1 10:12:16 2009  Skipping getAllReverseProxyURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException myserver:389) 
Sun Feb  1 10:12:19 2009  Skipping All Reverse Proxy Backends update.
Sun Feb  1 10:12:19 2009  Skipping getAllReverseProxyBackends ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException myserver:389) 
Sun Feb  1 10:12:22 2009  Skipping All Memcached Servers update.
Sun Feb  1 10:12:22 2009  Skipping getAllMemcachedServers ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException myserver:389) 
Sun Feb  1 10:12:25 2009  Skipping All MTA Authentication Target URLs update.
Sun Feb  1 10:12:25 2009  Skipping getAllMtaAuthURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException myserver:389) 
Sun Feb  1 10:12:27 2009  Skipping Configuration for server myserver update.
Sun Feb  1 10:12:27 2009  gs:myserver ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException myserver:389) 
Sun Feb  1 10:12:27 2009  Sleeping...Key lookup failed.
Sun Feb  1 10:12:37 2009  Skipping Global system configuration update.
Sun Feb  1 10:12:37 2009  gacf ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException myserver:389) 
Sun Feb  1 10:12:40 2009  Skipping All Reverse Proxy URLs update.
Sun Feb  1 10:12:40 2009  Skipping getAllReverseProxyURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException myserver:389) 
Sun Feb  1 10:12:42 2009  Skipping All Reverse Proxy Backends update.
Sun Feb  1 10:12:42 2009  Skipping getAllReverseProxyBackends ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException myserver:389) 
Sun Feb  1 10:12:45 2009  Skipping All Memcached Servers update.
Sun Feb  1 10:12:45 2009  Skipping getAllMemcachedServers ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException myserver:389) 
Sun Feb  1 10:12:48 2009  Skipping All MTA Authentication Target URLs update.
Sun Feb  1 10:12:48 2009  Skipping getAllMtaAuthURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException myserver:389) 
Sun Feb  1 10:12:51 2009  Skipping Configuration for server myserver update.
Sun Feb  1 10:12:51 2009  gs:myserver ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException myserver:389) 
Sun Feb  1 10:12:51 2009  Sleeping...Key lookup failed.
Sun Feb  1 10:13:00 2009  Skipping Global system configuration update.
Sun Feb  1 10:13:00 2009  gacf ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException myserver:389) 
Sun Feb  1 10:13:03 2009  Skipping All Reverse Proxy URLs update.
Sun Feb  1 10:13:03 2009  Skipping getAllReverseProxyURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException myserver:389) 
Sun Feb  1 10:12:25 2009  Skipping getAllMtaAuthURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException myserver:389) 
Sun Feb  1 10:12:27 2009  Skipping Configuration for server myserver update.
Sun Feb  1 10:12:27 2009  gs:myserver ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException myserver:389) 
Sun Feb  1 10:12:27 2009  Sleeping...Key lookup failed.
Would it be related to this error I found in the clam log:

Code:
LibClamAV Warning: ***********************************************************
LibClamAV Warning: ***  This version of the ClamAV engine is outdated.     ***
LibClamAV Warning: *** DON'T PANIC! Read http://www.clamav.net/support/faq ***
LibClamAV Warning: ***********************************************************
Or is it something totally different?


And here's from the syslog:


Code:
Feb  1 10:09:25 mccreations zimbramon[22828]: 22828:info: Stopping antivirus via zmcontrol 
Feb  1 10:09:28 mccreations clamd[20701]: Pid file removed. 
Feb  1 10:09:28 mccreations clamd[20701]: --- Stopped at Sun Feb  1 10:09:28 2009 
Feb  1 10:09:29 mccreations zimbramon[22828]: 22828:info: Stopping antispam via zmcontrol 
Feb  1 10:09:59 mccreations zimbramon[22828]: 22828:info: Stopping imapproxy via zmcontrol 
Feb  1 10:09:59 mccreations zimbramon[22828]: 22828:info: Stopping mailbox via zmcontrol 
Feb  1 10:10:01 mccreations zimbramon[23581]: 23581:info: 2009-02-01 10:10:01, QUEUE: 0 0 
Feb  1 10:10:03 mccreations zimbramon[23599]: 23599:info: 2009-02-01 10:10:01, DISK: mccreations.us: dev: /dev/sda1, mp: /, tot: 17223, avail: 15057 
Feb  1 10:10:03 mccreations zimbramon[23599]: 23599:info: 2009-02-01 10:10:01, DISK: mccreations.us: dev: /dev/sdd1, mp: /backup, tot: 17223, avail: 5499 
Feb  1 10:10:03 mccreations zimbramon[23599]: 23599:info: 2009-02-01 10:10:01, DISK: mccreations.us: dev: /dev/sdc1, mp: /opt, tot: 17223, avail: 14561 
Feb  1 10:10:03 mccreations zimbramon[23599]: 23599:info: 2009-02-01 10:10:01, DISK: mccreations.us: dev: /dev/sdb1, mp: /usr/local, tot: 17223, avail: 13750 
Feb  1 10:10:14 mccreations zimbramon[23595]: 23595:info: 2009-02-01 10:10:01, STATUS: mccreations.us: antispam: Stopped 
Feb  1 10:10:14 mccreations zimbramon[23595]: 23595:info: 2009-02-01 10:10:01, STATUS: mccreations.us: antivirus: Stopped 
Feb  1 10:10:14 mccreations zimbramon[23595]: 23595:info: 2009-02-01 10:10:01, STATUS: mccreations.us: ldap: Running 
Feb  1 10:10:14 mccreations zimbramon[23595]: 23595:info: 2009-02-01 10:10:01, STATUS: mccreations.us: logger: Running 
Feb  1 10:10:14 mccreations zimbramon[23595]: 23595:info: 2009-02-01 10:10:01, STATUS: mccreations.us: mailbox: Running 
Feb  1 10:10:14 mccreations zimbramon[23595]: 23595:info: 2009-02-01 10:10:01, STATUS: mccreations.us: mta: Stopped 
Feb  1 10:10:14 mccreations zimbramon[23595]: 23595:info: 2009-02-01 10:10:01, STATUS: mccreations.us: snmp: Stopped 
Feb  1 10:10:14 mccreations zimbramon[23595]: 23595:info: 2009-02-01 10:10:01, STATUS: mccreations.us: spell: Stopped 
Feb  1 10:10:14 mccreations zimbramon[23595]: 23595:info: 2009-02-01 10:10:01, STATUS: mccreations.us: stats: Stopped 
Feb  1 10:10:15 mccreations zimbramon[3489]: 3489:info: zmmtaconfig: Watchdog: adding antivirus to restart list 
Feb  1 10:10:15 mccreations zimbramon[3489]: 3489:info: ANTIVIRUS restart initiated from zmmtaconfig 
Feb  1 10:10:41 mccreations zimbramon[22828]: 22828:info: Stopping logger via zmcontrol 
Feb  1 10:10:46 mccreations zimbramon[22828]: 22828:info: Stopping ldap via zmcontrol 
Feb  1 10:10:47 mccreations zimbramon[25917]: 25917:info: zmmtaconfig: Skipping All MTA Authentication Target URLs update. 
Feb  1 10:10:47 mccreations zimbramon[25917]: 25917:info: zmmtaconfig: Skipping getAllMtaAuthURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.net.ssl.SSLHandshakeException Remote host closed connection during handshake)  
Feb  1 10:10:49 mccreations zimbramon[25917]: 25917:info: zmmtaconfig: Skipping Configuration for server mccreations.us update. 
Feb  1 10:10:49 mccreations zimbramon[25917]: 25917:info: zmmtaconfig: gs:mccreations.us ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException mccreations.us:389)  
Feb  1 10:10:49 mccreations zimbramon[25917]: 25917:info: zmmtaconfig: Key lookup failed.
Why does zmmtaconfig want to restart clam instead of shutting it down?
Last edited by Mccreations : 02-01-2009 at 09:24 AM.
Reply With Quote
  #7 (permalink)  
Old 02-02-2009, 01:02 AM
Outstanding Member
  
Posts: 664
Default Somewhere...
There is a post somewhere about having too many files in you directory where your certificates reside causing some problems. I can't find it after doing a search. I don't know if this could have anything to do with your issue or not..
Reply With Quote
  #8 (permalink)  
Old 02-02-2009, 04:43 PM
Active Member
  
Posts: 49
Default
Quote:
Originally Posted by Bill Brock View Post
There is a post somewhere about having too many files in you directory where your certificates reside causing some problems. I can't find it after doing a search. I don't know if this could have anything to do with your issue or not..
Thanks for trying, but there appears to be a normal number of files in my ca directory. I've been reading a lot of logs and still have no idea.

Could it be because the shutdown is taking to long and the watchdog is restarting the AV? I'm not sure.
Reply With Quote
  #9 (permalink)  
Old 02-04-2009, 08:11 PM
Active Member
  
Posts: 49
Default
Hey... Sorry for the bump. I'm not a fan of bumping. But I'm just afraid of having to start from scratch. I'd really like to upgrade to 5.0.12 but can't with this issue... Any advice is appreciated!
Reply With Quote
  #10 (permalink)  
Old 02-05-2009, 12:48 AM
Moderator
  
Posts: 5,806
Default
Shutdown ZCS via the init.d script eg. /etc/init.d/zimbra stop. Once the init process believes everything is down check that all zimbra processes have indeed been stopped. Then attempt the upgrade.
__________________
SplatNIX IT Services :: Innovation through Collaboration™


http://www.messagefortress.com
Reply With Quote
Reply
Page 1 of 2 1 2

« Previous Thread | Today's Posts or Week's Posts | Next Thread »

Thread Tools
Display Modes
Linear Mode Linear Mode


Similar Threads

Product Information

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


Home - Blog - Contact Us - Archive - Top


 

Search Engine Optimization by vBSEO 3.1.0