Long shot question, but I'm running out of ideas...
I'm running puppet-0.25.2 on Fedora boxes to manage a simple Java
service started through an /etc/init.d script. I can start, stop,
restart, and examine the service status using the standard /sbin/
service command. Works like a champ.
The issue is that when I use puppet to start the service, the service
fails to run. Specifically, I have a basic 'service { "name": ensure
=> true }' defined. I run "puppetd --test" and I see it changing the
status of the service from stopped to running, and yet my Java service
fails with random NoClassDefFound errors.
I keep coming back to the fact that I can run my example service with
a direct call to '/sbin/service name start' and everything works
fine. Yet when Puppet makes that same call (I've seen it in the debug
logs), my service fails. What's the difference in execution contexts?
Now, I know you're immediately going to guess that I have some
classpath setup incorrectly or a permissions problem or something.
Believe me, I've gone crazy looking for something... anything. I've
stripped it down to the most basic set of classes. I've added logging
every where. I've looked at everything I can think of. Comparing
puppet vs non-puppet, I can find no difference in the environment,
path, executable, limits, or anything else I can think of at the point
of service execution.
Does anyone have an ideas, hints, or even vague notions of why
Puppet's service execution might be somehow different? I'm certainly
out of ideas to try.
Thanks,
Brian
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
