Client-Side timeout exceeded for operation

[Steven Barlow]

What would be causing the NodeJS SDK to repeatedly respond with: [Error: Client-Side timeout exceeded for operation. Inspect network conditions or increase the timeout] code: 23 for all view operations?

I have a test server at http://ec2-54-83-43-209.compute-1.amazonaws.com:8092/test that demonstrates this behaviour. I'm pretty sure I've opened all the requisite ports. 

For example

CURL http://ec2-54-83-43-209.compute-1.amazonaws.com:8092/test/_design/test

responds fine, but attempting the equivalent operation using the Couchbase SDK fails as described above.

var connection;

var config = {

host: 'http://ec2-54-83-43-209.compute-1.amazonaws.com',

bucket: 'test'

};

var couchbase = require('couchbase');

connection = new couchbase.Connection(config);

connection.getDesignDoc('test', function(err, result){

if (err) {

console.log('Error', err);

} else {

console.log(result);

}

});

I can't fathom this at all, it seems to me that the Couchbase SDK simply doesn't work. In fact I've actually managed to bypass the Couchbase SDK altogether (using dscape/nano) and hitting the server on 8092 using regular CouchDB style REST requests, and that works fine.

Cheers,

Steven

[Matt Ingenthron]

Hi Steven,

What version of the node client are you running?

Did you install libcouchbase directly, or is it the embedded one (will depend on OS to some degree)?

Also, with the latest libcouchbase, you can set an environment variable and get additional logging.

Thanks!

Matt

--
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 couchbase+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 

Matt Ingenthron

Couchbase, Inc.

[Steven Barlow]

Matt,

I'm using the latest couchbase SDK (1.2.4) installed with npm install couchbase. Presumably then, libcouchbase is installed bundled as part of that installation.

I'm running on OSX, and the server is the latest Couchbase Server release 2.5.1 running on Amazon Linux AMI.

How do I go about enabling logging on libcouchbase?

Cheers,

Steven

[Steven Barlow]

Matt,

Is it perhaps possible to get one of the Couchbase JS team to perform a quick test trying to hit my server (http://ec2-54-83-43-209.compute-1.amazonaws.com:8092/test) with the JS SDK 1.2.4?

As far as I can ascertain, the JS SDK is not working at all after a simple npm install (which seems absurd), but I've replicated on multiple environments. Is there something about my server instance, or is JS SDK indeed broken?

This can be as simple as:

var couchbase = require('couchbase');

new couchbase.Connection({

host: 'http://ec2-54-83-43-209.compute-1.amazonaws.com',

bucket: 'test'

}).stats(function(err, result){

if (err) {

console.log('Error', err);

} else {

console.log(result);

}

});

Cheers,

Steven

On Wednesday, 28 May 2014 17:13:47 UTC+10, Matt Ingenthron wrote:

[Matt Ingenthron]

Hi Steven, 

I just tried it myself and sure enough, I got the same thing.  Let me ask someone to have a look at it.

Thanks,

[Brett Lawson]

Hey Steven,

It looks like your server does not have the prerequisite ports opened.  What ports have you opened on your firewall?  I can't connect to your server, but any other server works fine, both on and off my own network.

Cheers, Brett

[Steven Barlow]

Brett,

I'll check the full list of open ports later, but it's basically all those in the default Couchbase AMI security group (as per Couchbase documentation too). I can certainly CURL and get responses on 8092.

Which ports should be open for this to work?

Cheers,

Steven

You received this message because you are subscribed to a topic in the Google Groups "Couchbase" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/couchbase/scrTb94Mj3w/unsubscribe.
To unsubscribe from this group and all its topics, send an email to couchbase+...@googlegroups.com.

[Steven Barlow]

Brett,

I've tried opening various ports (including all of them!), but nothing seems to make any difference. At the moment, I have open:

22	tcp	0.0.0.0/0	✔
4369	tcp	0.0.0.0/0	✔
4984	tcp	0.0.0.0/0	✔
8080	tcp	0.0.0.0/0	✔
8088	tcp	0.0.0.0/0	✔
8091	tcp	0.0.0.0/0	✔
8092	tcp	0.0.0.0/0	✔
11209	tcp	0.0.0.0/0	✔
11210	tcp	0.0.0.0/0	✔
11211	tcp	0.0.0.0/0	✔
11214	tcp	0.0.0.0/0	✔
11215	tcp	0.0.0.0/0	✔
18091	tcp	0.0.0.0/0	✔
18092	tcp	0.0.0.0/0	✔
21100-21199	tcp	0.0.0.0/0	✔

This seems to be consistent with the information here:

http://docs.couchbase.com/couchbase-manual-2.5/cb-install/#network-ports

Cheers,

Steven

[Brett Lawson]

Hey Steve,

Would you kindly attempt to provide your config as such (without the http scheme):

var config = {

host: 'ec2-54-83-43-209.compute-1.amazonaws.com',

bucket: 'test'

};

Cheers, Brett

[Jason Broughton]

Hi Guys

Did you find any resolution for this? Im getting the same thing. Im trying to insert 5,000 records with setMulti on Node.js.

Cheers

Jason

 

[jahanzaib...@gmail.com]

Hi Steven,

Did you find any solution to this problem. I am facing same problem and unable to found any soltion.

[Steven Barlow]

No, sorry, in the end I never got to the bottom of this. Since I now access Couchbase via sync gateway, it has ceased to be an issue for me.

--
You received this message because you are subscribed to a topic in the Google Groups "Couchbase" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/couchbase/scrTb94Mj3w/unsubscribe.
To unsubscribe from this group and all its topics, send an email to couchbase+...@googlegroups.com.