On Tue, Mar 17, 2015 at 4:52 AM, James Green
wrote:
> I am not convinced that this is to do with an agent being busy then
> attempting the next connection.
>
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Info: Loading facts
> Error: Could not retrieve catalog from remote server: end
I am not convinced that this is to do with an agent being busy then
attempting the next connection.
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: end of file reached
Warning: Not using cache on failed catalog
Error: C
On Thu, Mar 12, 2015 at 4:21 AM, James Green
wrote:
> I was running puppet agent -t --noop repeatedly with this error.
>
> Running again, this time omitting --noop, it succeeded. Not entirely clear
> what this tells me...
>
> On 12 March 2015 at 10:58, James Green wrote:
>
>> Error:
>> /Stage[ma
I was running puppet agent -t --noop repeatedly with this error.
Running again, this time omitting --noop, it succeeded. Not entirely clear
what this tells me...
On 12 March 2015 at 10:58, James Green wrote:
> Error:
> /Stage[main]/Our_unattended_upgrades/File[/etc/apt/apt.conf.d/20auto-upgrade
Error:
/Stage[main]/Our_unattended_upgrades/File[/etc/apt/apt.conf.d/20auto-upgrades]:
Could not evaluate: Could not retrieve file metadata for
puppet:///modules/our_unattended_upgrades/etc/apt/apt.conf.d/20auto-upgrades:
end of file reached
Wrapped exception:
end of file reached
Versions on the s
Hi,
Sorry for the delayed response.
In our case we are using Passenger.
On 5 March 2015 at 15:24, Henrik Lindberg
wrote:
> On 2015-05-03 12:02, James Green wrote:
>
>> We occasionally have an agent fail because of this. I'm told by others
>> running the agents more frequently that it appears t
On 2015-05-03 12:02, James Green wrote:
We occasionally have an agent fail because of this. I'm told by others
running the agents more frequently that it appears to be at random and
not on anything particularly large.
If you are using webrick then it is most likely a concurrency problem
(more
It seems like other people have had this issue, and maybe it's when the
puppetmaster process restarts in the middle of somebody's agent run?
https://projects.puppetlabs.com/issues/3019
https://projects.puppetlabs.com/issues/4808
In your place I would probably do the following:
a) turn up the lo
We occasionally have an agent fail because of this. I'm told by others
running the agents more frequently that it appears to be at random and not
on anything particularly large.
Looks like server and agents are 3.7.4, both Ubuntu. Can't see much in the
way of server logs.
Any ideas where to go to
