Puppet users - Apr 2011 - Manifest not applied unless touched

Hi all,

I''m in the process of trying to set up a new puppet server.  We have a
few hundred servers that we manage and we''re looking to migrate to
puppet for a number of reasons I won''t bother getting into.  Given the
number of hosts I''ve installed passenger to leverage Apache, so
here''s
a quick rundown of my setup:

Red Hat linux 5.6 64-bit
puppet 2.6.7
passenger 3.0.7
rack 1.1.0
Apache httpd 2.2.3

I''ve got a painfully simple site.pp file:

  file { "/tmp/test1":
    ensure => present
  }

The first time I ran "puppet agent --test" from a test host using the
above it created /tmp/test1 on the test host, but then I changed the
name to test2, re-ran it, and nothing happened.  After a bit of
troubleshooting I''ve discovered that no edits I make to site.pp are
applied unless I either restart Apache or manually touch site.pp
first.  Simply editing the file and saving it isn''t enough.

I''ve verified that the clocks on both hosts are in sync -
they''re both
configured to use NTP & are fully synced.  I''m not sure what else
to
check.  Any ideas why I''m seeing this behavior?

Thanks,

-Bruce

-- 
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
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Hi,

Yeah, I''ve seen this too. 

Passenger performs caching out of the box. You can turn this off by specifying
''RackEnv development'' in your apache vhost. That should turn
off caching.

It should re-read manifest without it after a timeout (probably also
configurable) for when you want to run in production.

Cheers,
Den

On 29/04/2011, at 5:50, Bruce P <bruce.pennypacker@gmail.com> wrote:
> Hi all,
> 
> I''m in the process of trying to set up a new puppet server.  We
have a
> few hundred servers that we manage and we''re looking to migrate to
> puppet for a number of reasons I won''t bother getting into.  Given
the
> number of hosts I''ve installed passenger to leverage Apache, so
here''s
> a quick rundown of my setup:
> 
> Red Hat linux 5.6 64-bit
> puppet 2.6.7
> passenger 3.0.7
> rack 1.1.0
> Apache httpd 2.2.3
> 
> I''ve got a painfully simple site.pp file:
> 
> file { "/tmp/test1":
>   ensure => present
> }
> 
> The first time I ran "puppet agent --test" from a test host using
the
> above it created /tmp/test1 on the test host, but then I changed the
> name to test2, re-ran it, and nothing happened.  After a bit of
> troubleshooting I''ve discovered that no edits I make to site.pp
are
> applied unless I either restart Apache or manually touch site.pp
> first.  Simply editing the file and saving it isn''t enough.
> 
> I''ve verified that the clocks on both hosts are in sync -
they''re both
> configured to use NTP & are fully synced.  I''m not sure what
else to
> check.  Any ideas why I''m seeing this behavior?
> 
> Thanks,
> 
> -Bruce
> 
> -- 
> 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
puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
> 
-- 
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
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.