[chef] Re: RE: Re: tomcat6 start failing; not much info

["Julian C. Dunn" < >]

On Mon, Nov 4, 2013 at 8:06 PM, Kadel-Garcia, Nico
<
 >
 wrote:
> I'm afraid that the built-in tomcat6 init script isn't very good. It uses
> several different techniques in different parts of the script to detect if
> there is a running tomcat6, it has the root user create a
> /var/run/tomcat6.pid file owned by the tomcat6 user but leaves it empty,
> because only the tomcat6  daemon knows that its pid is, and if the "stop"
> command sent to the tomcat6 user as an "su" command does not succeed it does
> not go back and make sure that the daemon is dead. So the several tomcat6
> "start" and "stop" steps in a row as a configuration is modified by chef can
> interfere with each other, because by the time the tomcat6 init script has
> completed, it's not *really* up and running and has left in place the empty,
> root generated pid file and not populated it yet.
>
> Hilarity then ensues.
>
> This is one of the reasons I dislike the tomcat6 cookbook, and in general
> dislike and building software packages from source tarballs: the RPM or apt
> bundled tomcat packages are, generally, much better about this sort of
> thing.

AFAIK, the opscode tomcat cookbook uses the vendor packages (Debian/Ubuntu's).

- Julian

-- 
[ Julian C. Dunn 
<
 >
          * Sorry, I'm    ]
[ WWW: http://www.aquezada.com/staff/julian    * only Web 1.0  ;]
[ gopher://sdf.org/1/users/keymaker/           * compliant!    ;]
[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9       ]