couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anthony Ananich <anton.anan...@inpun.com>
Subject Re: os_daemon status
Date Thu, 28 Feb 2013 20:47:09 GMT
I've got what the problem is, thanks!

In log file daemon name is recorded, but I was looking for executable
name. After I found it in log, it became obvious that it crashes and
halted.

On Thu, Feb 28, 2013 at 11:13 PM, Paul Davis
<paul.joseph.davis@gmail.com> wrote:
> Yeah, os daemons should start when the server boots. Check if yours is
> dying a lot by checking error logs. Could be that it fails a couple
> times and then gets shut off.
>
> On Thu, Feb 28, 2013 at 1:54 PM, Anthony Ananich
> <anton.ananich@inpun.com> wrote:
>> Well... Actually I need this daemon to watch /mydb/_changes and my
>> expectation was that it starts with CouchDB.
>>
>> Here is why I was thinking so:
>> This doc http://docs.couchdb.org/en/latest/os-daemons.html points to
>> http://davispj.com/2010/09/26/new-couchdb-externals-api.html
>>
>> Quote:
>> When CouchDB boots it will start each configured OS daemon. If one of
>> these daemons fails at some point, it will be restarted.
>>
>>
>> On Thu, Feb 28, 2013 at 10:04 PM, Robert Newson <rnewson@apache.org> wrote:
>>> started on demand, iirc.
>>>
>>> On 28 February 2013 19:02, Anthony Ananich <anton.ananich@inpun.com> wrote:
>>>> Hi!
>>>>
>>>> Is there a way to check if os_daemon is started or not?
>>>>
>>>> I tried "ps -A | grep python", but I do not see the process.
>>>>
>>>> # cat /etc/couchdb/local.d/mydaemon.ini
>>>> [os_daemons]
>>>> mydaemon = /path/to/my/daemon.py
>>>>
>>>>  (I'm using CentOS 6.3 and CouchDB 1.2.1)
>>>>
>>>> Thanks!
>>>> Anthony

Mime
View raw message