Found the issue (not that anyone cares or tried to help here, but just in case someone stumbles on this thread…).
When i did netstat -ab i saw that the projector was using port 9999. So i assumed it’s ok.
But it wasn’t.
ngnix was also using it for OUTBOUND communications which didn’t show up in netstat.
once i changed Couchbase’s port the issue was resolved.
I am glad that you are able to resolve the issue by your own. Apologies from our side for not responding soon enough. Going forward, if you did not get any response soon enough, please ping on the issue so that we can prioritise the issue.
I’m still having issues.
After changing the projector port, I was finally able to create the GSI index on the machine, but I am unable to use it.
Couchbase is throwing a panic error when I try to run a DELETE statement.
I have a Couchbase type bucket. Lets call it bucketA
I created an index:
CREATE INDEX SCindex on bucketA (META().id)
I try to run a select and I get this:
I try to run a delete and I get this:
I try to run a delete from the .NET SDK (188.8.131.52) and the request hangs until my http request times out.
@vsr1, No I haven’t.
Our product is an Enterprise product and we do a lot of QA, so just upgrading Couchbase is something that’s going to require much testing. It’s not something we can just do on a production environment of a customer.
I can upgrade just for the sake of testing, but it would help to know what is this issue and if it’s a known issue with Couchbase 5.01