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

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-16-2010, 10:20 AM
Active Member
 
Posts: 31
Default migration from 6.0.6 to 6.0.7 failed with single cluster node

hello
i have tried to upgrade to 6.0.7
received the following error
Setting defaults from saved config in /opt/zimbra/.saveconfig/config.save
HOSTNAME=ms.xxx.net
LDAPHOST=ms.xxx.net
LDAPPORT=389
SNMPTRAPHOST=ms.xxx.net
SMTPSOURCE=admin@xxxxx.net
SMTPDEST=admin@xxx.net
SNMPNOTIFY=yes
SMTPNOTIFY=yes
LDAPROOTPW=zgto48Z3
LDAPZIMBRAPW=redhat00
LDAPPOSTPW=zgto48Z3
LDAPREPPW=zgto48Z3
LDAPAMAVISPW=zgto48Z3
LDAPNGINXPW=zgto48Z3
Restoring existing configuration file from /opt/zimbra/.saveconfig/localconfig.xml...done
Operations logged to /tmp/zmsetup.06162010-192940.log
Upgrading from 6.0.6_GA_2324 to 6.0.7_GA_2470
Stopping zimbra services...done.
Verifying /opt/zimbra/conf/my.cnf
Starting mysql...done.
This appears to be 6.0.6_GA
Checking ldap status...not running.
Running zmldapapplyldif...failed.
Checking ldap status...not running.
Starting ldap...failed with exit code: 256.
daemon: bind(7) failed errno=99 (Cannot assign requested address)
slap_open_listener: failed on ldap://xxxxx:389
UPGRADE FAILED - exiting.
... OCF_RESKEY_service_name=xxxx.net /opt/zimbra-cluster/bin/zmcluctl stop
stop - Zimbra stop initiated via zmcluctl
Host ms.xxxxx.net
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 memcached...Done.
Stopping mailbox...Done.
Stopping convertd...Done.
Stopping logger...Done.
Stopping ldap...Done.
... ip addr del 172.16.1.7/24/32 dev eth0
Error: an inet prefix is expected rather than "172.16.1.7/24/32".
... umount /opt/zimbra-cluster/mountpoints/ms.xxxx.net

any hints i have enabled the cluster back and thank god it started fine and all services are working
Reply With Quote
  #2 (permalink)  
Old 06-17-2010, 04:40 AM
Moderator
 
Posts: 2,207
Default

The IP address is wrongly formatted.
Check your cluster.conf file.
Reply With Quote
  #3 (permalink)  
Old 06-18-2010, 06:06 PM
Active Member
 
Posts: 31
Default

i did check it nothing wrong in there i did enable the cluster did fail over all working fine
Reply With Quote
  #4 (permalink)  
Old 06-19-2010, 02:06 AM
Moderator
 
Posts: 7,928
Default

As Klug has said this does not look right at all
Quote:
172.16.1.7/24/32
__________________
Reply With Quote
  #5 (permalink)  
Old 06-19-2010, 06:01 PM
Active Member
 
Posts: 31
Default

i totaly agree but i cant find this entry on /etc/cluster/cluster.cfg nor any were
also the failer over for cluster works fine any idea were it might be
Reply With Quote
  #6 (permalink)  
Old 06-19-2010, 06:39 PM
Active Member
 
Posts: 31
Default

<service autostart="1" domain="zfo" name="ms.xxxx.net" recovery="relocate">
<ip ref="172.16.1.7/24"/>
<fs ref="zm-fs"/>
<script ref="zimbra"/>
</service>

i mean iam guessing there should be no / and that what translate to /32 in log
</rm>
</cluster>

does this look right
Reply With Quote
  #7 (permalink)  
Old 06-21-2010, 12:46 AM
Moderator
 
Posts: 2,207
Default

Or there's an bug in the cluster upgrade script that add /32 to the IP...

You should open a case on this.
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.