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

Upgrade 1.8.1->2.0 gives Stopping couchbase-serverNOTE: shutdown failed {badrpc,nodedown}

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 2.1.0
    • 2.0
    • installer
    • Security Level: Public
    • None
    • build 1976

    Description

      Upgrade 1.8.1->2.0 on linux gives Stopping couchbase-serverNOTE: shutdown failed

      {badrpc,nodedown} at the end of the upgrade.
      The data/buckets are available after upgrade.

      Not clear why the installer is trying to stop the couchbase-server at the end after starting it:

      Done.
      Starting couchbase-server[ OK ]

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

      Steps to reproduce:
      (On centos linux CentOS release 5.7 (Final))
      1. rm -Rf /opt/couchbase(after uninstall previous version of rpm)
      2. Install 1.8.1
      3. Create default/1 sasl/ 1 standard data bucket and load 10k rows each.
      4. rpm -U couchbase-server-community_x86_64_2.0.0-1976-rel.rpm

      The above error is shown. Complete console output and diagnostics are attached.

      Attachments

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

        Activity

          People

            deepkaran.salooja Deepkaran Salooja
            deepkaran.salooja Deepkaran Salooja
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty