Oh! For some reason I didn't just copy over the default /etc/default/couchdb script in my EC2 setup...
The default one includes this: COUCHDB_STDOUT_FILE=/dev/null COUCHDB_STDERR_FILE=/dev/null Whereas my custom one sent them to /usr/local/var/log/couchdb. I'd guess that explains why there's not more newbs tripped up like this. On Fri, Jan 8, 2010 at 2:16 PM, Kevin Ferguson <[email protected]> wrote: > I don't think he was proposing turning off all logs, just couchdb.stdout. > > We turned off couchdb.stdout on our cluster because 1) it was enormous; 2) > it did not appear to contain anything useful that's not in couch.log; and 3) > we had trouble making it rotate correctly. So I would totally advise > redirecting stdout to /dev/null on a busy production setup. stderr has been > useful, though. > > Kevin > > On Fri, Jan 8, 2010 at 12:11 PM, Noah Slater <[email protected]> wrote: > >> The log files are useful for diagnosing problems. Keep them under >> /var/log/couchdb which the init script takes care of. I would also recommend >> rotating them so they don't get so big. Check the /etc/logrotate.d/couchdb >> script which is provided with CouchDB. The README also mentions this. >> >> On 8 Jan 2010, at 17:58, Zachary Zolton wrote: >> >> > On Fri, Jan 8, 2010 at 11:30 AM, Noah Slater <[email protected]> >> wrote: >> >> Yes, but don't. Why would you do that? >> > >> > Sheer ignorance—I'm just trying to figure out how to improve my >> > CouchDB configuration. (^_^) >> > >> > What happened was I was rotating the couch.log file, but I forgot >> > about the stdout file, which eventually filled up my partition. >> > (Doh...!) When I logged in found the stdout file full of request, >> > which already seemed to be recorded by the couch.log file, so I wasn't >> > sure if the stdout file was useful. (I know: disk space costs approach >> > zero as time goes to infinity, so I shouldn't worry about storing >> > stuff redundantly!) >> > >> > So, I guess I should be asking you about purpose of the stdout/stderr >> > files in order to figure out the best practice. >> > >> > Am I still making sense? My silly thread has grow so long now... (^_-) >> >> >
