Thanks guys, I'll definitely give the auto restart a go, but I am a little worried about what the debug level logging is going to do to my production servers.
On Fri, Oct 29, 2010 at 11:21 AM, Randall Leeds <[email protected]> wrote: > On Fri, Oct 29, 2010 at 02:08, Dirkjan Ochtman <[email protected]> wrote: >> On Fri, Oct 29, 2010 at 11:05, Russell <[email protected]> wrote: >>> I am well aware that a crash report with no information is useless, >>> but I cannot find any logs that tell me what happened. So my question >>> is: >>> >>> 1. Where should I be looking for information about the crash? >> >> You could try to turn on debug-level logs to see what happens right >> before it goes down. Also, is there any memory pressure on the server? >> You might also want to check your syslog. >> >>> 2. What is the best way to auto restart couch on Ubuntu whenever this >>> happens? >> >> I think you can just use normal monitoring services (monit, >> supervisor, that kind of thing). > > There's heartbeat option (-r X) which will restart the server after X > seconds if it dies. > If you're starting couchdb from an init script you may also find > /etc/default/couchdb (or something equivalent in your distro) is a > good place to set this. >
