Hi Behrad, Could it be that your system is trying to stop/restart your couch service at this 5 sec interval? There was a thread about this a few weeks ago where the problem was that the system was stopping and restarting couch, but couch was not properly getting stopped.
See e.g. here for the beginning of the thread: http://bit.ly/1o6q8EI Cheers, Mike On Mon, May 19, 2014 at 12:20 PM, Behrad <behr...@gmail.com> wrote: > In my 1.3.1 production environmet I see this error every 5secs while > couchdb is working and no monit, upstart, ... process is monitoring it! > > [Mon, 19 May 2014 07:14:08 GMT] [error] [<0.125.0>] {error_report,<0.31.0>, > {<0.125.0>,crash_report, > [[{initial_call, > > {mochiweb_socket_server,init,['Argument__1']}}, > {pid,<0.125.0>}, > {registered_name,[]}, > {error_info, > {exit,eaddrinuse, > [{gen_server,init_it,6}, > {proc_lib,init_p_do_apply,3}]}}, > {ancestors, > [couch_secondary_services,couch_server_sup, > <0.32.0>]}, > {messages,[]}, > {links,[<0.94.0>]}, > {dictionary,[]}, > {trap_exit,true}, > {status,running}, > {heap_size,1597}, > {stack_size,24}, > {reductions,458}], > []]}} > > What does it mean? is another CouchDB process being started? or Couchdb is > facing an error while creating a new socket for a client connection? > > -- > --Behrad >
