Re: [Puppet Users] Re: Variable Interpolation (double interpolation)
On 10/27/2010 07:37 PM, Roberto Bouza wrote: Thanks!!! It worked like a charm. On Oct 27, 3:23 pm, Joe McDonagh wrote: FYI, if you're using 2.6, the new pure Ruby stuff might look better. Unfortunately I have not yet deployed 2.6 for prod so I don't have much experience using the pure Ruby DSL stuff. -- -- Joe McDonagh Operations Engineer AIM: YoosingYoonickz IRC: joe-mac on freenode "When the going gets weird, the weird turn pro." -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Uppercase Class Parameters Don't Work - Is this expected?
Nigel Kersten writes: > On Wed, Oct 27, 2010 at 10:17 AM, Peter Meier wrote: > >> > Is this behaviour by design, and if so, where in the documentation can I >> > discover this? It wasn't mentioned in the section on parameterised >> > classes or variables. >> >> Some of the errors are documented here: >> >> http://projects.puppetlabs.com/projects/1/wiki/Frequently_Asked_Questions# >> Puppet+Syntax+Errors >> >> to help people in such cases. Furthermore, if you file a feature request to >> improve the error reporting in your case, it will probably get improved in >> future versions. >> > > +wade who had a similar issue in another email. > > I just filed https://projects.puppetlabs.com/issues/5119 to try and adress > these issues. > > We've actually just hired a tech writer who will be starting in a couple of > weeks, so please everyone file documentation bugs, it would be immensely > helpful. One of our sysadmins recently hit that uppercase tags in StoreConfig didn't work, but lowercase did. I never got around to finding out if this was a PostgreSQL specific oddity in storeconfig or an actual restriction of the tool, but while we are in the area... Daniel -- ✣ Daniel Pittman✉ dan...@rimspace.net☎ +61 401 155 707 ♽ made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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 Application Server Deployment
On Mon, Oct 25, 2010 at 1:21 AM, James Turnbull wrote: > ajinkya prabhune wrote: > > Hi, > > > > So what do u thing is good and better than Puppet ? > > > > thanks > > I second Nigel's question. I know a number of people who deploy Java, > Ruby, PHP, etc, etc applications with Puppet. > Me too. I do it several times a day. Doug. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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: Variable Interpolation (double interpolation)
Thanks!!!
It worked like a charm.
On Oct 27, 3:23 pm, Joe McDonagh wrote:
> On 10/27/2010 04:39 PM, Roberto Bouza wrote:
>
>
>
> > Hello,
>
> > I have a group of variables like
>
> > $a_logs_project1 = machine1
> > $b_logs_project2 = machine2
>
> > then on the definition I'm genrating a variable like:
>
> > $machine_name = "${letter}_logs_${project}"
>
> > So $machine name will be something like: a_logs_project1
>
> > Now I need to convert that (or interpolate it somehow) into the real
> > value "machine1"
>
> > So I have a variable $machine_name which has the name of the variable
> > which has the real value. Do you have any ideas how to obtain this
> > value?
>
> > Any help will be appreciated.
>
> > Thank you.
>
> This works, but... yea:
>
> $machine_name = "machine1"
> $machine1 = "thordur"
> $value = inline_template("<%= scope.lookupvar(machine_name) -%>")
> notice("machine 1 is $value")
>
> --
> --
> Joe McDonagh
> Operations Engineer
> AIM: YoosingYoonickz
> IRC: joe-mac on freenode
> "When the going gets weird, the weird turn pro."
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Variable Interpolation (double interpolation)
On 10/27/2010 04:39 PM, Roberto Bouza wrote:
Hello,
I have a group of variables like
$a_logs_project1 = machine1
$b_logs_project2 = machine2
then on the definition I'm genrating a variable like:
$machine_name = "${letter}_logs_${project}"
So $machine name will be something like: a_logs_project1
Now I need to convert that (or interpolate it somehow) into the real
value "machine1"
So I have a variable $machine_name which has the name of the variable
which has the real value. Do you have any ideas how to obtain this
value?
Any help will be appreciated.
Thank you.
This works, but... yea:
$machine_name = "machine1"
$machine1 = "thordur"
$value = inline_template("<%= scope.lookupvar(machine_name) -%>")
notice("machine 1 is $value")
--
--
Joe McDonagh
Operations Engineer
AIM: YoosingYoonickz
IRC: joe-mac on freenode
"When the going gets weird, the weird turn pro."
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@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] Variable Interpolation (double interpolation)
Hello,
I have a group of variables like
$a_logs_project1 = machine1
$b_logs_project2 = machine2
then on the definition I'm genrating a variable like:
$machine_name = "${letter}_logs_${project}"
So $machine name will be something like: a_logs_project1
Now I need to convert that (or interpolate it somehow) into the real
value "machine1"
So I have a variable $machine_name which has the name of the variable
which has the real value. Do you have any ideas how to obtain this
value?
Any help will be appreciated.
Thank you.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Uppercase Class Parameters Don't Work - Is this expected?
On Wed, Oct 27, 2010 at 10:17 AM, Peter Meier wrote: > > Is this behaviour by design, and if so, where in the documentation > > can I discover this? It wasn't mentioned in the section on > > parameterised classes or variables. > > Some of the errors are documented here: > > > http://projects.puppetlabs.com/projects/1/wiki/Frequently_Asked_Questions#Puppet+Syntax+Errors > > to help people in such cases. Furthermore, if you file a feature request > to improve the error reporting in your case, it will probably get > improved in future versions. > > +wade who had a similar issue in another email. I just filed https://projects.puppetlabs.com/issues/5119 to try and adress these issues. We've actually just hired a tech writer who will be starting in a couple of weeks, so please everyone file documentation bugs, it would be immensely helpful. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] ANNOUNCE: Puppet 2.6.3 - Release Candidate 1 available!
John Warburton wrote: Hi James Is there an ETA for the full release of 2.6.3? For what it is worth, I have been running 2.6.3rc1 for almost 13 days on Solaris 10 U8 & U9 as server and clients. Server is running passenger 2.2.14 with clients and servers weighing in at managing between 500 & 780 resources depending on class chosen. No incidents! Thanks for testing! That's a great data point. We're finalising an rc2 with some minor updates and then hopefully the release shortly after that! Thanks James -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Module names - limitations / reserved words?
Greeting, I'm attempting to solve a mystery we had with a puppet module we couldn't get to auto load. The module named / folder was called "nfs" We notice when we ran 'puppetmasterd --no-daemonize --verbose' that when the client connected that our 'nfs' module was not being auto loaded. We reviewed and triple checked our syntax. We located no errors. As a result of the module not being loaded we were unable to access a resource defined within the init.pp. Finally as a "Hail Mary" we renamed the module to 'nfsexports'. On the next client run the module was auto loaded and all was well in puppet land. My question today is, Are there "reserved" words that can't be used as module to resource names? If yes, does anyone have the list or a URL to the list? We've looked but all we found are references to class name limitations, "ie can't begin with a CAPTIAL letter". Thanks in advance, Wade -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Custom Fact Location Issues
On Mon, Oct 25, 2010 at 5:19 AM, Tomehb wrote:
> Hi Guys,
>
> I have tried changing the default location of puppet facts /var/lib/
> puppet/facts to /etc/puppet/development/modules/custom/lib/facter .
> However, it fails to check the new location, and still pulls the facts
> from the default location.
> My puppet.conf is as follows:
> [main]
> logdir=/var/log/puppet
> vardir=/var/lib/puppet
> ssldir=/etc/puppet/ssl
> rundir=/var/run/puppet
> templatedir=$confdir/templates
>
> factpath=/etc/puppet/development/modules/custom/lib/facter
> factsync = true
>
It looks like you're already using modules, I suggest moving away from
factsync and instead switching to the more modern
pluginsync/plugins-in-modules.
http://docs.puppetlabs.com/guides/plugins_in_modules.html
Your settings look a little confused to me, but if you read through that
doc, it should hopefully become clearer.
Basically factpath is where facts from factsync/pluginsync should be
delivered *to* on the client by the puppetmaster, not where they come
*from*.
> [puppetmasterd]
> #entries read by the puppetmaster itself
> templatedir=/var/lib/puppet/templates
> #reportdir=/var/puppet/lib
> reports=store, log, foreman
> report=true
> ca=true
> autosign=true
> certname=puppeteer.myowndomain.co.uk
> ca_md = sha
> keylength=4096
>
> ssl_client_header = SSL_CLIENT_S_DN
> ssl_client_verify_header = SSL_CLIENT_VERIFY
>
> [production]
>manifest = /etc/puppet/manifests/site.pp
>modulepath = /etc/puppet/production/modules:/etc/puppet/common/
> modules
>
>
> [development]
>manifest = /etc/puppet/development/manifests/site.pp
>modulepath = /etc/puppet/development/modules:/etc/puppet/common/
> modules:/etc/puppet/production/modules
>
>
> [puppetd]
> #entries read by the clients about puppetmaster
> templatedir=/var/lib/puppet/templates
> server=pupppeteer.myowndomain.co.uk
> report=true
>
>
>
>
> --
>
> And on the puppet client..
>
> info: Retrieving facts
> debug: Calling fileserver.list
> debug: Calling fileserver.describe
> debug: /File[/var/lib/puppet/facts]: Changing checksum
> debug: /File[/var/lib/puppet/facts]: 1 change(s)
> debug: /File[/var/lib/puppet/facts]/checksum: Replacing /var/lib/
> puppet/facts checksum {mtime}Mon Oct 25 12:40:07 +0100 2010 with
> {mtime}Mon Oct 25 13:07:46 +0100 2010
> notice: /File[/var/lib/puppet/facts]/checksum: checksum changed
> '{mtime}Mon Oct 25 12:40:07 +0100 2010' to '{mtime}Mon Oct 25 13:07:46
> +0100 2010'
> debug: Finishing transaction -613821548 with 1 changes
> debug: Retrieved facts in 0.72 seconds
>
>
>
>
>
>
> 1) Why is it still reading the default location?
> 2) Any idea where I have gone wrong?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@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.
>
>
--
Nigel Kersten
Product Manager, Puppet Labs
http://www.puppetlabs.com
Twitter: @nigelkersten
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] /var/lib/puppet/clientbucket
On Tue, Oct 26, 2010 at 11:30 PM, Marek Dohojda wrote:
>
> Hello everyone
>
> I looked online, but didn't see any solution to the problem of
> /var/lib/puppet/clientbucket filling up.
>
> After a while that directory is getting very big, 3-4gigs. I have to
> shutdown puppet and remove everything.
>
> Is there a way to either limit the size of this directory, or better yet
> make sure that it isn't filling constantly?
>
Do you actually have a need to use the filebucked on the client? You can
disabling backups for any individual file resource with:
file { "/foo/bar":
backup => false,
}
and many people in fact set this with a global resource default, and
explicitly backup files they care about by setting backup to true for those
individual resources, like:
File { backup => false, }
file { "/etc/important-file":
backup => true,
}
http://docs.puppetlabs.com/guides/language_tutorial.html#resource_defaults
You could also choose to use the tidy resource type to manage the bucket
itself.
http://docs.puppetlabs.com/guides/types/tidy.html
>
> I am running puppet version 0.25.4
>
> Thank you!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@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.
>
--
Nigel Kersten
Product Manager, Puppet Labs
http://www.puppetlabs.com
Twitter: @nigelkersten
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] ANNOUNCE: Puppet 2.6.3 - Release Candidate 1 available!
On Tue, Oct 26, 2010 at 9:11 PM, John Warburton wrote: > Hi James > > Is there an ETA for the full release of 2.6.3? > We have another rc release coming very soon first. > > For what it is worth, I have been running 2.6.3rc1 for almost 13 days on > Solaris 10 U8 & U9 as server and clients. Server is running passenger 2.2.14 > with clients and servers weighing in at managing between 500 & 780 resources > depending on class chosen. No incidents! > Awesome to hear John. > > Cheers > > John > > > On 14 October 2010 16:02, James Turnbull wrote: > >> All too quickly we're back with a maintenance release: 2.6.3. This >> release addresses some issues in the 2.6.2 release. >> >> 2.6.3 is a maintenance release in the 2.6.x branch and it contains only >> bug fixes and no new features or other changes. >> >> The release candidate is available for download at: >> >> http://puppetlabs.com/downloads/puppet/puppet-2.6.3rc1.tar.gz >> >> Please note that all final releases of Puppet are signed with the >> Puppet Labs key. >> >> See the Verifying Puppet Download section at >> http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet >> >> Please test this release candidate and report feedback via the >> Puppet Labs Redmine site: >> >> http://projects.puppetlabs.com >> >> Please select an affected version of 2.6.3rc1. >> >> CHANGELOG >> 3c56705 Fix for #4832 -- Making PSON handle arbitrary binary data >> e232770 Minimal fix for #4975 -- only call chage when managing password >> age rules >> a090e86 Fix for #4963 -- Use correct commands for password expiry on >> solaris >> >> Regards >> >> James Turnbull >> >> -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To post to this group, send email to puppet-us...@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. >> >> > > > -- > John Warburton > Ph: 0417 299 600 > Email: jwarbur...@gmail.com > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@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. > -- Nigel Kersten Product Manager, Puppet Labs http://www.puppetlabs.com Twitter: @nigelkersten -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] puppetdoc and wrong comparison
On Tue, 2010-10-26 at 15:37 +0100, Klaus Ethgen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hello,
>
> at the moment I fight with puppetdoc and end in a ruby confusion.
>
> To the problem:
> > puppetdoc --debug --trace --mode rdoc --all manifests/site.pp
> info: scanning: ["manifests/site.pp"]
> /usr/lib/ruby/1.8/puppet/util/rdoc.rb:82:in `output_resource_doc'
> /usr/lib/ruby/1.8/puppet/util/rdoc.rb:82:in `sort'
> /usr/lib/ruby/1.8/puppet/util/rdoc.rb:82:in `output_resource_doc'
> /usr/lib/ruby/1.8/puppet/util/rdoc.rb:77:in `output_astnode_doc'
> /usr/lib/ruby/1.8/puppet/util/rdoc.rb:67:in `output'
> /usr/lib/ruby/1.8/puppet/util/rdoc.rb:66:in `each'
> /usr/lib/ruby/1.8/puppet/util/rdoc.rb:66:in `output'
> /usr/lib/ruby/1.8/puppet/util/rdoc.rb:47:in `manifestdoc'
> /usr/lib/ruby/1.8/puppet/util/rdoc.rb:43:in `each'
> /usr/lib/ruby/1.8/puppet/util/rdoc.rb:43:in `manifestdoc'
> /usr/lib/ruby/1.8/puppet/application/doc.rb:82:in `rdoc'
> /usr/lib/ruby/1.8/puppet/application/doc.rb:59:in `send'
> /usr/lib/ruby/1.8/puppet/application/doc.rb:59:in `run_command'
> /usr/lib/ruby/1.8/puppet/application.rb:287:in `run'
> /usr/lib/ruby/1.8/puppet/application.rb:393:in `exit_on_fail'
> /usr/lib/ruby/1.8/puppet/application.rb:287:in `run'
> /usr/bin/puppetdoc:4
> Could not generate documentation: undefined method `<=>' for nil:NilClass
>
> The used version is Puppet 2.6.2 on a debian system.
>
> If I look to the code I find the following line:
>code.sort { |a,b| a.line <=> b.line }.each do |stmt|
Which means the code has no line information.
> If I output the code with puts I get the following:
>[]
>[]
>#
>#
>[Filebucket[local]]
>
> I think there is something wrong but I do not know what.
>
> Anybody an idea?
Please open a redmine ticket and include the smallest manifests that can
trigger the bug, so that we can reproduce the bug.
BTW, do you have the same issue when running in so-called html mode?
--
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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: Solaris 10 Client "Default Provider for User" Woes Again
On Wed, Oct 27, 2010 at 6:00 AM, nickt wrote: > Sorry, answered my own question again. Turns out for some reason on > Solaris if you use the --trace and/or --debug flags (not sure which) > when starting your puppetd it will be "unable" to execute /usr/bin/ > passwd. As soon as you take those off it works fine! > > /opt/csw/bin/puppetd --verbose --trace --debug --server > cmsvl01.d1.peapod.com --no-daemonize > It would be immensely appreciated if you could isolate which of these flags causes that issue and you bug report it. We live and die by our bug queue, and issues aren't likely to get fixed unless they're reported. > > > On Oct 27, 7:55 am, nickt wrote: > > Thanks, Felix! I figured it out. Turns out it was because when I > > copied my shadow.so (from ruby-shadow lib build) I'd not changed > > permissions on it to be world read/execute. So, anyone who's trying > > the Solaris client, hope that helps! > > > > Now if only I can figure out how to "let" puppetd execute /usr/bin/ > > passwd to set passwords for users I'll be all set! :) > > > > Let me ask a related question, what is the "best" way to add lines to / > > etc/passwd and /etc/shadow with puppet? I'm setting things up to > > initialize LDAP support on the same Solaris box and need to add lines > > to allow login for specific LDAP groups. The only answer I've found > > so far is to use a module like concat, but I've not gotten that to > > work right so far. > > > > On Oct 27, 7:46 am, Felix Frank > > wrote: > > > > > > > > > > > > > > > > > On 10/27/2010 02:36 PM, nickt wrote: > > > > > > Hopefully I'm just missing something simple, but I'm having trouble > > > > getting just the absolute bare-bones puppet set up on a new, clean > > > > Solaris 10 install. > > > > > > When I try to run: > > > > > > /opt/csw/bin/puppetd --verbose --no-daemonize --server > > > > puppet.mydomain.com > > > > > I may be wrong, but adding a --debug should give you more hints as to > > > what providers are being considered. This is what one of my Linux > > > vservers has to say: > > > debug: Puppet::Type::User::ProviderLdap: feature ldap is missing > > > debug: Puppet::Type::User::ProviderPw: file pw does not exist > > > debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not > > > exist > > > debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl > > > does not exist > > > > > Not at all pertinent to you, but that kind of message is what will help > > > you, I hope. > > > > > HTH, > > > Felix > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@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. > > -- Nigel Kersten Product Manager, Puppet Labs http://www.puppetlabs.com Twitter: @nigelkersten -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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: Puppet hangs
On Wed, Oct 27, 2010 at 1:34 AM, kit wrote: > Thanks Fredrik for submitting the bug report. > > Hopefully it will be looked at soon. I like puppet, > however when it keeps hanging it's next to unusable. > > Doesn't look like anything's happened over at puppet > yet though, and it's been two months already. > You mean this one? I feel the log does a decent job of capturing the current state, and that is a great bug report Fredrik. http://projects.puppetlabs.com/issues/4681 Is anyone on FreeBSD 8 *not* seeing this issue? kit, it would be helpful if you appended to the bug if you're seeing the same issue with a newer puppet version than 2.6.1r2 as well. > Regards > Erik > > On 1 Sep, 20:21, Fredrik Eriksson wrote: > > On 2010-09-01 13:44, Fredrik Eriksson wrote: > > > > > > > > > > > > > On 26 Aug, 16:22, Brice Figureau > > > wrote: > > >> On Thu, 2010-08-26 at 05:08 -0700, kit wrote: > > >>> This server is 7.2-RELEASE-p4 #0 > > > > >> So it has the fix I sent. > > > > >>> debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw > > >>> yaml; using pson > > >>> debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw > > >>> yaml; using pson > > >>> debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw > > >>> yaml; using pson > > > > >> This time it was able to ask for 3 files instead of freezing at the > 1st > > >> one. > > > > >>> (gdb) thread apply all > > >>> Please specify a command following the thread ID list > > >>> (gdb) bt full > > > > >> My bad, those two commands are in fact only one: > > > > >> thread apply all bt full > > > > >> But the issue is that I'm not sure we can find the issue. It is > > >> certainly some locking issues inside ruby that are invalid onFreeBSD. > > > > >> My advice if you really want to get rid of this issue is to rebuild > ruby > > >> without pthreads. > > > > >> You might also open a ticket on ruby 1.8 bug tracker (or on theFreeBSD > > >> ruby port). > > >> -- > > >> Brice Figureau > > >> Follow the latest Puppet Community evolutions onwww.planetpuppet.org! > > > > > Hello, > > > > > I think this is the same problem I have seen with my experiments with > > > puppet onfreebsd. Puppet randomly hangs after exec-statements. A few > > > examples of where it hangs (ruby18 --debug /usr/local/bin/puppet agent > > > --test --debug --trace) > > > > > /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1881: warning: > > > instance variable @virtual not initialized > > > /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1881: warning: > > > instance variable @virtual not initialized > > > /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1881: warning: > > > instance variable @virtual not initialized > > > debug: /Stage[main]/Webbase::Backup/Line[sudo_backup]/Exec[echo > > > 'backup ALL= ( root ) NOPASSWD: /usr/sbin/backup' >> '/usr/local/ > > > etc/sudoers']: Executing check '/usr/bin/grep -qFx 'backup ALL= > > > ( root ) NOPASSWD: /usr/sbin/backup' '/usr/local/etc/sudoers'' > > > debug: Executing '/usr/bin/grep -qFx 'backup ALL= ( root ) > > > NOPASSWD: /usr/sbin/backup' '/usr/local/etc/sudoers'' > > > removing /tmp/puppet20100901-36732-16mgs1p-0...done > > > > > > > > debug: /Stage[main]/Webbase::Apache/Exec[apache_purge]: Executing > > > check '/bin/test -e /usr/local/etc/apache/ssl.crt' > > > debug: Executing '/bin/test -e /usr/local/etc/apache/ssl.crt' > > > removing /tmp/puppet20100901-50535-1p6j13j-0...done > > > > > > > > /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1881: warning: > > > instance variable @virtual not initialized > > > debug: /Stage[main]/Webbase::Nas/Exec[/sbin/mount /proc]: Executing > > > check '/sbin/mount | /usr/bin/egrep ^procfs' > > > debug: Executing '/sbin/mount | /usr/bin/egrep ^procfs' > > > removing /tmp/puppet20100901-95974-1n5jg13-0...done > > > > > > > > I'm not really familliar with debugging tools (especially not for ruby > > > applications), but I've added a few debug-statements and started a > > > loop that runs puppet to see where it hangs. So far all I know is that > > > it hangs after Puppet::Util::SUIDManager.run_and_capture() but before > > > it returns from run(), I'll see if I can find exact statement where it > > > hangs... > > > > > Regards > > > -- > > > Fredrik Eriksson > > > > I created a bug report over at puppetlabs so that someone who has more > > knowledge and/or time could take a look at it: > http://projects.puppetlabs.com/issues/4681 > > > > Regards > > -- > > Fredrik Eriksson > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@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. > > -- Nigel Kersten Product Manager, Puppet Labs http://www.puppetlabs.com Twitter: @nigelkersten -- You receiv
[Puppet Users] Re: Solaris 10 Client "Default Provider for User" Woes Again
Sorry, answered my own question again. Turns out for some reason on Solaris if you use the --trace and/or --debug flags (not sure which) when starting your puppetd it will be "unable" to execute /usr/bin/ passwd. As soon as you take those off it works fine! /opt/csw/bin/puppetd --verbose --trace --debug --server cmsvl01.d1.peapod.com --no-daemonize On Oct 27, 7:55 am, nickt wrote: > Thanks, Felix! I figured it out. Turns out it was because when I > copied my shadow.so (from ruby-shadow lib build) I'd not changed > permissions on it to be world read/execute. So, anyone who's trying > the Solaris client, hope that helps! > > Now if only I can figure out how to "let" puppetd execute /usr/bin/ > passwd to set passwords for users I'll be all set! :) > > Let me ask a related question, what is the "best" way to add lines to / > etc/passwd and /etc/shadow with puppet? I'm setting things up to > initialize LDAP support on the same Solaris box and need to add lines > to allow login for specific LDAP groups. The only answer I've found > so far is to use a module like concat, but I've not gotten that to > work right so far. > > On Oct 27, 7:46 am, Felix Frank > wrote: > > > > > > > > > On 10/27/2010 02:36 PM, nickt wrote: > > > > Hopefully I'm just missing something simple, but I'm having trouble > > > getting just the absolute bare-bones puppet set up on a new, clean > > > Solaris 10 install. > > > > When I try to run: > > > > /opt/csw/bin/puppetd --verbose --no-daemonize --server > > > puppet.mydomain.com > > > I may be wrong, but adding a --debug should give you more hints as to > > what providers are being considered. This is what one of my Linux > > vservers has to say: > > debug: Puppet::Type::User::ProviderLdap: feature ldap is missing > > debug: Puppet::Type::User::ProviderPw: file pw does not exist > > debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not > > exist > > debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl > > does not exist > > > Not at all pertinent to you, but that kind of message is what will help > > you, I hope. > > > HTH, > > Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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: Solaris 10 Client "Default Provider for User" Woes Again
Thanks, Felix! I figured it out. Turns out it was because when I copied my shadow.so (from ruby-shadow lib build) I'd not changed permissions on it to be world read/execute. So, anyone who's trying the Solaris client, hope that helps! Now if only I can figure out how to "let" puppetd execute /usr/bin/ passwd to set passwords for users I'll be all set! :) Let me ask a related question, what is the "best" way to add lines to / etc/passwd and /etc/shadow with puppet? I'm setting things up to initialize LDAP support on the same Solaris box and need to add lines to allow login for specific LDAP groups. The only answer I've found so far is to use a module like concat, but I've not gotten that to work right so far. On Oct 27, 7:46 am, Felix Frank wrote: > On 10/27/2010 02:36 PM, nickt wrote: > > > Hopefully I'm just missing something simple, but I'm having trouble > > getting just the absolute bare-bones puppet set up on a new, clean > > Solaris 10 install. > > > When I try to run: > > > /opt/csw/bin/puppetd --verbose --no-daemonize --server > > puppet.mydomain.com > > I may be wrong, but adding a --debug should give you more hints as to > what providers are being considered. This is what one of my Linux > vservers has to say: > debug: Puppet::Type::User::ProviderLdap: feature ldap is missing > debug: Puppet::Type::User::ProviderPw: file pw does not exist > debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not > exist > debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl > does not exist > > Not at all pertinent to you, but that kind of message is what will help > you, I hope. > > HTH, > Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Solaris 10 Client "Default Provider for User" Woes Again
On 10/27/2010 02:36 PM, nickt wrote: > Hopefully I'm just missing something simple, but I'm having trouble > getting just the absolute bare-bones puppet set up on a new, clean > Solaris 10 install. > > When I try to run: > > /opt/csw/bin/puppetd --verbose --no-daemonize --server > puppet.mydomain.com I may be wrong, but adding a --debug should give you more hints as to what providers are being considered. This is what one of my Linux vservers has to say: debug: Puppet::Type::User::ProviderLdap: feature ldap is missing debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist Not at all pertinent to you, but that kind of message is what will help you, I hope. HTH, Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Solaris 10 Client "Default Provider for User" Woes Again
Hopefully I'm just missing something simple, but I'm having trouble getting just the absolute bare-bones puppet set up on a new, clean Solaris 10 install. When I try to run: /opt/csw/bin/puppetd --verbose --no-daemonize --server puppet.mydomain.com I just get: err: Could not create resources for managing Puppet's files and directories in sections [:main, :agent, :ssl]: Could not find a default provider for user err: Could not create resources for managing Puppet's files and directories in sections [:main, :ssl]: Could not find a default provider for user err: Could not create resources for managing Puppet's files and directories in sections [:main, :ssl]: Could not find a default provider for user warning: peer certificate won't be verified in this SSL session info: Caching certificate for ca err: Could not request certificate: Could not find a default provider for user I'd be happy to post whatever, but I'm watching the puppetmasterd on the other end and I'm not seeing anything come through so it makes me think there's some quirky Solaris nonsense on the client side and it's not even "talking" to the puppetmasterd. I started the puppetmasterd on the other end with: sudo puppetmasterd --no-daemonize --verbose --trace --debug Any ideas? I'm absolutely certain all the sbin stuff is in my path when I launch the puppetd on the client because before launching it I did a: export PATH=/usr/sfw/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/csw/bin:/ usr/ccs/bin:/usr/ucb -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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-zenoss plugin
> I'm testing the puppet-zenoss plugin: > http://github.com/mamba/puppet-zenoss > > I'm able to export and collect host properly. I however, can't get > the provider to work. I can't see much of the provider or type from > running puppetmaster in debug/verbose mode. Are there any tools to > test out a provider and/type? Also, if anyone has this module > working, please share your init, provider and type files... There is more up2date version of that module @ http://puppet-modules.git.puzzle.ch/?p=module-zenoss.git;a=summary ~pete -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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: Puppet hangs
Thanks Fredrik for submitting the bug report. Hopefully it will be looked at soon. I like puppet, however when it keeps hanging it's next to unusable. Doesn't look like anything's happened over at puppet yet though, and it's been two months already. Regards Erik On 1 Sep, 20:21, Fredrik Eriksson wrote: > On 2010-09-01 13:44, Fredrik Eriksson wrote: > > > > > > > On 26 Aug, 16:22, Brice Figureau > > wrote: > >> On Thu, 2010-08-26 at 05:08 -0700, kit wrote: > >>> This server is 7.2-RELEASE-p4 #0 > > >> So it has the fix I sent. > > >>> debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw > >>> yaml; using pson > >>> debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw > >>> yaml; using pson > >>> debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw > >>> yaml; using pson > > >> This time it was able to ask for 3 files instead of freezing at the 1st > >> one. > > >>> (gdb) thread apply all > >>> Please specify a command following the thread ID list > >>> (gdb) bt full > > >> My bad, those two commands are in fact only one: > > >> thread apply all bt full > > >> But the issue is that I'm not sure we can find the issue. It is > >> certainly some locking issues inside ruby that are invalid onFreeBSD. > > >> My advice if you really want to get rid of this issue is to rebuild ruby > >> without pthreads. > > >> You might also open a ticket on ruby 1.8 bug tracker (or on theFreeBSD > >> ruby port). > >> -- > >> Brice Figureau > >> Follow the latest Puppet Community evolutions onwww.planetpuppet.org! > > > Hello, > > > I think this is the same problem I have seen with my experiments with > > puppet onfreebsd. Puppet randomly hangs after exec-statements. A few > > examples of where it hangs (ruby18 --debug /usr/local/bin/puppet agent > > --test --debug --trace) > > > /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1881: warning: > > instance variable @virtual not initialized > > /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1881: warning: > > instance variable @virtual not initialized > > /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1881: warning: > > instance variable @virtual not initialized > > debug: /Stage[main]/Webbase::Backup/Line[sudo_backup]/Exec[echo > > 'backup ALL= ( root ) NOPASSWD: /usr/sbin/backup' >> '/usr/local/ > > etc/sudoers']: Executing check '/usr/bin/grep -qFx 'backup ALL= > > ( root ) NOPASSWD: /usr/sbin/backup' '/usr/local/etc/sudoers'' > > debug: Executing '/usr/bin/grep -qFx 'backup ALL= ( root ) > > NOPASSWD: /usr/sbin/backup' '/usr/local/etc/sudoers'' > > removing /tmp/puppet20100901-36732-16mgs1p-0...done > > > > > debug: /Stage[main]/Webbase::Apache/Exec[apache_purge]: Executing > > check '/bin/test -e /usr/local/etc/apache/ssl.crt' > > debug: Executing '/bin/test -e /usr/local/etc/apache/ssl.crt' > > removing /tmp/puppet20100901-50535-1p6j13j-0...done > > > > > /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1881: warning: > > instance variable @virtual not initialized > > debug: /Stage[main]/Webbase::Nas/Exec[/sbin/mount /proc]: Executing > > check '/sbin/mount | /usr/bin/egrep ^procfs' > > debug: Executing '/sbin/mount | /usr/bin/egrep ^procfs' > > removing /tmp/puppet20100901-95974-1n5jg13-0...done > > > > > I'm not really familliar with debugging tools (especially not for ruby > > applications), but I've added a few debug-statements and started a > > loop that runs puppet to see where it hangs. So far all I know is that > > it hangs after Puppet::Util::SUIDManager.run_and_capture() but before > > it returns from run(), I'll see if I can find exact statement where it > > hangs... > > > Regards > > -- > > Fredrik Eriksson > > I created a bug report over at puppetlabs so that someone who has more > knowledge and/or time could take a look at > it:http://projects.puppetlabs.com/issues/4681 > > Regards > -- > Fredrik Eriksson -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
