Sorry, I replied the other day, guess I forgot to hit send (always
helpful).
Anyway, So yes restarting puppet solved the problem, however, I'm
noticing 9 out of ever 10 changes require me to restart for them to
take effect. Surely this cannot be expected behavior can it?
It's working now, and restarting isn't the worst thing in the world,
but it seems that restarting shouldn't be required just for a change
to take effect.
Thoughts?
On Oct 14, 3:09 am, Peter Meier <[EMAIL PROTECTED]> wrote:
> Hi
>
> >> What version of puppet is this ?
>
> >> # rpm -qa | grep puppet
> >> puppet-0.24.4-1.el5
> >> puppet-server-0.24.4-1.el5
>
> could you then to try run an example manifest, like the one I posted on
> your host?
> So not to get the compiled manifest from puppetmaster rather applying
> the .pp directly on the client.
>
> So something like:
>
> # echo "
> $packages = ["subversion"]
> package { $packages:
> ensure => installed
> }
> " > test.pp
> # puppet test.pp
>
> like that we should be able to exclude any problems which might be
> related to your puppetmaster. afair 0.24.4 this had worked fine for me
> on this version.
>
> greets pete
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
