Displaying 20 results from an estimated 9000 matches similar to: "puppetd doing noting as daemon"
2009 Apr 22
3
Puppet doesnt run
Hi guys,
Apologies if this is covered elsewhere. I''ve had a hunt through
Google, Redline, and the FAQs but dont see it.
Puppet 0.24.8 (and 24.7 on teh same box) starts up fine, but then just
sits there, regardless of what I set runinterval to be.
Puppet Server debug output stops at:
debug: Creating default schedules
debug:
2009 Jun 12
7
Obtaining puppet and facter for RHEL5/Centos5
What''s the correct yum repo to use for installing Puppet & Facter on
RHEL5 and Centos5?
I used to get them from the dlutter-rhel5 repo but this seems to be
massively out of date now - latest version of puppet-server in there is
0.24.5-1.el5 and facter 1.5.4-1.el5.
In Epel I see puppet-server 0.24.8-1.el5.1 and facter 1.5.4-1.el5 which
is better but isn''t 1.5.4 the version
2009 Jun 13
0
problems with puppetd on some of my solaris machines
I am having troubles with getting puppetd running on some of my
Solaris10 update 7 (05/2009) boxes.
I use Jumpstart to build my servers, so the installation is
repeatable, consistent, and automated, so it is especially confusing
that some boxes work, and others don''t.
I can ssh into both of these machines, so the host certs should be OK.
As part of my installation, I download the
2009 Sep 03
2
Problems with puppetd on ubuntu server
If you install puppet from the ubuntu 9.04 repositories (apt-get
install puppet) it sets up puppet differently than the gem. The
differences are obvious from the /etc/puppet/puppet.conf which looks
like this
[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/var/lib/puppet/ssl
rundir=/var/run/puppet
factpath=$vardir/lib/facter
pluginsync=true
[puppetmasterd]
2009 Apr 24
4
uninitialized constant Facter::IPAddress (NameError)
I just started getting this error on some machines after a yum update
from centos 5.2 to centos 5.3. Does anyone know what it means? Since
I''m not a ruby person, I''m not sure how to debug this, but it looks to
me like facter is having trouble parsing information about my
interfaces.
# facter
/usr/lib/ruby/site_ruby/1.8/facter/ipmess.rb:19: uninitialized constant
2011 Nov 01
2
Custom fact not set with mc-puppetd
Hello,
I''ve mcollective 1.2.1 with puppet 2.6.12 on rhel5.6, facter 1.6.2
setup from http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML.
Now I''ve create a custom fact in /usr/lib/ruby/site_ruby/1.8/facter/
customer_status.rb.
On the client;
Running facter customer_status works.
Running ''puppet agent --test'' works, customer_status
2009 Mar 05
2
Exposing environment variables to Facter
Hey gang,
During the build of our Linux (EL4 and EL5) images, the kickstart
process writes out a file (/etc/sysconfig/soe) that contains:
SOE_VERSION="Version string"
SOE_BUILD_DATE="2009-03-06"
I then have /etc/profile.d/facter.sh scripts that has this:
. /etc/sysconfig/puppet
. /etc/sysconfig/soe
FACTER_PUPPETMASTER=$PUPPET_SERVER
FACTER_SOE_VERSION=$SOE_VERSION
2008 Apr 02
1
service won't restart puppetd
I''ve got the following class that runs if I activate the repo in
/etc/yum.conf. If I run "puppetd -t" from the command line it will
restart puppetd fine. If I let the class run on it''s own as a deamon
puppetd does not restart. The puppetmaster on the other hand does
restart using either method. I ran the client in "--debug" but that
doesn''t seem to
2008 Dec 04
4
puppetmaster built via puppetd
hi,
i''m trying to set up my puppetmaster infrastructure with multiple
puppetservers behind load balancers in each of our datacenters. i''m
using 0.24.6. i''ve read the howto on puppet scalability, and i think
i''ve got the ssl config working correct, but i''m noticing that when
puppetd is used to build a puppetmaster, some of the files in $vardir/
ssl
2009 Jul 13
7
puppetd no-daemonize
So I have been trying to run puppet once in my kickstart %post scripts but
every time it detaches and daemonizes even though I have explicitly stated
otherwise. Am I missing something?
# rpm -q puppet
puppet-0.24.8-1
# /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug
debug: Creating default schedules
debug: Failed to load library ''shadow'' for feature
2006 Sep 23
4
"server" config option (and cmd-line option) don''t do anything for puppetd?
Hi guys,
Unlike what it says in the documentation and the --help output, I
can''t seem to get puppetd to use the --server setting. The only way I
can get puppetd to work is to include a ''puppet'' alias to the ip of
the machine I''m running puppetmasterd on in my hosts file.
The strange thing though, is that the logs of my puppetmaster show
that it *is* getting
2010 Nov 25
1
Problem starting puppetd for the first time (Could not create resources ...)
Hi,,,
I have a strange problem when installing puppet client 2.6.3 on a
node.
I have installed facter-1.3.8-4 and ruby-1.8.6-8.
When I start puppetd as a normal user everything behaves normally.
A .puppet directory is installed under $HOME and ssl key is installed
under $HOME/.puppet/ssl.. I sign the certificat on the puppet master
and the client is working fine.
However I cannot change
2009 Mar 23
7
ANNOUNCE: Puppet 0.24.8 now available!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Puppet 0.24.8 is now available!
This is a maintenance release for the 0.24.x branch but contains a small
number of new features including some significant performance
enhancements for large installations and stored configurations.
The tarball is available at:
http://reductivelabs.com/downloads/puppet/puppet-0.24.8.tgz
MD5 hash:
2007 Jan 10
2
puppet on RHEL4
Hello,
I''m seeing the following when I run puppetd --version
/usr/sbin/puppetd:157:in `require'': no such file to load -- puppet
(LoadError)
from /usr/sbin/puppetd:157
I thought upgrading ruby to 1.8.5 would solve the issue but it has not.
In any case, here are the relevant rpm versions...
ruby-1.8.5-1.el4.centos
ruby-rdoc-1.8.5-1.el4.centos
2007 May 30
7
Ticket 616, service resource takes over puppetd port
Hello Luke,
After our services do now successfully restart, we hit now the already
opened bug where the restarted service takes over puppetd port if it''s
configured to listen.
One solution is to remove the listen option but it''s very nice to invoke a
puppetrun on the clients from the central server without waiting for its
next run.
Where you already able to take a look? It
2009 Nov 16
1
puppetd 0.24.7-r1 has lots of close_wait connections
Hi folks
I know that has, to some degree, been run over the past year in different
ways, but, I may have yet another instance of an issue on this.
The puppetmaster system and the puppet system are both running 0.24.7-r1,
on a gentoo system. Other puppet systems are running 0.24.4.
The puppet system (not the puppetmaster system) that is running 0.24.7-r1
is showing multiple close_wait
2009 Dec 21
5
custom fact and environment variable
Hello,
I''m trying to add an environment variable as fact like this :
#export $FACTER_test="infof"
#facter | grep test
test => infof
But my fact don''t synchronize with puppet master. I don''t see it in /
var/puppet/yaml/clientfile.yaml
If I want this works, I''ve need to start puppet like this :
#puppetd -vt --factsync
but factsync''s
2009 Sep 25
1
Puppetd hangs with 100% CPU usage
Hi again,
puppetd started to hang with 100% CPU usage all of the sudden. Strace
just keeps repeating these 2 lines:
--- SIGVTALRM (Virtual timer expired) @ 0 (0) ---
sigreturn() = ? (mask now [])
In logs it hangs with this message:
debug: Calling fileserver.describe
But lots of these fileserver.describe calls prior to hang are
successful.
If I run it with puppetd
2010 Oct 20
9
puppetd 0.25.4 with puppetmaster 0.24.8?
Our puppetmaster runs 0.24.8 on Ubuntu 9.10. Our clients are either
Ubuntu 9.10 or Ubuntu 8.04.
We''ve just brought up our first Ubuntu 10.04 machine. This machine
installs puppetd 0.25.4.
The Ubuntu 10.04 machine can''t seem to present it''s certificate request
properly.
In my masterhttp.log, I see
[2010-10-20 13:09:06] 174-143-141-55.static.cloud-ips.com - -
2007 Jan 10
7
Problem adding facts ...
I have created my first ''fact'', first attempt at Ruby too, and
configured the fileserver to server it but when a Fedora (5 or 6)
client sync''s puppetd appears to hang. CentOS clients sync and use the
new fact fine.
Find attached the fact file and the output from ''puppetd --debug
--factsync'' on a FC5 client is below. This is a 0.20.1 client and