I had this same problem and couldn't figure out why it did it. I was
moving from 2.7.23 to 3.x and it was driving me nuts, I never found what
was the exact cause as there weren't any errors showing up and ' puppet
agent -t' ran clean.
I ended up blowing away my whole puppet/passenger/puppetdb install and
starting from 3.4 in order to get past it. I wish you better luck.
On 12/30/2013 06:04 PM, Jon Yeargers wrote:
I have a group of services that are supposed to be maintained by
puppet agent. Up until I moved from 2.6 to 3.4 they were kept up to
date and running (as expected).
Since the upgrade of the puppet agent these services are no longer
being monitored. I'm sure that the server is still seeing the files as
errors in them are flagged.
Running 'puppet agent --debug' shows the requests for 'service <name>
status' go by and yet even though the service is not running there is
no move to start it. Running the 'service <name> start' command starts
the service normally.
So: what have I broken by upgrading my clients? As I mentioned - this
used to work.
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/dba2294d-826c-46d1-817c-6fd383818220%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/52C1FDA2.6090106%40gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
