Ok, so yea, it was a good samaritan updating all the puppet agents via
satellite. No big deal on the clients, but that does break the server in a
very annoying way.
Thank you for the assistance!
On Thursday, November 9, 2023 at 12:23:05 PM UTC-8 James Millsap wrote:
> Migrating/upgrading th
Migrating/upgrading this whole stack is on my list.
A newer version of the puppet agent was installed on this server right
before everything started failing. Main difference appears to be hiera
3.12 vs the 3.4 that was part of the 5.x agent. No idea how that happened
yet, as no one was logg
> On 8. Nov 2023, at 20:17, James Millsap wrote:
>
> Thank you very much for the reply! We are running these versions...
>
> puppetserver version: 5.3.11
> ruby 2.0.0p648
> psych (2.0.0)
> hiera 3.12.0
That is super outdated Puppet version.
Can you please check the puppetserver log file.
The
Thank you very much for the reply! We are running these versions...
puppetserver version: 5.3.11
ruby 2.0.0p648
psych (2.0.0)
hiera 3.12.0
On Wednesday, November 8, 2023 at 11:01:16 AM UTC-8 ben.ford wrote:
> Hey James! That error sounds like you have an out-of-date Psych YAML gem.
>
> What ve
Hey James! That error sounds like you have an out-of-date Psych YAML gem.
What versions of Puppet, Ruby, Hiera, and Psych are you using?
On Nov 8, 2023, at 8:54 AM, James Millsap wrote:
We have a fairly mature puppet instance along with foreman for classification.
For some reason, yesterday
We have a fairly mature puppet instance along with foreman for
classification. For some reason, yesterday, everything started failing
with this error:
Info: Using environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog
Hi,
Puppet server is launching this error message in test environment:
Error: /Stage[main]/Ejecuta/File[nombre.sh]: Could not evaluate: Could not
> retrieve file metadata for puppet:///files/nombre.sh: Error 500 on SERVER:
> Server Error: Not authorized to call find on /file_metadata/files/no
On Friday, October 3, 2014 9:06:09 AM UTC-5, Brian Morris wrote:
>
> I was wrong, Jonathan. That error is actually somewhere in a manifest. You
> can troubleshoot it the same way, though. Just start commenting out
> sections of code in the order that your manifests are invoked in, until you
>
I was wrong, Jonathan. That error is actually somewhere in a manifest. You can
troubleshoot it the same way, though. Just start commenting out sections of
code in the order that your manifests are invoked in, until you find the
culprit.
--
You received this message because you are subscribed t
On 03/10/14 13:43, Brian Morris wrote:
This is bombing on your facters. I would try commenting out successively more
facters, from the bottom of each facter file, until you locate the source of
the error.
OK. How do you tell this? I couldn't really make head or tail of the
error message.
This is bombing on your facters. I would try commenting out successively more
facters, from the bottom of each facter file, until you locate the source of
the error.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this grou
For quite a long time now, we've intermittently been receiving Error 500
when doing puppet runs. There's nothing bad in the puppetmaster log, but
the Apache log on the puppetmaster shows a segfault (see below). Any
ideas for debugging/fixing this?
Thanks,
Jonathan
[jg4461@radius03 ~]$ sudo p
12 matches
Mail list logo
