Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: feature-backlog
    • Fix Version/s: None
    • Component/s: installer
    • Security Level: Public
    • Labels:
      None
    • Environment:
      CentOS Linux, running on vmware. I had Couchbase Server 1870 running there, and had it removed from the cluster before upgrading.

      Description

      When I try to do a rolling upgrade, and following the Couchbase guide I end up with an upgraded node - not working.

      Here are the commands I ran on my CentOS box :

      [root@cbnode03 ~]# sudo /etc/init.d/couchbase-server stop
      Stopping couchbase-server
      =INFO REPORT==== 14-Nov-2012::17:52:54 ===
      Initiated server shutdown** at node ns_1@192.168.0.33 **

      =INFO REPORT==== 14-Nov-2012::17:52:59 ===
      Stopped ns_server application** at node ns_1@192.168.0.33 **

      [root@cbnode03 ~]# wget http://packages.couchbase.com/builds/1941/couchbase-server-community_x86_64_2.0.0-1941-rel.rpm
      -2012-11-14 17:53:36- http://packages.couchbase.com/builds/1941/couchbase-server-community_x86_64_2.0.0-1941-rel.rpm
      Resolving packages.couchbase.com... 207.171.163.3
      Connecting to packages.couchbase.com|207.171.163.3|:80... connected.
      HTTP request sent, awaiting response... 200 OK
      Length: 126517192 (121M) [application/x-redhat-package-manager]
      Saving to: "couchbase-server-community_x86_64_2.0.0-1941-rel.rpm"

      100%[=====================================================================================================================>] 126,517,192 8.66M/s in 21s

      2012-11-14 17:53:57 (5.83 MB/s) - "couchbase-server-community_x86_64_2.0.0-1941-rel.rpm" saved [126517192/126517192]

      [root@cbnode03 ~]# rpm -U couchbase-server-community_x86_64_2.0.0-1941-rel.rpm
      Stopping couchbase-server ...
      Stopping couchbase-server
      Upgrading couchbase-server ...
      /opt/couchbase/bin/install/cbupgrade -c /opt/couchbase/var/lib/couchbase/config -a yes
      Automatic mode: running without interactive questions or confirmations.
      Upgrading your Couchbase Server to 2.0.0-1941-rel.
      The upgrade process might take awhile.
      Analysing...
      Previous config.dat file is /opt/couchbase/var/lib/couchbase/config/config.dat
      Target node: ns_1@192.168.0.33
      ERROR: no previously configured dbdir
      Starting couchbase-server[ OK ]

      You have successfully installed Couchbase Server.
      Please browse to http://cbnode03:8091/ to configure your server.
      Please refer to http://couchbase.com for additional resources.

      Please note that you have to update your firewall configuration to
      allow connections to the following ports: 11211, 11210, 11209, 4369,
      8091 and from 21100 to 21299.

      By using this software you agree to the End User License Agreement.
      See /opt/couchbase/LICENSE.txt.

      Stopping couchbase-serverNOTE: shutdown failed

      {badrpc,nodedown}

      [root@cbnode03 ~]#

      No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

        Hide
        fonager Tony Fonager added a comment -

        Anyone reading this ?

        Show
        fonager Tony Fonager added a comment - Anyone reading this ?
        Hide
        farshid Farshid Ghods (Inactive) added a comment -

        Hi Tony,

        Thanks for reporting this issue. upgrade between nightly builds are not supported at the moment. There could be changes in the storage layer , indexing layer ( file format changes ) or the management layer which breaks the upgrade.

        also the rpm ,debian and windows scripts do not support upgrade from same version ( different build # )

        the workaround is to run rpm -e and then rpm -i

        -Farshid

        Show
        farshid Farshid Ghods (Inactive) added a comment - Hi Tony, Thanks for reporting this issue. upgrade between nightly builds are not supported at the moment. There could be changes in the storage layer , indexing layer ( file format changes ) or the management layer which breaks the upgrade. also the rpm ,debian and windows scripts do not support upgrade from same version ( different build # ) the workaround is to run rpm -e and then rpm -i -Farshid
        Hide
        fonager Tony Fonager added a comment -

        Hi Farshid,

        I have tried both.

        Using rpm -e and then rpm-i does not work either with the 1941 version.

        So, we have to re-install our boxes to help you test your builds ?

        Show
        fonager Tony Fonager added a comment - Hi Farshid, I have tried both. Using rpm -e and then rpm-i does not work either with the 1941 version. So, we have to re-install our boxes to help you test your builds ?
        Hide
        farshid Farshid Ghods (Inactive) added a comment -

        Hi Tony,

        the full instructions is indeed sth like this ( filed a bug to add this to documentation

        1- uninstall previous installation
        2- make sure couchbase server processes are not running upon uninstallation ( processes such as memcached,beam.smp)
        3- remove previous data and config files ( default on linux /opt/couchbase - rm -rf /opt/couchbase_
        4- install the newest build

        Show
        farshid Farshid Ghods (Inactive) added a comment - Hi Tony, the full instructions is indeed sth like this ( filed a bug to add this to documentation 1- uninstall previous installation 2- make sure couchbase server processes are not running upon uninstallation ( processes such as memcached,beam.smp) 3- remove previous data and config files ( default on linux /opt/couchbase - rm -rf /opt/couchbase_ 4- install the newest build
        Hide
        farshid Farshid Ghods (Inactive) added a comment -

        can you please try this . if the server does not start please do run cbcollect_info and attach to this jira ticket

        Show
        farshid Farshid Ghods (Inactive) added a comment - can you please try this . if the server does not start please do run cbcollect_info and attach to this jira ticket
        Hide
        fonager Tony Fonager added a comment -

        HI Farshid,

        That is exactly what I have tried several times. I had no data on the node, as I was a part of a cluster from where I had removed it.

        So every time I also checked processes, which Matt told me to do, and removed old data and config files.

        The strange part is, if I do this uninstall, removal of data files and everything, and then in the end reinstall the 1870 version, it starts up with no problems.

        Anyway, I have now skipped the 3 boxes and spun up 3 new instances all running 1941.

        I will let you know when I have tested this on the 3 x 1870 boxes.

        Thanks.

        Show
        fonager Tony Fonager added a comment - HI Farshid, That is exactly what I have tried several times. I had no data on the node, as I was a part of a cluster from where I had removed it. So every time I also checked processes, which Matt told me to do, and removed old data and config files. The strange part is, if I do this uninstall, removal of data files and everything, and then in the end reinstall the 1870 version, it starts up with no problems. Anyway, I have now skipped the 3 boxes and spun up 3 new instances all running 1941. I will let you know when I have tested this on the 3 x 1870 boxes. Thanks.
        Hide
        farshid Farshid Ghods (Inactive) added a comment -

        Thanks Tony.

        if this occurs next time please do collect cbcollect_info zip and attach to the ticket.

        also recntly there is a new log file added start*.log under ../var/lib/couchbase/logs location that will contain errors if couchbase server fails to start , however if couchbase server starts but then crashes during the initialization phase other logs files will tell us what happened.

        Show
        farshid Farshid Ghods (Inactive) added a comment - Thanks Tony. if this occurs next time please do collect cbcollect_info zip and attach to the ticket. also recntly there is a new log file added start*.log under ../var/lib/couchbase/logs location that will contain errors if couchbase server fails to start , however if couchbase server starts but then crashes during the initialization phase other logs files will tell us what happened.
        Hide
        fonager Tony Fonager added a comment -

        No problem, I will do that for you

        Show
        fonager Tony Fonager added a comment - No problem, I will do that for you

          People

          • Assignee:
            farshid Farshid Ghods (Inactive)
            Reporter:
            fonager Tony Fonager
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes