Don't keep looping when couchjs fails to start
----------------------------------------------
Key: COUCHDB-619
URL: https://issues.apache.org/jira/browse/COUCHDB-619
Project: CouchDB
Issue Type: Improvement
Environment: couchdb trunk
ubuntu karmic x64
Reporter: Brian Candler
Priority: Minor
Ubuntu just sent out a new version of xulrunner (1.9.1.6 -> 1.9.1.7)
As a result, couchjs no longer worked, as it was linked against 1.9.1.6 in a
specific directory, and that directory had been removed.
However it took me a bit to work out what was going on. When I ran the test
suite, it just got stuck at "> Basic > Running...". A curl
http://127.0.0.1:5984/ was fine, but any attempt to make a query just hung.
Eventually I found that loads of these were being logged:
[Sat, 09 Jan 2010 12:07:43 GMT] [error] [<0.129.0>] OS Process Error <0.1918.0>
:: {os_process_error,{exit_status,127}}
[Sat, 09 Jan 2010 12:07:43 GMT] [error] [<0.129.0>] OS Process Error <0.1921.0>
:: {os_process_error,{exit_status,127}}
[Sat, 09 Jan 2010 12:07:43 GMT] [error] [<0.129.0>] OS Process Error <0.1924.0>
:: {os_process_error,{exit_status,127}}
[Sat, 09 Jan 2010 12:07:43 GMT] [error] [<0.129.0>] OS Process Error <0.1927.0>
:: {os_process_error,{exit_status,127}}
...
(over 3MB by the time I'd realised).
I wonder if couchdb could handle this a bit more gracefully? For example, if
couchjs starts and dies before even a single request has been sent to it, then
disable it for a few minutes and/or log a more specific error message?
Returning an error to the view client would be good too, rather than hanging
waiting for a view update which can never complete. Just a thought.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
