Unable to start sync gateway using sync-gateway config file

Hi,

I got following error while running sync gateway

ERROR:
2017-04-12T13:58:23.759+05:30 WARNING: Error installing Couchbase design doc: Put http://192.168.43.112:8092/sync_gateway/_design/sync_gateway: dial tcp 192.168.43.112:8092: getsockopt: connection refused – db.installViews.func1() at database.go:609
2017-04-12T13:58:23.759+05:30 Debug: RetryLoop retrying Attempt to install Couchbase design doc bucket : sync_gateway after 2560 ms.
_time=2017-04-12T13:58:26.319+05:30 _level=INFO _msg= Trying with selected node 0
2017-04-12T13:58:31.439+05:30 WARNING: Error installing Couchbase design doc: Put ttp://192.168.43.112:8092/sync_gateway/_design/sync_gateway: dial tcp 192.168.43.112:8092: getsockopt: connection refused – db.installViews.func1() at database.go:609
2017-04-12T13:58:31.439+05:30 WARNING: RetryLoop for Attempt to install Couchbase design doc bucket : sync_gateway giving up after 12 attempts – base.RetryLoop() at util.go:301
2017-04-12T13:58:31.439+05:30 FATAL: Error opening database: Put http://192.168.43.112:8092/sync_gateway/_design/sync_gateway: dial tcp 192.168.43.112:8092: getsockopt: connection refused – rest.RunServer() at config.go:758

my conig file

{
“interface”: “:4984”,
“adminInterface”: “:4985”,
“log”:[“CRUD”, “CRUD+”, “HTTP”, “HTTP+”, “Access”, “Cache”, “Shadow”, “Shadow+”, “Changes”, “Changes+”],
“databases”: {
“sync_gateway”: {
“server”: “http://localhost:8091”,
“username”:“sync_gateway”,
“password”:“ineda123”,
“sync”: function(doc) {channel(doc.channels);}
}
}
}

  1. I can able to launch couch base admin console running at 8091.
  2. I created a bucket named sync_gateway with password “ineda123” .

My question why it is trying to install couchbase design doc on “8092” port, as per my knowledge there is nothing running on port 8092. Can any one please help me understand why I am facing this error.

Port 8092 is the Couchbase API port. See https://developer.couchbase.com/documentation/server/3.x/admin/Install/install-networkPorts.html

So if that’s not accessible, it will cause problems like the one you are seeing.

Hi Traun,
Thanks for your reply.
What it mean it is not 8092 is accessible. We are not blocking this port.

Regards,
Srikar