"badrecord" error:
2014-06-11 17:21:00.154 [error] {<<"method=POST; path=/environments/production/cookbook_versions; status=500; ">>,{error,{error,{badrecord,chef_cookbook_version},[{chef_wm_depsolver,'-assemble_response/3-lc$^0/1-0-',2,[{file,"src/chef_wm_depsolver.erl"},{line,291}]},{chef_wm_depsolver,'-assemble_response/3-lc$^0/1-0-',2,[{file,"src/chef_wm_depsolver.erl"},{line,293}]},{chef_wm_depsolver,assemble_response,3,[{file,"src/chef_wm_depsolver.erl"},{line,291}]},{webmachine_resource,resource_call,3,[{file,"src/webmachine_resource.erl"},{line,186}]},{webmachine_resource,do,3,[{file,"src/webmachine_resource.erl"},{line,142}]},{webmachine_decision_core,resource_call,1,[{file,"src/webmachine_decision_core.erl"},{line,48}]},{webmachine_decision_core,decision,1,[{file,"src/webmachine_decision_core.erl"},{line,486}]},{webmachine_decision_core,handle_request,2,[{file,"src/webmachine_decision_core.erl"},{line,33}]}]}}}
And a new one:
2014-06-11 17:30:47.316 [error] Supervisor pooler_chef_depsolver_member_sup had child chef_depsolver_worker started with {chef_depsolver_worker,start_link,undefined} at <0.19090.54> exit with reason killed in context child_terminated
For the "no connections" error, we tried to raise the db client pool to 400 and Postgres max connections to 500 without much success. (As a side note, I'd really like to understand why erchef uses a db connection pool, unless Postgres connections are really much more expensive to establish than MySQL's. Last I can remember connection pools being useful was way back in my Oracle PL*SQL days.)
For /search queries are we tuning the right thing? I expect them to be directed to solr, not Postgres - someone clue me in? Is there a different tunable we should be looking at?
Just a general comment about erchef logging - the log information is almost inscrutable to the hapless administrator. If there any work being done to make the messaging clearer?
Thanks,
--Michael
Archive powered by MHonArc 2.6.16.