similar to: Service Availability

I''m trying to run puppet on a node I''m cloning from CD. No IP, no DNS, puppet with a standalone manifest and --use-nodes. I get dnsdomainname errors and a "Network is unreachable" error. I''m using 0.20, but I checked for new options in 0.23 and didn''t see one to turn off networking. Is this an option? Thanks.

I''ve got about 40 linux/aix machines that I''d like assimilate into config management with puppet. I''ve been reading lots of docs, recipes and best practices. I''m wondering if there''s a guide somewhere that lays out the most efficient way to spread the use of puppet across a quantity of installed machines. I''d like to do first things first,

Just curious as to the functionality of puppet. Does Puppet ensure that a service is up and running as long as puppet is running? Ie, I want to make sure ssh is always running, if for some reason ssh get''s shut down, does puppet start it back up when it does it''s config sync run? Thanks! --------------------------------- Pinpoint customers who are looking for

Hi all Luke and I have been discussing the wiki and how its future development might pan out. As a result I thought I''d canvas people for feedback. Currently the wiki''s layout and structure is fairly ad hoc and it''s a mix of wiki mark-up and REStructured Text (RST). We''d like to make it more "manual" like or at least move a significant portion of

Greetings all, My deployment of puppet includes a monitrc to make sure that puppetd stays up and running. It seems like (across all of my hosts) that pupeptd will end up dying and restarted by monit. I''m running puppetd under a screen session now on one particular host with --debug --verbose to see if any thing comes out on console but until it happens again, any anybody else

Hi all, I''m having problems making some manifest work, and it''s so simple that I don''t know where the issue is: I get this error message when trying to load this vhost.pp file: "Could not retrieve configuration: Syntax error at ''}'' in file /etc/puppet/manifests/classes/vhost.pp at line 9" define vhost ( $domain, $admin, $docroot, $enable )

Anybody else experience the need to restart puppetmasterd before a node can register itself. I''ve been cleaning up my installation here on client nodes and every once and a while I find myself needing to restart the puppetmaster daemon. A client node attempts to connect and never does. A restart fixes things. There doesn''t seem to be anything useful in the error messages

I am having a difficult time understanding and determining which module method is best for the env I help to support. Overview of systems supported: -There are 17+ clients. -4+ envs (dev, stage, beta, prod ..) per client -Several flavors and versions of OS ( Mostly fedora and centos ) -All are apache, some mongrel and most passenger -code deployments are capistrano -configurations are done with

With both puppet-0.23.0 and 0.23.1 if I setup just the configuration file puppet.conf, none of the puppetd options seem to get parsed. I first noticed this when monit failed to start/stop services due to the lack of a pid file being generated (and mine is not in one of the usual places). I''m sure that something like the patch attached but I bet it breaks other assumptions :-) Cheers,

Heya, I''m using puppet on Ubuntu (Gutsy/Hardy) and there''s a problem with the default setup of Ubuntu. Ubuntu uses network-manager to start the network in the background, which in turn causes puppet to start before the network is up. Puppet will then exit because it can''t resolve the server name. Currently I "solve" this problem by uninstalling

We want to use Nagios to monitor out puppet server so we can be notified if it goes down. We are using Fusion Passenger and Apache on Red Hat. Any suggestion for what and how to monitor? -- Thanks, Allan Marcus 505-667-5666 Allan@lanl.gov -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

Hi all, Can someone pls help me on how to make this bash script? I want to monitor a process, and then when the process (for some reason) dies, the script will start the process again. Thank you, -- Fajar Priyanto | Reg'd Linux User #327841 | Linux tutorial http://linux2.arinet.org 18:39:44 up 10:21, 2.6.16-1.2111_FC5 GNU/Linux Let's use OpenOffice. http://www.openoffice.org

I am experiencing a curious event, and wondering if others have seen this... As well, I have a question related to it. Today, I noticed my puppet summary report from Foreman this morning, that 60 of my 160 hosts all stopped reporting at nearly the exact same time, and have not since restarted. Investigating, it appears that my puppetmaster temporarily ran out of disk space on the /var

Hi- Recently starting using puppet while migrating an existing messy group of systems to some nice new hardware. Things are going incredibly well, and puppet''s functioning great. Have a bit of a headache. I''d like to keep myself from duplicating lots of included classes. Lets say I have this (snippet of a) class: class dbserver { file { "/etc/my_${db}.cnf":

Hi, I''m new to puppet and trying to get started using it just in local mode. My basic question is: how can i reference a static file within the module (eg in the module''s files/ subdirectory, as described in http://reductivelabs.com/trac/puppet/wiki/ModuleOrganisation). I suppose i could try using a full.absolute path to the file, but that seems to completely defeat the purpose

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

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

Hi, installing puppet at my first site was quite easy (not w/o problems, but still). At the second site, I''ve run into something more serious. First things first - I install puppetmaster on existing server, used to keep LDAP db (my puppetmaster DOES NOT use LDAP, it just tries to coexist on the same machine). The thing is, I need to puppet this baby, so I''m running into a

Here is my class class puppetconf { file { "/etc/puppet/puppetd.conf": mode => 644, owner => root, group => root, source => "puppet://puppet/cci/etc/puppet/puppetd.conf", notify => exec[puppet_restart] } file { "/etc/init.d/puppet": mode => 755, owner => root, group => root,

I''m just starting a roll out of Puppet and I''m seeing a problem on maybe 25% of client nodes. The symptoms are that the clients stop updating. In the Puppetmaster log, I''m seeing things like: Feb 9 20:10:23 vs4 puppetmasterd[17942]: Compiled catalog for xxxx in 0.05 seconds Feb 9 20:40:41 vs4 puppetmasterd[17942]: Compiled catalog for xxxx in 0.05 seconds Feb 9