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 "puppetmaste
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
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) provision
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 wrote:
> I'm hoping someone else has experienced the error. The puppetmaster and
agent are on the same system and its having trouble pulling
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":
-
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
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 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
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 y
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 akub
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 runni
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
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 wrote:
> What does this error mean or what does it indicate?
>
> puppet-agent: Could not retrieve catalog from remote s
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 VMWar
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 i
> 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
> c
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
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 wrote:
> I have one of 18+ servers in an environment that just started having a
> problem when attempting to do an update.
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)
--
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 i
Solved - God I had SELinux sometimes.
On Wed, Jun 9, 2010 at 4:57 PM, Matt Keating 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: ssl
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
`a
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 wrote:
> I'm getting this frustrating error message and can't figure out why.
> Puppet claims I'm missing a template file:
>
> err:
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
23 matches
Mail list logo
