[Puppet Users] Re: Could not retrieve catalog from remote server: Error 400 on SERVER: cannot generate tempfile `/var/lib/puppet/yaml/facts/vagrant1.localdomain.yaml20131009-16545-8oie5i-9'
Thx so much John as you explained was a permission problem:
as you explained i fixed like this:
On pupputmaster :
service puppetmaster stop
chown puppet:puppet /etc/init.d/puppetmaster
rm -r /var/lib/puppet/yaml/facts
chown puppet:puppet /var/lib/puppet/yaml/node/hostname and puppetmaster
name, before has root permission(my bad)
service puppetmaster restart
I also checked that facts has been created with puppet permission
Il giorno mercoledì 9 ottobre 2013 17:16:20 UTC+2, alessandro mazzoli ha
scritto:
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 a
parameter to choice nginx or lamp module,
-i have my Enc node with path /var/lib/puppet/yaml/facts/ on my
puppetmaster
-Selinux disabled
node 'vagrant1.localdomain'{
include webserv
class{ 'webserv':
typews=[nginx],
}
}
puppet agent -t --debug
debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not
exist
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Puppet::Type::User::ProviderLdap: true value when expecting false
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl
does not exist
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Failed to load library 'ldap' for feature 'ldap'
debug: /File[/var/lib/puppet/clientbucket]: Autorequiring
File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/private_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/private_keys]
debug: /File[/var/lib/puppet/state/graphs]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/state/resources.txt]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/client_yaml]: Autorequiring
File[/var/lib/puppet]
debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/etc/puppet/ssl/public_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/public_keys]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/state/last_run_summary.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/client_data]: Autorequiring
File[/var/lib/puppet]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/var/lib/puppet/classes.txt]: Autorequiring
File[/var/lib/puppet]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/run/puppet/agent.pid]: Autorequiring
File[/var/run/puppet]
debug: Finishing transaction -614883798
debug: /File[/etc/puppet/ssl/private_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/private_keys]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/certs/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/public_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/public_keys]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
File[/etc/puppet/ssl]
debug: Finishing
[Puppet Users] Re: Could not retrieve catalog from remote server: Error 400 on SERVER: cannot generate tempfile `/var/lib/puppet/yaml/facts/vagrant1.localdomain.yaml20131009-16545-8oie5i-9'
Il giorno mercoledì 9 ottobre 2013 17:16:20 UTC+2, alessandro mazzoli ha
scritto:
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 a
parameter to choice nginx or lamp module,
-i have my Enc node with path /var/lib/puppet/yaml/facts/ on my
puppetmaster
-Selinux disabled
node 'vagrant1.localdomain'{
include webserv
class{ 'webserv':
typews=[nginx],
}
}
puppet agent -t --debug
debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not
exist
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Puppet::Type::User::ProviderLdap: true value when expecting false
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl
does not exist
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Failed to load library 'ldap' for feature 'ldap'
debug: /File[/var/lib/puppet/clientbucket]: Autorequiring
File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/private_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/private_keys]
debug: /File[/var/lib/puppet/state/graphs]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/state/resources.txt]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/client_yaml]: Autorequiring
File[/var/lib/puppet]
debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/etc/puppet/ssl/public_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/public_keys]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/state/last_run_summary.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/client_data]: Autorequiring
File[/var/lib/puppet]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/var/lib/puppet/classes.txt]: Autorequiring
File[/var/lib/puppet]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/run/puppet/agent.pid]: Autorequiring
File[/var/run/puppet]
debug: Finishing transaction -614883798
debug: /File[/etc/puppet/ssl/private_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/private_keys]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/certs/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/public_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/public_keys]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
File[/etc/puppet/ssl]
debug: Finishing transaction -615437368
debug: Using cached certificate for ca
debug: Using cached certificate for vagrant1.localdomain
debug: Finishing transaction -615696088
debug: Loaded state in 0.00 seconds
debug: Executing '/etc/puppet/etckeeper-commit-pre'
debug: catalog supports formats: b64_zlib_yaml dot pson raw yaml; using
pson
debug: Using cached certificate for ca
debug: Using cached certificate for vagrant1.localdomain
debug: Using
[Puppet Users] Re: Could not retrieve catalog from remote server: Error 400 on SERVER: cannot generate tempfile `/var/lib/puppet/yaml/facts/vagrant1.localdomain.yaml20131009-16545-8oie5i-9'
I had this come up a couple of weeks ago.
Basic of the problem was that the source file it was looking for didn't
exist.
In depth, the file it should have been grabbing did exist, but it wasn't
being evaluated correctly due to a missing rb file in facter. I was
evaluating the source as
puppet:///module/exmaple/file${operatingsystemmajversion}.ext and since
facter on the client did not have the method for getting the major version
it was returning nothing. It would try and get file.ext instead of
file7.ext
When it couldn't find the file it gave me an error about not being able to
create the temp file.
On Wednesday, October 9, 2013 9:16:20 AM UTC-6, alessandro mazzoli wrote:
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 a
parameter to choice nginx or lamp module,
-i have my Enc node with path /var/lib/puppet/yaml/facts/ on my
puppetmaster
-Selinux disabled
node 'vagrant1.localdomain'{
include webserv
class{ 'webserv':
typews=[nginx],
}
}
puppet agent -t --debug
debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not
exist
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Puppet::Type::User::ProviderLdap: true value when expecting false
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl
does not exist
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Failed to load library 'ldap' for feature 'ldap'
debug: /File[/var/lib/puppet/clientbucket]: Autorequiring
File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/private_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/private_keys]
debug: /File[/var/lib/puppet/state/graphs]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/state/resources.txt]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/client_yaml]: Autorequiring
File[/var/lib/puppet]
debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/etc/puppet/ssl/public_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/public_keys]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/state/last_run_summary.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/client_data]: Autorequiring
File[/var/lib/puppet]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/var/lib/puppet/classes.txt]: Autorequiring
File[/var/lib/puppet]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/run/puppet/agent.pid]: Autorequiring
File[/var/run/puppet]
debug: Finishing transaction -614883798
debug: /File[/etc/puppet/ssl/private_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/private_keys]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/certs/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/public_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/public_keys]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug:
[Puppet Users] Re: Could not retrieve catalog from remote server: Error 400 on SERVER: No managed repo yet for this distro.
Removing the node from MySQL resolved the issue, wish someone could elaborate why this happens every few months? On Tuesday, February 5, 2013, Mailing Lists mailingl...@theflux.net wrote: 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 months, any suggestions on how to resolve the issue, maybe a misconfiguration? Master and agent on the same system ok? err: Could not retrieve catalog from remote server: Error 400 on SERVER: No managed repo yet for this distro. at /etc/puppet/modules/yum/manifests/init.pp:54 on node warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Could not retrieve catalog from remote server: Error 400 on SERVER: No managed repo yet for this distro.
After investigating a little futhur I found that the yaml file for this node (and puppetmaster) has only time stamps: --- !ruby/object:Puppet::Node classes: [] expiration: 2013-02-05 16:52:21.747019 -05:00 name: node parameters: environment: production --- !ruby/sym _timestamp: - 2013-02-05 14:05:44 - 2013-02-05 13:58:05 - 2013-02-05 13:28:06 - 2013-02-05 12:58:06 - 2013-02-05 12:28:06 - 2013-02-05 11:58:06 - 2013-02-05 11:28:12 - 2013-02-05 11:28:12 - 2013-02-05 10:58:06 - 2013-02-05 10:28:04 - 2013-02-05 09:58:04 - 2013-02-05 09:28:05 - 2013-02-05 08:58:04 - 2013-02-05 08:28:05 - 2013-02-05 08:26:45 - 2013-02-05 07:58:05 - 2013-02-05 10:58:06 - 2013-02-05 10:28:04 - 2013-02-05 09:58:04 - 2013-02-05 09:28:05 - 2013-02-05 08:58:04 - 2013-02-05 08:28:05 - 2013-02-05 08:26:45 - 2013-02-05 07:58:05 - 2013-02-05 07:28:05 - 2013-02-05 07:28:05 - 2013-02-05 06:58:05 - 2013-02-05 06:28:05 - 2013-02-05 05:58:04 - 2013-02-05 05:28:04 Instead of having populating facts/node information like the other nodes: --- !ruby/object:Puppet::Node classes: [] environment: id001 production expiration: 2013-02-05 16:51:05.079351 -05:00 name: node1 parameters: swapfree: 3.97 GB Can anyone explain to me why this happens? On Tuesday, February 5, 2013, Mailing Lists mailingl...@theflux.net wrote: 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 months, any suggestions on how to resolve the issue, maybe a misconfiguration? Master and agent on the same system ok? err: Could not retrieve catalog from remote server: Error 400 on SERVER: No managed repo yet for this distro. at /etc/puppet/modules/yum/manifests/init.pp:54 on node warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Could not retrieve catalog from remote server: end of file reached
On Tuesday, July 24, 2012 12:47:09 PM UTC-4, Matt Wise wrote: 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 retrieve catalog; skipping run I don't see any obvious accompanying errors on the Puppet master sides... any thoughts on what this might be? Did you have any luck in resolving this issue? The problem has just arisen for me when working with Eucalyptus nodes (I'm calling puppet agent ... to bootstrap from /etc/rc.local). I am running mod_passenger on the Puppet master. This is a single master, single agent setup. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/0htYlM-hmwwJ. To post to this group, send email to puppet-users@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.
[Puppet Users] Re: Could not retrieve catalog from remote server
I sometimes get the same error on puppet 2.6.4 and don't know the cause. Restarting the agent helps, but I would welcome a solution to this. On Jan 12, 1:25 am, Mohamed Lrhazi lrh...@gmail.com wrote: 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:http://projects.puppetlabs.com/issues/5547 Thanks, Mohamed. -- 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.
Re: [Puppet Users] Re: Could not retrieve catalog from remote server
I get this very often... I only have a 4 or 5 hosts setup right now... with version 2.6.3 everywhere. Sometimes I run puppetd --verbose --onetime --no-daemonize, get the error, then run again and not get it. Sometimes I run it dozens of times in a row and get it all the time it's driving me crazy... is this related to my modules/classes themselves? am in the middle of developing them, so sometimes I think its happening because of mistakes in the actual source of my configs could it be? Mohamed. On Wed, Jan 12, 2011 at 5:35 AM, Sven Sporer s...@intothespirit.com wrote: I sometimes get the same error on puppet 2.6.4 and don't know the cause. Restarting the agent helps, but I would welcome a solution to this. On Jan 12, 1:25 am, Mohamed Lrhazi lrh...@gmail.com wrote: 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:http://projects.puppetlabs.com/issues/5547 Thanks, Mohamed. -- 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. -- يوم نلقاك يوم فرحي و هنايا -- 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.
Re: [Puppet Users] Re: Could not retrieve catalog from remote server
Are you using Passenger? If you don't know, the answer is probably no. If not, do this: Shutdown your puppet server. This might work: service puppetmaster stop Start it in debug: puppetmasterd --verbose --debug --no-daemonize --trace Then watch the output on the console for hints while running the clients against it. On Jan 12, 2011, at 9:23 AM, Mohamed Lrhazi wrote: I get this very often... I only have a 4 or 5 hosts setup right now... with version 2.6.3 everywhere. Sometimes I run puppetd --verbose --onetime --no-daemonize, get the error, then run again and not get it. Sometimes I run it dozens of times in a row and get it all the time it's driving me crazy... is this related to my modules/classes themselves? am in the middle of developing them, so sometimes I think its happening because of mistakes in the actual source of my configs could it be? Mohamed. On Wed, Jan 12, 2011 at 5:35 AM, Sven Sporer s...@intothespirit.com wrote: I sometimes get the same error on puppet 2.6.4 and don't know the cause. Restarting the agent helps, but I would welcome a solution to this. On Jan 12, 1:25 am, Mohamed Lrhazi lrh...@gmail.com wrote: 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:http://projects.puppetlabs.com/issues/5547 Thanks, Mohamed. -- 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. -- يوم نلقاك يوم فرحي و هنايا -- 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. -- 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.
Re: [Puppet Users] Re: Could not retrieve catalog from remote server
Thanks Patrick. I see no clues at all: $sudo /opt/ruby-enterprise/bin/ruby /opt/ruby-enterprise/bin/puppet master --no-daemonize --debug --verbose --trace ... notice: Starting Puppet master version 2.6.3 ... info: Expiring the node cache of akubra.example.com info: Not using expired node for akubra.example.com from cache; expired at Wed Jan 12 15:35:15 -0500 2011 debug: Using cached facts for akubra.example.com info: Caching node for akubra.example.com debug: template[inline]: Bound template variables for inline template in 0.00 seconds debug: template[inline]: Interpolated template inline template in 0.00 seconds notice: Compiled catalog for akubra.example.com in environment testing in 0.12 seconds info: Caching catalog for akubra.example.com debug: Searched for resources in 0.00 seconds debug: Searched for resource params and tags in 0.01 seconds debug: Resource removal in 0.00 seconds debug: Resource merger in 0.05 seconds debug: Resource addition in 0.00 seconds debug: Performed resource comparison in 0.05 seconds debug: Using cached node for akubra.example.com debug: Saved catalog to database in 0.07 seconds err: //akubra.example.com/Puppet: Could not retrieve catalog from remote server: Could not intern from pson: source did not contain any PSON! notice: //akubra.example.com/Puppet: Using cached catalog info: //akubra.example.com/Puppet: Applying configuration version '1294864403' Thanks, Mohamed. On Wed, Jan 12, 2011 at 1:48 PM, Patrick kc7...@gmail.com wrote: Are you using Passenger? If you don't know, the answer is probably no. If not, do this: Shutdown your puppet server. This might work: service puppetmaster stop Start it in debug: puppetmasterd --verbose --debug --no-daemonize --trace Then watch the output on the console for hints while running the clients against it. On Jan 12, 2011, at 9:23 AM, Mohamed Lrhazi wrote: I get this very often... I only have a 4 or 5 hosts setup right now... with version 2.6.3 everywhere. Sometimes I run puppetd --verbose --onetime --no-daemonize, get the error, then run again and not get it. Sometimes I run it dozens of times in a row and get it all the time it's driving me crazy... is this related to my modules/classes themselves? am in the middle of developing them, so sometimes I think its happening because of mistakes in the actual source of my configs could it be? Mohamed. On Wed, Jan 12, 2011 at 5:35 AM, Sven Sporer s...@intothespirit.com wrote: I sometimes get the same error on puppet 2.6.4 and don't know the cause. Restarting the agent helps, but I would welcome a solution to this. On Jan 12, 1:25 am, Mohamed Lrhazi lrh...@gmail.com wrote: 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:http://projects.puppetlabs.com/issues/5547 Thanks, Mohamed. -- 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. -- يوم نلقاك يوم فرحي و هنايا -- 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. -- 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. -- 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.
Re: [Puppet Users] Re: Could not retrieve catalog from remote server
I get it too. It's not related to the compilation of the modules but I figure it's possibly related to the webrick server. I don't see it on my passenger/apache set up(which I run on another master). For what it is worth this is good reading for checking the validity of of your modules before you test on hosts (--parseonly). http://www.devco.net/archives/2009/08/19/tips_and_tricks_for_puppet_debugging.php For your actual issue, I ignore it. Cheers Den On 13/01/2011, at 4:23, Mohamed Lrhazi lrh...@gmail.com wrote: I get this very often... I only have a 4 or 5 hosts setup right now... with version 2.6.3 everywhere. Sometimes I run puppetd --verbose --onetime --no-daemonize, get the error, then run again and not get it. Sometimes I run it dozens of times in a row and get it all the time it's driving me crazy... is this related to my modules/classes themselves? am in the middle of developing them, so sometimes I think its happening because of mistakes in the actual source of my configs could it be? Mohamed. On Wed, Jan 12, 2011 at 5:35 AM, Sven Sporer s...@intothespirit.com wrote: I sometimes get the same error on puppet 2.6.4 and don't know the cause. Restarting the agent helps, but I would welcome a solution to this. On Jan 12, 1:25 am, Mohamed Lrhazi lrh...@gmail.com wrote: 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:http://projects.puppetlabs.com/issues/5547 Thanks, Mohamed. -- 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. -- يوم نلقاك يوم فرحي و هنايا -- 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. -- 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.
Re: [Puppet Users] Re: Could not retrieve catalog from remote server
Thanks a lot. I setup and fired up httpd/passenger if I don't post again on this thread, it means it fixed it :) On Wed, Jan 12, 2011 at 4:39 PM, Denmat tu2bg...@gmail.com wrote: I get it too. It's not related to the compilation of the modules but I figure it's possibly related to the webrick server. I don't see it on my passenger/apache set up(which I run on another master). For what it is worth this is good reading for checking the validity of of your modules before you test on hosts (--parseonly). http://www.devco.net/archives/2009/08/19/tips_and_tricks_for_puppet_debugging.php For your actual issue, I ignore it. Cheers Den On 13/01/2011, at 4:23, Mohamed Lrhazi lrh...@gmail.com wrote: I get this very often... I only have a 4 or 5 hosts setup right now... with version 2.6.3 everywhere. Sometimes I run puppetd --verbose --onetime --no-daemonize, get the error, then run again and not get it. Sometimes I run it dozens of times in a row and get it all the time it's driving me crazy... is this related to my modules/classes themselves? am in the middle of developing them, so sometimes I think its happening because of mistakes in the actual source of my configs could it be? Mohamed. On Wed, Jan 12, 2011 at 5:35 AM, Sven Sporer s...@intothespirit.com wrote: I sometimes get the same error on puppet 2.6.4 and don't know the cause. Restarting the agent helps, but I would welcome a solution to this. On Jan 12, 1:25 am, Mohamed Lrhazi lrh...@gmail.com wrote: 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:http://projects.puppetlabs.com/issues/5547 Thanks, Mohamed. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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. -- يوم نلقاك يوم فرحي و هنايا -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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. -- يوم نلقاك يوم فرحي و هنايا -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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.
[Puppet Users] Re: Could not retrieve catalog from remote server - random
Let me also add that I have several servers that have the same exact role in their node definitions and don't have any problem with updates. On Nov 10, 11:40 am, PBWebGuy pbweb...@gmail.com 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 catalog from remote server I set the puppetmaster into debug mode with command 'puppetmasterd -- no-daemonize --debug -v'. When the node attempts to update there is no output by the PM. I therefore setup tcpdump to watch the traffic and there is in fact traffic as shown below. Therefore I know that there is communications. On occasions it will update but is completely random. Any suggestions? Thanks, John tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 11:31:02.253921 IP (tos 0x0, ttl 64, id 59181, offset 0, flags [DF], proto: TCP (6), length: 60) devcas1.domain.local.41082 util3.domain.local.8140: S, cksum 0xb458 (correct), 297236183:297236183(0) win 5840 mss 1380,sackOK,timestamp 666800634 0,nop,wscale 7 11:31:02.254422 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: TCP (6), length: 60) util3.domain.local.8140 devcas1.domain.local.41082: S, cksum 0x7cda (correct), 1623860666:1623860666(0) ack 297236184 win 5792 mss 1460,sackOK,timestamp 3608730031 666800634,nop,wscale 7 11:31:02.255511 IP (tos 0x0, ttl 64, id 59182, offset 0, flags [DF], proto: TCP (6), length: 52) devcas1.domain.local.41082 util3.domain.local.8140: ., cksum 0xc215 (correct), ack 1 win 46 nop,nop,timestamp 666800637 3608730031 11:31:02.357588 IP (tos 0x0, ttl 64, id 64523, offset 0, flags [DF], proto: TCP (6), length: 52) util3.domain.local.8140 devcas1.domain.local.41082: F, cksum 0xc1ad (correct), 1:1(0) ack 1 win 46 nop,nop,timestamp 3608730134 666800637 11:31:02.358933 IP (tos 0x0, ttl 64, id 59183, offset 0, flags [DF], proto: TCP (6), length: 52) devcas1.domain.local.41082 util3.domain.local.8140: ., cksum 0xc146 (correct), ack 2 win 46 nop,nop,timestamp 666800740 3608730134 11:31:02.450472 IP (tos 0x0, ttl 64, id 59184, offset 0, flags [DF], proto: TCP (6), length: 157) devcas1.domain.local.41082 util3.domain.local.8140: P 1:106(105) ack 2 win 46 nop,nop,timestamp 666800831 3608730134 11:31:02.450498 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: TCP (6), length: 40) util3.domain.local.8140 devcas1.domain.local.41082: R, cksum 0xee79 (correct), 1623860668:1623860668(0) win 0 11:33:11.491647 IP (tos 0x0, ttl 64, id 44612, offset 0, flags [DF], proto: TCP (6), length: 334) devcas1.domain.local.55540 util3.domain.local.ldaps: P 3058489015:3058489297(282) ack 81338168 win 128 nop,nop,timestamp 666929878 3608244168 11:33:11.492744 IP (tos 0x0, ttl 64, id 48557, offset 0, flags [DF], proto: TCP (6), length: 446) util3.domain.local.ldaps devcas1.domain.local.55540: P 1:395(394) ack 282 win 155 nop,nop,timestamp 3608859274 666929878 11:33:11.492818 IP (tos 0x0, ttl 64, id 48558, offset 0, flags [DF], proto: TCP (6), length: 142) util3.domain.local.ldaps devcas1.domain.local.55540: P 395:485(90) ack 282 win 155 nop,nop,timestamp 3608859274 666929878 11:33:11.493585 IP (tos 0x0, ttl 64, id 44613, offset 0, flags [DF], proto: TCP (6), length: 52) devcas1.domain.local.55540 util3.domain.local.ldaps: ., cksum 0x102d (correct), ack 395 win 142 nop,nop,timestamp 666929880 3608859274 11:33:11.493595 IP (tos 0x0, ttl 64, id 44614, offset 0, flags [DF], proto: TCP (6), length: 52) devcas1.domain.local.55540 util3.domain.local.ldaps: ., cksum 0x0fd3 (correct), ack 485 win 142 nop,nop,timestamp 666929880 3608859274 -- 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.
[Puppet Users] Re: Could not retrieve catalog from remote server - random
A few more findings: 1. I removed the /var/lib/puppet/clientbucket and ran update manually it worked one time. Repeating this does not work. 2. Here is the Trace of the puppetd command: /usr/lib/ruby/1.8/net/http.rb:586:in `connect' /usr/lib/ruby/1.8/net/http.rb:586:in `connect' /usr/lib/ruby/1.8/net/http.rb:553:in `do_start' /usr/lib/ruby/1.8/net/http.rb:542:in `start' /usr/lib/ruby/1.8/net/http.rb:1035:in `request' /usr/lib/ruby/1.8/net/http.rb:772:in `get' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:69:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:202:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/indirector.rb:51:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:208:in `retrieve_new_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:418:in `thinmark' /usr/lib/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib/ruby/1.8/benchmark.rb:307:in `realtime' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:417:in `thinmark' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:207:in `retrieve_new_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:104:in `retrieve_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:142:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:21:in `lock' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run' /usr/lib/ruby/1.8/sync.rb:229:in `synchronize' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:134:in `with_client' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:51:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetd.rb:103:in `onetime' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `send' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `run_command' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `exit_on_fail' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' /usr/sbin/puppetd:160 3. I'm using .25.5. Any help or suggestions are much appreciated. Thanks, John -- 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.
[Puppet Users] Re: Could not retrieve catalog from remote server - random
Make sure that you get output from the puppetmaster for some things. It's easy to look at the wrong log if you are using passenger. I've seen a similar error problem when the puppetmaster is overloaded so the client times out. For me, this is when It gets all 50 clients ask for a catalog at the same time (don't ask). Could this be the problem? Hi Patrick, I'm running PM in --no-daemonize so I see all output. I'm not using passenger and the server is only being hit by manual invocations by nodes so it is not being overtaxed. It seems completely random in that it will work one out of 20 tries. I don't have any other nodes having an issue. John -- 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.
[Puppet Users] Re: Could not retrieve catalog from remote server - random
I have continued troubleshooting this and have gone as far as: 1. Removed all code from the nodes.pp for this particular node. 2. Deleted the /var/lib/puppet directory on the node and resigned with the PM. Note that the signing failed repeatedly as well where the PM did not report any messages in debug mode. The tcpdump showed traffic for every request from the node. Regards, John -- 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.
[Puppet Users] Re: Could not retrieve catalog from remote server - random
After 6 hours of troubleshooting, we found that there was a process (Alfresco/Tomcat) running on the node that was consuming large amounts of the CPU. Running 'top', there was a sustained load of 2.x. As soon as I killed the process, Puppet started running perfectly! This node is a VM in a VMWare cloud. Hope that this will help someone else someday... Regards, John -- 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.
Re: [Puppet Users] Re: Could not retrieve catalog from remote server Duplicate definition
On Wed, 11 Aug 2010, martin kummer wrote: [files] path /etc/puppet/files allow 178.78.72.121 -space here this breaks the puppetmaster silently. this is real bad. this must be a bug. This is puppet bug #3514. It's supposed to be fixed in version 2.6.0. --apb (Alan Barrett) -- 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.
[Puppet Users] Re: Could not retrieve catalog from remote server Duplicate definition
So I was tried it to fix myself. I found the reason: First, there was no master running. I restarted it several time to find the problem, even with: puppetmasterd -l console --debug it just died, silently. Second: In the file /etc/puppet/fileserver.conf I inserted an space at the end of the ip. [files] path /etc/puppet/files allow 178.78.72.121 -space here this breaks the puppetmaster silently. this is real bad. this must be a bug. I try to look at the ticket at http://projects.puppetlabs.com/projects/puppet/issues, but there is no search. I have to make an account to search? (ok I am a little bit angry, searching for a day for the dam space) ;-) On 11 Aug., 14:44, martin kummer mr...@yahoo.com wrote: 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 warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run So I looked into the syslog on the client side, and found this: Aug 8 07:44:38 localhost puppetd[909]: Using cached catalog Aug 8 07:44:38 localhost puppetd[909]: Could not retrieve catalog; skipping run Aug 8 08:14:39 localhost puppetd[909]: Could not retrieve catalog from remote server: Error 400 on SERVER: Duplicate definition: User[web] is already defined in file /etc/puppet/manifests/classes/ web.pp at line 52; cannot redefine at /etc/puppet/manifests/classes/ users.pp:36 on node web1 Aug 8 08:14:39 localhost puppetd[909]: Using cached catalog Aug 8 08:14:39 localhost puppetd[909]: Could not retrieve catalog; skipping run Aug 8 08:44:40 localhost puppetd[909]: Could not retrieve catalog from remote server: undefined method `closed?' for nil:NilClass So I found out, that I have an, Duplicate definition. But this Duplicate definition Error exists in my Log, since Aug 6 21:43:27: Aug 6 21:43:27 localhost puppetd[909]: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter 'uid' for type 'Group' at /etc/puppet/manifests/classes/users.pp:42 on node web1 Aug 6 21:43:28 localhost puppetd[909]: Using cached catalog But the behavior changed just 36 hours later, this must have something to to with the caching catalog. I fixed the Duplicate definition, but still get the Could not retrieve catalog from remote server Error. Any hints? Thanks in Advance Martin Kummer -- 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.
[Puppet Users] Re: Could not retrieve catalog from remote server: undefined method `closed?' for nil:NilClass
Thanks James, I installed the patch and got the proper error message err: Could not retrieve catalog from remote server: hostname was not match with the server certificate. I'm using ruby 1.8.7. It's still weird however that it complains about the hostname as it was working before. Nevertheless, I remade the CA and it's now working so I'm happy. On 8 Jun, 18:46, James Turnbull ja...@puppetlabs.com wrote: 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 - hostname wasnotmatch with theservercertificate Exception `NoMethodError' at /usr/local/lib/ruby/1.8/net/http.rb:1060 - undefined method `closed?' for nil:NilClass err:Couldnotretrievecatalogfromremoteserver: undefined method `closed?' for nil:NilClass warning:Notusing cache on failedcatalog err:Couldnotretrievecatalog; skipping run However if I ommit the --test part in debug mode the certificate error goes away and I get the usual error message in the /var/log/message (Couldnotretrievecatalogfromremoteserver: undefined method `closed?' for nil:NilClass). So now I'm just really confused about the whole thing, been fighting with it for half a day. Anyone got some insights. Funny thing is that it was working fine until the reboot, but no changes were made... What Ruby version and platform are you on? This rather annoying message is often the result of a Ruby 1.8.7 bug that hides the actual problem. See: http://projects.puppetlabs.com/issues/3101 And the patch (in Puppet 0.25.5): http://projects.puppetlabs.com/projects/puppet/repository/revisions/a... I suspect the underlying message above about a hostname mismatch is your actual problem - has anything changed there? Regards James Turnbull -- 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.
[Puppet Users] Re: Could not retrieve catalog from remote server
Nevermind, I found out that I had accidentially overwritten the puppet.conf... Luckily I had a backup and everything is up and running again :) On 9 Jun, 09:32, kit efossv...@gmail.com wrote: 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 on node auth001.mid.no warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run I do know, however, that the template is there: # ll /usr/local/etc/puppet/modules/nrpe/manifests/init.pp -rw-rw-r-- 1 root wheel 1599 30 mar 14:34 /usr/local/etc/puppet/ modules/nrpe/manifests/init.pp # ll /usr/local/etc/puppet/templates/nagios/nrpe.cfg/MASTER.erb -rw-rw-r-- 1 root wheel 7225 26 mar 16:06 templates/nagios/nrpe.cfg/ MASTER.erb And the syntax is also correct: # erb -x -T '-' /usr/local/etc/puppet/modules/nrpe/manifests/init.pp | ruby -c Syntax OK # erb -x -T '-' templates/nagios/nrpe.cfg/MASTER.erb | ruby -c Syntax OK So what is it then that is wrong? -- 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.
[Puppet Users] Re: Could not retrieve catalog from remote server: certificate verify failed
Update - After the client tries to connect, I found this in the puppetmaster WEBrick log: [2010-06-09 17:52:10] DEBUG accept: 10.1.1.70:49980 [2010-06-09 17:52:10] ERROR OpenSSL::SSL::SSLError: sslv3 alert bad certificate /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:44:in `accept' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:44:in `listen' /usr/lib/ruby/1.8/webrick/server.rb:173:in `call' /usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:95:in `start' /usr/lib/ruby/1.8/webrick/server.rb:92:in `each' /usr/lib/ruby/1.8/webrick/server.rb:92:in `start' /usr/lib/ruby/1.8/webrick/server.rb:23:in `start' /usr/lib/ruby/1.8/webrick/server.rb:82:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:42:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:41:in `initialize' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:41:in `new' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:41:in `listen' /usr/lib/ruby/1.8/thread.rb:135:in `synchronize' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:38:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:131:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:146:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:128:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetmasterd.rb:122:in `main' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `send' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `run_command' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `exit_on_fail' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' /usr/sbin/puppetmasterd:66 [2010-06-09 17:52:10] DEBUG close: 10.1.1.70:49980 On Wed, Jun 9, 2010 at 4:27 PM, Matt Keating keats...@gmail.com wrote: 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 break. See below for the debug output from the client. Any clue as to what I'm doing wrong? Thanks. -- 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.
[Puppet Users] Re: Could not retrieve catalog from remote server: certificate verify failed
Solved - God I had SELinux sometimes. On Wed, Jun 9, 2010 at 4:57 PM, Matt Keating keats...@gmail.com wrote: Update - After the client tries to connect, I found this in the puppetmaster WEBrick log: [2010-06-09 17:52:10] DEBUG accept: 10.1.1.70:49980 [2010-06-09 17:52:10] ERROR OpenSSL::SSL::SSLError: sslv3 alert bad certificate /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:44:in `accept' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:44:in `listen' /usr/lib/ruby/1.8/webrick/server.rb:173:in `call' /usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:95:in `start' /usr/lib/ruby/1.8/webrick/server.rb:92:in `each' /usr/lib/ruby/1.8/webrick/server.rb:92:in `start' /usr/lib/ruby/1.8/webrick/server.rb:23:in `start' /usr/lib/ruby/1.8/webrick/server.rb:82:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:42:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:41:in `initialize' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:41:in `new' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:41:in `listen' /usr/lib/ruby/1.8/thread.rb:135:in `synchronize' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:38:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:131:in `listen' /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:146:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:128:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetmasterd.rb:122:in `main' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `send' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `run_command' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `exit_on_fail' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' /usr/sbin/puppetmasterd:66 [2010-06-09 17:52:10] DEBUG close: 10.1.1.70:49980 On Wed, Jun 9, 2010 at 4:27 PM, Matt Keating keats...@gmail.com wrote: 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 break. See below for the debug output from the client. Any clue as to what I'm doing wrong? Thanks. -- 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.
