Description
I notice a behaviour of the update_notification process that I cannot
understand.
I setup CouchDB to send update notifications to an external process in my
local.d/example.ini:
[update_notification]
example = /usr/local/bin/example.py
The script example.py keeps reading lines from stdin and simply logs.
Everything seems to work fine when a normal document is
created/modified/deleted
in a db; the scripts receives the expected notification line:
The problem arises when a DESIGN document gets modified in example_db. In
this
case the script is relaunched and I notice the following in CouchDB logs:
[Mon, 02 Jul 2012 12:03:32 GMT] [info] [<0.127.0>] 10.0.1.18 - - PUT
/example_db/_design/status 201
[Mon, 02 Jul 2012 12:03:32 GMT] [debug] [<0.96.0>] OS Process #Port<0.1894>
Input ::
[Mon, 02 Jul 2012 12:03:32 GMT] [error] [<0.96.0>] Failed sending data:
{[
,
{db,
{<<"example_db">>,
<<"_design/status">>}}]} ->
{json_encode,
{bad_term,
{<<"example_db">>, <<"_design/status">>}}}
[Mon, 02 Jul 2012 12:03:32 GMT] [error] [<0.88.0>] Update notification
process
<0.96.0> died: normal
[Mon, 02 Jul 2012 12:03:32 GMT] [debug] [<0.127.0>] 'GET'
/_utils/document.html?example_db/_design/status
from "10.0.1.18"
Headers:
[
,
,
,
,
,
,
,
,
]
[Mon, 02 Jul 2012 12:03:32 GMT] [error] [<0.94.0>] {error_report,<0.31.0>,
{<0.94.0>,supervisor_report,
[{supervisor,{local,couch_db_update_notifier_sup}},
,
,
{offender,
[
,
,
{mfargs,
{couch_db_update_notifier,start_link,
["/usr/local/bin/example.py"]}},
,
,
]}]}}
Can anyone explain me what is going wrong?
I am using CouchDB 1.2.0
Thanks in advance,
Antonino