http://www.couchbase.com/issues This file is an XML representation of an issue en-us 5.2.4 845 26-12-2012 http://www.couchbase.com/issues/browse/MB-6751 Couchbase Server Not sure if this is the server sending back the wrong message, or the stats script malforming the commend. <br/> <br/> Running this command: <br/> /opt/couchbase/bin/cbstats localhost:11210 vkey pkrug 316 <br/> Stats &#39;vkey pkrug 316&#39; are not available from the requested engine. <br/> <br/> In 1.8, it would return &quot;not found&quot; because the request is valid, but the key is not there. In 2.0, something changed and now it doesn&#39;t actually recognize the command which leads to confusion with the error response. MB-6751

Incorrect error message from 'vkey' when key does not exist

Bug Major Resolved Fixed Public Mike Wiederhold Perry Krug Wed, 26 Sep 2012 16:35:43 -0500 Fri, 26 Oct 2012 15:26:18 -0500 Wed, 26 Sep 2012 19:44:31 -0500 2.0 2.0-beta-2 couchbase-bucket 0 1 Mike,<br/> <br/> Please take a look at this issue when you have time. It seems to me that this is the regression from our recent changes in stats key to support the OBSERVE command. <a href="http://review.couchbase.org/#/c/21160/1">http://review.couchbase.org/#/c/21160/1</a> Integrated in github-ep-engine-2-0 #435 (See [<a href="http://qa.hq.northscale.net/job/github-ep-engine-2-0/435/">http://qa.hq.northscale.net/job/github-ep-engine-2-0/435/</a>])<br/> &nbsp;&nbsp;&nbsp;&nbsp;<a href="http://www.couchbase.com/issues/browse/MB-6751" title="Incorrect error message from &#39;vkey&#39; when key does not exist"><strike>MB-6751</strike></a>: Fix vkey not found in cbstats script (Revision fdecb33cb44a99f3c2b62c324042ca569cd5591d)<br/> <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Result = SUCCESS<br/> Mike Wiederhold : <br/> Files : <br/> * management/cbstats<br/> RN: Incorrect message had been sent in response to <br/> a cbstats vkey command. Server had returned the string &#39;not found&#39; <br/> for valid request. Now correct the memcached protocol <br/> error is returned. Date of First Response Wed, 26 Sep 2012 19:06:47 -0500 Rank 3881 Time In Status