On Friday, November 22, 2013 4:23:30 PM UTC-6, David Ashby wrote: > > I've been experiencing some odd behavior with puppet and checking the > status of running processes. Let me see if I can explain it: > > I have a very simple node.js socket server I'm attempting to puppetize. It > is managed through an init.d script with start, stop, status, and restart. > The init.d script runs perfectly fine as any other user in the system. > However, when puppet attempts to check status or start the server, it fails > and reports it received '1' on exit. > >
[...] > > /etc/init.d/node is > https://github.com/chovy/node-startup<https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fchovy%2Fnode-startup&sa=D&sntz=1&usg=AFQjCNEi0LMzwvGbldWNdo2wNojZ5zvBuQ>with > some minor variations for my specific environment. > > Again, everything works great when I run it manually but falls down when I > throw puppet at it. Any advice, more debugging angles I could take? > Have you checked what the exit code is when you run the script manually? I bet it's 1. The initscript you link to makes no attempt to return LSB-compliant status codes. See http://refspecs.linuxbase.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html. In fact, the initscript also doesn't use the standard initscript functions to do any of its work (see http://refspecs.linuxbase.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptfunc.html), though that's not likely to present a problem for Puppet. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/b57180e8-acbe-4a8e-99e4-ab9d0c5189ac%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
