couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Bisbee (Closed) (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (COUCHDB-606) specifying a [Update_Notification] block in local.ini causes crashes (looping)
Date Sat, 18 Feb 2012 21:43:59 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sam Bisbee closed COUCHDB-606.
------------------------------

    Resolution: Not A Problem

This ticket wasn't actually a bug as the reporter points out.
                
> specifying a [Update_Notification] block in local.ini causes crashes (looping)
> ------------------------------------------------------------------------------
>
>                 Key: COUCHDB-606
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-606
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 0.10.1
>         Environment: Centos5.4, Erlang R13 (otp_src_R13B03.tar.gz), All other dependencies
installed via YUM
>            Reporter: Ollie
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> When the [Update_Notification] block in the INI file is commeted out, everything works.
> As soon as something is specified. e.g. db_update=/usr/local/etc/couchdb/dummy couchdb
spits out hundreds of crash dumps:
> [Tue, 22 Dec 2009 20:32:53 GMT] [info] [<0.1.0>] Apache CouchDB has started on
http://0.0.0.0:5984/
> [Tue, 22 Dec 2009 20:32:53 GMT] [error] [<0.55.0>] OS Process died with status:
0
> [Tue, 22 Dec 2009 20:32:53 GMT] [error] [<0.55.0>] ** Generic server <0.55.0>
terminating 
> ** Last message in was {#Port<0.1157>,{exit_status,0}}
> ** When Server state == {os_proc,"/usr/local/etc/couchdb/dummy",#Port<0.1157>,
>                                  #Fun<couch_os_process.0.4707866>,
>                                  #Fun<couch_os_process.1.68874858>,5000}
> ** Reason for termination == 
> ** {exit_status,0}
> [Tue, 22 Dec 2009 20:32:53 GMT] [error] [<0.55.0>] {error_report,<0.21.0>,
>               {<0.55.0>,crash_report,
>                [[{pid,<0.55.0>},
>                  {registered_name,[]},
>                  {error_info,{exit,{exit_status,0},
>                                    [{gen_server,terminate,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.49.0>]},
>                  {dictionary,[]},
>                  {trap_exit,false},
>                  {status,running},
>                  {heap_size,377},
>                  {stack_size,23},
>                  {reductions,273}],
>                 []]}}
> [Tue, 22 Dec 2009 20:32:53 GMT] [error] [<0.49.0>] Update notification process
<0.55.0> died: {exit_status,0}
> [Tue, 22 Dec 2009 20:32:53 GMT] [error] [<0.53.0>] {error_report,<0.21.0>,
>     {<0.53.0>,supervisor_report,
>      [{supervisor,{local,couch_db_update_notifier_sup}},
>       {errorContext,child_terminated},
>       {reason,normal},
>       {offender,
>           [{pid,<0.54.0>},
>            {name,"db_update"},
>            {mfa,
>                {couch_db_update_notifier,start_link,
>                    ["/usr/local/etc/couchdb/dummy"]}},
>            {restart_type,permanent},
>            {shutdown,1000},
>            {child_type,supervisor}]}]}}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message