The plugin requires the EPEL repo so I had to install that with this
plugin:
https://forge.puppetlabs.com/stahnma/epel
That solved many of the issues.
On Sun, Nov 2, 2014 at 10:26 AM, Ed Young wrote:
> How do I configure the tomcat plugin?
> Do I execute the examples code fragments?
How do I configure the tomcat plugin?
Do I execute the examples code fragments? If so, how are they executed?
RE: https://github.com/puppetlabs/puppetlabs-tomcat#beginning-with-tomcat
It looks like the code fragments in the examples directory correspond to
the instructions above.
../modules/tomc
better understanding.
On Thursday, August 22, 2013 10:00:38 AM UTC-6, Stephen Gran wrote:
>
> On 22/08/13 16:39, Ed Young wrote:
> > Thanks for the response. There doesn't seem to be another process
> > updating the files on before the puppet run. I believe the issue wa
ts.
> You may have to check the contents of httpd.conf file before and running
> the puppet(use vimdiff command). There may possibility that httpd.conf file
> is edited by another service,
>
> Thanks and Regards,
> Rahul Khengare,
> NTT DATA OSS Center, Pune, India.
&g
Despite no change in file (actually, template) content, with each catalog
run I get such log output as:
Aug 19 20:49:50 app-dev puppet-agent[30132]:
(/Stage[main]/Apache-httpd/File[/etc/httpd/conf/httpd.conf]/content)
content changed '{md5}b8a5c22154e45771bc09ef5c34
[root@chimps-dev puppet]#
