We experience this problem too. Our puppetmaster is overloaded (was fine
until we enabled storeconfigs against a mysql server on the same host, now
it's CPU bound, but we're okay with this for the short term).

Do you have something chewing CPU on your systems?

On 8 December 2010 00:07, James Louis <jgloui...@gmail.com> wrote:

> I'm kind of new at all this too but has something been changed recently on
> the server(s) or the network? It looks like there might be a problem with
> accessing network information.
>
>
> On Tue, Dec 7, 2010 at 5:35 AM, Himanshu Raina <dopedoxy...@gmail.com>wrote:
>
>> Hi,
>>
>> Is there anyone who can help in this regard ??
>>
>> On Mon, Dec 6, 2010 at 7:00 PM, Himanshu Raina <dopedoxy...@gmail.com>
>> wrote:
>> > Hi,
>> >
>> > Any help in this regard would be appreciated. Also, when I run the
>> puppetmasterd
>> > with --verbose --no-daemonize --debug mode I get the following output
>> >
>> > debug: Creating default schedules
>> > debug:
>> /Settings[/etc/puppet/puppet.conf]/Settings[puppetmasterd]/File[/etc/puppet/manifests/site.pp]:
>> > Autorequiring File[/etc/puppet/manifests
>> > ]
>> > debug: Finishing transaction -607314048 with 0 changes
>> > info: Listening on port 8140
>> > notice: Starting Puppet server version 0.24.8
>> > debug: Overriding ::ffff:192.168.2.2 with cert name 192.168.2.2
>> > debug: Allowing authenticated client 192.168.2.2(::ffff:192.168.2.2)
>> > access to puppetmaster.getconfig
>> > debug: Our client is remote
>> > info: Expiring the node cache of 192.168.2.2
>> > warning: Could not retrieve fact ipaddress
>> > warning: Could not retrieve fact fqdn
>> > err: Could not call: Could not find terminus plain for indirection node
>> >
>> > regards,
>> >
>> > On Mon, Dec 6, 2010 at 4:43 PM, dopedoxygen <dopedoxy...@gmail.com>
>> wrote:
>> >> Hi,
>> >>
>> >> I have been getting the below error for sometime now. Both master and
>> >> client are using version 0.24.8.
>> >>
>> >> Output from /var/log/messages
>> >>
>> >> err: Could not call puppetmaster.getconfig: #<#<Class:0xb7b50a9c>:
>> >> execution expired>
>> >> err: Could not retrieve catalog: execution expired
>> >>
>> >>
>> >> P.S- all of this was working absolutely fine and suddenly has started
>> >> to misbehave.
>> >>
>> >> Regards,
>> >>
>> >
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To post to this group, send email to puppet-us...@googlegroups.com.
>> To unsubscribe from this group, send email to
>> puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@googlegroups.com>
>> .
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>>
>>
>
>
> --
>  “Twenty years from now you will be more disappointed by the things that
> you didn’t do than by the ones you did do. So throw off the bowlines. Sail
> away from the safe harbor. Catch the trade winds in your sails. Explore.
> Dream. Discover.”
> – Mark Twain
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@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-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to