Users] Re: Random Internal Server Error after upgrading
from 2.7.19 to 3.3.1
Thank you both for your responses :)
On Wed, Dec 11, 2013 at 9:25 AM, Felix Frank
mailto:felix.fr...@alumni.tu-berlin.de>> wrote:
On 11/29/2013 01:39 PM,
james.eckers...@fasthosts.com<mailto:james.eckers...
Thank you both for your responses :)
On Wed, Dec 11, 2013 at 9:25 AM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:
> On 11/29/2013 01:39 PM, james.eckers...@fasthosts.com wrote:
> >
> > If you aren't setting the vardir explicitly in all clients puppet.conf,
> > I'd suggest doing so befo
On 11/29/2013 01:39 PM, james.eckers...@fasthosts.com wrote:
>
> If you aren't setting the vardir explicitly in all clients puppet.conf,
> I'd suggest doing so before upgrading.
> After my upgrade, I had to manually intervene on almost all client nodes
> because puppet was failing to run. Bug fil
No the error occurred randomly. Once I found the module which seemed to
cause the issue and excluded all other module from the node declaration I
could reproduce the error on every single puppetrun.
On Tue, Dec 10, 2013 at 6:11 PM, Louise Baker wrote:
> Thanks for the response ... will do. Just
Thanks for the response ... will do. Just to clarify though, were you
getting the internal server errors every time the agent ran for a
particular node, or were they sometimes successful?
Lou
On Wed, Dec 11, 2013 at 8:47 AM, Laurent Domb wrote:
> Hi Louise,
>
> In my case the error was trigger
Hi Louise,
In my case the error was triggered by a faulty manifest which contained a
variable ::$fqdn instead of $::fqdn. So it might be worth looking at the
manifests and check for faulty vars.
Laurent
On Dec 10, 2013 5:29 PM, "Louise Baker" wrote:
>
> Hi,
>
> Apologies for the delay in replyi
Hi,
Apologies for the delay in replying. I completely missed the posts!
I am yet to find a solution. I ended up reverting to 2.7.23 until I had
more time to investigate the issue. Laurent, have you had any success in
the past week or so?
Thanks for the heads up James. I'm not explicitly sett
Hi,
For reference, I've just upgraded my puppet masters from 2.7.22 to 3.3.2
and haven't seen any errors of this kind.
I presume you are running with passenger? I am too. CentOS EL6 masters.
Maybe there is a change between 3.3.1 and 3.3.2 that will resolve this for
you both.
I have seen one
I am running into the exact same issue with 3.3.1 Did you find a solution
for it?
On Thursday, October 24, 2013 1:54:28 AM UTC-4, Lou wrote:
>
> Hello,
>
> I have a rhel 6 puppet master with the following packages installed:
>
> facter.x86_641:1.7.3-1.el6
> hiera.noarch
