couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From CGS <>
Subject Re: CouchDB log to Syslog
Date Wed, 20 Jun 2012 09:58:29 GMT
The best practice for logging an applications under Linux is to do it under
/var/log/<application_name>/ and CouchDB follows it (you just need to set
PREFIX option to / at configuration time). Combining CouchDB log with
webserver log with... in syslog may be a bad idea because of the following
1. write access;
2. enormous size of the log;
3. difficulty in searching for specific errors.
These are but the main reasons I can see now. I am sure that if one sits on
it he/she can find more.

But if you still think of that idea, find in default.ini (or local.ini for
that matter) the log part:

file = /var/log/couchdb/couch.log
level = info
include_sasl = true

and you can redefine it to

file = /var/log/syslog

Force CouchDB to reload the initialization files or restart it and you have
CouchDB log thrown into your syslog.


On Wed, Jun 20, 2012 at 11:17 AM, Peter Lemenkov <> wrote:

> 2012/6/20 Alexander Shorin <>:
> > Hi Thomas,
> >
> > AFAIK, such feature currently available only by self source patching:
> >
> >
> > but I suppose any feedback and improvements would be welcomed(:
> Log everything to stdout/stderr and redirect both of them to the
> syslog by using systemd's Journald - I'm currently considering this
> approach for Fedora package. I'm sure this won't work for everyone but
> you asked for alternatives so here it is.
> --
> With best regards, Peter Lemenkov.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message