gistfile1.txt

2016-01-08T01:44:15.094Z Enabling logging: [HTTP]
2016-01-08T01:44:15.094Z ==== Couchbase Sync Gateway/feature/issue_1392_cbgt(df359ca) ====
2016-01-08T01:44:15.094Z Opening db /db as bucket "data-bucket", pool "default", server <http://ec2-54-145-134-37.compute-1.amazonaws.com:8091>
2016-01-08T01:44:15.095Z Opening Couchbase database data-bucket on <http://ec2-54-145-134-37.compute-1.amazonaws.com:8091>
2016/01/08 01:44:15  Trying with selected node 0
2016/01/08 01:44:15  Trying with http://ec2-54-145-134-37.compute-1.amazonaws.com:8091/pools/default/bucketsStreaming/data-bucket
2016/01/08 01:44:15 Got new configuration for bucket data-bucket
2016/01/08 01:44:15  Trying with selected node 0
2016-01-08T01:44:15.418Z Opening Couchbase database index-bucket on <http://ec2-54-145-134-37.compute-1.amazonaws.com:8091>
2016-01-08T01:44:15.432Z Opening Couchbase database index-bucket on <http://ec2-54-145-134-37.compute-1.amazonaws.com:8091>
2016-01-08T01:44:15.439Z Opening Couchbase database index-bucket on <http://ec2-54-145-134-37.compute-1.amazonaws.com:8091>
2016-01-08T01:44:15.459Z Using default sync function 'channel(doc.channels)' for database "db"
2016-01-08T01:44:15.663Z WARNING: No users have been defined in the 'db' database, which means that you will not be able to get useful data out of the sync gateway over the standard port.  FIX: define users in the configuration json or via the REST API on the admin port, and grant users to channels via the admin_channels parameter. -- rest.emitAccessRelatedWarnings() at server_context.go:1089
2016/01/08 01:44:15 main: manager uuid: 1e6711f1d4d8a805
2016/01/08 01:44:15 main: manager uuid was generated
2016/01/08 01:44:15 MCResponse status=KEY_EEXISTS, opcode=SET, opaque=0, msg: Data exists for key