Couchbase Server

cbbackup fails with no design source node error

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Incomplete
  • Affects Version/s: None
  • Fix Version/s: 2.0
  • Component/s: tools
  • Security Level: Public
  • Labels:
    None

Description

I try to backup a cluster of 2 nodes and got an error:

https://gist.github.com/4071813
Error:
error: no design source node; spec_parts: ('192.168.42.16',
 '8091', 'Administrator', 'Administrator', '')

Both are #1870.


Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Farshid Ghods added a comment -
Steve,

if you need more information please assign this ticket back to QE in order to reproduce.
this bug came from community users and might not contain enough information
Show
Farshid Ghods added a comment - Steve, if you need more information please assign this ticket back to QE in order to reproduce. this bug came from community users and might not contain enough information
Hide
Permalink
Steve Yen added a comment -
Hi Farshid & team,

Two things pop to mind...

First, getting the output of a "curl http://HOST:8091/pools/default/buckets" would be a useful next step. What seems to be happening is the cmd-line parameter of "http://192.168.42.16:8091" says to try to use the server "192.168.42.16". However, that (poorly written) error message means that "192.168.42.16" is not appearing in the REST/JSON server map, so the cbbackup errors out saying there isn't a good source-node to use to backup the design-doc.

The workaround is for the user to specify the same server IP/hostname that appears in the server-map, and that should work.

Secondly, the "-t" threads parameter of 128 is probably quite too high and might steal from performancel. If there are 4 nodes in the cluster, for example, even with -t 128, only 4 threads of those 128 worker threads would have any work to do.
Show
Steve Yen added a comment - Hi Farshid & team, Two things pop to mind... First, getting the output of a "curl http://HOST:8091/pools/default/buckets " would be a useful next step. What seems to be happening is the cmd-line parameter of " http://192.168.42.16:8091 " says to try to use the server "192.168.42.16". However, that (poorly written) error message means that "192.168.42.16" is not appearing in the REST/JSON server map, so the cbbackup errors out saying there isn't a good source-node to use to backup the design-doc. The workaround is for the user to specify the same server IP/hostname that appears in the server-map, and that should work. Secondly, the "-t" threads parameter of 128 is probably quite too high and might steal from performancel. If there are 4 nodes in the cluster, for example, even with -t 128, only 4 threads of those 128 worker threads would have any work to do.
Hide
Permalink
Farshid Ghods added a comment -
Don,

as Steve mentioned the IP that user has listed does not match the IP we retrieved from the cluster map.

can you please ask the user to post output from
curl http://HOST:8091/pools/default/buckets"
Show
Farshid Ghods added a comment - Don, as Steve mentioned the IP that user has listed does not match the IP we retrieved from the cluster map. can you please ask the user to post output from curl http://HOST:8091/pools/default/buckets "
Hide
Permalink
Don Pinto added a comment -

Francis Varga to me - Output of the curl can be found here -
https://gist.github.com/4089474
Show
Don Pinto added a comment - Francis Varga to me - Output of the curl can be found here - https://gist.github.com/4089474
Hide
Permalink
Don Pinto added a comment -
Re-assigning back - Let me know if you need any more info.
Show
Don Pinto added a comment - Re-assigning back - Let me know if you need any more info.
Hide
Permalink
Farshid Ghods added a comment -
cbbackup is run against 192.168.42.16 but server map shows that there are two nodes with these ips ( "192.168.42.18:11210","192.168.42.179:11210" ) . looks like there is some internal/external ip thing going on here

core/bin/cbbackup -u Administrator -p Administrator -t 256 -v http://192.168.42.16:8091 /Users/hissterkiller/cbbackups
Show
Farshid Ghods added a comment - cbbackup is run against 192.168.42.16 but server map shows that there are two nodes with these ips ( "192.168.42.18:11210","192.168.42.179:11210" ) . looks like there is some internal/external ip thing going on here core/bin/cbbackup -u Administrator -p Administrator -t 256 -v http://192.168.42.16:8091 /Users/hissterkiller/cbbackups
Hide
Permalink
Farshid Ghods added a comment -
to work around this he can run cbbackup against 192.168.42.179 or 192.168.42.18
Show
Farshid Ghods added a comment - to work around this he can run cbbackup against 192.168.42.179 or 192.168.42.18
Hide
Permalink
Farshid Ghods added a comment -
please re-open if user is not able to backup the data after specifying the suggested IP
Show
Farshid Ghods added a comment - please re-open if user is not able to backup the data after specifying the suggested IP

People

  • Assignee:
    Don Pinto
    Reporter:
    Farshid Ghods
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: