Details
-
Task
-
Resolution: Won't Fix
-
Major
-
None
-
3.0.1
-
None
-
Security Level: Public
-
None
-
EC2 t1.micro instance:
Linux ip-10-248-10-219 3.2.0-41-virtual #66-Ubuntu SMP Thu Apr 25 03:47:17 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Description
I had started with a pre-release version of 3.0 and
ran into trouble there with it pegging the machine at full CPU. I may have accidentally killed all Erlang processes on the machine at one point, so I chalked it up to either that or running a pre-release version. The main notes I have from that are this log snippet: https://gist.github.com/natevw/ea4748ce91b5d7408bd2
Anyway, when I noticed that I installed the 3.0.1 release instead and it seemed to resolve the problem. However, today I logged back into that server and noticed the CPU was getting chewed up by Couchbase again. The admin console was not responding on port 8091. I ran `sudo /etc/init.d/couchbase-server stop` and it took forever but did eventually work.
At this point I tried restarting with `sudo /etc/init.d/couchbase-server start` and same thing: CPU pegged, nothing reponding on port 8091. The stop command took a long time again. Note that in the months between the original problem and [noticing] a similar issue today the CB daemon was pretty much unused, maybe some occasional tire kicking. Single node, no significant data, no XDCR, mostly just playing around with geospatial views through the admin console, then logging out and leaving it alone…
I've posted a bit of log info to https://gist.github.com/natevw/e0f7759b317dfe87d800 and sent @ingenthr a cb_collectinfo dump taken while the server was running.