I’m running (Couchbase server 5.0, sync gateway 2.0 and CBL 2.0.0 for android app).
After running a month, the android application synced so slow (around 10 mins). After investigating, I saw android app synced to server after create new document but server doesn’t notify to other android device immediately.
When I find in sync_gateway_error.log, it shown a lot of message like:
_time=2018-07-02T03:01:51.145+07:00 _level=INFO _msg=Using plain authentication for user xxxxx
2018-07-02T03:01:52.163+07:00 WARNING: Error processing DCP stream - will attempt to restart/reconnect if appropriate: pkt.Receive, err: EOF. – base.(*DCPReceiver).OnError() at dcp_feed.go:137
2018-07-02T03:01:53.187+07:00 WARNING: Error processing DCP stream - will attempt to restart/reconnect if appropriate: worker auth, server: 127.0.0.1:11210, user: xxxxx, err: read tcp 127.0.0.1:58812->127.0.0.1:11210: read: connection reset by peer. – base.(*DCPReceiver).OnError() at dcp_feed.go:137
2018-07-02T03:01:54.188+07:00 WARNING: Error processing DCP stream - will attempt to restart/reconnect if appropriate: worker connect, server: 127.0.0.1:11210, err: dial tcp 127.0.0.1:11210: getsockopt: connection refused. – base.(*DCPReceiver).OnError() at dcp_feed.go:137
So could you help me find what problem? It was running ok before and I didn’t change anything on server side.
SG is getting connection requests flat out rejected by Server. That usually means the port isn’t open, or is being blocked by a firewall. Can you verify you can connect to 127.0.0.1:11210 from your host machine?
It’s opening by checking command " telnet localhost 11210"
I also check netstat and machine open 11210 on ipv4 & ipv6.
This machine doesn’t enable firewall(iptables)
I don’t know those log is the right issue or not. But the case is “server slow/unable to sync CBL client” all stat of couchbase server UI is normal. bucket is having 8k documents and 40 channels.
I’am also getting this error, have you found a solution?
It might be best to check the Couchbase Server side logs for any info. There are some scenarios where the cluster will terminate connections if a client appears to be offline (e.g., it’s not responding to requests) or if the client isn’t reading data fast enough.
@traun may be able to tell you what to look for specifically in the server side logs.
@traun let me know what we nee to look for.
2018-07-10T16:26:04.389-03:00 WARNING: Error processing DCP stream - will attempt to restart/reconnect if appropriate: worker connect, server: 172.17.0.2:11210, err: dial tcp 172.17.0.2:11210: getsockopt: operation timed out. – base.(*DCPReceiver).OnError() at dcp_feed.go:137
I am receiving this warning what does it mean/what is the solution?