简体   繁体   English

CouchDB:不提供被褥

[英]CouchDB: Not Serving Futon

I've installed CouchDB in Ubuntu 11.10. 我已经在Ubuntu 11.10中安装了CouchDB。 I have an HTTPD server running (which functions properly) as well as all of the prerequisites for CouchDB. 我有一个正在运行的HTTPD服务器(其功能正常)以及CouchDB的所有先决条件。

I've started up CouchDB in the background for a user on the system: 我已经在后台为系统上的用户启动了CouchDB:

sudo -i -u bpetruk couchdb -b 须藤-i -u bpetruk couchdb -b

And it tells me that it's started, and "it's time to relax". 它告诉我它已经开始,并且是“放松的时候了”。 Unfortunately, I can't relax just yet -- because even though the server has loaded, I can't access Futon from the standard http://127.0.0.1:5984/_utils location. 不幸的是,我不能放松-因为即使服务器已加载,我也无法从标准的http://127.0.0.1:5984/_utils位置访问Futon。

Here's some error output from the startup routine. 这是启动例程的一些错误输出。 Horrible, I know lol. 太可怕了,我知道。 It seems to have just dumped some JSON to the terminal: 似乎刚刚将一些JSON转储到了终端:

Apache CouchDB 1.2.0 (LogLevel=info) is starting. Apache CouchDB 1.2.0(LogLevel = info)已启动。 [error] [<0.96.0>] {error_report,<0.31.0>, {<0.96.0>,crash_report, [[{initial_call,{couch_auth_cache,init,['Argument__1']}}, {pid,<0.96.0>}, {registered_name,[]}, {error_info, {exit, {{badmatch,{error,eacces}}, [{couch_auth_cache,ensure_users_db_exists,2}, {couch_auth_cache,open_auth_db,0}, {couch_auth_cache,reinit_cache,1}, {couch_auth_cache,init,1}, {gen_server,init_it,6}, {proc_lib,init_p_do_apply,3}]}, [{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>,<0.97.0>]}, {dictionary,[]}, {trap_exit,true}, {status,running}, {heap_size,610}, {stack_size,24}, {reductions,227}], [{neighbour, [{pid,<0.97.0>}, {registered_name,[]}, {initial_call,{couch_event_sup,init,['Argument__1']}}, {current_function,{gen_server,loop,6}}, {ancestors, [couch_auth_cache,couch_secondary_services, couch_server_sup,<0.32.0>]}, {messages,[]}, {links,[<0.96.0>,<0.89.0>]}, {dictionary,[]}, {trap_exit,false}, {st [错误] [<0.96.0>] {错误报告,<0.31.0>,{<0.96.0>,崩溃报告,[[{initial_call,{couch_auth_cache,init,['Argument__1']}}}},{pid,< 0.96.0>},{registered_name,[]},{error_info,{exit,{{badmatch,{error,eacces}}},[{couch_auth_cache,ensure_users_db_exists,2},{couch_auth_cache,open_auth_db,0},{couch_auth_cache, reinit_cache,1},{couch_auth_cache,init,1},{gen_server,init_it,6},{proc_lib,init_p_do_apply,3}]},[{gen_server,init_it,6},{proc_lib,init_p_do_apply,3}]}} ,{祖先,[couch_secondary_services,couch_server_sup,<0.32.0>]},{消息,[]},{链接,[<0.94.0>,<0.97.0>]},{字典,[]},{ trap_exit,true},{status,running},{heap_size,610},{stack_size,24},{reductions,227}],[{neighbour,[{pid,<0.97.0>}},{registered_name,[] },{initial_call,{couch_event_sup,init,['Argument__1']}},{current_function,{gen_server,loop,6}},{祖先,[couch_auth_cache,couch_secondary_services,couch_server_sup,<0.32.0>]},{消息,[]},{links,[<0.96.0>,<0.89.0>]},{dictionary,[]},{trap_exit,false},{st atus,waiting}, {heap_size,233}, {stack_size,9}, {reductions,32}]}]]}} {"init terminating in do_boot",{{badmatch,{error,{bad_return,{{couch_app,start,[normal,["/usr/local/etc/couchdb/default.ini","/usr/local/etc/couchdb/local.ini"]]},{'EXIT',{{badmatch,{error,shutdown}},[{couch_server_sup,start_server,1},{application_master,start_it_old,4}]}}}}}},[{couch,start,0},{init,start_it,1},{init,start_em,1}]}} atus,waiting},{heap_size,233},{stack_size,9},{reductions,32}]}]}}}} {“初始化终止于do_boot”,{{badmatch,{error,{bad_return,{{couch_app,开始,[正常,[“ / usr / local / etc / couchdb / default.ini”,“ / usr / local / etc / couchdb / local.ini”]]},{'退出',{{badmatch,{错误,shutdown}},[{couch_server_sup,start_server,1},{application_master,start_it_old,4}]}}}}}}}}}}},} [{couch,start,0},{init,start_it,1},{init,start_em ,1}]}}

Equally frustrating is the fact that defining the -s flag on couchdb (which is supposed to print the status of the background process) yields absolutely nothing! 同样令人沮丧的事实是,在沙发床上定义-s标志(应该打印后台进程的状态)绝对不会产生任何结果! So I can't provide information in that regard, either. 因此,我也无法提供这方面的信息。

Are there any common issues I may be blind to in my first foray into the CouchDB world? 在我首次进入CouchDB世界时,我可能会忽略任何常见的问题吗? I'm really stuck on this one! 我真的被这个卡住了!

As suggested by " {{badmatch,{error,eacces}} " in the third line of the error output above, CouchDB was running into some file permissions errors, and couldn't properly write to some file. 正如上面错误输出第三行中的“ {{badmatch,{error,eacces}}} ”所建议的那样,CouchDB遇到了一些文件许可权错误,无法正确写入某些文件。 I wasn't able to determine which file was causing this problem, but taking ownership of the entire CouchDB directory solved the problem. 我无法确定是哪个文件导致了此问题,但是获得整个CouchDB目录的所有权可以解决此问题。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM