Thanks Justin/Josh. Josh, I did come across this during my recent searches
on trying to resolve my original issue.
On Tuesday, September 15, 2020 at 1:48:47 PM UTC-4 Josh Cooper wrote:
>
>
> On Tue, Sep 15, 2020 at 5:25 AM pkraw...@gmail.com
> wrote:
>
>> So I've done some research on the pup
On Tue, Sep 15, 2020 at 5:25 AM pkraw...@gmail.com
wrote:
> So I've done some research on the puppet generate types command. I'm
> seeing many different results from not having issues to causing issues with
> puppet apply and puppet agent executions.
We fixed an issue in 6.18.0 (https://ticket
On Tue, Sep 15, 2020 at 5:25 AM pkraw...@gmail.com
wrote:
> So I've done some research on the puppet generate types command. I'm
> seeing many different results from not having issues to causing issues with
> puppet apply and puppet agent executions.
If I was to run this command and things go w
So I've done some research on the puppet generate types command. I'm
seeing many different results from not having issues to causing issues with
puppet apply and puppet agent executions. If I was to run this command and
things go wrong, how do you reverse it? Remove the .resource_types
direc
Justin, yes it's happening in all environments which leads me to believe
it's related to an old copy
in /opt/puppetlabs/puppet/cache/lib/puppet/type. Still trying to wrap my
head around why one domain installation is fine and the other domain
installation is not.
Here is the contents of that
On Fri, Aug 28, 2020 at 10:14 AM pkraw...@gmail.com
wrote:
> Great info but I think I might have found the issue.
>
> So we don't use r10k to deploy code we use a different tool. But what I
> found is on the puppet server (master) the httpfile.rb in
> /opt/puppetlabs/puppet/cache/lib/puppet/type
Great info but I think I might have found the issue.
So we don't use r10k to deploy code we use a different tool. But what I
found is on the puppet server (master) the httpfile.rb in
/opt/puppetlabs/puppet/cache/lib/puppet/type is the older version. I
didn't find any ./resource_types director
> why wouldn't puppet just do this automatically when a module changes?
Some background. Puppet's type and provider system modifies the running
Puppet instance when they're _loaded_. This causes issues when you try to
load multiple conflicting versions of a type in different environments. To
work
So a followup to the original question.
As a test we created a simple module on the node which is failing when
puppet agent executes. Running puppet apply, the parameter quick_check is
found and the module completes successfully. So why would puppet apply
work and not puppet agent?
Code:
cl
Dirk, why wouldn't puppet just do this automatically when a module
changes? Is there a bug somewhere?
On Tuesday, August 25, 2020 at 2:43:03 AM UTC-4 Dirk Heinrichs wrote:
> Am Montag, den 24.08.2020, 11:06 -0700 schrieb pkraw...@gmail.com:
>
> Justin, I implemented the suggestion you made howe
Am Montag, den 24.08.2020, 11:06 -0700 schrieb pkraw...@gmail.com:
> Justin, I implemented the suggestion you made however after running
> the curl command against the 2 environments having the issue and
> receiving the 204 response, the puppet module is still getting the
> 500 error. Do you or an
Justin, I implemented the suggestion you made however after running the
curl command against the 2 environments having the issue and receiving the
204 response, the puppet module is still getting the 500 error. Do you or
anyone else have any other suggestions? Is it possible it's related to
r
On Fri, Jul 17, 2020 at 7:41 AM Peter Krawetzky
wrote:
> Ok I figured out the curl command but I get this error:
>
> [root@mypuppetserver private_keys]# curl -v --header "Content-Type:
> application/json" --cert
> /etc/puppetlabs/puppet/ssl/certs/mypuppetserver.mydomain.com.pem
> --key
> /etc/pup
Ok I figured out the curl command but I get this error:
[root@mypuppetserver private_keys]# curl -v --header "Content-Type:
application/json" --cert
/etc/puppetlabs/puppet/ssl/certs/mypuppetserver.mydomain.com.pem
--key
/etc/puppetlabs/puppet/ssl/private_keys/mypuppetserver.mydomain.com.pem
-
Does this work for Open Source or PE? My installation is using Open Source.
Also can you provide an example of the actual curl command? I can't seem
to get the exact syntax down for it to work.
Thanks for the advice.
On Thursday, July 16, 2020 at 7:55:51 PM UTC-4, Justin Stoller wrote:
>
>
It maybe because of a long environment timeout:
https://puppet.com/docs/puppet/5.5/environments_creating.html#task-3930
In PE this is set to unlimited by default when using code management. The
code manager will then manually evict the cache after a code deployment to
ensure that new code is viewab
I've reviewed sever 500 error posts in here but the answers seem to differ
based on the situation.
One of our developers modified code to include a parameter available in
httpfile 0.1.9 called quick_check.
We have two installation of puppetserver one in lab domain and one in
production do
Thanks Wyatt, that was the issue!
On Wednesday, January 18, 2017 at 9:27:21 AM UTC-8, Wyatt Alt wrote:
>
>
>
> On 01/16/2017 07:05 PM, aloha...@gmail.com wrote:
> > Hello,
> > I just added postgresql 9.6 to my puppet server and receive this error.
> > Error: Could not retrieve catalog from rem
On 01/16/2017 07:05 PM, alohaaa...@gmail.com wrote:
Hello,
I just added postgresql 9.6 to my puppet server and receive this error.
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: [400 ] Unsupported query parameter 'command'
I also looked at the debug info and insta
Hello,
I just added postgresql 9.6 to my puppet server and receive this error.
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
[400 ] Unsupported query parameter 'command'
I also looked at the debug info and installed the gem msgpack just in case,
which seemed like just
Bingo! I set the timeout to 15s on server and agent both (some of our
network links are pretty crappy) and now everyone's connecting as before.
Thanks for the tip!
On Wednesday, October 1, 2014 6:24:07 PM UTC-4, Josh Cooper wrote:
>
>
>
> On Wed, Oct 1, 2014 at 10:47 AM, Bret Wortman > wrote:
>
On Wed, Oct 1, 2014 at 10:47 AM, Bret Wortman wrote:
> I guess not. I upgraded the server to match but the problem persists.
>
>
> On Wednesday, October 1, 2014 1:38:16 PM UTC-4, Bret Wortman wrote:
>>
>> We're running through Passenger and Apache. Puppetdb back-end. Puppet
>> 3.6.2-1 on F20 on t
I guess not. I upgraded the server to match but the problem persists.
On Wednesday, October 1, 2014 1:38:16 PM UTC-4, Bret Wortman wrote:
>
> We're running through Passenger and Apache. Puppetdb back-end. Puppet
> 3.6.2-1 on F20 on the server, Puppet 3.7.1-1 C6.5 on the client. H.
> Could th
We're running through Passenger and Apache. Puppetdb back-end. Puppet
3.6.2-1 on F20 on the server, Puppet 3.7.1-1 C6.5 on the client. H.
Could the newer client be the problem?
On Wednesday, October 1, 2014 1:31:00 PM UTC-4, Henrik Lindberg wrote:
>
> On 2014-01-10 19:21, Bret Wortman wrote:
On 2014-01-10 19:21, Bret Wortman wrote:
This is happening on some of my clients. It'll happen about 1 out of 20
runs, but it's really getting to be a problem. There's nothing
indicative in /var/log/messages or any other server-side log that I can
find, and this is all the output I'm seeing on th
This is happening on some of my clients. It'll happen about 1 out of 20
runs, but it's really getting to be a problem. There's nothing indicative
in /var/log/messages or any other server-side log that I can find, and this
is all the output I'm seeing on the client:
# puppet agent - t
Info: Retr
On Thursday, October 10, 2013 6:58:10 AM UTC-5, alessandro mazzoli wrote:
>
> Thanks Jason and Jared,
> I think, like Jared said, that the user trying to create the tempfile
> cannot write to it (this user may well be puppet, not root.
> So i checked on puppetmaster:
> -permissions:/etc/init.d
Thanks Jason and Jared,
I think, like Jared said, that the user trying to create the tempfile
cannot write to it (this user may well be puppet, not root.
So i checked on puppetmaster:
-permissions:/etc/init.d ls -la
-rwsr-xr-x 1 root root 3727 Sep 12 22:57 puppetmaster
/var/lib/puppet
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
cannot generate tempfile
`/var/lib/puppet/yaml/facts/vagrant1.localdomain.yaml20131009-16545-8oie
5i-9'
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
Security Problem?Suggestion
Hi,
i'm a newbie about Puppet( 1 month ~)
i got error on generate temp file, i'll explain my situation:
-i have a puppetmaster(version: 3.3.0),executed on root
and a puppet agent(version 2.7) provisioning by vagrant,executed on root
-my site.pp, where webserv is a parametrized class, and typews is
Hi,
please share the complete output of 'puppet agent --test'.
On 03/23/2013 01:28 PM, Saeid Ansaripour wrote:
> Hello
> I get the error in title when I run puppet agent on my windows 7 machine
> I can ping puppet master just fine with no problem.
>
> thanks
--
You received this message becaus
Hello
I get the error in title when I run puppet agent on my windows 7 machine
I can ping puppet master just fine with no problem.
thanks
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails f
I'm hoping someone else has experienced the error. The puppetmaster and
agent are on the same system and its having trouble pulling the facter
variables. I've got storedconfigs on MySQL and the last time this happened
I deleted the configs and it started working again. This pops up every
couple of
Hello,
2012/11/24 Nigel Horne
> What are the reasons for the above error (apart from clocks out of sync -
> they aren't, and different versions of Ruby - they aren't).
>
>
Are you sure you have proper content in '/srv/puppet/var/lib/puppet/ssl'?
Does it occur only on one or more systems? Did yo
What are the reasons for the above error (apart from clocks out of sync -
they aren't, and different versions of Ruby - they aren't).
-Nigel
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://grou
Hi,
You sure, cos it seem to be really ugly certificate issue
openssl x509 -text -noout -in
/var/lib/puppet/ssl/certs/hostname.tld.pem | grep -A2 Validity
Can you check the time period of your certificate.. and compare it with
master one.
if it is same, then something serious is happening
That didn't seem to help. I got some weird errors about the certs not
being able to be signed. I was finally able to get one test run, but after
that it went back to giving me the same error.
Any other suggestions?
On Tue, Aug 28, 2012 at 12:18 PM, Ashish Jaiswal wrote:
> Hi,,
>
> Have you tri
Hi,,
Have you tried deleting the existing directory of master and agent..
rm -frv /var/lib/puppet/ssl
Try this and see if this work!!
Regards,
Ashish Jaiswal
On Aug 28, 2012 8:58 PM, "Bai Shen" wrote:
> I'm trying to get puppet to connect to my puppetmaster, but I keep getting
> the same error
I'm trying to get puppet to connect to my puppetmaster, but I keep getting
the same error.
err: Could not retrieve catalog from remote server: SSL_connect returned=1
errno=0 state=SSLv3 read server certificate B: certificate verify failed
I've made sure ntpd is running during the kickstart and th
I've got a few puppet servers running behind Nginx, load balanced with an ELB.
I occasionally see this error in bursts..
>
> Tue Jul 24 09:41:23 + 2012 Puppet (err): Could not retrieve catalog from
> remote server: end of file reached
> Tue Jul 24 09:41:24 + 2012 Puppet (err): Could not
Hello!
I am using puppet-2.7.6 on FreeBSD.
master is running with apache22 and passenger.
I have about 50 clients which share about 20 config files via puppet.
agents are configured to query master every 30 minutes with
splay=true.
After 2-3 days of running, server stops to respond. I see in
What does this error mean or what does it indicate?
puppet-agent: Could not retrieve catalog from remote server: Could
not intern from pson: source did not contain any PSON!
What can I try to resolve it? uninstall/reinstall puppet on the client?
I found a bug report, but not much info in it:
h
Hi,
I just recently upgraded my puppetmaster and clients from 0.25.3 to
2.6.3.rc3. Everything worked fine for a while. Now, none of my
clients are able to retrieve their catalog. Here is some [hopefully]
relevant information:
$ puppetd --server fc-pupm01 --verbose --waitforcert 60 --
environme
Ever since I've upgraded from 2.6.0 to 2.6.2 I've been randomly
getting the following reports from my clients:
Sun Nov 14 16:13:35 -0600 2010 Puppet (err): Could not retrieve
catalog from remote server: end of file reached Sun Nov 14 16:13:35
-0600 2010 Puppet (notice): Using cached catalog Sun No
On Nov 10, 2010, at 8:40 AM, PBWebGuy wrote:
> I have one of 18+ servers in an environment that just started having a
> problem when attempting to do an update. On the node I enter the
> command 'puppetd -t --debug --trace'. I don't see anything obvious
> but the error is: "Could not retrieve
I have one of 18+ servers in an environment that just started having a
problem when attempting to do an update. On the node I enter the
command 'puppetd -t --debug --trace'. I don't see anything obvious
but the error is: "Could not retrieve catalog from remote server"
I set the puppetmaster in
hi all
I run puppet version 0.25.4 on Ubuntu 10.4 LTS as client and as
master.
Everything worked fin, but now I got a problem:
If I try to update with puppetd --test, I get this Error Message:
err: Could not retrieve catalog from remote server: undefined method
`closed?' for nil:NilClass
warnin
Sorry for the double post. Thought the first didnt send.
--
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...@
Hi guys,
I'm trying to setup my first puppet installation and I'm running into
problems.
I've got the puppetmaster running on a fresh install of Centos 5.4.
The puppet client is also on another Centos 5.4 server.
Once I've signed the client certificate on the puppetmaster, the
client seems to bre
Hi guys,
I'm trying to setup my first puppet installation and I'm running into problems.
I've got the puppetmaster running on a fresh install of Centos 5.4.
The puppet client is also on another Centos 5.4 server.
Once I've signed the client certificate on the puppetmaster, the
client seems to bre
I'm getting this frustrating error message and can't figure out why.
Puppet claims I'm missing a template file:
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Could not find template 'nagios/nrpe.cfg/MASTER.erb' at /usr/
local/etc/puppet/modules/nrpe/manifests/init.pp:22
kit wrote:
> If I start ruby in debug mode and puppet in test the error message is
> different:
> ~# /usr/local/bin/ruby --debug /usr/local/sbin/puppetd --server
> puppet.kit.no --rundir /var/run/puppet --test
> Exception `OpenSSL::SSL::SSLError' at /usr/local/lib/ruby/1.8/openssl/
> ssl.rb:123 - h
We are getting this frustrating error on all of our servers after
restarting the puppet server. Can't seem to get rid of it no matter
what.
The following pops up in /var/log/messages after trying to start
puppetd:
Jun 8 10:59:04 svn001 puppetd[92558]: Could not retrieve catalog;
skipping run
Jun
> I get this complaint in Serverlog when I try to define this service:
client/master version?
cheers pete
--
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 t
Hi all,
I get this complaint in Serverlog when I try to define this service:
service { 'svc:/application/jboss:default':
enable => true,
require => [Wf_conf_files['/opt/jboss-4.2.3.GA/server/ontario/conf/
wrapper.conf',
'/opt/jboss-4.2.3.GA/server/
Luv Linux wrote:
> I'm running puppet for the first ime. I've finished the install but
> I'm stuck at the certificate part.
> The puppet master (0.24.4-3) is running on Ubuntu Lenny and the puppet
> client (0.24.8-4.el5) is running on CentOS 5.3.
Not a good idea to have clients with a later versi
Hello all,
I'm running puppet for the first ime. I've finished the install but
I'm stuck at the certificate part.
The puppet master (0.24.4-3) is running on Ubuntu Lenny and the puppet
client (0.24.8-4.el5) is running on CentOS 5.3.
After the install, from the client side, I've run:
puppetd --ser
This one is driving me a little crazy.
This is a Xen host. The first we're trying to get into puppet. I
continuously get:
Could not retrieve catalog: Could not find node 'blah'; cannot compile
I can't figure out why this is happening.
No problem with resolving. The puppetmaster is saying t
58 matches
Mail list logo
