[chef] Re: Problem installing chef server on Ubuntu 10.04 LTS

[Sam Hamilton < >]

Hi,

I have managed to move forward a little bit there was a problem with rabbitmq resolving the local host name and that was stopping the installation process. You could successfully resolve svr004.dfw but not svr004. So I reinstalled the machine and started from scratch this time making sure the svr004 hostname resolved before installing. 

It now looks like rabbitmq installs but the full install fails:

:~# sudo apt-get install chef chef-server

[SNIP]

Setting up libjetty-extra-java (6.1.22-1ubuntu1) ...

Setting up solr-jetty (1.4.0+ds1-1ubuntu1) ...

 * Not starting jetty - edit /etc/default/jetty and change NO_START to be 0 (or comment it out).

Setting up chef-solr (0.10.4-1) ...

Creating vhost "/chef" ...

...done.

sh: Syntax error: EOF in backquote substitution

dpkg: error processing chef-solr (--configure):

 subprocess installed post-installation script returned error exit status 2

dpkg: dependency problems prevent configuration of chef-expander:

 chef-expander depends on chef-solr (>= 0.10.4); however:

  Package chef-solr is not configured yet.

dpkg: error processing chef-expander (--configure):

 dependency problems - leaving unconfigured

Setting up libstdc++6-4.4-dev (4.4.3-4ubuntu5) ...

No apport report written because the error message indicates its a followup error from a previous failure.

                                                                                                          Setting up libboost1.40-dev (1.40.0-4ubuntu4) ...

Setting up libboost-dev (1.40.0.1) ...

Setting up libgecode-dev (3.5.0-1~lucid1) ...

Setting up libdep-selector-ruby (0.0.7-0opscode1) ...

dpkg: dependency problems prevent configuration of chef-server-api:

 chef-server-api depends on chef-solr (>= 0.10.4); however:

  Package chef-solr is not configured yet.

dpkg: error processing chef-server-api (--configure):

 dependency problems - leaving unconfigured

No apport report written because the error message indicates its a followup error from a previous failure.

                                                                                                          dpkg: dependency problems prevent configuration of chef-server:

 chef-server depends on chef-server-api (>= 0.10.4); however:

  Package chef-server-api is not configured yet.

 chef-server depends on chef-solr (>= 0.10.4); however:

  Package chef-solr is not configured yet.

 chef-server depends on chef-expander (>= 0.10.4); however:

  Package chef-expander is not configured yet.

dpkg: error processing chef-server (--configure):

 dependency problems - leaving unconfigured

No apport report written because MaxReports is reached already

                                                              dpkg: dependency problems prevent configuration of chef-server-webui:

 chef-server-webui depends on chef-server (>= 0.10.4); however:

  Package chef-server is not configured yet.

dpkg: error processing chef-server-webui (--configure):

 dependency problems - leaving unconfigured

No apport report written because MaxReports is reached already

                                                              Setting up libcommons-compress-java (1.0-1) ...

Setting up libcommons-digester-java (1.8.1-2) ...

Setting up libdb-je-java (3.3.62-3) ...

Setting up libicu4j-java (4.0.1.1-1) ...

Setting up libjetty-extra (6.1.22-1ubuntu1) ...

Setting up libjline-java (0.9.94-5) ...

Setting up libjtidy-java (7+svn20070309-4) ...

Setting up icedtea-6-jre-cacao (6b20-1.9.9-0ubuntu1~10.04.2) ...

Setting up default-jre-headless (1.6-34) ...

Setting up ca-certificates-java (20100406ubuntu1) ...

creating /etc/ssl/certs/java/cacerts...

  removed untrusted certificate mozilla/DigiNotar_Root_CA.crt

done.

Processing triggers for libc-bin ...

ldconfig deferred processing now taking place

Errors were encountered while processing:

 chef-solr

 chef-expander

 chef-server-api

 chef-server

 chef-server-webui

E: Sub-process /usr/bin/dpkg returned an error code (1)

:~# 

On 15 Nov 2011, at 13:42, Sam Hamilton wrote:

Many thanks for all the replies - I will go do some more testing and find out what works.

Cheers

Sam 

 

On 15 Nov 2011, at 11:20, Jessica Bourne wrote:

Hi Sam,

Not sure if this will be helpful at this point, but I ran into this same error while testing in Ubuntu 10.04. It was an issue with rabbitmq, but perhaps some extra information will be helpful. In my case, this was specific to an issue with the hostname most likely related to this bug: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/653405

The hostname was not resolving, for instance using the command "ping $HOSTNAME" would respond with unknown host. If you notice that you're having these same symptoms, you can resolve it by editing /etc/hostname and /etc/hosts so the current hostname in /etc/hostname points to 127.0.1.1 or 127.0.0.1 in /etc/hosts, and then rebooting. After that is done you can run these commands to get chef-server re-installed correctly:

sudo apt-get remove rabbitmq-server chef chef-server

sudo rm -R /var/lib/rabbitmq

sudo apt-get install chef chef-server

Hope that helps!

Jessica

On Mon, Nov 14, 2011 at 8:20 AM, Bryan McLellan < "> > wrote:

On Mon, Nov 14, 2011 at 11:15 AM, Daniel DeLeo < "> > wrote:
>> I'm not sure how/why it wasn't created and I was able to briefly speak to ssd7 on the irc chan, but he needed to step away.
> FYI, Chef Server will create these files on startup. From the other information you provided, it seems likely that Chef Server errored out on submitting the client info to RabbitMQ. Getting RabbitMQ working and then restarting chef-server would fix this problem.

Right. When installing from debian packages, debian would not have
started the chef-server because the script that does so runs after
rabbitmq is started, which didn't start either.

Bryan

Attachment: smime.p7s
Description: S/MIME cryptographic signature