Just to be clear, you're saying that perhaps the best option would have been to retry reconfigure again after hitting the initial solr related error, but without first stopping?
I just hit the /version path in the web-ui, which now returns this:
On Jan 18, 2014, at 4:42 PM, Stephen Delano < "> > wrote:
> Again, what data paint are you using to determine what version of the chef server is running?
chef-server 11.0.10
bundler 1.1.5
Component Installed Version Version GUID
-------------------------------------------------------------------------------------------
bookshelf 0.2.1 git:0a01f74ffd1313c4dc9bf0d236e03a871add4e01
cacerts 2012.12.19-1 md5:349ba2d6964db9ca558c9e1daf38e428
chef-expander 11.0.0 git:14b11a96da1273b362f39ab11c411470688a8bd6
chef-gem 11.6.0
chef-pedant 1.0.3 git:15de6cd06f16ee5dee501d6aba36f4ba60162e62
chef-server-cookbooks 11.0.10
chef-server-ctl 11.0.10
chef-server-scripts 11.0.10
chef-server-webui 11.0.10 git:3334f2a577f1cc792b3ca960508bc7e4ac12ee9d
chef-solr 11.0.1 git:bcd45175fd402f3082e7146f94c5d571b0620434
curl 7.23.1 md5:8e23151f569fb54afef093ac0695077d
erchef 1.2.6 git:77ade20f166367b5f0cde468e3c6066b8a327475
erlang R15B02 md5:ccbe5e032a2afe2390de8913bfe737a1
jre 7u3-b04 md5:3d3e206cea84129f1daa8e62bf656a28
libedit 20120601-3.0 md5:e50f6a7afb4de00c81650f7b1a0f5aea
libgcc 11.0.10
libiconv 1.14 md5:e34509b1623cec449dfeb73d7ce9c6c6
libxml2 2.7.8 md5:8127a65e8c3b08856093099b52599c86
libxslt 1.1.26 md5:e61d0364a30146aaa3001296f853b2b9
libyaml 0.1.4 md5:36c852831d02cf90508c29852361d01b
ncurses 5.9 md5:8cb9c412e5f2d96bc6f459aa8c6282a1
nginx 1.4.4 md5:5dfaba1cbeae9087f3949860a02caa9f
omnibus-ctl 0.0.7 git:0dae72b0f55f804294e004632ffaea4418d094a5
openssl 1.0.1e md5:66bf6f10f060d561929de96f9dfe5b8c
pcre 8.31 md5:fab1bb3b91a4c35398263a5c1e0858c1
popt 1.16 md5:3743beefa3dd6247a73f8f7a32c14c33
postgresql 9.2.4 md5:6ee5bb53b97da7c6ad9cb0825d3300dd
preparation 11.0.10
rabbitmq 2.7.1 md5:34a5f9fb6f22e6681092443fcc80324f
rebar retry_use_source git:f21561caf3400a78ee5c17e2032292896fa021ab
rsync 3.0.9 md5:5ee72266fe2c1822333c407e1761b92b
ruby 1.9.3-p484 md5:8ac0dee72fe12d75c8b2d0ef5d0c2968
rubygems 1.8.24 md5:3a555b9d579f6a1a1e110628f5110c6b
runit 2.1.1 md5:8fa53ea8f71d88da9503f62793336bc3version-manifest 11.0.10
unicorn 4.2.0
zlib 1.2.6 md5:618e944d7c7cd6521551e30b32322f4a
Regarding the solr issues, it looks like after running reconfigure with the service stopped, I hit the postgres related error, and then started chef-server again using ...ctl, then reran reconfigure again and everything was fine. I'm sure it's a bit unorthodox, but it got the job done. Just to be clear, you're saying that perhaps the best option would have been to retry reconfigure again after hitting the initial solr related error, but without first stopping? Thanks again, Stephen.
Archive powered by MHonArc 2.6.16.