[chef] Re: Re: Re: Re: Re: Chef v11 fails on Centos 6.4

[Daniel DeLeo < >]

On Monday, May 6, 2013 at 5:41 PM, Lunixer wrote:

The chef-solr service starts but status still shows down.

~]# chef-server-ctl stop chef-solr
ok: down: chef-solr: 1s, normally up, want up

~]# chef-server-ctl start chef-solr
ok: run: chef-solr: (pid 26072) 0s

~]# chef-server-ctl status
run: bookshelf: (pid 1148) 2427s; run: log: (pid 1142) 2427s
run: chef-expander: (pid 1150) 2427s; run: log: (pid 1144) 2427s
down: chef-solr: 1s, normally up, want up; run: log: (pid 1143) 2427s
run: erchef: (pid 1145) 2427s; run: log: (pid 1139) 2427s
run: postgresql: (pid 13826) 1193s; run: log: (pid 1141) 2427s
run: rabbitmq: (pid 1146) 2427s; run: log: (pid 1140) 2427s

~]# ps -ef | grep solr
root      1134  1115  0 17:00 ?        00:00:01 runsv chef-solr
root      1143  1134  0 17:00 ?        00:00:00 svlogd -tt /var/log/chef-server/chef-solr


~]# chef-server-ctl service-list
bookshelf*
chef-expander*
chef-solr*
erchef*
postgresql*
rabbitmq*

-lun

solr may be in a crash loop for some reason. Out of the blue guess is that the java min memory setting is too high for your machine. Try 'chef-server-ctl tail' or just look at  /var/log/chef-server/chef-solr

-- 

Daniel DeLeo