Sync Gateway hangs on Recomputing document channels

Hi everyone,

Here’s what happens for me on ubuntu.

% cd webserver/sgw
% /opt/couchbase-sync-gateway/bin/sync_gateway -verbose config.json

13:38:46.441707 Enabling logging: [CRUD CRUD+ HTTP HTTP+ Access Changes Changes+]
13:38:46.442237 ==== Couchbase Sync Gateway/1.00 (1.0.0-23; commit 46d2fdaf) ====
13:38:46.442272 Configured MaxFileDescriptors (RLIMIT_NOFILE) to 4096
13:38:46.442306 Opening db /maum2 as bucket “default”, pool “default”, server <http://localhost:8091>
13:38:46.442367 Opening Couchbase database default on <http://localhost:8091>
13:38:46.639504 Recomputing document channels…

Then it just hangs.
It used to work perfectly before I reboot my ubuntu (on AWS) after a touch /forcefsck

I’m waiting for the log to say something about starting admin server and server, but to no avail.

What should I look into?

with warmth and curiosity,


Is that really version 1.00 or did you do a custom compile. First thing I would suggest is getting a current version of sync gateway.

It’s really version 1.00. I haven’t updated in a long time. :slight_smile:
I’m afraid things my python code will break if I update to a new version…
Is there anything I have to worry about?

Well you have to worry about nobody helping you with version 1.00. It’s been end of life since November 2015. There should be very little impact from upgrading it since it doesn’t actually store any data itself (that’s all in Couchbase server). However what is your Couchbase server version then? I hope it is not equally old.

ha ha. :slightly_smiling_face:

It is equally old.

How do I find out the version?

It should be written in many places if you access the Couchbase server UI.

Version: 3.0.2-1603 Enterprise Edition (build-1603)

Cluster State ID: 01B-010-110

That was was end of life April 2016. The enterprise edition makes things more complicated because there are a few possible scenarios here:

  1. You have just been testing something a lot on AWS, in which case you should definitely upgrade because no one is relying on your service
  2. This is a production deployment and people are consuming this service, in which case you should talk to your support representative that is assigned to your enterprise edition license (who will definitely tell you to upgrade)
  3. This is a production deployment and you haven’t paid for a license, in which case you are violating the terms of service and must switch to the community edition (the latest version) or we cannot continue to talk


I’m hesitating to upgrade. Yes, nobody is relying on my service, but I’m worried I may have to completely rewrite everything I’ve written in the past. I don’t have that kind of time. I want to focus more on the thing I’m testing, not on managing databases.

Why would you have to rewrite anything? It’s not like the REST API has changed…

I don’t know what changed. So it’s the fear of the unknown. :slight_smile:

I’m imagining me spending a week trying to get up-to-speed on all the stuff that has changed with sync gateway and the related python API before I can get my web server back up. The web server was written using tornado and depends on the old python API

Alright. Lemme upgrade and see what happens. SIGH

Python API? You mean this thing? Actually I never heard of it before now. That’s a tough situation but that’s the downside of relying on alpha products (they may suddenly end development like this one seems to have). The REST calls implemented in version 1.0 have not changed in the past years so it should still function the same way especially if you only use simple calls like get and put.

No, I mean the Python SDK for couchbase.