couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Newson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-372) update_notification broken with couchspawnkillable change
Date Mon, 01 Jun 2009 02:11:07 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714952#action_12714952
] 

Robert Newson commented on COUCHDB-372:
---------------------------------------

davisp on IRC suggested this fix, which works for me;

Index: src/couchdb/couch_db_update_notifier.erl
===================================================================
--- src/couchdb/couch_db_update_notifier.erl	(revision 780544)
+++ src/couchdb/couch_db_update_notifier.erl	(working copy)
@@ -37,7 +37,7 @@
     couch_event_sup:stop(Pid).
 
 init(Exec) when is_list(Exec) -> % an exe
-    couch_os_process:start_link(Exec, [], [stream, exit_status, hide]);
+    couch_os_process:start_link(Exec, []);
 init(Else) ->
     {ok, Else}.
 

> update_notification broken with couchspawnkillable change
> ---------------------------------------------------------
>
>                 Key: COUCHDB-372
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-372
>             Project: CouchDB
>          Issue Type: Bug
>            Reporter: Robert Newson
>            Priority: Critical
>
> as of at least r780544, my update_notification cannot be launched by couchdb. I get this;
> Apache CouchDB 0.10.0a780544 (LogLevel=info) is starting.
> [error] [<0.49.0>] {error_report,<0.22.0>,
>     {<0.49.0>,crash_report,
>      [[{pid,<0.49.0>},
>        {registered_name,[]},
>        {error_info,
>            {exit,
>                {bad_return_value,{os_process_error,{data,"kill -9 19883\n"}}},
>                [{gen_server,init_it,6},{proc_lib,init_p_do_apply,3}]}},
>        {initial_call,{couch_os_process,init,['Argument__1']}},
>        {ancestors,
>            [couch_db_update,couch_primary_services,couch_server_sup,<0.1.0>]},
>        {messages,[]},
>        {links,[<0.43.0>]},
>        {dictionary,[]},
>        {trap_exit,false},
>        {status,running},
>        {heap_size,610},
>        {stack_size,23},
>        {reductions,244}],
>       []]}}
> {"init terminating in do_boot",{{badmatch,{error,shutdown}},[{couch_server_sup,start_server,1},{erl_eval,do_apply,5},{erl_eval,exprs,5},{init,start_it,1},{init,start_em,1}]}}
> If I comment out the first line in src/couchdb/priv/couchspawnkillable my process is
launched correctly but is then killed shortly afterwards by couch;
> Apache CouchDB 0.10.0a780544 (LogLevel=info) is starting.
> [couchdb-lucene] INFO indexer started.
> [couchdb-lucene] INFO indexer stopped.
> [error] [<0.49.0>] {error_report,<0.22.0>,
>     {<0.49.0>,crash_report,
>      [[{pid,<0.49.0>},
>        {registered_name,[]},
>        {error_info,
>            {exit,
>                {bad_return_value,{os_process_error,"OS process timed out."}},
>                [{gen_server,init_it,6},{proc_lib,init_p_do_apply,3}]}},
>        {initial_call,{couch_os_process,init,['Argument__1']}},
>        {ancestors,
>            [couch_db_update,couch_primary_services,couch_server_sup,<0.1.0>]},
>        {messages,[]},
>        {links,[<0.43.0>]},
>        {dictionary,[]},
>        {trap_exit,false},
>        {status,running},
>        {heap_size,610},
>        {stack_size,23},
>        {reductions,244}],
>       []]}}
> {"init terminating in do_boot",{{badmatch,{error,shutdown}},[{couch_server_sup,start_server,1},{erl_eval,do_apply,5},{erl_eval,exprs,5},{init,start_it,1},{init,start_em,1}]}}
> Crash dump was written to: erl_crash.dump
> init terminating in do_boot ()
> real	0m5.769s
> user	0m0.648s
> sys	0m0.520s

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message