I added the LCB_OPTIONS. It now says Timeout Couchbase::Error::Timeout - failed to get value, Client-Side timeout exceeded for operation. Inspect network condition s or increase the timeout (key="printer_1", error=0x17)
I can still access it through through port 8091 on my browser, and it works fine. Could it be my AWS instance is too small? On Wednesday, January 14, 2015 at 6:31:19 PM UTC-8, M. Nunberg wrote: > > As far as the detailed error codes go, this is a hint that you might be > able to gain better information about the specific error code by enabling > this feature. > I do not think the current version of the Ruby client exposes the > connection string feature, so you can accomplish the same aim by setting > *LCB_OPTIONS="detailed_errcodes=1”* in your environment (Sergey Avseyev, > who maintains the Ruby client, might have a better idea of how to enable > these extended codes). > > Once the detailed error codes have been enabled, you should be able to see > more details about why your request failed. There is also an option of > logging (http://docs.couchbase.com/developer/c-2.4/logging.html). > > Mark > > On Jan 14, 2015, at 6:11 PM, Dump Hole <[email protected] <javascript:>> > wrote: > > Hello, > > I am using Couchbase Community Edition 3.0.1 build 1444 > I built a Ruby-Sinatra app with a Couchbase backend. > > This error is occuring only on this specific instance of Couchbase that I > have on AWS. When tested on my development machine, everything seems to > work okay. This is the error I got from the stacktrace: > > Couchbase::Error::Network - failed to execute HTTP request, Generic > network failure. Enable detailed error codes (via > LCB_CNTL_DETAILED_ERRCODES, or via `detailed_errcodes` in the connection > string) and/or enable logging to get more information > (key="_design/printers/_view/by_cpu_id?connection_timeout=75000&limit=1", > error=0x10): > > /../.bundle/ruby/2.1.0/gems/couchbase-1.3.10/lib/couchbase/view.rb:492:in > `continue' > /../.bundle/ruby/2.1.0/gems/couchbase-1.3.10/lib/couchbase/view.rb:492:in > `fetch_sync' > /../.bundle/ruby/2.1.0/gems/couchbase-1.3.10/lib/couchbase/view.rb:378:in > `fetch' > /../.bundle/ruby/2.1.0/gems/couchbase-1.3.10/lib/couchbase/view.rb:205:in > `first' > > > What is going on here and what does it mean by detailed_errcodes in the > connection string? This problem seems to occur only when there's actually > a document found. If I used a different key, which I know does not exist, > it properly returns not found. > > -- > You received this message because you are subscribed to the Google Groups > "Couchbase" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "Couchbase" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
