Home | Forums | Couchbase | Couchbase Server 1.8.x

Moxi to sasl couchbase bucket

2 replies [Last post]
Wed, 11/14/2012 - 19:43
thekev
Offline
Joined: 02/17/2012
Groups: None

I've configured moxi for what I think is correct to declare sasl auth and proxy for a couchbase bucket named 'api'. However, it's always reporting "SERVER_ERROR unauthorized, null bucket" (ascii protocol). My intent is to provide localhost:11211 with a moxi that maps into a couchbase bucket other than "default". I do not wish to use the memcache bucket type.

Here is a pastebin of the configs and -vvv output. http://pastebin.com/EUt0p29b Note these lines in particular:

2012-11-15 02:38:58: (memcached.c.403) <49 new auto-negotiating client connection
2012-11-15 02:38:58: (cproxy.c.489) <49 assigning to default bucket: api
2012-11-15 02:38:58: (cproxy.c.505) <49 assigning to null bucket, default bucket missing: api
2012-11-15 02:38:58: (cproxy.c.519) <49 assigning to first bucket, missing default/null bucket: api

And here's the output of "stats proxy" http://pastebin.com/rAW74daB

Top
Thu, 11/15/2012 - 12:12
thekev
Offline
Joined: 02/17/2012
Groups: None

More information discovered today. There is not a single packet passed between moxi and the couchbase servers when the client is rejected with this message logged:

2012-11-15 19:08:06: (cproxy.c.2009) 49: upstream_error: SERVER_ERROR unauthorized, null bucket

I can see it clearly talking to port 8091 during startup:
GET /pools/default/bucketsStreaming/api
Authorization: Basic *************
Host: cbase01.domain.com:8091
Accept: */*
...snip...
HTTP/1.1 200 OK
...snip...
{"name":"api","bucketType":"membase","authType":"sasl","saslPassword":"********","proxyPort":0,"uri":"/pools/default/buckets/api","streamingUri":"/pools/default/bucketsStreaming/api"...
...snip...

Top
Thu, 11/15/2012 - 12:30
thekev
Offline
Joined: 02/17/2012
Groups: None

For the archives:

I figured out my mistake. default_bucket= should not be declared if I'm putting the bucket name in the cluster bucketsStreaming URL. It works fine when the bucket is "default" that requires no sasl auth, which is inconsistent.

Top