Issue #2294 has been updated by Brice Figureau.

Luke Kanies wrote:
> I don't know if it will help us fix the problem, but I extracted the code 
> related to managing the hashes of classes and definitions into a new class, 
> LoadedCode.
> 
> It's in the tickets/master/2294 branch in my repo.
> 
> I haven't yet tried to put mutexes in the places that might protect us from a 
> race condition.

Before you add the mutexes, check that the bug is still present :-)
Next, add instrumentation/thread specific debugging. This way we'll gather more 
valuable information (I'm OK to analyse/trace pile of logs).

Note: the branch doesn't exists in your github repo. I think you forgot to push 
it :-)
----------------------------------------
Bug #2294: Classes sometimes cannot be found
http://projects.reductivelabs.com/issues/2294

Author: Luke Kanies
Status: Accepted
Priority: Normal
Assigned to: Luke Kanies
Category: language
Target version: 0.25.0
Complexity: Unknown
Affected version: 0.24.8
Keywords: 


This kind of error occurs multiple times over the course of a week at a client 
of mine:
<pre>
puppetmasterd err puppetmasterd[11913]: Could not find class allusers::charles 
in namespaces allusers::sss at /etc/puppet/modules/allusers/manifests/sss.pp:15 
on node d3i002.view.domain.com
</pre>
I believe it is the result of some kind of race condition or timeout, as I've 
been able to force it to happen under load, but only then.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" 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-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to