Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-7389

Offline Upgrade fails if ip file is empty on Linux

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Incomplete
    • Affects Version/s: 2.0.1
    • Fix Version/s: 2.0.1
    • Component/s: installer
    • Security Level: Public
    • Labels:
      None
    • Environment:
      Linux version 2.6.18-308.el5 (mockbuild@builder10.centos.org)

      Description

      If the ip file under /opt/couchbase/var/lib/couchbase is empty, offline upgrade will not start transfer data.

      [root@thor08 ~]# time rpm -U couchbase-server-enterprise_x86_64_2.0.0-1976-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-1976-rel.
      The upgrade process might take awhile.
      NOTE: all item data will be read from 1.8.x sqlite database files
      and converted to new files in 2.0 couchstore file format. This can
      be a lengthy, slow operation for large datasets and/or fragmented
      database files.
      Analysing...
      Previous config.dat file is /opt/couchbase/var/lib/couchbase/config/config.dat
      Target node: ns_1@127.0.0.1
      ERROR: no previously configured dbdir
      Starting couchbase-server[ OK ]

      You have successfully installed Couchbase Server.
      Please browse to http://thor08: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}

      real 0m14.480s
      user 0m5.445s
      sys 0m1.660s

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

        Activity

        Hide
        steve Steve Yen added a comment -

        chisheng, does this happen all the time? for single node? for multiple node?

        thanks,
        steve

        Show
        steve Steve Yen added a comment - chisheng, does this happen all the time? for single node? for multiple node? thanks, steve
        Hide
        Chisheng Chisheng Hong (Inactive) added a comment -

        Hi Steve,
        That's a node from a cluster. I try a single node scenario. Empty ip file is default and offline upgrade is not affected. If your node is in a cluster and ip file is empty, then you will hit this problem.

        Show
        Chisheng Chisheng Hong (Inactive) added a comment - Hi Steve, That's a node from a cluster. I try a single node scenario. Empty ip file is default and offline upgrade is not affected. If your node is in a cluster and ip file is empty, then you will hit this problem.
        Hide
        bcui Bin Cui (Inactive) added a comment -

        From that test cluster, we don't know what leads to the empty ip file.

        Show
        bcui Bin Cui (Inactive) added a comment - From that test cluster, we don't know what leads to the empty ip file.
        Hide
        farshid Farshid Ghods (Inactive) added a comment -

        Aliaksey,

        under what circumstances do we create an ip file in 1.8.1 cluster ? in the tests which chisheng ran some nodes did not have an ip file and upgrade failed because of that.

        Show
        farshid Farshid Ghods (Inactive) added a comment - Aliaksey, under what circumstances do we create an ip file in 1.8.1 cluster ? in the tests which chisheng ran some nodes did not have an ip file and upgrade failed because of that.
        Hide
        alkondratenko Aleksey Kondratenko (Inactive) added a comment -

        We only create ip file when we have to. It happens when node is first clustered.

        So on single-node cluster ip file will be empty of even missing.

        Show
        alkondratenko Aleksey Kondratenko (Inactive) added a comment - We only create ip file when we have to. It happens when node is first clustered. So on single-node cluster ip file will be empty of even missing.
        Hide
        farshid Farshid Ghods (Inactive) added a comment -

        Alk,

        in this case we have a cluster but with empty ip file.
        i dont see a diag file and based on the comments by alk.bin,steve i dont see any progress on this ticket.

        closing this as incomplete. IF Qe can reproduce this a new issue will be opened.

        Show
        farshid Farshid Ghods (Inactive) added a comment - Alk, in this case we have a cluster but with empty ip file. i dont see a diag file and based on the comments by alk.bin,steve i dont see any progress on this ticket. closing this as incomplete. IF Qe can reproduce this a new issue will be opened.

          People

          • Assignee:
            farshid Farshid Ghods (Inactive)
            Reporter:
            Chisheng Chisheng Hong (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes