Me and another guy having problems with the latest build on Ubuntu. Random Disconnecting errors, can't view documents, you can see the errors on this thread.
I looked at the thread that you linked to and think I know what the issue is. Since you are using a micro instance you don't have a lot of memory. When you create your memcached bucket and everything starts running Couchbase quickly consumes whatever memory you have left over. This causes the os oom killer to take down the process that is consuming the most memory which it looks like is memcached. Error 137 means that the process was killed due to a fatal error, in this case signal 9, which is sigkill. I would recommend trying to use a larger ec2 instance if you are going into production, but for development on a micro instance you can just set up some swap space on the server.
What do you mean by 'swap space', do you mean assigning less memory space for couchbase. I thought that couchbase shouldn't fail on such situation - how can I prevent is from happening so couchbase can work with a micro instance too, MySQL never failed to work when I tested it on micro for development.
Couchbase doesn't appear to be failing, your operating system is killing it. Even with any other application if someone or something sends sigkill to it it will crash. You can liken the situation to not having the appropriate resources that the application needs in order to run. You can get around this by enabling swap space which is described by the link below.
© 2013 COUCHBASE All rights reserved.