Actually, it seems that several nodes have collapsed in my cluster again. This setup is just so instable.
--- Sébastien Arbogast http://sebastien-arbogast.com 2015-01-10 17:02 GMT+01:00 Sebastien ARBOGAST <[email protected]> : > Actually after waiting for a few seconds, I have a few new interesting > lines in the log: > > Jan 10 15:59:16 ip-10-37-182-214.ec2.internal bash[25234]: 15:59:16.714687 > HTTP: #112: GET / > Jan 10 15:59:20 ip-10-37-182-214.ec2.internal bash[25234]: 2015/01/10 > 15:59:20 go-couchbase: call to > Do("_sync:local:198164831c8c009a63aa4ad672089e659ae6c4da") in > github.com/couchbaselabs/go-couchbase.(*Bucket).GetsRaw took 2m7.26569433s > Jan 10 15:59:20 ip-10-37-182-214.ec2.internal bash[25234]: 15:59:20.838861 > WARNING: Couldn't interpret error type *net.OpError, value dial tcp > 10.154.17.142:11210: connection timed out -- base.ErrorAsHTTPStatus() at > error.go:63 > Jan 10 15:59:20 ip-10-37-182-214.ec2.internal bash[25234]: 15:59:20.838905 > HTTP: #094: --> 500 Internal error: dial tcp 10.154.17.142:11210: > connection timed out (127266.8 ms) > Jan 10 15:59:25 ip-10-37-182-214.ec2.internal bash[25234]: 2015/01/10 > 15:59:25 go-couchbase: Error connecting to tap feed of 10.154.17.142:11210: > dial tcp 10.154.17.142:11210: connection timed out > Jan 10 15:59:25 ip-10-37-182-214.ec2.internal bash[25234]: 2015/01/10 > 15:59:25 go-couchbase: TAP connection lost; reconnecting to bucket "mydb" > in 30s > Jan 10 15:59:30 ip-10-37-182-214.ec2.internal bash[25234]: 2015/01/10 > 15:59:30 go-couchbase: call to Do("F36DD77F-ED7A-4725-B081-4D823B7E2E23") > in github.com/couchbaselabs/go-couchbase.(*Bucket).GetsRaw took > 2m7.224263906s > Jan 10 15:59:30 ip-10-37-182-214.ec2.internal bash[25234]: 15:59:30.950869 > WARNING: RevDiff("F36DD77F-ED7A-4725-B081-4D823B7E2E23") --> *net.OpError > dial tcp 10.154.17.142:11210: connection timed out -- > db.(*Database).RevDiff() at crud.go:837 > Jan 10 15:59:41 ip-10-37-182-214.ec2.internal bash[25234]: 15:59:41.851243 > HTTP: #115: GET / > Jan 10 15:59:46 ip-10-37-182-214.ec2.internal bash[25234]: 15:59:46.714265 > HTTP: #116: GET / > Jan 10 16:00:11 ip-10-37-182-214.ec2.internal bash[25234]: 16:00:11.851351 > HTTP: #117: GET / > Jan 10 16:00:16 ip-10-37-182-214.ec2.internal bash[25234]: 16:00:16.714894 > HTTP: #118: GET / > Jan 10 16:00:25 ip-10-37-182-214.ec2.internal bash[25234]: 2015/01/10 > 16:00:25 go-couchbase: call to Do("_sync:user:") in > github.com/couchbaselabs/go-couchbase.(*Bucket).casNext took > 2m7.241817405s > Jan 10 16:00:25 ip-10-37-182-214.ec2.internal bash[25234]: 16:00:25.350854 > HTTP: #105: GET /mydb/_local/198164831c8c009a63aa4ad672089e659ae6c4da > Jan 10 16:00:25 ip-10-37-182-214.ec2.internal bash[25234]: 16:00:25.350877 > WARNING: Couldn't interpret error type *net.OpError, value dial tcp > 10.69.87.151:11210: connection timed out -- base.ErrorAsHTTPStatus() at > error.go:63 > Jan 10 16:00:25 ip-10-37-182-214.ec2.internal bash[25234]: 16:00:25.350917 > HTTP: #105: --> 500 Internal error: dial tcp 10.69.87.151:11210: > connection timed out (127241.9 ms) > Jan 10 16:00:35 ip-10-37-182-214.ec2.internal bash[25234]: 2015/01/10 > 16:00:35 go-couchbase: call to Do("_sync:user:") in > github.com/couchbaselabs/go-couchbase.(*Bucket).casNext took > 2m7.188404953s > Jan 10 16:00:35 ip-10-37-182-214.ec2.internal bash[25234]: 16:00:35.334857 > HTTP: #106: POST /mydb/_revs_diff > Jan 10 16:00:35 ip-10-37-182-214.ec2.internal bash[25234]: 16:00:35.334880 > WARNING: Couldn't interpret error type *net.OpError, value dial tcp > 10.69.87.151:11210: connection timed out -- base.ErrorAsHTTPStatus() at > error.go:63 > Jan 10 16:00:35 ip-10-37-182-214.ec2.internal bash[25234]: 16:00:35.334941 > HTTP: #106: --> 500 Internal error: dial tcp 10.69.87.151:11210: > connection timed out (127188.5 ms) > Jan 10 16:00:41 ip-10-37-182-214.ec2.internal bash[25234]: 16:00:41.851589 > HTTP: #121: GET / > > --- > Sébastien Arbogast > http://sebastien-arbogast.com > > 2015-01-10 16:51 GMT+01:00 Sebastien ARBOGAST < > [email protected]>: > >> I updated the sync gateway logging configuration, restarted SG, created a >> document on one device, and launched the app on the other device to trigger >> a pull. And here is the log I got: >> >> Jan 10 15:47:21 ip-10-37-182-214.ec2.internal bash[25234]: >> 15:47:21.357266 HTTP: #031: GET >> /mydb/_local/6738235ebe0dc3781dbf4c60e1d41300baf00004 >> Jan 10 15:47:21 ip-10-37-182-214.ec2.internal bash[25234]: >> 15:47:21.458146 HTTP: #032: POST /mydb/_revs_diff >> Jan 10 15:47:21 ip-10-37-182-214.ec2.internal bash[25234]: >> 15:47:21.592168 HTTP: #033: POST /mydb/_bulk_docs >> Jan 10 15:47:21 ip-10-37-182-214.ec2.internal bash[25234]: >> 15:47:21.593726 CRUD+: Invoking sync on doc >> "4CBDCF46-47B7-4A05-AB79-756E1770D6F2" rev >> 1-d0dd28be1217281025feebd90280ab4b >> Jan 10 15:47:21 ip-10-37-182-214.ec2.internal bash[25234]: >> 15:47:21.753224 Cache: SAVING #29 >> Jan 10 15:47:21 ip-10-37-182-214.ec2.internal bash[25234]: >> 15:47:21.754983 CRUD: Stored doc "4CBDCF46-47B7-4A05-AB79-756E1770D6F2" / >> "1-d0dd28be1217281025feebd90280ab4b" >> Jan 10 15:47:26 ip-10-37-182-214.ec2.internal bash[25234]: >> 15:47:26.869186 HTTP: #034: PUT >> /mydb/_local/6738235ebe0dc3781dbf4c60e1d41300baf00004 >> Jan 10 15:47:35 ip-10-37-182-214.ec2.internal bash[25234]: >> 15:47:35.823625 HTTP: #035: GET >> /mydb/_local/9278eeb52d066d61a4fdf5390e2a40384443c827 >> Jan 10 15:47:35 ip-10-37-182-214.ec2.internal bash[25234]: >> 15:47:35.823755 HTTP: #036: GET >> /mydb/_local/03d822f2ced50a9a4a21a1c00115808151ffe4b4 >> Jan 10 15:47:35 ip-10-37-182-214.ec2.internal bash[25234]: >> 15:47:35.825118 HTTP: #035: --> 404 missing (3.2 ms) >> Jan 10 15:47:36 ip-10-37-182-214.ec2.internal bash[25234]: >> 15:47:36.215847 HTTP: #037: GET /mydb/_changes?feed=websocket >> Jan 10 15:47:38 ip-10-37-182-214.ec2.internal bash[25234]: >> 15:47:38.705134 HTTP: #038: GET /mydb/_changes?feed=websocket >> Jan 10 15:47:41 ip-10-37-182-214.ec2.internal bash[25234]: >> 15:47:41.851050 HTTP: #039: GET / >> Jan 10 15:47:43 ip-10-37-182-214.ec2.internal bash[25234]: >> 15:47:43.371586 HTTP: #040: GET /mydb/_changes?feed=websocket >> Jan 10 15:47:46 ip-10-37-182-214.ec2.internal bash[25234]: >> 15:47:46.714613 HTTP: #041: GET / >> Jan 10 15:47:51 ip-10-37-182-214.ec2.internal bash[25234]: >> 15:47:51.908295 HTTP: #042: GET /mydb/_changes?feed=websocket >> >> --- >> Sébastien Arbogast >> http://sebastien-arbogast.com >> >> 2015-01-10 16:33 GMT+01:00 ajres <[email protected]>: >> >>> So you are getting docs back in the changes feed, which is what the >>> mobile clients call to see which docs revisions need to be pulled. >>> >>> This suggests that the SG is setup correctly. >>> >>> Can you see the document ID of the document you expected to appear on >>> the second mobile client? >>> >>> It would be useful if you can set the logging in SG as follows: >>> >>> "log": ["Access","Channels","Cache","CRUD+", "REST+", "Changes+"], >>> >>> >>> restart SG >>> >>> Then post a snippet from your SG log showing a doc being pushed from >>> Mobile client 1 and then mobile client 2 starting and (hopefully) >>> connecting to SG with a request for the _changes feed. >>> >>> This will help a lot to debug the issue. >>> >>> Andy >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Couchbase Mobile" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/mobile-couchbase/3fe357e4-5ae2-47f0-8b47-b204c86a4444%40googlegroups.com >>> <https://groups.google.com/d/msgid/mobile-couchbase/3fe357e4-5ae2-47f0-8b47-b204c86a4444%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/CAG1DMa_7bdoHonEnem7EUuktSqVhD0A_w8M7sd%3DSvVQf%2Bvfg%3DA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
