[chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Recipe application does not work because chef_envronment is not defined

[Andrea Campi < >]

On Thu, Apr 12, 2012 at 12:23 PM, Jesus M. Movilla
<
 >
 wrote:
> Hi Andrea
>
> You are completely right. It was missing "tomcat" cookbook in the type
> attribute of the databag.
>
> Everything worked fine excepto with the tomcat cookbook. The process of
> starting tomcat gives back the following error.
>
> [Thu, 12 Apr 2012 12:18:34 +0200] DEBUG: service[tomcat] runlevel 5, action
> start, priority 92
> [Thu, 12 Apr 2012 12:18:34 +0200] DEBUG: Executing /usr/sbin/invoke-rc.d
> tomcat6 start
> [Thu, 12 Apr 2012 12:18:39 +0200] DEBUG: ---- Begin output of
> /usr/sbin/invoke-rc.d tomcat6 start ----
> [Thu, 12 Apr 2012 12:18:39 +0200] DEBUG: STDOUT:  * Starting Tomcat servlet
> engine tomcat6
>    ...fail!

What happens if you run /usr/sbin/invoke-rc.d tomcat6 start manually?

Chances are it will fail there too; on some platforms/distros that's
what happens when you start a service that is already started.
Does the service "tomcat" declaration has this for your platform:

supports :status => true

?


Try to at least see it running cleanly once: stop tomcat, remove the
war and its context, and do a chef-client run once; it should run
cleanly and start tomcat.
If it does, then as far as the application cookbook goes everything
should be good.

Sorry, hard to help you much further without getting into a lot of details.