After doing what, exactly? Did you actually try adding these users manually via adduser and/or useradd?
No I didn't add them manually some times puppet works and add them if not existed some time it just hang. Please forgive me if I am skeptical. Does the command 'puppet resource user' agree about how many users there are? (And / or does it exhibit similar behavior?) "puppet resource user" finishing timely in 2-3 seconds. Define "eventually". How long have you let it run before killing the job? What changes has it succeeded in making before you kill it? I waited even more then 24 hours. Also, is there a particular user or users in that class that trigger the behavior, or do they all do so individually? And I don't see where you presented the code for your users::useraccount definition. Perhaps there's a problem with that. For instance, is it by any chance managing very large files or a large number of files? Do you have the same problem with plain User resources that you have with Users::Useraccount? You need to determine what is actually happening before you can fix it. Felix's suggestion to strace the puppet run is a good one, but before that I would look for clues in the agent's and master's logs. Running one or both with --debug output turned on would make clues more likely to appear there. I will try that and let you know. On Thu, Jun 28, 2012 at 6:06 PM, jcbollinger <[email protected]>wrote: > > > On Wednesday, June 27, 2012 8:14:21 AM UTC-5, Azfar Hashmi wrote: >> >> Thanks Jhon for the response but I am still in black-hole. >> > > After doing what, exactly? Did you actually try adding these users > manually via adduser and/or useradd? > > >> Btw total no of users on the system are only below which are in the class. > > > Please forgive me if I am skeptical. Does the command 'puppet resource > user' agree about how many users there are? (And / or does it exhibit > similar behavior?) > > >> So I don't think puppet should take much time to find free UIDs. >> Regarding other classess if I disable all classes and and use only this >> class the behavior is same no matter how long I remain the process running >> puppet just do nothing and consume 100% cpu then I have to kill the process >> eventually. > > > Define "eventually". How long have you let it run before killing the > job? What changes has it succeeded in making before you kill it? > > Also, is there a particular user or users in that class that trigger the > behavior, or do they all do so individually? And I don't see where you > presented the code for your users::useraccount definition. Perhaps there's > a problem with that. For instance, is it by any chance managing very large > files or a large number of files? Do you have the same problem with plain > User resources that you have with Users::Useraccount? > > You need to determine what is actually happening before you can fix it. > Felix's suggestion to strace the puppet run is a good one, but before that > I would look for clues in the agent's and master's logs. Running one or > both with --debug output turned on would make clues more likely to appear > there. > > > John > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/kmtBjDmWbBUJ. > 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. > -- 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.
