On 07/27/2010 08:08 AM, Monachus wrote:
On Jul 27, 8:40 am, Tore<[email protected]>  wrote:
Could it be that when you change "nagios_name.rb" file on
pupptermaster A, there is an event triggered so that Apache reloads
this file? But since this event isn't passed over to nfs in any way,
this doesn't happend to puppetmaster B?
NFS caching was one of the things that I looked at.  NFS stats the
file to determine if it needs to be reloaded, and I've adjusted this
to as aggressive as possible.  I know that the puppetmasters reload
other files immediately on change (manifests, modules, other file
resources being pushed to the clients) - it's only the function that
is having an issue, and only _this_ function, which is even weirder.
That's why I posted the function on pastebin - maybe there's some ruby
shortcut in there which makes Puppet barf when it's between 1 and 3 in
the afternoon and the moon is between 36% and 42% full on any of the
last 4 Tuesdays.

Have you tried to restart every component after you change a file,
just to verify that it is read correct by all components?
I have.  When I had the problem the other day on one puppetmaster and
not the other, I went through a battery of tests including bouncing
Apache and thus puppetmasterd (since it runs under Passenger).  In an
earlier iteration I even put the entire NFS datastore on local storage
and removed NFS from the equation.  It doesn't help.  The only thing
that helps is if I physically change the nagios_name.rb file somehow.
It's like there's a cache somewhere that isn't obvious - some place
where puppetmasterd is storing the functions in a serialized form for
quick reload, maybe?

Have no idea if this is to any help but its better than nothing.
Thanks for the thoughts - any and all help is appreciated.  It's a
weird weird bug to try and track down.  I'm pleased that my workaround
is holding, though I'd like to know that a long-term fix is possible.

Adrian

I don't have much in the way of suggestions, but I ran into a lot of problems recently when I tried to have a docroot sitting on NFS. No matter what I did I always ran into weird problems just like this. It sort of worked but definitely not something I could use in production...

--
Joe McDonagh
Operations Engineer
AIM: YoosingYoonickz
IRC: joe-mac on freenode
"When the going gets weird, the weird turn pro."

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to [email protected].
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.

Reply via email to