Re: [Puppet Users] avoiding duplicate package definitions with stdlib's ensure_packages
On Tue, 21 May 2013 13:27:28 -0400, Jonathan Proulx j...@jonproulx.com wrote: One of the most frustrating things about puppet is duplicate definitions of packages, The ensure_packages function from stdlib seems very much like the correct way to handle this: newfunction(:ensure_packages, :type = :statement, :doc = -EOS Takes a list of packages and only installs them if they don't already exist. EOS ) do |arguments| Why isn't this a core feature? Or better why aren't resources that are identical merged? Clearly there is a conflict if they are defined with different parameter (ensure = installed -vs ensure = latest for example) but if they are really identical where is the conflict? My current situation is that we define parted and xfsprogs in our local site configs and the enovance ceph modules also do so. Both of these seem reasonable to me as we need them to make all our systems go and the ceph module needs them to set up the object storage volumes (which is it's primary function) and can't assume everyone uses parted and xfs. The two prevailing opinions in my web readings seem to be to use Virtual resources which is fine for local modules but not so good for sharing and the purist opinion that if there is a conflict the conflicting parts should be split out into an independent module, which is fine for large functional chunks like httpd but ridiculous for single utilities that require no configuration. Yet there is little discussion of ensure_packages as an alternative. Is this for cause or just because it is not well known? Just because it is not well known. ensure_packages seems to be designed for exactly the use-case you are describing: you have two modules both requiring the same utility packages without caring at all about versions or anything else. To elaborate: contrary to (most, all?) other resources, packages have this no-parameter use case, which allows conflict-free merging. Managing more complex resources (users, files) would require more cooperation between modules to ensure that the different requirements do not step on each other. Regards, David -- 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.
Re: [Puppet Users] Trouble with file in module 'source = puppet://...'
Ah yes ! Thank you, that makes sense actually, I didn't realized it before.
Thank to both of you, have a nice day :)
Le mardi 21 mai 2013 18:00:53 UTC+2, Ramin K a écrit :
On 5/21/2013 8:55 AM, Charly Mathieu wrote:
Hello,
I'm trying to write my first module, but I have a problem with a conf
file I want to be managed with puppet.
It's an apache2 vhost file, so the name is www.example.com, my
ressource is like :
file { 'a2site' :
ensure = present,
path = '/etc/apache2/sites-available/www.example.com',
source =
puppet://modules/websitemodule/${conf_file}/etc/apache2/sites-available/
www.example.com,
require = File['a2conf'],
}
It's possible to serve files from other places than the Puppetmaster
using this syntax. Note the two forward slashes.
puppet://servername/path/to/file
In your case you want the file to come from the local server, so you
need three forward slashes to indicate that as in following.
puppet:///local/path/to/file
Ramin
--
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] PuppetDB database tunning
Hi, I've been use puppetdb about 6 months ago, and now the database more than 6gigs Is that any way to recycle database? the data on database more than 30days removed, I try to find is that any option in puppetDB so far, or we need to tune from database side(i use postgresql)? Thanks for any comment. Best regards, Heriyanto -- 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] facter wrong report
Hi, I just check from my virtual machine: [root@host ~]# facter|grep virtual is_virtual = false virtual = physical My operating system is CentOS 6.4 running as domu, running under dom0 CentOS 5.9. I use facter-1.6.6-1.el6. Its bug? Thanks for any comment. Regards, Heriyanto -- 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.
Re: [Puppet Users] Problem creating user with Puppet
Hi,
Thanks for responses. I added piece of code that will create home dir. Code
now looks like this:
file { /home/clavis:
ensure = directory,
owner = clavis,
group = clavis,
mode = 700,
require = [ User[clavis], Group[clavis] ],
}
user { clavis:
ensure = present,
home = /home/clavis,
name = clavis,
shell = /bin/bash,
managehome = true,
groups = 'clavis',
require = Group['clavis']
}
When I try to execute it, I see this error on client:
err: Failed to apply catalog: Could not find dependency Group[clavis] for
User[clavis] at /etc/puppet/manifests/site.pp:25
If I understand it properly, it means it cannot create user because group
clavis do not exist. However, when I add line to add group:
file { /home/clavis:
ensure = directory,
owner = clavis,
group = clavis,
mode = 700,
require = [ User[clavis], Group[clavis] ],
}
group { 'clavis':
ensure = present,
}
user { clavis:
ensure = present,
home = /home/clavis,
name = clavis,
shell = /bin/bash,
managehome = true,
groups = 'clavis',
require = Group['clavis']
}
It tells me:
err: /Stage[main]//Node[puppetclient2]/User[clavis]/ensure: change from
absent to present failed: Could not create user clavis: Execution of
'/usr/sbin/useradd -d /home/clavis -s /bin/bash -G clavis -m clavis'
returned 9: useradd: group clavis exists - if you want to add this user to
that group, use -g.
So what is proper way to add user, create it's home dir, create it's group
and add it to group. Simply speaking, do the same what standard useradd
command would do ?
Thanks...
Best regards,
Dušan
On Tue, May 21, 2013 at 11:37 PM, Jeff Zellner j...@olark.com wrote:
From the docs for `home`: The home directory of the user. The
directory must be created separately and is not currently checked for
existence.
`managehome` doesn't ensure the creation of the home directory, I
believe it just checks permissions.
Cheers!
-Jeff
On Tue, May 21, 2013 at 6:22 PM, Denmat tu2bg...@gmail.com wrote:
Hi,
That should work. Can you provide a bit more info? Versions of puppet and
Ubuntu.
Can you also provide the output from your run with --debug?
Make sure the user is removed before you run again.
Cheers
Den
On 21/05/2013, at 22:39, dusan.dorde...@clavistechnology.com wrote:
Hi,
I am trying to create user on Ubuntu using this code:
user { clavis:
ensure = present,
home = /home/clavis,
name = clavis,
shell = /bin/bash,
managehome = true,
groups = 'clavis',
require = Group['clavis']
}
User is created properly, but home directory is not created, although I
explicitly set mamagehome to true. Any idea what might be the problem
here ?
Thanks in advance,
Dusan
--
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.
--
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.
--
You received this message because you are subscribed to a topic in the
Google Groups Puppet Users group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/puppet-users/EkT8H779j4E/unsubscribe?hl=en
.
To unsubscribe from this group and all its topics, 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.
--
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: Need help with python msi install on windows
Try:
class python::install {
package { 'python':
ensure = installed,
source = example.com
\\software\\python\\python-2.7.3.amd64.msi,
install_options = [ { 'INSTALLDIR' = 'C:\python27' }, {
'ALLUSERS' = '1' } ],
}
}
p.s. with puppet 3 - provider should be windows - and should be so pr.
default.
notice that it HAS to be a valid UNC path - otherwise you could try to put
a file resource - to throw the msi to c:\temp f.ex. - and use that as UNC
path to package.
--
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.
Re: [Puppet Users] Problem creating user with Puppet
On 22 May 2013 09:43, Dusan Dordevic dusan.dorde...@clavistechnology.comwrote: groups = 'clavis', you don't need this next line, it'll be auto-required. require = Group['clavis'] -- 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.
Re: [Puppet Users] Problem creating user with Puppet
Hi,
I changed code to:
file { /home/clavis:
ensure = directory,
owner = clavis,
group = clavis,
mode = 700,
require = [ User[clavis], Group[clavis] ],
}
group { 'clavis':
ensure = present,
}
user { clavis:
ensure = present,
home = /home/clavis,
name = clavis,
shell = /bin/bash,
managehome = true,
groups = 'clavis',
}
(removed require = Group['clavis'])
but it is still the same. here is error message:
notice: /Stage[main]//Node[puppetclient2]/Group[clavis]/ensure: created
err: /Stage[main]//Node[puppetclient2]/User[clavis]/ensure: change from
absent to present failed: Could not create user clavis: Execution of
'/usr/sbin/useradd -d /home/clavis -s /bin/bash -G clavis -m clavis'
returned 9: useradd: group clavis exists - if you want to add this user to
that group, use -g.
Best regards,
Dušan
On Wed, May 22, 2013 at 12:19 PM, Dick Davies
rasput...@hellooperator.netwrote:
On 22 May 2013 09:43, Dusan Dordevic
dusan.dorde...@clavistechnology.comwrote:
groups = 'clavis',
you don't need this next line, it'll be auto-required.
require = Group['clavis']
--
You received this message because you are subscribed to a topic in the
Google Groups Puppet Users group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/puppet-users/EkT8H779j4E/unsubscribe?hl=en
.
To unsubscribe from this group and all its topics, 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.
--
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.
Re: [Puppet Users] Problem creating user with Puppet
file { /home/clavis:
ensure = directory,
owner = clavis,
group = clavis,
mode = 700,
require = [ User[clavis], Group[clavis] ],
}
group { 'clavis':
ensure = present,
}
user { clavis:
ensure = present,
home = /home/clavis,
name = clavis,
shell = /bin/bash,
managehome = true,
# groups = 'clavis', --- This is the problem remove it and this will work
}
I think you are confusing the user's primary group with additional groups
From http://docs.puppetlabs.com/references/latest/type.html#user :
gid:
The user’s primary group. Can be specified numerically or by name. Note that
users on Windows systems do not have a primary group; manage groups with the
groups attribute instead.
groups:
The groups to which the user belongs. The primary group should not be listed,
and groups should be identified by name rather than by GID. Multiple groups
should be specified as an array.
From http://www.computerhope.com/unix/useradd.htm :
-g initial_group
The group name or number of the user's initial login group. The group name must
exist. A group number must refer to an already existing group. The default
group number is 1.
-G group,[,...]
A list of supplementary groups which the user is also a member of. Each group
is separated from the next by a comma, with no intervening whitespace. The
groups are subject to the same restrictions as the group given with the -g
option. The default is for the user to belong only to the initial group.
“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)
- Original Message -
From: Dusan Dordevic dusan.dorde...@clavistechnology.com
To: puppet-users@googlegroups.com
Sent: Wednesday, May 22, 2013 7:27:45 AM
Subject: Re: [Puppet Users] Problem creating user with Puppet
Hi,
I changed code to:
file { /home/clavis:
ensure = directory,
owner = clavis,
group = clavis,
mode = 700,
require = [ User[clavis], Group[clavis] ],
}
group { 'clavis':
ensure = present,
}
user { clavis:
ensure = present,
home = /home/clavis,
name = clavis,
shell = /bin/bash,
managehome = true,
groups = 'clavis',
}
(removed require = Group['clavis'])
but it is still the same. here is error message:
notice: /Stage[main]//Node[puppetclient2]/Group[clavis]/ensure: created
err: /Stage[main]//Node[puppetclient2]/User[clavis]/ensure: change from absent
to present failed: Could not create user clavis: Execution of
'/usr/sbin/useradd -d /home/clavis -s /bin/bash -G clavis -m clavis' returned
9: useradd: group clavis exists - if you want to add this user to that group,
use -g.
Best regards,
Dušan
On Wed, May 22, 2013 at 12:19 PM, Dick Davies rasput...@hellooperator.net
wrote:
On 22 May 2013 09:43, Dusan Dordevic dusan.dorde...@clavistechnology.com
wrote:
groups = 'clavis',
you don't need this next line, it'll be auto-required.
require = Group['clavis']
--
You received this message because you are subscribed to a topic in the Google
Groups Puppet Users group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/puppet-users/EkT8H779j4E/unsubscribe?hl=en .
To unsubscribe from this group and all its topics, 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 .
--
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 .
--
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.
Re: [Puppet Users] Problem creating user with Puppet
This was the problem, when I removed
groups = 'clavis',
everything started working.
Thanks !
Best regards,
Dušan
On Wed, May 22, 2013 at 2:03 PM, Dan White y...@comcast.net wrote:
file { /home/clavis:
ensure = directory,
owner = clavis,
group = clavis,
mode = 700,
require = [ User[clavis], Group[clavis] ],
}
group { 'clavis':
ensure = present,
}
user { clavis:
ensure = present,
home = /home/clavis,
name = clavis,
shell = /bin/bash,
managehome = true,
# groups = 'clavis', --- This is the problem remove it and this will work
}
I think you are confusing the user's primary group with additional groups
From http://docs.puppetlabs.com/references/latest/type.html#user :
gid:
The user’s primary group. Can be specified numerically or by name. Note
that users on Windows systems do not have a primary group; manage groups
with the groups attribute instead.
groups:
The groups to which the user belongs. The primary group should not be
listed, and groups should be identified by name rather than by GID.
Multiple groups should be specified as an array.
From http://www.computerhope.com/unix/useradd.htm :
-g initial_group
The group name or number of the user's initial login group. The group name
must exist. A group number must refer to an already existing group. The
default group number is 1.
-G group,[,...]
A list of supplementary groups which the user is also a member of. Each
group is separated from the next by a comma, with no intervening
whitespace. The groups are subject to the same restrictions as the group
given with the -g option. The default is for the user to belong only to the
initial group.
“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)
- Original Message -
From: Dusan Dordevic dusan.dorde...@clavistechnology.com
To: puppet-users@googlegroups.com
Sent: Wednesday, May 22, 2013 7:27:45 AM
Subject: Re: [Puppet Users] Problem creating user with Puppet
Hi,
I changed code to:
file { /home/clavis:
ensure = directory,
owner = clavis,
group = clavis,
mode = 700,
require = [ User[clavis], Group[clavis] ],
}
group { 'clavis':
ensure = present,
}
user { clavis:
ensure = present,
home = /home/clavis,
name = clavis,
shell = /bin/bash,
managehome = true,
groups = 'clavis',
}
(removed require = Group['clavis'])
but it is still the same. here is error message:
notice: /Stage[main]//Node[puppetclient2]/Group[clavis]/ensure: created
err: /Stage[main]//Node[puppetclient2]/User[clavis]/ensure: change from
absent to present failed: Could not create user clavis: Execution of
'/usr/sbin/useradd -d /home/clavis -s /bin/bash -G clavis -m clavis'
returned 9: useradd: group clavis exists - if you want to add this user to
that group, use -g.
Best regards,
Dušan
On Wed, May 22, 2013 at 12:19 PM, Dick Davies
rasput...@hellooperator.net wrote:
On 22 May 2013 09:43, Dusan Dordevic dusan.dorde...@clavistechnology.com
wrote:
groups = 'clavis',
you don't need this next line, it'll be auto-required.
require = Group['clavis']
--
You received this message because you are subscribed to a topic in the
Google Groups Puppet Users group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/puppet-users/EkT8H779j4E/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, 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 .
--
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 .
--
You received this message because you are subscribed to a topic in the
Google Groups Puppet Users group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/puppet-users/EkT8H779j4E/unsubscribe?hl=en
.
To unsubscribe from this group and all its topics, 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.
--
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] Re: Puppet - rbuf_fill timeout error periodically on puppet client runs
On Tuesday, May 21, 2013 8:18:58 AM UTC-5, phundisk wrote: Occasionally I am seeing this error below on puppet client runs from several different clients. The clients and the server in this environment are rather old and this started to happen more after I used to nagios module which uses stored configs. Does anyone know where this slowness might be coming from (client, server, db, etc) or how I can increase this timeout parameter? Or does this indicate some poor programming in my puppet code in terms of inefficiency. I would say this happens maybe one or two times a week out of 20 servers running every 30 minutes. *Current Setup:* Puppet Server: puppet-server-2.7.20-1 Ruby: 1.8.7.370 Stored Configs: MySQL 5.5.15 Cron Run Command (no service): /usr/sbin/puppetd --server puppet --onetime --no-daemonize --verbose --logdest syslog *Error* /usr/lib/ruby/1.8/timeout.rb:54:in `rbuf_fill': execution expired (Timeout::Error) from /usr/lib/ruby/1.8/timeout.rb:56:in `timeout' from /usr/lib/ruby/1.8/timeout.rb:76:in `timeout' from /usr/lib/ruby/1.8/net/protocol.rb:132:in `rbuf_fill' from /usr/lib/ruby/1.8/net/protocol.rb:116:in `readuntil' from /usr/lib/ruby/1.8/net/protocol.rb:126:in `readline' from /usr/lib/ruby/1.8/net/http.rb:2020:in `read_status_line' from /usr/lib/ruby/1.8/net/http.rb:2009:in `read_new' from /usr/lib/ruby/1.8/net/http.rb:1050:in `request' ... 24 levels... from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `exit_on_fail' from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' from /usr/sbin/puppetd:159 It looks like you are running about at the edge of your master's capacity. Especially since you're running out of cron, that could be related to an uneven workload, where all of your servers make catalog requests at approximately the same time. If you have not already done so, then you should ensure that your crontab entries spread out requests relatively evenly over time. Are you running the master via its built-in webrick server, or have you set it up in apache/passenger, mongrel, or some other more featureful rack server? The webrick version is single-threaded, serving only one client at a time, and that can cause delays and client-side timeouts when multiple requests arrive close together, even if the server has enough raw power that it should be able to serve them all adequately. Twenty clients is in the range where the single-threaded webrick server may start to have trouble keeping up, though that depends heavily on your manifests and the pattern of requests. I have a webrick server supporting many more clients than that, but the manifest set it's working with is pretty simple. Nagios resources themselves are not a special problem, but exported resources and stored configs very well could be. Do use thin stored configs if possible, as that will lighten the load somewhat. John -- 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.
Re: [Puppet Users] Problem creating user with Puppet
Glad I could help.
“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)
- Original Message -
From: Dusan Dordevic dusan.dorde...@clavistechnology.com
To: puppet-users@googlegroups.com
Sent: Wednesday, May 22, 2013 9:07:53 AM
Subject: Re: [Puppet Users] Problem creating user with Puppet
This was the problem, when I removed
groups = 'clavis',
everything started working.
Thanks !
Best regards,
Dušan
On Wed, May 22, 2013 at 2:03 PM, Dan White y...@comcast.net wrote:
file { /home/clavis:
ensure = directory,
owner = clavis,
group = clavis,
mode = 700,
require = [ User[clavis], Group[clavis] ],
}
group { 'clavis':
ensure = present,
}
user { clavis:
ensure = present,
home = /home/clavis,
name = clavis,
shell = /bin/bash,
managehome = true,
# groups = 'clavis', --- This is the problem remove it and this will work
}
I think you are confusing the user's primary group with additional groups
From http://docs.puppetlabs.com/references/latest/type.html#user :
gid:
The user’s primary group. Can be specified numerically or by name. Note that
users on Windows systems do not have a primary group; manage groups with the
groups attribute instead.
groups:
The groups to which the user belongs. The primary group should not be listed,
and groups should be identified by name rather than by GID. Multiple groups
should be specified as an array.
From http://www.computerhope.com/unix/useradd.htm :
-g initial_group
The group name or number of the user's initial login group. The group name must
exist. A group number must refer to an already existing group. The default
group number is 1.
-G group,[,...]
A list of supplementary groups which the user is also a member of. Each group
is separated from the next by a comma, with no intervening whitespace. The
groups are subject to the same restrictions as the group given with the -g
option. The default is for the user to belong only to the initial group.
“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)
- Original Message -
From: Dusan Dordevic dusan.dorde...@clavistechnology.com
To: puppet-users@googlegroups.com
Sent: Wednesday, May 22, 2013 7:27:45 AM
Subject: Re: [Puppet Users] Problem creating user with Puppet
Hi,
I changed code to:
file { /home/clavis:
ensure = directory,
owner = clavis,
group = clavis,
mode = 700,
require = [ User[clavis], Group[clavis] ],
}
group { 'clavis':
ensure = present,
}
user { clavis:
ensure = present,
home = /home/clavis,
name = clavis,
shell = /bin/bash,
managehome = true,
groups = 'clavis',
}
(removed require = Group['clavis'])
but it is still the same. here is error message:
notice: /Stage[main]//Node[puppetclient2]/Group[clavis]/ensure: created
err: /Stage[main]//Node[puppetclient2]/User[clavis]/ensure: change from absent
to present failed: Could not create user clavis: Execution of
'/usr/sbin/useradd -d /home/clavis -s /bin/bash -G clavis -m clavis' returned
9: useradd: group clavis exists - if you want to add this user to that group,
use -g.
Best regards,
Dušan
On Wed, May 22, 2013 at 12:19 PM, Dick Davies rasput...@hellooperator.net
wrote:
On 22 May 2013 09:43, Dusan Dordevic dusan.dorde...@clavistechnology.com
wrote:
groups = 'clavis',
you don't need this next line, it'll be auto-required.
require = Group['clavis']
--
You received this message because you are subscribed to a topic in the Google
Groups Puppet Users group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/puppet-users/EkT8H779j4E/unsubscribe?hl=en .
To unsubscribe from this group and all its topics, 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 .
--
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 .
--
You received this message because you are subscribed to a topic in the Google
Groups Puppet Users group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/puppet-users/EkT8H779j4E/unsubscribe?hl=en .
To unsubscribe from this group and all its topics, send an email to
Re: [Puppet Users] avoiding duplicate package definitions with stdlib's ensure_packages
On Wednesday, May 22, 2013 1:48:26 AM UTC-5, David Schmitt wrote: Just because it is not well known. ensure_packages seems to be designed for exactly the use-case you are describing: you have two modules both requiring the same utility packages without caring at all about versions or anything else. To elaborate: contrary to (most, all?) other resources, packages have this no-parameter use case, which allows conflict-free merging. Managing more complex resources (users, files) would require more cooperation between modules to ensure that the different requirements do not step on each other. No, the only resource types that could have no-parameter use cases would be those with no parameters, but there are none such. Some types, including Package, admit sensible use cases involving only default parameter values, but that's a rather different thing, and not necessarily the thing you want. Also, either ensure_packages() must ignore the context-specific Package parameter defaults (in which case those won't work, which could be a hard-to-debug surprise) or else uses of the function in different contexts can be inequivalent, so that one set of package parameters is chosen over all others, at semi-random (also a potential nasty surprise). Furthermore, ensure_packages() is inherently parse-order dependent, and parse-order dependencies are a major source of concern in Puppet manifest design. That is mitigated in this case if you require that packages used with ensure_packages() are never declared any other way, but then you're placing a constraint on your manifest set that is easy to overlook, that might not be enforced by the catalog compiler, and that you cannot by any means expect third-party modules to comply with. Ensure_packages() is bad juju. If you design your manifest set well in the first place then you will not need it. Sadly, the current state of module compatibility is that in some cases you may need to refactor third-party modules to achieve the overall design criteria you want. At least Puppet will notify you of those cases (provided that ensure_packages() or some similar device doesn't mask it). John -- 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.
Re: [Puppet Users] Problem creating user with Puppet
On Tuesday, May 21, 2013 5:37:52 PM UTC-5, Jeff Zellner wrote: From the docs for `home`: The home directory of the user. The directory must be created separately and is not currently checked for existence. `managehome` doesn't ensure the creation of the home directory, I believe it just checks permissions. On the contrary, for providers that support the 'manages_homedir' feature, managehome = true should indeed cause the provider to create or remove the home directory as needed and appropriate. And most User providers do support that feature. The agent's debug output should show which provider is being used. John -- 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: PuppetDB database tunning
http://docs.puppetlabs.com/puppetdb/1.3/maintain_and_tune.html Den onsdag den 22. maj 2013 09.56.36 UTC+2 skrev Heriyanto: Hi, I've been use puppetdb about 6 months ago, and now the database more than 6gigs Is that any way to recycle database? the data on database more than 30days removed, I try to find is that any option in puppetDB so far, or we need to tune from database side(i use postgresql)? Thanks for any comment. Best regards, Heriyanto -- 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] Pupppet 3.1.1. Ignoring schedules
Greetings.
Puppet 3.1.1, Debian 7.0
I am trying to sync resource(file) from master to agent host.
When schedule metaparameter is not defined - sync is successfull.
if not - schedule is skipped and sync does not start
clock is synchronized, timezone is ok.
part of master config:
*schedule { test:*
*range = 18-19, *
*period = daily,*
*}*
*class sl_movie_main*
*{*
*file {/tmp/rolik.mpg:*
*ensure = file,*
*owner = root,*
*mode = 777,*
*schedule = test,*
*source = puppet:///media/company/sl.movie.main.mpg,*
*}*
Debug from agent:
*Debug: file_metadata supports formats: b64_zlib_yaml pson raw yaml; using
pson*
*Debug: Finishing transaction 70219949229800*
*Debug: catalog supports formats: b64_zlib_yaml dot pson raw yaml; using
pson*
*Info: Caching catalog for somename*
*Debug: Creating default schedules*
*Debug: Loaded state in 0.00 seconds*
*Info: Applying configuration version '1369234836'*
*Debug: /Schedule[daily]: Skipping device resources because running on a
host*
*Debug: /Schedule[monthly]: Skipping device resources because running on a
host*
*Debug: /Schedule[hourly]: Skipping device resources because running on a
host*
*Debug: file_metadata supports formats: b64_zlib_yaml pson raw yaml; using
pson*
*Debug: /Stage[main]/Sl_movie_main/File[/tmp/rolik.mpg]: Not scheduled*
*Debug: /Stage[main]/Sl_movie_kiev/File[/tmp/rolik.kiev.mpg]: Not scheduled*
*Debug: /Schedule[never]: Skipping device resources because running on a
host*
*Debug: /Stage[main]//Schedule[test]: Skipping device resources because
running on a host*
*Debug: file_metadata supports formats: b64_zlib_yaml pson raw yaml; using
pson*
*Debug: /Schedule[weekly]: Skipping device resources because running on a
host*
*Debug: /Schedule[puppet]: Skipping device resources because running on a
host*
*Debug: file_metadata supports formats: b64_zlib_yaml pson raw yaml; using
pson*
*Debug: Finishing transaction 70219948774900*
*Debug: Storing state*
*Debug: Stored state in 0.02 seconds*
*Notice: Finished catalog run in 1.51 seconds*
*Debug: Value of 'preferred_serialization_format' (pson) is invalid for
report, using default (b64_zlib_yaml)*
*Debug: report supports formats: b64_zlib_yaml raw yaml; using b64_zlib_yaml
*
*ls: cannot access /tmp/rol*: No such file or directory*
*Debug: Finishing transaction 70219949503360*
--
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] Initial agent setup - signing procedure fails.
I'm following the instructions at http://docs.puppetlabs.com/guides/setting_up.html from Start the Central Daemon, but the signing procedure didn't work first time and nothing happens on a rerun after cleaning up as instructed. I can't see what (if anything!) I've done wrong, so suggestions as to what to investigate would be appreciated. Thanks. Master and agent logs are interpolated below - I'm fairly certain it's as chronological as is reasonably possible! [root@ncqd-isghub01 ~]# id puppet uid=52(puppet) gid=52(puppet) groups=52(puppet) [root@ncqd-isghub01 ~]# pgrep pup [root@ncqd-isghub01 ~]# ps -ef | grep puppet root 29444 29421 0 07:32 pts/000:00:00 grep puppet [root@ncqd-isghub01 ~]# puppet master [root@ncqd-isghub01 ~]# ps -ef | grep puppet puppet 29454 1 0 07:32 ?00:00:00 /usr/bin/ruby /usr/bin/puppet master root 29458 29421 0 07:32 pts/000:00:00 grep puppet # puppet agent --server puppet --waitforcert 60 --test info: Creating a new SSL key for ntm-igdev02.nott.ime.mycompany.com warning: peer certificate won't be verified in this SSL session info: Caching certificate for ca warning: peer certificate won't be verified in this SSL session warning: peer certificate won't be verified in this SSL session info: Caching certificate_request for ntm-igdev02.nott.ime.mycompany.com warning: peer certificate won't be verified in this SSL session warning: peer certificate won't be verified in this SSL session warning: peer certificate won't be verified in this SSL session notice: Did not receive certificate warning: peer certificate won't be verified in this SSL session info: Caching certificate for ntm-igdev02.nott.ime.mycompany.com [root@ncqd-isghub01 ~]# puppet cert list ntm-igdev02.nott.ime.mycompany.com (MD5) DF:FA:7F:ED:B3:C6:EB:A7:15:6E:66:07:E3:D4:55:D1 [root@ncqd-isghub01 ~]# puppet cert --sign ntm-igdev02.nott.ime.mycompany.com Notice: Signed certificate request for ntm-igdev02.nott.ime.mycompany.com Notice: Removing file Puppet::SSL::CertificateRequest ntm-igdev02.nott.ime.mycompany.com at '/var/lib/puppet/ssl/ca/requests/ntm-igdev02.nott.ime.mycompany.com.pem' err: Could not request certificate: The certificate retrieved from the master does not match the agent's private key. Certificate fingerprint: F5:9E:07:34:4B:59:AA:A9:7E:B1:78:A3:D2:CA:F9:52 To fix this, remove the certificate from both the master and the agent and then start a puppet run, which will automatically regenerate a certficate. On the master: puppet cert clean ntm-igdev02.nott.ime.mycompany.com On the agent: rm -f /var/opt/csw/puppet/ssl/certs/ntm-igdev02.nott.ime.mycompany.com.pem puppet agent -t err: Could not retrieve catalog from remote server: The certificate retrieved from the master does not match the agent's private key. Certificate fingerprint: F5:9E:07:34:4B:59:AA:A9:7E:B1:78:A3:D2:CA:F9:52 To fix this, remove the certificate from both the master and the agent and then start a puppet run, which will automatically regenerate a certficate. On the master: puppet cert clean ntm-igdev02.nott.ime.mycompany.com On the agent: rm -f /var/opt/csw/puppet/ssl/certs/ntm-igdev02.nott.ime.mycompany.com.pem puppet agent -t warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run err: Could not send report: SSL_CTX_use_PrivateKey:: key values mismatch [root@ncqd-isghub01 ~]# puppet cert clean ntm-igdev02.nott.ime.mycompany.com Notice: Revoked certificate with serial 3 Notice: Removing file Puppet::SSL::Certificate ntm-igdev02.nott.ime.mycompany.com at '/var/lib/puppet/ssl/ca/signed/ntm-igdev02.nott.ime.mycompany.com.pem' Notice: Removing file Puppet::SSL::Certificate ntm-igdev02.nott.ime.mycompany.com at '/var/lib/puppet/ssl/certs/ntm-igdev02.nott.ime.mycompany.com.pem' [root@ncqd-isghub01 ~]# puppet cert list [root@ncqd-isghub01 ~ [root@ncqd-isghub01 init.d]# ./puppetmaster stop Stopping puppetmaster: [ OK ] [root@ncqd-isghub01 init.d]# ps -ef | grep puppet root 29552 29421 0 07:46 pts/000:00:00 grep puppet [root@ncqd-isghub01 init.d]# ./puppetmaster start Starting puppetmaster: [ OK ] # rm -f /var/opt/csw/puppet/ssl/certs/ntm-igdev02.nott.ime.mycompany.com.pem # puppet agent -t warning: peer certificate won't be verified in this SSL session warning: peer certificate won't be verified in this SSL session warning: peer certificate won't be verified in this SSL session Exiting; no certificate found and waitforcert is disabled # puppet agent --server puppet --waitforcert 60 --test warning: peer certificate won't be verified in this SSL session warning: peer certificate won't be verified in this SSL session warning: peer certificate won't be verified in this SSL session warning: peer certificate won't be verified in this SSL session notice: Did not receive certificate warning: peer certificate won't be verified in this SSL session notice: Did not receive certificate warning: peer certificate won't be
[Puppet Users] Re: Puppet 3.0: Not authorized to call find on /file_metadata, more issues?
Thank you for clearing this up. What I am not understanding is why this fails. If anyone could help me figure this out would be greatly appreciated. [files] path /etc/puppet/files allow_ip 10.0.0.0/8 But this works, [files] path /etc/puppet/files allow * It resulted in much hair loss. On Tuesday, October 23, 2012 9:55:16 AM UTC+11, Nick Fagerlund wrote: Hi everybody, This is a bug, and we're working on it. I'm about to update the auth.conf docs with info about allow_ip. Additionally, have a complete workaround for anyone being affected by this today. This offers complete equivalence to the fileserver.conf behavior that worked in 2.x and broke in 3.0.0. **In fileserver.conf:** Put the name of your mount point, the path, and an `allow *` directive. [files] path /etc/puppet/files allow * **In auth.conf:** Use a regular expression path to match both the `file_metadata` and `file_content` endpoints followed by the name of your custom mount point. Then, use any combination of `allow` and `allow_ip` directives to control access. path ~ ^/file_(metadata|content)/files/ auth yes allow /^(.+\.)?example.com$/ allow_ip 192.168.100.0/24 **Effect:** This fully re-implements the previous behavior of the following fileserver.conf: [files] path /etc/puppet/files allow *.example.com allow 192.168.100.0/24 It does this by: * Allowing any request to fulfill fileserver.conf's requirements... * ...but using auth.conf to ensure that only authorized requests ever reach fileserver.conf. This pattern will be forward-compatible with whatever permanent fix we implement for this bug. It's not very attractive, but it works. -- 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: facter wrong report
I'm on 1.7.1, Facter finds xen fine. is_virtual = true virtual = xen odd part is I'm not sure the detection method has changed since 1.6. It just check if any of these paths exist: /proc/sys/xen, /sys/bus/xen, /proc/xen On Wednesday, May 22, 2013 1:06:02 AM UTC-7, Heriyanto wrote: Hi, I just check from my virtual machine: [root@host ~]# facter|grep virtual is_virtual = false virtual = physical My operating system is CentOS 6.4 running as domu, running under dom0 CentOS 5.9. I use facter-1.6.6-1.el6. Its bug? Thanks for any comment. Regards, Heriyanto -- 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] new user help
I have spent a couple of weeks with the documentation at puppet labs. But I am struggling with writting some basic modules and some other basic operations to get me up to speed. Is there any groups for newbies to help them get over the initial hump? -- 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: Dashboard showing newline character
I am having this exact same issue. I installed Puppet this past April, from the PuppetLabs repository on a Debian Wheezy box. I see these new line characters under the reports, as you have shown. I am also new to Puppet and new to Ruby, which makes this problem even more frustrating. On Thursday, April 4, 2013 7:46:34 AM UTC-7, Kevin Squire wrote: I just completed the install of dashboard on a Debian Wheezy box, using the deb package provided by puppetlabs repository. After following the directions http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html I now have it up and running (collecting reports only at the moment) I am noticing that on all my reports page, I get a ton of \n characters showing up. Since I am new to Ruby as well as Puppet, I am having a hard time finding WHY these are getting inserted. Any help would be appreciated. Attached is a screenshot showing the issue... same image is also available at http://www.wikiak.org/temp/dashboard.png -- 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: Puppet - rbuf_fill timeout error periodically on puppet client runs
I am using passenger setup right now. I agree with your thought that it is either the addition of tons of exported resources or the puppet master server. I will run some experiments and see if this can be resolved. On Tuesday, May 21, 2013 9:18:58 AM UTC-4, phundisk wrote: Occasionally I am seeing this error below on puppet client runs from several different clients. The clients and the server in this environment are rather old and this started to happen more after I used to nagios module which uses stored configs. Does anyone know where this slowness might be coming from (client, server, db, etc) or how I can increase this timeout parameter? Or does this indicate some poor programming in my puppet code in terms of inefficiency. I would say this happens maybe one or two times a week out of 20 servers running every 30 minutes. *Current Setup:* Puppet Server: puppet-server-2.7.20-1 Ruby: 1.8.7.370 Stored Configs: MySQL 5.5.15 Cron Run Command (no service): /usr/sbin/puppetd --server puppet --onetime --no-daemonize --verbose --logdest syslog *Error* /usr/lib/ruby/1.8/timeout.rb:54:in `rbuf_fill': execution expired (Timeout::Error) from /usr/lib/ruby/1.8/timeout.rb:56:in `timeout' from /usr/lib/ruby/1.8/timeout.rb:76:in `timeout' from /usr/lib/ruby/1.8/net/protocol.rb:132:in `rbuf_fill' from /usr/lib/ruby/1.8/net/protocol.rb:116:in `readuntil' from /usr/lib/ruby/1.8/net/protocol.rb:126:in `readline' from /usr/lib/ruby/1.8/net/http.rb:2020:in `read_status_line' from /usr/lib/ruby/1.8/net/http.rb:2009:in `read_new' from /usr/lib/ruby/1.8/net/http.rb:1050:in `request' ... 24 levels... from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `exit_on_fail' from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' from /usr/sbin/puppetd:159 _ This email and any files transmitted with it are confidential and intended solely for the addressee. If you received this email in error, please do not disclose the contents to anyone; kindly notify the sender by return email and delete this email and any attachments from your system. © 2011 Currensee Inc. is a member of the National Futures Association (NFA) Member ID 0403251 | Over the counter retail foreign currency (Forex) trading may involve significant risk of loss. It is not suitable for all investors and you should make sure you understand the risks involved before trading and seek independent advice if necessary. Performance, strategies and charts shown are not necessarily predictive of any particular result and past performance is no indication of future results. Investor returns may vary from Trade Leader returns based on slippage, fees, broker spreads, volatility or other market conditions. Currensee Inc | 54 Canal St 4th Floor | Boston, MA 02114 | +1.617.624.3824 -- _ This email and any files transmitted with it are confidential and intended solely for the addressee. If you received this email in error, please do not disclose the contents to anyone; kindly notify the sender by return email and delete this email and any attachments from your system. © 2011 Currensee Inc. is a member of the National Futures Association (NFA) Member ID 0403251 | Over the counter retail foreign currency (Forex) trading may involve significant risk of loss. It is not suitable for all investors and you should make sure you understand the risks involved before trading and seek independent advice if necessary. Performance, strategies and charts shown are not necessarily predictive of any particular result and past performance is no indication of future results. Investor returns may vary from Trade Leader returns based on slippage, fees, broker spreads, volatility or other market conditions. Currensee Inc | 54 Canal St 4th Floor | Boston, MA 02114 | +1.617.624.3824 -- 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] Announce: Puppet 3.2.1 Available
Puppet 3.2.1 is a bugfix release for the 3.x series of Puppet. This release addresses two major issues that were uncovered in 3.2.0 and caused us to pull that release (#20726 and #20742). It also includes a fix for Solaris support (#19760). Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-3.2.1.tar.gz Available in native package format at: http://yum.puppetlabs.com and http://apt.puppetlabs.com Gems are available via rubygems at https://rubygems.org/downloads/puppet-3.2.1.gem or by using `gem install puppet` Mac packages are available at https://downloads.puppetlabs.com/mac/puppet-3.2.1.dmg Windows packages are available at https://downloads.puppetlabs.com/windows/puppet-3.2.1.msi Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 3.2.1: https://projects.puppetlabs.com/projects/puppet/ === ## Puppet 3.2.1 Contributors ## === Andrew Parker, Hailee Kenney, Josh Cooper, Josh Partlow, Matthaus Owens = ## Puppet 3.2.1 Release Notes ## = ### Issues fixed: * [Bug #19760]: install sun packages failed with: `Error: /Stage[main]/Inf_sol10defaultpkg/Package[SMCcurl]: Could not evaluate: Unable to get information about package SMCcurl because of: No message` * [Bug #20726]: usermod command arguments out of order * [Bug #20742]: unauthenticated clients unable to communicate with puppet master (running in passenger) ### Known Regressions On Windows, Puppet 3.2.1 is unable to manage the home directory for a user account. ([Bug #20768]) This is a regression from Puppet 3.1.1; it was introduced by switching to Ruby 1.9 in the Windows .msi package. This bug will be fixed soon in a point release, but wasn't severe enough to delay shipping. ### All 3.2.1 Changes To see a list of the issues addressed by this release, check out the 3.2.1 version in our issue tracker at: https://projects.puppetlabs.com/versions/405 == ## Puppet 3.2.1 Changelog ## == Andrew Parker (3): 76664ae (Maint) Give each test a meaningful name ab670d1 (#20742) Handle DNs that cannot be parsed de34775 (#20742) Only use certifcate info if there is a CN Josh Cooper (1): 4274d66 (#20726) Manage home has issues on Solaris Josh Partlow (4): 0588e57 (#20726) Add user managehome acceptance tests 6f92379 Revert Merge branch 'pull-1512' 46df39d (#20726) Include password for useradd managehome tests on windows 866ecbc (maint) Change load order for puppet/provider/package/windows/package Matthaus Owens (2): 2576f8f (packaging) Update PUPPETVERSION to 3.2.1-rc1 025f00d (packaging) Update PUPPETVERSION to 3.2.1 Nick Fagerlund (1): b301ada Maint: Improve documentation of filebucket attributes Stefan Schulte (3): 5e091bb (#19760) Use combine when running pkginfo 887c2037 (#19760) Use pkginfo method instead of execute f04d271 (#19760) Remove unnecessary stubbing in sun_spec -- 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] Puppet 3.2.1 and Facter 1.7.1 for Solaris
Folks, Puppet 3.2.1 and Facter 1.7.1 are available as OpenCSW packages. They're currently in the testing area[1] - if anybody would like to check them out, it'd be appreciated. I'm without a Solaris host right now. --Mark [1] http://buildfarm.opencsw.org/experimental.html#markp -- 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] if word1 match so I replaced it with word2
Hi I would like to replace a word with another in a config file if word1 match so I replaced it with word2 I looked augeas but it does not seem to. you would have a different track? thank you regards -- 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: Need help with python msi install on windows
Matt,
I tried your class in my test environment. Here are my findings:
Using Microsoft's Process
Monitorhttp://technet.microsoft.com/en-us/sysinternals/bb896645.aspx,
we capture Puppet's call to MSIEXE, the command line value reads:
msiexec.exe /qn /no restart /i
example.com\\temp\\python-2.7.3.amd64.msi INSTALLDIR=C:\python27
ALLUSERS=1
It makes sense that you are getting an error because msiexec cannot find
example.com\\temp\\python-2.7.3.amd64.msi.
In order to successfully install, change the source line single quotes
(') to double quotes(). On next Puupet run, Process Monitor command
line value reads:
msiexec.exe /qn /no restart /i \\example.com\temp\python-2.7.3.amd64.msi
INSTALLDIR=C:\python27 ALLUSERS=1
*Another note:
*Using Microsoft's
orca.exehttp://msdn.microsoft.com/en-us/library/windows/desktop/aa370557%28v=vs.85%29.aspx,
the python-2.7.3.amd64.msi doesn't contain properties for INSTALLDIR or
ALLUSERS. These aren't msiexec default properties either. As a result,
these parameters are being ignored by msiexec. You wouldn't notice this
because the values you happen provided for these errant keys are the
defaults. If you comment the install_options line, it will still
install in C:\Python27 for all users.
If you wanted to specify a custom install directory, you would need to use
TARGETDIR.
If you wanted to restrict user access, you would need to use WHICHUSERS.
WHICHUSERS accepts ALL or JUSTME
To install for the current user in specified directory C:\python273
install_options = [ { 'TARGETDIR' = 'C:\python273' }, { 'WHICHUSERS' =
'JUSTME' } ],
Here is your stanza fixed (with the install_options line optional [since
you are using the defaults]):
class python::install {
package { 'python':
ensure = installed,
provider= 'msi',
source = example.com
\\software\\python\\python-2.7.3.amd64.msi,
#install_options = [ { 'TARGETDIR' = 'C:\python27' }, {
'WHICHUSER = 'ALL' } ],
}
}
I hope this helps.
-Kev
--
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: Need help with python msi install on windows
Oops... you should also change the provider as Klavs recommends:
class python::install {
package { 'python':
ensure = installed,
provider= 'windows',
source = example.com\\software\\
python\\python-2.7.3.amd64.msi,
#install_options = [ { 'TARGETDIR' = 'C:\python27' }, {
'WHICHUSER = 'ALL' } ],
}
}
--
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] apt repository appears to have dependency issue with latest release (3.2.1)
When trying to install puppetmaster-passenger from puppetlabs apt repo I get... was working 2ish hours ago (before the 3.2 release) Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: puppetmaster-passenger : Depends: puppetmaster-common (= 3.2.1-1puppetlabs1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. Thanks, Matt -- 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: Announce: Puppet 3.2.1 Available
It seems that the puppetlabs apt repository is broken with the release of these packages. When trying to install puppetmaster-passenger I now get this was working 2 hours ago. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: puppetmaster-passenger : Depends: puppetmaster-common (= 3.2.1-1puppetlabs1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. Matt On Wednesday, May 22, 2013 1:54:00 PM UTC-6, Matthaus Litteken wrote: Puppet 3.2.1 is a bugfix release for the 3.x series of Puppet. This release addresses two major issues that were uncovered in 3.2.0 and caused us to pull that release (#20726 and #20742). It also includes a fix for Solaris support (#19760). Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-3.2.1.tar.gz Available in native package format at: http://yum.puppetlabs.com and http://apt.puppetlabs.com Gems are available via rubygems at https://rubygems.org/downloads/puppet-3.2.1.gem or by using `gem install puppet` Mac packages are available at https://downloads.puppetlabs.com/mac/puppet-3.2.1.dmg Windows packages are available at https://downloads.puppetlabs.com/windows/puppet-3.2.1.msi Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 3.2.1: https://projects.puppetlabs.com/projects/puppet/ === ## Puppet 3.2.1 Contributors ## === Andrew Parker, Hailee Kenney, Josh Cooper, Josh Partlow, Matthaus Owens = ## Puppet 3.2.1 Release Notes ## = ### Issues fixed: * [Bug #19760]: install sun packages failed with: `Error: /Stage[main]/Inf_sol10defaultpkg/Package[SMCcurl]: Could not evaluate: Unable to get information about package SMCcurl because of: No message` * [Bug #20726]: usermod command arguments out of order * [Bug #20742]: unauthenticated clients unable to communicate with puppet master (running in passenger) ### Known Regressions On Windows, Puppet 3.2.1 is unable to manage the home directory for a user account. ([Bug #20768]) This is a regression from Puppet 3.1.1; it was introduced by switching to Ruby 1.9 in the Windows .msi package. This bug will be fixed soon in a point release, but wasn't severe enough to delay shipping. ### All 3.2.1 Changes To see a list of the issues addressed by this release, check out the 3.2.1 version in our issue tracker at: https://projects.puppetlabs.com/versions/405 == ## Puppet 3.2.1 Changelog ## == Andrew Parker (3): 76664ae (Maint) Give each test a meaningful name ab670d1 (#20742) Handle DNs that cannot be parsed de34775 (#20742) Only use certifcate info if there is a CN Josh Cooper (1): 4274d66 (#20726) Manage home has issues on Solaris Josh Partlow (4): 0588e57 (#20726) Add user managehome acceptance tests 6f92379 Revert Merge branch 'pull-1512' 46df39d (#20726) Include password for useradd managehome tests on windows 866ecbc (maint) Change load order for puppet/provider/package/windows/package Matthaus Owens (2): 2576f8f (packaging) Update PUPPETVERSION to 3.2.1-rc1 025f00d (packaging) Update PUPPETVERSION to 3.2.1 Nick Fagerlund (1): b301ada Maint: Improve documentation of filebucket attributes Stefan Schulte (3): 5e091bb (#19760) Use combine when running pkginfo 887c2037 (#19760) Use pkginfo method instead of execute f04d271 (#19760) Remove unnecessary stubbing in sun_spec -- 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] Announce: PuppetDB 1.3.1 Available
PuppetDB 1.3.1 is now available for download! This is a bug-fix release for the 1.3 series of PuppetDB. = ## Downloads ## = Available in native package format at: http://yum.puppetlabs.com and http://apt.puppetlabs.com Puppet module: http://forge.puppetlabs.com/puppetlabs/puppetdb Source (same license as Puppet): http://github.com/puppetlabs/puppetdb/ # Documentation (including how to install): http://docs.puppetlabs.com/puppetdb/1.http://docs.puppetlabs.com/puppetdb/1.2 3 # Issues can be filed at: http://projects.puppetlabs.com/projects/puppetdb/issues # See our development board on Trello: http://links.puppetlabs.com/puppetdb-trello ## PuppetDB 1.3.1 Release Notes ## Many thanks to the following people who contributed patches to this release: * Chris Price * Deepak Giridharagopal * Ken Barber * Matthaus Owens * Nick Fagerlund Bug fixes: * (#19884) Intermittent SSL errors in Puppet master / PuppetDB communication There is a bug in OpenJDK 7 (starting in 1.7 update 6) whereby SSL communication using Diffie-Hellman ciphers will error out a small percentage of the time. In 1.3.1, we've made the list of SSL ciphers that will be considered during SSL handshake configurable. In addition, if you're using an affected version of the JDK and you don't specify a legal list of ciphers, we'll automatically default to a list that does not include the Diffie-Hellman variants. When this issue is fixed in the JDK, we'll update the code to re-enable them on known good versions. * (#20563) Out of Memory error on PuppetDB export Because the `puppetdb-export` tool used multiple threads to retrieve data from PuppetDB and a single thread to write the data to the export file, it was possible in certain hardware configurations to exhaust all of the memory available to the JVM. We've moved this back to a single-threaded implementation for now, which may result in a minor performance decrease for exports, but will prevent the possibility of hitting an OOM error. * Don't check for newer versions in the PE-PuppetDB dashboard When running PuppetDB as part of a Puppet Enterprise installation, the PuppetDB package should not be upgraded independently of Puppet Enterprise. Therefore, the notification message that would appear in the PuppetDB dashboard indicating that a newer version is available has been removed for PE environments. -- 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.
Re: [Puppet Users] Re: Announce: Puppet 3.2.1 Available
Matt, What platform are you on? Are you using a cache of some sort in front of apt? We haven't been able to reproduce this problem. On Wed, May 22, 2013 at 2:50 PM, Matthew Kennedy mattkenn4...@gmail.com wrote: It seems that the puppetlabs apt repository is broken with the release of these packages. When trying to install puppetmaster-passenger I now get this was working 2 hours ago. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: puppetmaster-passenger : Depends: puppetmaster-common (= 3.2.1-1puppetlabs1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. Matt On Wednesday, May 22, 2013 1:54:00 PM UTC-6, Matthaus Litteken wrote: Puppet 3.2.1 is a bugfix release for the 3.x series of Puppet. This release addresses two major issues that were uncovered in 3.2.0 and caused us to pull that release (#20726 and #20742). It also includes a fix for Solaris support (#19760). Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-3.2.1.tar.gz Available in native package format at: http://yum.puppetlabs.com and http://apt.puppetlabs.com Gems are available via rubygems at https://rubygems.org/downloads/puppet-3.2.1.gem or by using `gem install puppet` Mac packages are available at https://downloads.puppetlabs.com/mac/puppet-3.2.1.dmg Windows packages are available at https://downloads.puppetlabs.com/windows/puppet-3.2.1.msi Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 3.2.1: https://projects.puppetlabs.com/projects/puppet/ === ## Puppet 3.2.1 Contributors ## === Andrew Parker, Hailee Kenney, Josh Cooper, Josh Partlow, Matthaus Owens = ## Puppet 3.2.1 Release Notes ## = ### Issues fixed: * [Bug #19760]: install sun packages failed with: `Error: /Stage[main]/Inf_sol10defaultpkg/Package[SMCcurl]: Could not evaluate: Unable to get information about package SMCcurl because of: No message` * [Bug #20726]: usermod command arguments out of order * [Bug #20742]: unauthenticated clients unable to communicate with puppet master (running in passenger) ### Known Regressions On Windows, Puppet 3.2.1 is unable to manage the home directory for a user account. ([Bug #20768]) This is a regression from Puppet 3.1.1; it was introduced by switching to Ruby 1.9 in the Windows .msi package. This bug will be fixed soon in a point release, but wasn't severe enough to delay shipping. ### All 3.2.1 Changes To see a list of the issues addressed by this release, check out the 3.2.1 version in our issue tracker at: https://projects.puppetlabs.com/versions/405 == ## Puppet 3.2.1 Changelog ## == Andrew Parker (3): 76664ae (Maint) Give each test a meaningful name ab670d1 (#20742) Handle DNs that cannot be parsed de34775 (#20742) Only use certifcate info if there is a CN Josh Cooper (1): 4274d66 (#20726) Manage home has issues on Solaris Josh Partlow (4): 0588e57 (#20726) Add user managehome acceptance tests 6f92379 Revert Merge branch 'pull-1512' 46df39d (#20726) Include password for useradd managehome tests on windows 866ecbc (maint) Change load order for puppet/provider/package/windows/package Matthaus Owens (2): 2576f8f (packaging) Update PUPPETVERSION to 3.2.1-rc1 025f00d (packaging) Update PUPPETVERSION to 3.2.1 Nick Fagerlund (1): b301ada Maint: Improve documentation of filebucket attributes Stefan Schulte (3): 5e091bb (#19760) Use combine when running pkginfo 887c2037 (#19760) Use pkginfo method instead of execute f04d271 (#19760) Remove unnecessary stubbing in sun_spec -- 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. -- Matthaus Owens Release Manager, Puppet Labs Join us at PuppetConf 2013, August 22-23 in San Francisco - http://bit.ly/pupconf13 Register now and take advantage of the Early Bird discount - save 25%! -- 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
Re: [Puppet Users] new user help
Hi Dan, You are more than welcome to post here. You will also find there have been loads of questions already asked and answered on this list - so the archives are a wealth of knowledge too. Things to help: Try to break down the things you are having trouble with into a simple test case. Include the error you are getting - check the master and the client. Most people start by peppering the list with loads of questions and go on to lead happy lives :) On 23/05/2013, at 2:58, Dan Hyatt hyat...@gmail.com wrote: I have spent a couple of weeks with the documentation at puppet labs. But I am struggling with writting some basic modules and some other basic operations to get me up to speed. Is there any groups for newbies to help them get over the initial hump? -- 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. -- 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: Announce: Puppet 3.2.1 Available
I neglected to mention in the announcement email, to support the Future parser, we have added dependencies on ruby-rgen to our puppet packages that support dependency resolution (gem, deb, rpm). It is available as a gem on rubygems.org and packaged as a library in our apt and yum dependencies repos. On Wed, May 22, 2013 at 12:54 PM, Matthaus Owens matth...@puppetlabs.com wrote: Puppet 3.2.1 is a bugfix release for the 3.x series of Puppet. This release addresses two major issues that were uncovered in 3.2.0 and caused us to pull that release (#20726 and #20742). It also includes a fix for Solaris support (#19760). Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-3.2.1.tar.gz Available in native package format at: http://yum.puppetlabs.com and http://apt.puppetlabs.com Gems are available via rubygems at https://rubygems.org/downloads/puppet-3.2.1.gem or by using `gem install puppet` Mac packages are available at https://downloads.puppetlabs.com/mac/puppet-3.2.1.dmg Windows packages are available at https://downloads.puppetlabs.com/windows/puppet-3.2.1.msi Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 3.2.1: https://projects.puppetlabs.com/projects/puppet/ === ## Puppet 3.2.1 Contributors ## === Andrew Parker, Hailee Kenney, Josh Cooper, Josh Partlow, Matthaus Owens = ## Puppet 3.2.1 Release Notes ## = ### Issues fixed: * [Bug #19760]: install sun packages failed with: `Error: /Stage[main]/Inf_sol10defaultpkg/Package[SMCcurl]: Could not evaluate: Unable to get information about package SMCcurl because of: No message` * [Bug #20726]: usermod command arguments out of order * [Bug #20742]: unauthenticated clients unable to communicate with puppet master (running in passenger) ### Known Regressions On Windows, Puppet 3.2.1 is unable to manage the home directory for a user account. ([Bug #20768]) This is a regression from Puppet 3.1.1; it was introduced by switching to Ruby 1.9 in the Windows .msi package. This bug will be fixed soon in a point release, but wasn't severe enough to delay shipping. ### All 3.2.1 Changes To see a list of the issues addressed by this release, check out the 3.2.1 version in our issue tracker at: https://projects.puppetlabs.com/versions/405 == ## Puppet 3.2.1 Changelog ## == Andrew Parker (3): 76664ae (Maint) Give each test a meaningful name ab670d1 (#20742) Handle DNs that cannot be parsed de34775 (#20742) Only use certifcate info if there is a CN Josh Cooper (1): 4274d66 (#20726) Manage home has issues on Solaris Josh Partlow (4): 0588e57 (#20726) Add user managehome acceptance tests 6f92379 Revert Merge branch 'pull-1512' 46df39d (#20726) Include password for useradd managehome tests on windows 866ecbc (maint) Change load order for puppet/provider/package/windows/package Matthaus Owens (2): 2576f8f (packaging) Update PUPPETVERSION to 3.2.1-rc1 025f00d (packaging) Update PUPPETVERSION to 3.2.1 Nick Fagerlund (1): b301ada Maint: Improve documentation of filebucket attributes Stefan Schulte (3): 5e091bb (#19760) Use combine when running pkginfo 887c2037 (#19760) Use pkginfo method instead of execute f04d271 (#19760) Remove unnecessary stubbing in sun_spec -- Matthaus Owens Release Manager, Puppet Labs Join us at PuppetConf 2013, August 22-23 in San Francisco - http://bit.ly/pupconf13 Register now and take advantage of the Early Bird discount - save 25%! -- 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.
Re: [Puppet Users] Re: PuppetDB database tunning
This what i'am find, thank you Klavs. On Wed, May 22, 2013 at 9:44 PM, Klavs Klavsen kl...@enableit.dk wrote: http://docs.puppetlabs.com/puppetdb/1.3/maintain_and_tune.html Den onsdag den 22. maj 2013 09.56.36 UTC+2 skrev Heriyanto: Hi, I've been use puppetdb about 6 months ago, and now the database more than 6gigs Is that any way to recycle database? the data on database more than 30days removed, I try to find is that any option in puppetDB so far, or we need to tune from database side(i use postgresql)? Thanks for any comment. Best regards, Heriyanto -- 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. -- 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.
Re: [Puppet Users] Re: facter wrong report
Hi Ellison, thank you for help, theres some bug i think in that version, now i use 1.6.18-3.el6 its solved. On Wed, May 22, 2013 at 11:49 PM, Ellison Marks gty...@gmail.com wrote: I'm on 1.7.1, Facter finds xen fine. is_virtual = true virtual = xen odd part is I'm not sure the detection method has changed since 1.6. It just check if any of these paths exist: /proc/sys/xen, /sys/bus/xen, /proc/xen On Wednesday, May 22, 2013 1:06:02 AM UTC-7, Heriyanto wrote: Hi, I just check from my virtual machine: [root@host ~]# facter|grep virtual is_virtual = false virtual = physical My operating system is CentOS 6.4 running as domu, running under dom0 CentOS 5.9. I use facter-1.6.6-1.el6. Its bug? Thanks for any comment. Regards, Heriyanto -- 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. -- 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: Announce: Puppet 3.2.1 Available
Oops, sorry, I found it in the dependencies repo as you said :) Adding deb http://apt.puppetlabs.com precise dependencies to my sources.list fixed it. cheers, -Tore On Thursday, May 23, 2013 2:08:42 AM UTC+2, Matthaus Litteken wrote: I neglected to mention in the announcement email, to support the Future parser, we have added dependencies on ruby-rgen to our puppet packages that support dependency resolution (gem, deb, rpm). It is available as a gem on rubygems.org and packaged as a library in our apt and yum dependencies repos. On Wed, May 22, 2013 at 12:54 PM, Matthaus Owens matt...@puppetlabs.com javascript: wrote: Puppet 3.2.1 is a bugfix release for the 3.x series of Puppet. This release addresses two major issues that were uncovered in 3.2.0 and caused us to pull that release (#20726 and #20742). It also includes a fix for Solaris support (#19760). Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-3.2.1.tar.gz Available in native package format at: http://yum.puppetlabs.com and http://apt.puppetlabs.com Gems are available via rubygems at https://rubygems.org/downloads/puppet-3.2.1.gem or by using `gem install puppet` Mac packages are available at https://downloads.puppetlabs.com/mac/puppet-3.2.1.dmg Windows packages are available at https://downloads.puppetlabs.com/windows/puppet-3.2.1.msi Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 3.2.1: https://projects.puppetlabs.com/projects/puppet/ === ## Puppet 3.2.1 Contributors ## === Andrew Parker, Hailee Kenney, Josh Cooper, Josh Partlow, Matthaus Owens = ## Puppet 3.2.1 Release Notes ## = ### Issues fixed: * [Bug #19760]: install sun packages failed with: `Error: /Stage[main]/Inf_sol10defaultpkg/Package[SMCcurl]: Could not evaluate: Unable to get information about package SMCcurl because of: No message` * [Bug #20726]: usermod command arguments out of order * [Bug #20742]: unauthenticated clients unable to communicate with puppet master (running in passenger) ### Known Regressions On Windows, Puppet 3.2.1 is unable to manage the home directory for a user account. ([Bug #20768]) This is a regression from Puppet 3.1.1; it was introduced by switching to Ruby 1.9 in the Windows .msi package. This bug will be fixed soon in a point release, but wasn't severe enough to delay shipping. ### All 3.2.1 Changes To see a list of the issues addressed by this release, check out the 3.2.1 version in our issue tracker at: https://projects.puppetlabs.com/versions/405 == ## Puppet 3.2.1 Changelog ## == Andrew Parker (3): 76664ae (Maint) Give each test a meaningful name ab670d1 (#20742) Handle DNs that cannot be parsed de34775 (#20742) Only use certifcate info if there is a CN Josh Cooper (1): 4274d66 (#20726) Manage home has issues on Solaris Josh Partlow (4): 0588e57 (#20726) Add user managehome acceptance tests 6f92379 Revert Merge branch 'pull-1512' 46df39d (#20726) Include password for useradd managehome tests on windows 866ecbc (maint) Change load order for puppet/provider/package/windows/package Matthaus Owens (2): 2576f8f (packaging) Update PUPPETVERSION to 3.2.1-rc1 025f00d (packaging) Update PUPPETVERSION to 3.2.1 Nick Fagerlund (1): b301ada Maint: Improve documentation of filebucket attributes Stefan Schulte (3): 5e091bb (#19760) Use combine when running pkginfo 887c2037 (#19760) Use pkginfo method instead of execute f04d271 (#19760) Remove unnecessary stubbing in sun_spec -- Matthaus Owens Release Manager, Puppet Labs Join us at PuppetConf 2013, August 22-23 in San Francisco - http://bit.ly/pupconf13 Register now and take advantage of the Early Bird discount - save 25%! -- 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: Announce: Puppet 3.2.1 Available
I'm unable to find the ruby-rgen package in the precise apt repo. This is on a fresh EC2 instance, so I don't believe there are any caching going on. It also seems like you have made previous releases of puppet-common dependent on ruby-rgen as well. Is that it really necessary? cheers, -Tore On Thursday, May 23, 2013 2:08:42 AM UTC+2, Matthaus Litteken wrote: I neglected to mention in the announcement email, to support the Future parser, we have added dependencies on ruby-rgen to our puppet packages that support dependency resolution (gem, deb, rpm). It is available as a gem on rubygems.org and packaged as a library in our apt and yum dependencies repos. On Wed, May 22, 2013 at 12:54 PM, Matthaus Owens matt...@puppetlabs.com javascript: wrote: Puppet 3.2.1 is a bugfix release for the 3.x series of Puppet. This release addresses two major issues that were uncovered in 3.2.0 and caused us to pull that release (#20726 and #20742). It also includes a fix for Solaris support (#19760). Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-3.2.1.tar.gz Available in native package format at: http://yum.puppetlabs.com and http://apt.puppetlabs.com Gems are available via rubygems at https://rubygems.org/downloads/puppet-3.2.1.gem or by using `gem install puppet` Mac packages are available at https://downloads.puppetlabs.com/mac/puppet-3.2.1.dmg Windows packages are available at https://downloads.puppetlabs.com/windows/puppet-3.2.1.msi Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 3.2.1: https://projects.puppetlabs.com/projects/puppet/ === ## Puppet 3.2.1 Contributors ## === Andrew Parker, Hailee Kenney, Josh Cooper, Josh Partlow, Matthaus Owens = ## Puppet 3.2.1 Release Notes ## = ### Issues fixed: * [Bug #19760]: install sun packages failed with: `Error: /Stage[main]/Inf_sol10defaultpkg/Package[SMCcurl]: Could not evaluate: Unable to get information about package SMCcurl because of: No message` * [Bug #20726]: usermod command arguments out of order * [Bug #20742]: unauthenticated clients unable to communicate with puppet master (running in passenger) ### Known Regressions On Windows, Puppet 3.2.1 is unable to manage the home directory for a user account. ([Bug #20768]) This is a regression from Puppet 3.1.1; it was introduced by switching to Ruby 1.9 in the Windows .msi package. This bug will be fixed soon in a point release, but wasn't severe enough to delay shipping. ### All 3.2.1 Changes To see a list of the issues addressed by this release, check out the 3.2.1 version in our issue tracker at: https://projects.puppetlabs.com/versions/405 == ## Puppet 3.2.1 Changelog ## == Andrew Parker (3): 76664ae (Maint) Give each test a meaningful name ab670d1 (#20742) Handle DNs that cannot be parsed de34775 (#20742) Only use certifcate info if there is a CN Josh Cooper (1): 4274d66 (#20726) Manage home has issues on Solaris Josh Partlow (4): 0588e57 (#20726) Add user managehome acceptance tests 6f92379 Revert Merge branch 'pull-1512' 46df39d (#20726) Include password for useradd managehome tests on windows 866ecbc (maint) Change load order for puppet/provider/package/windows/package Matthaus Owens (2): 2576f8f (packaging) Update PUPPETVERSION to 3.2.1-rc1 025f00d (packaging) Update PUPPETVERSION to 3.2.1 Nick Fagerlund (1): b301ada Maint: Improve documentation of filebucket attributes Stefan Schulte (3): 5e091bb (#19760) Use combine when running pkginfo 887c2037 (#19760) Use pkginfo method instead of execute f04d271 (#19760) Remove unnecessary stubbing in sun_spec -- Matthaus Owens Release Manager, Puppet Labs Join us at PuppetConf 2013, August 22-23 in San Francisco - http://bit.ly/pupconf13 Register now and take advantage of the Early Bird discount - save 25%! -- 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.
