[Puppet Users] Database and user not created (Puppetlabs mysql module)

[Moteo]

Hi everyone,

I am new to Puppet and try to make some simple "automation things".
I have succeed with apache2, ssh modules, but have problems with
Puppetlabs mysql module.

It installs mysql server, changes/creates admin user password, but
does not create database and user.
I cannot find anything wrong in logs (--debug --verbose). I see that
manifests is read, but no db/user in mysql.

There is all my node config:

  include openssh
  include apache
  include php
  php::module { "mysql": }
  include mysql

  class { 'mysql::server':
config_hash => { root_password => ""}
  }

  mysql::db { 'mydb1':
user => 'user1',
password => 'x1',
host => 'localhost',
grant=> ['all'],
  }


  apache::virtualhost { "s1.test.com": }
  apache::virtualhost { "s2.test.com": }

What I have missed?

Thank You
Moteo

-- 
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] CentOS upgrade with puppet?

[Jakov Sosic]

Hi.

How do you handle CentOS updates/upgrades with puppet? Is there only way 
to count all the packages and put them in manifests like:


package: ensure=>latest,


I am evaluating puppet, and currently I have problem with upgrading from 
CentOS 5.x->5.x+1.


ty.


--
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.

Re: [Puppet Users] CentOS upgrade with puppet?

[Walter Heck]

Slightly off-topic but still important imho: Read Q24 in the CentOS
FAQ: http://wiki.centos.org/FAQ/General. Officially major version
upgrades are not supported, but more importantly, they are not
recommended.

cheers,

Walter

On Mon, Mar 12, 2012 at 17:46, Jakov Sosic  wrote:
> Hi.
>
> How do you handle CentOS updates/upgrades with puppet? Is there only way to
> count all the packages and put them in manifests like:
>
> package: ensure=>latest,
>
>
> I am evaluating puppet, and currently I have problem with upgrading from
> CentOS 5.x->5.x+1.
>
> ty.
>
>
> --
> 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.
>



-- 
Walter Heck

--
follow @walterheck on twitter to see what I'm up to!
--
Check out my new startup: Server Monitoring as a Service @ http://tribily.com
Follow @tribily on Twitter and/or 'Like' our Facebook page at
http://www.facebook.com/tribily

-- 
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] Puppet on OpenSuSE & SLES

[Julien C.]

Hi,

I'm a big fan of Puppet and managed to have my company accept it.
However, I'm having issues deploying it (I'm used to the debian version 
which works perfectly out of the box) :

- There doesn't seem to be an official repository for Suse (I've seen it 
mentionned in the bugtracker but yum.puppetlabs.com doesn't contain SUSE 
packages).
- I can't find a package for ruby-shadow.
- I can't find a package for augeas either.

I circumvented these problems by installing Puppet by hand (tarball) and 
writing ugly code (execs) to manage config files and user passwords. 
However, I'd like to know if I missed anything or if you can suggest 
solutions for any of these 3 issues...

Cheers,

-- 
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/-/vbFHM5R8Q_4J.
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] Using Hash in define

[Jean Baptiste Favre]

Hello,
I want to pass a hash as parameters for a define

$hash = { name => 'aname', key1 => 'akey', key2 => 'anotherkey' }
mydefine { 'define': hash => $hash }


define mydefine ( $hash ) {
	notice("Hash is as follow: name is ${hash[name]}, key1 is 
${hash[key1]}, key2 is ${hash[key2]}")

}

When running it , always got an error message:
Error 400 on SERVER: hash is not an hash or array when accessing it with 
name.


What I'm doing wrong ?

Regards,
JB

--
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.

Re: [Puppet Users] Using Hash in define

[Jean Baptiste Favre]

Answer to myself: always double check for misspelling variable names...

Sorry for noise,
JB


On 3/12/12 12:26 PM, Jean Baptiste Favre wrote:

Hello,
I want to pass a hash as parameters for a define

$hash = { name => 'aname', key1 => 'akey', key2 => 'anotherkey' }
mydefine { 'define': hash => $hash }


define mydefine ( $hash ) {
notice("Hash is as follow: name is ${hash[name]}, key1 is 
${hash[key1]}, key2 is ${hash[key2]}")

}

When running it , always got an error message:
Error 400 on SERVER: hash is not an hash or array when accessing it 
with name.


What I'm doing wrong ?

Regards,
JB



--
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.

Re: [Puppet Users] CentOS upgrade with puppet?

[Jakov Sosic]

On 03/12/2012 11:07 AM, Walter Heck wrote:

Slightly off-topic but still important imho: Read Q24 in the CentOS
FAQ: http://wiki.centos.org/FAQ/General. Officially major version
upgrades are not supported, but more importantly, they are not
recommended.


Hi.

I know that major version upgrades are not recomended (for example 4->5 
or 5->6). But I am asking about minor upgrades, note the 5.x -> 5.x+1 
formula in original question.


--
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.

Re: [Puppet Users] CentOS upgrade with puppet?

[Markus Falb]

On 12.3.2012 11:07, Walter Heck wrote:
> Slightly off-topic but still important imho: Read Q24 in the CentOS
> FAQ: http://wiki.centos.org/FAQ/General. Officially major version
> upgrades are not supported, but more importantly, they are not
> recommended.

Yes, but I think Jakov was talking about minor version upgrades, e.g.
upgrade from 5.7 to 5.8 and such updates are supported of course.
A major upgrade would be from 5.x to 6.x

> On Mon, Mar 12, 2012 at 17:46, Jakov Sosic  wrote:
>> How do you handle CentOS updates/upgrades with puppet? Is there only way to
>> count all the packages and put them in manifests like:
>>
>> package: ensure=>latest,
>>
>>
>> I am evaluating puppet, and currently I have problem with upgrading from
>> CentOS 5.x->5.x+1.

-- 
Kind Regards, Markus Falb



signature.asc
Description: OpenPGP digital signature

[Puppet Users] Re: puppetlabs-firewall stages and persistence

[jcbollinger]

On Feb 15, 1:00 pm, Christian McHugh 
wrote:
> Hi all,
>
> I'm attempting to use the puppetlabs-firewall module. In testing,
> rules are enabled in a random order, so it seems necessary to utilize
> puppet stages to guarantee proper ordering.


It is incorrect that you must use run stages to achieve your desired
ordering.  In fact, it is *never* the case that run stages are the
only solution to ordering issues in Puppet, because there is nothing
you can do with them that you cannot also do with ordinary resource
relationships.

In many cases, solving an ordering problem by use of run stages is
like putting in a tack with a sledgehammer: not only is it overkill,
it also doesn't afford much precision or finesse.

I have no experience with the module in question, so I have no
specific suggestions to offer, but if you find run stages too crude a
tool for your task then I can advise you about how to achieve your
ordering requirements otherwise.


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-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: Intermittent logic error

[jcbollinger]

On Mar 9, 10:15 pm, Len Rugen  wrote:
> We seem to be getting intermittent errors production this message.
>
> err: Failed to apply catalog: Could not find dependency
> Package[zabbix-agent] for Service[undef] at
> /etc/puppet/modules/zabbix-agent/manifests/init.pp:76
>
> It will usually work OK on the next rerun.


That sounds like a parse-order problem.  At the time the Service
declaration is parsed, Package[zabbix-agent] has not (yet) been
declared for the node.


>  The class is addressing a
> service that was zabbix-agent prior to version 1.8.9 but was renamed to
> zabbix-agent.  I am puzzled that "undef" can result in the if / else as
> it's set in either case.   (Copy paste changed some indentation)
>
> Puppet version is 2.7.9, OS RHEL, some 5 and 6, which doesn't seem to
> matter, and the error occurs on hosts running either zabbix version.
>
> Any thoughts?  Doc follows
>
> This uses a custom fact:
>
> Facter.add(:zabbix_version) do
>   setcode do
>     output = %x{/bin/rpm -qa --queryformat "%{VERSION}" zabbix-agent}
>   end
> end
>
> Parts of the manifest
> 
>
> if versioncmp($zabbix_version, '1.8.9') >= 0 {
>         $packages = [ "zabbix-agent", "zabbix-get", "zabbix-sender" ]
>         $agent = "zabbix-agentd" }
> else {
>         $packages = [ "zabbix-agent" ]
>     $agent = "zabbix-agent"
>
> }
>
> 
>     service {
>         $agent:
>             enable => true,
>             ensure => running,
>             hasstatus => true,
>             require => Package["zabbix-agent"];
>     }    # This is line 76


The bit about "Service[undef]" in your log also suggests an ordering
issue.  I conclude that the two manifest fragments you present are at
least in different classes, if not different files, and that
occasionally puppet tries to parse the latter class before parsing a
declaration (not definition) of the former.


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-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.

Re: [Puppet Users] Puppet on OpenSuSE & SLES

[Darin Perusich]

Hi Julien,

While there is no "official" repo from puppet labs for OpenSuSE/SuSE
systems, there is an up to date repo in OBS,
home:/eclipseagent:/puppet, see link below. Ben, the maintainer, and I
make a pretty good effort to ensure the packages are updated, tested,
and include all those dependencies not distributes to SuSE. We've also
had some minimal discussion about pushing these packages into the
"sysetmsmanagement" OBS repo but we just haven't had the time. I also
maintain the "zypprepo" module which can be gotten from Puppet Forge,
again link below.

I build the srpm's and deploy from a local repo to all my hosts,
instead of pointing them at OBS. It's a little more work on my part,
but it affords me tighter control on the packages so I can test things
before I deploy.

http://download.opensuse.org/repositories/home:/eclipseagent:/puppet/
http://download.opensuse.org/repositories/systemsmanagement/
http://forge.puppetlabs.com/darin/zypprepo
--
Later,
Darin



On Mon, Mar 12, 2012 at 6:19 AM, Julien C.  wrote:
> Hi,
>
> I'm a big fan of Puppet and managed to have my company accept it.
> However, I'm having issues deploying it (I'm used to the debian version
> which works perfectly out of the box) :
>
> - There doesn't seem to be an official repository for Suse (I've seen it
> mentionned in the bugtracker but yum.puppetlabs.com doesn't contain SUSE
> packages).
> - I can't find a package for ruby-shadow.
> - I can't find a package for augeas either.
>
> I circumvented these problems by installing Puppet by hand (tarball) and
> writing ugly code (execs) to manage config files and user passwords.
> However, I'd like to know if I missed anything or if you can suggest
> solutions for any of these 3 issues...
>
> Cheers,
>
> --
> 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/-/vbFHM5R8Q_4J.
> 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: CentOS upgrade with puppet?

[jcbollinger]

On Mar 12, 4:46 am, Jakov Sosic  wrote:
> Hi.
>
> How do you handle CentOS updates/upgrades with puppet? Is there only way
> to count all the packages and put them in manifests like:
>
> package: ensure=>latest,
>
> I am evaluating puppet, and currently I have problem with upgrading from
> CentOS 5.x->5.x+1.


If your yum repositories are configured to point at the generic URLs
for your CentOS major version (and Puppet can ensure that), then you
could put this in your manifests to keep all installed packages up to
date:

exec { 'update-all-packages':
  command => '/usr/bin/yum update'
}

Really, however, performing a singular action such as an operating
system update is not what Puppet is designed to do.  Any way you try
to do it with Puppet has its problems, including the above Exec.  This
sort of job more appropriate for MCollective or a similar tool.


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-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.

Re: [Puppet Users] Puppet on OpenSuSE & SLES

[Julien C.]

Hi, thank you for your answer, I didn't know about your repository. It will 
definitely help on my most recent servers.

However, that only solves part of my problem : about two thirds of my 
servers still run SLES 10.
Even if SLES 10 isn't listed in the Supported Operating Systems page, 
puppet (installed by hand) runs fine on it.

Le lundi 12 mars 2012 14:03:20 UTC+1, Darin Perusich a écrit :
>
> http://download.opensuse.org/repositories/home:/eclipseagent:/puppet/
> http://download.opensuse.org/repositories/systemsmanagement/
> http://forge.puppetlabs.com/darin/zypprepo
>
>

-- 
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/-/viotSZofy8MJ.
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.

Re: [Puppet Users] X509v3 Subject Alternative Name in puppet generated certs...

[Jonathan Proulx]

Hi Nigel,

Thanks for the fabulous response. I was convinced I was going to need to do
this by hand, happy to see my native pessimism proved wrong.

On Sat, Mar 10, 2012 at 4:23 PM, Nigel Kersten  wrote:

> Jon, what version of Puppet are you running?

2.7.11 on Debian/Squeeze from apt.puppetlabs.com

Thanks,
-Jon

-- 
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] Different versions for server and agents

[Julien C.]

Hi,

Due to severe heterogeneity among my servers (OS and version), I started my 
puppet infrastructure by deploying agents by hand (from the tarball). That 
way, I'm sure that I have the same version everywhere.

Having found up-to-date repositories for most of my systems, I'm now 
questioning that decision. Is it safe to have different versions of puppet :
- in the same major version (eg 2.7.x) ?
- in different major versions ?
- master older that some agents ?

Cheers

-- 
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/-/cI9KcF0yBvAJ.
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.

Re: [Puppet Users] Different versions for server and agents

[Peter Bukowinski]

On Mar 12, 2012, at 10:03 AM, Julien C. wrote:

> Hi,
> 
> Due to severe heterogeneity among my servers (OS and version), I started my 
> puppet infrastructure by deploying agents by hand (from the tarball). That 
> way, I'm sure that I have the same version everywhere.
> 
> Having found up-to-date repositories for most of my systems, I'm now 
> questioning that decision. Is it safe to have different versions of puppet :
> - in the same major version (eg 2.7.x) ?
> - in different major versions ?
> - master older that some agents ?
> 
> Cheers


Your master's version should always be equal to or greater than the latest 
client version you're using. You can count on a newer master working with older 
clients, but don't count on newer clients working with older masters.

-- 
Peter M. Bukowinski
Sr. Systems Engineer
Janelia Farm Research Campus, HHMI

-- 
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.

Re: [Puppet Users] Puppet on OpenSuSE & SLES

[Darin Perusich]

You can still build for unsupported SuSE distro's via the build
service, we're doing this in the server:monitoring repo for SLES10,
you just need to manually add. them. It shouldn't be a problem as long
as all the ruby requirements are there. I'll take a look at enabling
this.

--
Later,
Darin



On Mon, Mar 12, 2012 at 9:47 AM, Julien C.  wrote:
> Hi, thank you for your answer, I didn't know about your repository. It will
> definitely help on my most recent servers.
>
> However, that only solves part of my problem : about two thirds of my
> servers still run SLES 10.
> Even if SLES 10 isn't listed in the Supported Operating Systems page, puppet
> (installed by hand) runs fine on it.
>
> Le lundi 12 mars 2012 14:03:20 UTC+1, Darin Perusich a écrit :
>>
>> http://download.opensuse.org/repositories/home:/eclipseagent:/puppet/
>> http://download.opensuse.org/repositories/systemsmanagement/
>> http://forge.puppetlabs.com/darin/zypprepo
>
> --
> 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/-/viotSZofy8MJ.
>
> 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.

Re: [Puppet Users] Different versions for server and agents

[Julien C.]

Well, that's more than I expected. I can easily ensure that my server is 
up-to-date, and then use whatever package I find for the agents...

Thanks.

Le lundi 12 mars 2012 15:16:32 UTC+1, pmbuko a écrit :
>
> On Mar 12, 2012, at 10:03 AM, Julien C. wrote:
>
> Hi,
>
> Due to severe heterogeneity among my servers (OS and version), I started 
> my puppet infrastructure by deploying agents by hand (from the tarball). 
> That way, I'm sure that I have the same version everywhere.
>
> Having found up-to-date repositories for most of my systems, I'm now 
> questioning that decision. Is it safe to have different versions of puppet :
> - in the same major version (eg 2.7.x) ?
> - in different major versions ?
> - master older that some agents ?
>
> Cheers
>
>
> Your master's version should always be equal to or greater than the latest 
> client version you're using. You can count on a newer master working with 
> older clients, but don't count on newer clients working with older masters.
>
> -- 
> *Peter M. Bukowinski*
> Sr. Systems Engineer
> Janelia Farm Research Campus, HHMI 
>
>

-- 
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/-/dGEtHeu0bdUJ.
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: Cache for the local system while offline

[mukulm]

Hi,

Can anyone assist how cache issue can be solved  ?

Thanks


On Feb 24, 8:04 pm, mukulm  wrote:
> Hi,
>
> Please assist on the below request as I am not able to receive the
> updates offline.
>
> Thanks
> mukulm
>
> On Feb 20, 7:59 pm, mukulm  wrote:
>
>
>
>
>
>
>
> > I am not able tocachethe updates from the server as I had updated
> > the nodes puppet.conf with usecacheonfailure=true or any other info
> > need to be updated  ?
>
> > I am getting the error messages  as,
>
> > err: Could not retrieve catalog from remote server: getaddrinfo: Name
> > or service not known
> > err: Could not retrieve catalog; skipping run
> > err: Could not send report: getaddrinfo: Name or service not known
>
> > Please assist.
> > Thanks
> > mukulm
>
> > On Feb 16, 1:29 pm, mukulm  wrote:
>
> > > I am too getting the same message & error as,
>
> > > err: Could not retrieve catalog from remote server: getaddrinfo: Name
> > > or service not known
> > > err: Could not retrieve catalog; skipping run
> > > err: Could not send report: getaddrinfo: Name or service not known
>
> > > Can anyone assist howcachecachecan be achieve on the nodes.
>
> > > Thanks
> > > mukulm
>
> > > On Feb 16, 8:05 am, Khoury Brazil  wrote:
>
> > > > On Wed, Feb 15, 2012 at 5:51 PM, Daniel Pittman  
> > > > wrote:
> > > > > On Wed, Feb 15, 2012 at 17:26, Khoury Brazil 
> > > > >  wrote:
> > > > >> On Thu, Feb 9, 2012 at 1:09 PM, Daniel Pittman 
> > > > >>  wrote:
>
> > > > >>> On Thu, Feb 9, 2012 at 06:12, mukulm  
> > > > >>> wrote:
>
> > > > >>> > I want tocachethe updates for the users system received from the
> > > > >>> > server so that the users can get the updates
> > > > >>> > from the local systemcachewhile offline.
>
> > > > >>> > Any idea how can server updates be stored on the users system 
> > > > >>> > while
> > > > >>> > offline  ?
>
> > > > >>> You likely want `--usecacheonfailure`, or the equivalent setting in
> > > > >>> `puppet.conf`:
>
> > > > >>>http://docs.puppetlabs.com/references/stable/configuration.html#useca...
>
> > > > >>> Whether to use the cached configuration when the remote 
> > > > >>> configuration
> > > > >>> will not compile. This option is useful for testing new
> > > > >>> configurations, where you want to fix the broken configuration 
> > > > >>> rather
> > > > >>> than reverting to a known-good one.
>
> > > > >>> That should also apply when you can't communicate with the master.
>
> > > > >> Unfortunately, at least in my case, when I run puppet on a client 
> > > > >> that
> > > > >> is off of the network (in this particular case its a Macbook Pro) it
> > > > >> seems that something is failing locally, causing a "warning: not 
> > > > >> using
> > > > >>cacheon failed catalog".
> > > > > […]
> > > > >> This is the output from an offline debug run:
> > > > >> macbookproagent:/ admin$ sudo puppet agent -t --debug
>
> > > > > One of the features of the `-t` or `--test` flag is that it disables
> > > > > use of the cached catalog when you can't fetch it down.  Does it work
> > > > > better if you don't specify `--test`?
>
> > > > > If not, please file a bug report. :)
> > > > > --
> > > > > Daniel Pittman
> > > > > ⎋ Puppet Labs Developer –http://puppetlabs.com
> > > > > ♲ Made with 100 percent post-consumer electrons
>
> > > > > --
>
> > > > I guess I *was* missing something (something very obvious...). Thanks
> > > > for the help, that was indeed the issue. :)

-- 
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.

Re: [Puppet Users] Puppet on OpenSuSE & SLES

[Julien C.]

That would be great! Anything I can do to help?

Le lundi 12 mars 2012 15:26:19 UTC+1, Darin Perusich a écrit :
>
> You can still build for unsupported SuSE distro's via the build
> service, we're doing this in the server:monitoring repo for SLES10,
> you just need to manually add. them. It shouldn't be a problem as long
> as all the ruby requirements are there. I'll take a look at enabling
> this.
>
> --
> Later,
> Darin
>
>

-- 
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/-/F0epMjqsSzwJ.
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.

Re: [Puppet Users] Puppet on OpenSuSE & SLES

[Jeffrey Watts]

I took the RHEL/EPEL RPMs for ruby-shadow and puppet and rebuilt them for
SLES.  There are very few things that need changing.  The RHEL/EPEL RPMs
have really well put together SPECfiles.

I believe I posted the SPECfile diff for puppet to this list a month or so
ago.  You might search the archives.  Mostly what I did was comment out the
Red Hat specific dependencies - it was really easy.  You can build without
Augeas if you're not using it.

Good luck.
Jeffrey.

On Mon, Mar 12, 2012 at 5:19 AM, Julien C.  wrote:

> Hi,
>
> I'm a big fan of Puppet and managed to have my company accept it.
> However, I'm having issues deploying it (I'm used to the debian version
> which works perfectly out of the box) :
>
> - There doesn't seem to be an official repository for Suse (I've seen it
> mentionned in the bugtracker but yum.puppetlabs.com doesn't contain SUSE
> packages).
> - I can't find a package for ruby-shadow.
> - I can't find a package for augeas either.
>
> I circumvented these problems by installing Puppet by hand (tarball) and
> writing ugly code (execs) to manage config files and user passwords.
> However, I'd like to know if I missed anything or if you can suggest
> solutions for any of these 3 issues...
>
>

-- 
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] Memory Leak in dashboard?

[Peter Berghold]

Has anybody seen symptoms of a memory leak within the dashboard (or in ruby
itself?)  A couple of times my puppet master server has gone off in the
weeds with an error message to the console about being out of memory.  The
messages point the finger at apache and ruby.



-- 
Peter L. Berghold
Owner, Shark River Technical Solutions LLC

-- 
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: Unresponsive Agents - PE 2.0

[Robert Stinnett]

Thanks for the advice about checking the workers.  That did the trick
(the manual was for the open source pkg, but I managed to figure out
how to apply it to PE2).

Is there any available training on Puppet Enterprise out there?  I see
a lot of it on the open-source package, but have not yet found
anything about PE 2.0.

Robert


On Feb 28, 12:19 pm, "all.lucky.sevens" 
wrote:
> Try the 'Starting and managing delayed job workers' section in 
> here:http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html
>
> If the workers aren't running (and they don't run by default unless
> you follow the steps in that section) then you can see a backlog of
> tasks.
>
> On Thu, Feb 23, 2012 at 4:32 PM, Robert Stinnett
>
>
>
>  wrote:
> > And what do we do about that?  I've restarted the services, even
> > restarted the server and nothing comes back to life.
>
> > Robert
>
> > On Feb 23, 9:10 am, Kenneth Lo  wrote:
> >> If that's the case I believe your pe-puppet-dashboard-workers service died
> >> somehow in your master.
>
> >> --KL
>
> >> On 2/23/12 9:51 AM, "Robert Stinnett"  wrote:
>
> >> >We are using RHEL - 2.6.18-238.1.1.0.1.el5xen
>
> >> >I do not know of any recent kernel patches (let me put it this way --
> >> >I didn't make any!).
>
> >> >If I go to the "Live Management" part of the dashboard I can control
> >> >the agents, etc -- but they won't do anything in the dashboard view
> >> >and it shows up as over 800 tasks are backlogged on them.
>
> >> >I've searched the log files I could find for any error messages, but
> >> >haven't found anything yet.  It seems strange that the agents work in
> >> >command-line mode, and through the live management, but aren't via the
> >> >dashboard/cron process,
>
> >> >Thanks,
> >> >Robert Stinnett
>
> >> >On Feb 22, 3:53 pm, Aaron Grewell  wrote:
> >> >> Are you running RHEL 5?  Did you recently patch your kernel?  If so,
> >> >> you've probably been bitten by a kernel bug.  I've successfully used
> >> >> kernel-2.6.18-274.17.1.el5 and backrev versions from the
> >> >> kernel-2.6.18-238.x.x series.
>
> >> >> On 02/22/2012 12:26 PM, Robert Stinnett wrote:
>
> >> >> > Hi there,
>
> >> >> > I am relatively new to Puppet (totally new) and had been cruising
> >> >> > right along for a few days until about a week ago when our puppet
> >> >> > agents wentunresponsive.  I've restarted both them and the servers
> >> >> > several times to no avail.  Can anyone point me down the path of how
> >> >> > to diagnose this issue?  We are currently evaluating Puppet to bring
> >> >> > into our Enterprise for managing server provisions/configs/etc.
>
> >> >> > Thanks,
> >> >> > Robert Stinnett
>
> >> >--
> >> >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.
>
> >> This message is for the designated recipient only and may contain 
> >> privileged, proprietary, or otherwise private information. If you have 
> >> received it in error, please notify the sender immediately and delete the 
> >> original. Any other use of the email by you is prohibited.
>
> > --
> > 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 
> > athttp://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] Announce: Puppet 2.7.12 now available

[Michael Stahnke]

Puppet 2.7.12 is a maintenance release candidate for Puppet in the
2.7.x series.

Downloads are available:
 * Source http://downloads.puppetlabs.com/puppet/puppet-2.7.12.tar.gz

See the Verifying Puppet Download section at:
 
http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet#Verifying+Puppet+Downloads

Please report feedback via the Puppet Labs Redmine site, using an
affected version of 2.7.12
 http://projects.puppetlabs.com/projects/puppet

Full Release Notes at:
http://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes#2.7.12

Packages available at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com

## Community MVP for this release: Konrad Scherer for
 Updating the zypper package provider to support zypper 0.6

## Puppet 2.7.12 Highlights ##

## Features ##
* Zypper package provider supports zypper 0.6
* Raise default key lengths in Puppet
 * Restored agent lockfile behavior to 2.7.9;  in 2.7.10 and 2.7.11,
'puppet agent --disable' begun to use a new lock file named
'puppetdlock.disabled'.  This was determined to cause compatibility
issues with certain external tools, so the pre-2.7.10 behavior has
been restored.
 * Agent lockfile backwards compatibility to support users upgrading
from 2.7.10 or 2.7.11.
 * Improved status / notification message when attempting to run an
agent after agents have been administratively disabled (via 'puppet
agent --disable').
 * Cron error messages on Windows less cryptic
 * Don't overwrite symlinks in augeas provider
 * Fix zypper provider so ensure => 'latest' works

Plumbing For Puppet Module Tool improvements (note this feature will
be fully available in Puppet 2.7.13)
* Module requirements should include versions
* Fix SemVer's range behavior to work with Ruby 1.9
* Face actions should be able to set exit codes
* Implement a rich console logging prototype
* Enhance the uninstall PMT action
* All forge interactions should be centralized
* Add module dependency errors to module list output
* Enhance PMT search action output


## Bug Fixes ##
Windows Bug Fixes
* Fix puppet agent --listen on Windows
* Don't add execute bit to newly created files on Windows
* Skip default file permissions for sync'ed files on Windows
* Allow POSIX paths for files served to Windows agents
* Refactor Windows administrator detection
* Disable puppet kick on windows


Puppet 2.7.12 includes contributions from the following people:
Ben Hughes, Brice Figureau, Chris Price, Daniel Pittman, Deepak
Giridharagopal, Dominic Cleal, Dominic Maraglia, Gary Larizza, James
Turnbull, Jeff McCune, Jeff Weiss, Josh Cooper, Josh Lifton, Kelsey
Hightower, Konrad Scherer, Luke Kanies, Matt Robinson, Matthaus
Litteken, Michael Stahnke, Moses Mendoza, Nan Liu, Nick Fagerlund,
Nick Lewis, Ossi Herrala, Patrick Carlisle, Peter Meier, Pieter van de
Bruggen, R.I.Pienaar, Sean Millichamp, Stefan Schulte, Tim Bishop




---

Ben Hughes (1):
  4911faf (#12195) Fix future ruby warning messaves in process_name

Brice Figureau (1):
  0f19cbe (#11990) Puppetdoc rdoc should also parse README.rdoc

Daniel Pittman (43):
  9e7ce16 (#11057) Note why a scheduled run was skipped in Puppet.
  0f2bb27 (#6710) Fix Ruby 1.9.2 failures due to Array#to_s changes.
  dd0e405 Document why we disable GC during the test runs.
  ed24b80 (#6771) Disconnect any ActiveRecord connection after every test.
  80ecd88 (#6771) Stop stubbing some feature tests.
  3892875 (#6771) Stop other AR connection handling.
  3310470 (#12188) Better handling of PID file cleanup warnings.
  289dddc (#12188) Handle Win32 as well as Unix in pidfile tests.
  37a3e82 (#12296) Test cycle detection on real Puppet::Type instances.
  316de58 (#12296) Make `Puppet::Type` ordered.
  3f2 (#12296) Now that `Puppet::Type` is ordered, use that.
  83ca48d Make `Puppet::Provider` ordered.
  d89423f Use natural ordering of Puppet::Provider.
  f8d4be6 (#12296) Acceptance test for cycle detection in graphs.
  20e03a9 (#11423) Better error when imported resources overlap.
  a8a0f5f (#12268) String#each is not available in Ruby 1.9
  7da2c58 Alternate, and portable, stubbing of execution for upstart spec.
  03e3756 (#2927) Acceptance test for symbolic file modes.
  47510b0 Property Spec cleanup: extract new subclass to let method.
  8f9214e Property Spec cleanup: extract mock provider to let method.
  4157102 Property Spec cleanup: extract mock resource to let method.
  f17dbf7 Property Spec cleanup: extract property instance to a let method.
  a5d7bd6 Property Spec cleanup: remove some pointless extra stubs.
  cd536ab Property Spec cleanup: remove unused instance variable.
  2775dd7 Property Spec cleanup: extract more let methods.
  d66bb00 Property Spec cleanup: last let method extraction.
  7f84c49 Property Spec cleanup: eliminate stubbing of resource
and provider.
  c0e28b0 Add unit tests for the `insysc?` method of a pro

[Puppet Users] Use onlyif in EXEC

[Douglas Brancaglion]

Hi guys!

I need configure one command exec with onlyif parameter.

I want test file size exist or no.

Ho i do this?

Tks in advanced.

Douglas

--
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] Sanity Check Request: Trying something Out-Of-The-Box - MasterLess Puppet

[Dan White]

On my puppetmaster:

cd /etc/puppet
tar zcvf ../pmaster.tar.gz *

copy pmaster.tar.gz to another machine that is defined in the manifest/catalog

On different machine:

mkdir -p /usr/local/localPuppet
mv pmaster.tar.gz /usr/local/localPuppet/
cd /usr/local/localPuppet
tar zxvf pmaster.tar.gz

puppet apply [--noop] --debug --modulepath /usr/local/localPuppet/modules 
/usr/local/localPuppet/manifests/site.pp

The "--noop" is optional.

Does anyone see any glaringly obvious errors in this ?

“Sometimes I think the surest sign that intelligent life exists elsewhere in 
the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin & Hobbes)

-- 
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.

Re: [Puppet Users] Puppet dns requests

[Hugo Deprez]

Thank you for the answer guys.

I am currently migrating all the server on Debian Squeeze with  puppet 2.6.2
I'll consider migrating to your packages repository.

For the number of DNS requests, that's not an issue, I was just having a
look at the DNS logs.
But I think this is not optimized.  What is the point for one execution of
the daemon to request 80 times the same thing ?

Anyway using a record in the /etc/hosts could be an alternative.

Regards,

Hugo
On 9 March 2012 18:20, Nan Liu  wrote:

> The commands are puppetd instead of puppet agent and puppetmasterd
> instead of puppet master. This will give the options in 0.25:
>
> puppetmasterd --configprint all
>
> However rather than dealing with 0.25 and multiple puppet versions, I
> would recommend using our latest packages in apt.puppetlabs.com.
>
> Nan
>
> On Fri, Mar 9, 2012 at 8:44 AM, Hugo Deprez  wrote:
> > Thank you for the link.
> > But I am not able to know if the server parameter is available for 0.25
> > clients.
> >
> > Any idea ?
> >
> > Regards,
> >
> >
> > On 9 March 2012 17:32, Mohamed Lrhazi  wrote:
> >>
> >> http://docs.puppetlabs.com/references/stable/configuration.html
> >>
> >>
> >> On Fri, Mar 9, 2012 at 11:22 AM, Hugo Deprez 
> >> wrote:
> >> > Dear community,
> >> >
> >> > I just saw that when I execute puppetd -vt I can have up to 80 DNS
> >> > request
> >> > for the puppet server records.
> >> > I specified in the puppet.conf :
> >> >
> >> > server=puppetserver.example.fr in the [main] section of the client.
> >> >
> >> > It seems to work for my Debian Squeeze client, but not for Debian
> Lenny.
> >> > Squeeze version is 2.6.2-5 and Debian lenny 0.25.4-2.
> >> >
> >> > Do you know where I can found all the parameter available for
> >> > puppet.conf
> >> > file ?
> >> >
> >> > Regards,
> >> >
> >> > Hugo
> >> >
> >> > --
> >> > 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.
>
>

-- 
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.

Re: [Puppet Users] Use onlyif in EXEC

[Tim Sharpe]

Run command if file exists:
exec { 'foo'
  command => '',
  onlyif => '/usr/bin/test -f /file/that/must/exist/for/exec/to/run',
}

Run command unless file exists
exec {
  command => '',
  creates => '/path/to/file',
}



On Tuesday, 13 March 2012 at 6:23 AM, Douglas Brancaglion wrote:

> Hi guys!
> 
> I need configure one command exec with onlyif parameter.
> 
> I want test file size exist or no.
> 
> Ho i do this?
> 
> Tks in advanced.
> 
> Douglas
> 
> -- 
> 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 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto: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.

Re: [Puppet Users] Use onlyif in EXEC

[Doug Chapman]

Checkout the 'creates' property, it seems like a cleaner way of doing this:

http://docs.puppetlabs.com/references/2.6.8/type.html#exec

On Mon, Mar 12, 2012 at 12:23 PM, Douglas Brancaglion <
douglas.rea...@gmail.com> wrote:

> Hi guys!
>
> I need configure one command exec with onlyif parameter.
>
> I want test file size exist or no.
>
> Ho i do this?
>
> Tks in advanced.
>
> Douglas
>
> --
> 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+unsubscribe@**
> googlegroups.com .
> For more options, visit this group at http://groups.google.com/**
> group/puppet-users?hl=en
> .
>
>


-- 
Doug Chapman

-- 
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.

Re: [Puppet Users] Different versions for server and agents

[vagn scott]

On 03/12/2012 10:16 AM, Peter Bukowinski wrote:


Your master's version should always be equal to or greater than the 
latest client version you're using. You can count on a newer master 
working with older clients, but don't count on newer clients working 
with older masters.




So, no problems with 0.24.5 agent and 2.7.x master?
What about with 2.8 master and beyond?

How far will you let the versions skew? Where is the limit?

--
vagn

--
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] Puppet Master server migration and problem? 2.6 to 2.7

[MF]

Hello,

I am setting up a new master server and migrating my configuration
from my current master server.  I am also upgrading from 2.6 to 2.7.
I have the new server built and integrated with Apache, Passenger, and
Dashboard just like on my current server.  I moved over all my modules
in /etc/puppet/modules as well as my site and node manifests in /etc/
puppet/manifests.  I did not move over the entire /var/lib/puppet/ssl
dir.  At this point I am just testing with two nodes.  The two clients
connect fine and have their certs verified and can connect to puppet
and be seen in dashboard.  But when I try to add one of my existing
module/class to the nodes the configuration is never updated.

The puppet agent runs fine and says finished catalog run but the
configuration is not modified.  I see no errors on either the server
or the client and the certs seem to be just fine.

Anyone have any suggestions?

Thanks in advance for your help.

-- 
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.

Re: [Puppet Users] Puppet Master server migration and problem? 2.6 to 2.7

[vagn scott]

On 03/12/2012 08:22 PM, MF wrote:

Hello,

I am setting up a new master server and migrating my configuration
from my current master server.  I am also upgrading from 2.6 to 2.7.
I have the new server built and integrated with Apache, Passenger, and
Dashboard just like on my current server.  I moved over all my modules
in /etc/puppet/modules as well as my site and node manifests in /etc/
puppet/manifests.  I did not move over the entire /var/lib/puppet/ssl
dir.  At this point I am just testing with two nodes.  The two clients
connect fine and have their certs verified and can connect to puppet
and be seen in dashboard.  But when I try to add one of my existing
module/class to the nodes the configuration is never updated.

The puppet agent runs fine and says finished catalog run but the
configuration is not modified.  I see no errors on either the server
or the client and the certs seem to be just fine.

Anyone have any suggestions?

Thanks in advance for your help.

   

Maybe you need to do this:

touch /etc/puppet/manifests/site.pp


--
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.

Re: [Puppet Users] CentOS upgrade with puppet?

[Walter Heck]

On Mon, Mar 12, 2012 at 20:37, Jakov Sosic  wrote:
> I know that major version upgrades are not recomended (for example 4->5 or
> 5->6). But I am asking about minor upgrades, note the 5.x -> 5.x+1 formula
> in original question.
My bad, I read that as (5.x)+1 instead of as 5.(x+1) ;)

-- 
Walter Heck

--
follow @walterheck on twitter to see what I'm up to!
--
Check out my new startup: Server Monitoring as a Service @ http://tribily.com
Follow @tribily on Twitter and/or 'Like' our Facebook page at
http://www.facebook.com/tribily

-- 
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: No child processes error message in dashboard

[mukulm]

Can anyone assist whats the root cause of "Could not evaluate: No
child processes" error message in dashboard & how this can be
resolved  ?

Thanks


On Mar 1, 9:05 am, mukulm  wrote:
> Hi,
>
> I am getting the "Could not evaluate: No child processes" error
> message in dashboard for the task as
> /Stage[main]/Ubuntu_laptop/Exec[/bin/echo -e 'runinterval=7200' >> /
> etc/puppet/puppet.conf] but when I
> execute the puppet syntax (puppetd -td) manually in terminal on the
> node then it does not return any error.
>
> Any idea why I am receiving the above error message.
> 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-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.

RE: [Puppet Users] Re: No child processes error message in dashboard

[Steve Shipway]

Possibly the UID under which the process is running has a resource limit and is 
not able to spawn a new process?  You likely need to unlimit nproc for the 
puppet process.

Steve

Steve Shipway
University of Auckland ITS
UNIX Systems Design Lead
s.ship...@auckland.ac.nz
Ph: +64 9 373 7599 ext 86487



From: puppet-users@googlegroups.com [puppet-users@googlegroups.com] on behalf 
of mukulm [smilemukul2...@gmail.com]
Sent: Tuesday, 13 March 2012 5:17 p.m.
To: Puppet Users
Subject: [Puppet Users] Re: No child processes error message in dashboard

Can anyone assist whats the root cause of "Could not evaluate: No
child processes" error message in dashboard & how this can be
resolved  ?

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-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.