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 06-23-2010, 04:54 AM
Elite Member
 
Posts: 275
Default [SOLVED] Upgrade from 6.0.5 to 6.0.7 gives SOAP errors in Admin UI

Hi everyone

Previously we were running 6.0.5_GA_2213.RHEL5_64_20100202214931 CentOS5_64 NETWORK edition

And the other day I did a double upgrade to 6.0.7.
Firstly to the initial 6.0.7, then to the updated 6.0.7_GA_2473.RHEL5_64_20100616202447 CentOS5_64 NETWORK edition.
The only time I'd ever tried to upgrade was to 6.0.6 and this happened... http://www.zimbra.com/forums/install...-failures.html

The upgrade seemed to go ok, apart from some failures with Zimlets near the end.
Checked zimlet deployment status immediately after the upgrade and there were some extra zimlets deployed which I didn't have before (yemoticons, phone, dnd) so I undeployed those.
Also the email, url and date zimlets were disabled in my default COS whereas before they were manditory so I had to adjust that.

Service status was all "running" and our commercial SSL cert was preserved ok. Mail seems to be flowing.

However when I go to certain screens in the admin console I get the following or similar error:
Code:
Server error encountered Message: system failure: exception during auth {RemoteManager: zimbra.ourdomain.com->zimbra@zimbra.ourdomain.com:22} Error code: service.FAILURE Method: GetMailQueueInfoRequest Details:soap:Receiver
I get that error when I go to view the mail queue, expand the Servers section and select our server, or expand the Certificates section and select our certificate.
Everything else seems to be ok.

Though the method parameter in the error msg changes depending on what I'm trying to do.

Tried zmcontrol stop/start and the error persists. Cache cleared etc.

Any ideas on how to fix this?

Cheers, B
__________________
My Zimbra Bugs Wishlist: 16411, 24567, 35676, 36430, 37770, 41872, 43733, 44384, 46383, 47759
And a way to associate mailto: handlers with a Zimbra Prism webapp
Reply With Quote
  #2 (permalink)  
Old 06-23-2010, 05:13 AM
Zimbra Consultant & Moderator
 
Posts: 20,317
Default

There are a couple of choices, check these threads.
__________________
Regards


Bill
Reply With Quote
  #3 (permalink)  
Old 06-23-2010, 10:08 AM
Elite Member
 
Posts: 275
Default

Thanks.
Right so basically I need to re-install our commercial SSL cert?
__________________
My Zimbra Bugs Wishlist: 16411, 24567, 35676, 36430, 37770, 41872, 43733, 44384, 46383, 47759
And a way to associate mailto: handlers with a Zimbra Prism webapp
Reply With Quote
  #4 (permalink)  
Old 06-23-2010, 10:10 AM
Zimbra Consultant & Moderator
 
Posts: 20,317
Default

Quote:
Originally Posted by batfastad View Post
Thanks.
Right so basically I need to re-install our commercial SSL cert?
That's correct.
__________________
Regards


Bill
Reply With Quote
  #5 (permalink)  
Old 06-23-2010, 10:47 AM
Elite Member
 
Posts: 275
Default

Awesome. All sorted.

I re-issued our commercial cert but that didn't do the trick.

But this...
Code:
zmsshkeygen
zmupdateauthkeys
zmcontrol stop
zmcontrol start
Worked perfectly

Cheers, B
__________________
My Zimbra Bugs Wishlist: 16411, 24567, 35676, 36430, 37770, 41872, 43733, 44384, 46383, 47759
And a way to associate mailto: handlers with a Zimbra Prism webapp
Reply With Quote
  #6 (permalink)  
Old 06-29-2010, 12:59 AM
Elite Member
 
Posts: 275
Default

A quick additional comment on this... does this need to be done after every upgrade?
If so, would it not be better to incorporate those steps into the upgrade process?
Any idea what actually caused this problem?

Cheers, B
__________________
My Zimbra Bugs Wishlist: 16411, 24567, 35676, 36430, 37770, 41872, 43733, 44384, 46383, 47759
And a way to associate mailto: handlers with a Zimbra Prism webapp
Reply With Quote
  #7 (permalink)  
Old 06-29-2010, 02:50 AM
Zimbra Consultant & Moderator
 
Posts: 20,317
Default

Quote:
Originally Posted by batfastad View Post
A quick additional comment on this... does this need to be done after every upgrade?
No, it doesn't
__________________
Regards


Bill
Reply With Quote
  #8 (permalink)  
Old 07-03-2010, 01:17 AM
Elite Member
 
Posts: 275
Default

Quote:
Originally Posted by phoenix View Post
No, it doesn't
So is there any reason as to why I had to perform these steps to cure the SOAP errors?
Is it because I'm using a commercial SSL cert?
__________________
My Zimbra Bugs Wishlist: 16411, 24567, 35676, 36430, 37770, 41872, 43733, 44384, 46383, 47759
And a way to associate mailto: handlers with a Zimbra Prism webapp
Reply With Quote
  #9 (permalink)  
Old 07-03-2010, 02:49 AM
Zimbra Consultant & Moderator
 
Posts: 20,317
Default

Quote:
Originally Posted by batfastad View Post
Is it because I'm using a commercial SSL cert?
No, it isn't. IIRC there was a bug that caused that problem.
__________________
Regards


Bill
Reply With Quote
  #10 (permalink)  
Old 07-05-2010, 03:36 PM
Junior Member
 
Posts: 5
Default

Can't these bugs be QA tested before release first?
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.