[jira] [Commented] (COUCHDB-527) Add a check to see that the driver directory exists

["Alexander Shorin (JIRA)" <ji...@apache.org>]

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

Alexander Shorin commented on COUCHDB-527:
------------------------------------------

Currently, if driver directory is missed, CouchDB fails to start with next message:

{code}
{"init terminating in do_boot",{{badmatch,{error,{bad_return,{{couch_app,start,[normal,["/etc/couchdb/default.ini","/etc/couchdb/local.ini"]]},{'EXIT',{{badmatch,{error,{shutdown,{failed_to_start_child,couch_primary_services,{shutdown,{failed_to_start_child,collation_driver,"cannot open shared object file: No such file or directory"}}}}}},[{couch_server_sup,start_server,1,[{file,"couch_server_sup.erl"},{line,98}]},{application_master,start_it_old,4,[{file,"application_master.erl"},{line,274}]}]}}}}}},[{couch,start,0,[{file,"couch.erl"},{line,18}]},{init,start_it,1,[]},{init,start_em,1,[]}]}}
{code}

However, it's a bit unclear what file or directory actually missed. If only you link somehow in mind collation_driver atom with util_driver_dir config parameter...I leave it open assuming that this error could be a bit more user-friendly.
                
> Add a check to see that the driver directory exists
> ---------------------------------------------------
>
>                 Key: COUCHDB-527
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-527
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Database Core
>            Reporter: Glenn Rempe
>            Assignee: Paul Joseph Davis
>            Priority: Minor
>
> Adding ticket as reminder per Paul Davis.  Should be assigned to him.
> add a check to see that the driver directory exists 'Eh, $PREFIX/lib/couchdb-$(VERSION/priv/lib'
> and mention in couch_server_sup.erl just before couch_util:start_driver()

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira