I just saw this, glad you got it worked out. In my experience that sort of
behavior usually does have to do with resource ordering, when something
fails on one the first run but succeeds on the second. It's usually because
a dependency like that got created too late.
Rich
On Thursday, March 27,
Ok, I sorted it out... I used your suggestion too, but the problem was that
on the first run puppet created the log folder after initiating the service
start. And having nowhere to write the log, the application failed to
launch.
So I added require File["/var/log/java/java-app"] to the service
I think you should declare the require Jdk7::Install7['jdk1.7.0_51'] in the
service.
If it doesn't work, I would comment out the service and would try to run it
manually. It doesn't seem a puppet problem.
El 27/03/2014 09:09, "Bogdan Mania" escribió:
> Yes it does. But java gets installed first
Yes it does. But java gets installed first when executing the catalog for
the first time. In the Puppet dashboard it shows for the service "ensure
changed 'stopped' to 'running'".
But the service is not running. If I trigger a second puppet run it shows
again the
On Wednesday, March 26, 2014
The service requiere the java to be installed first?
El 26/03/2014 14:49, "Bogdan Mania" escribió:
> Hi,
>
> I've created a module to manage a custom java application. It has it's own
> SysV init script which is working perfectly.
>
> My issue is this: when a node pulls it's catalog from the mast
Hi,
I've created a module to manage a custom java application. It has it's own
SysV init script which is working perfectly.
My issue is this: when a node pulls it's catalog from the master for the
first time, it doesn't also start the service. It starts the service
however on the second run.
T
