similar to: custom package provider troubles

Started the discussion in puppet users mailing list based on recommendation from luke. This discussion is to a follow up regarding bug#1955 "Could not find server puppet" - installation/configuration error". jamtur01''s last recommendation: Rather than renaming things try the certname option (see http://reductivelabs.com/trac/puppet/wiki/ConfigurationReference). But

Seems that blastwave is all about pkgutil now. Are there any plans to support this? Best, Adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to

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,

In my puppet client I have puppet.conf defined puppet server as mypuppet server = mypuppet.example.net Not sure why the puppet client puppet-test is still sending these noises to the syslog Jun 10 13:36:23 puppet-test puppetd[10863]: [ID 702911 daemon.error] Could not find server : getaddrinfo: node name or service name not known Jun 10 13:36:23 puppet-test puppetd[10863]: [ID 702911

Not that I''m much of a Solaris guy, and definitely not a Solaris 10 guy, but since nobody else had posted anything yet: http://reductivelabs.com/trac/puppet/wiki/PuppetSolaris#Solaris10 The good news is that it appears to be a completely hands-off puppetd installation. Just sign the client key afterwards on the puppetmaster and you''re set. The bad news is that it''s

There''s a problem installing puppet on Solaris 10 -- in this situation, we aren''t really doing anything with puppet there. The version we''re using is: ruby 1.8.7 (2011-02-18 patchlevel 334) [i386-solaris2.9] Here''s the first error: # gem update puppet > > Updating installed gems > > Updating puppet > > Building native extensions. This

Hi all, I''m doing a new install of my puppet server and I''m doing it like: 1.-) adding epel repo: http://fedoraproject.org/wiki/EPEL/FAQ#howtouse 2.-) yum -y install puppet-server 3.-) rm -rf /etc/puppet 4.-) copy my old puppet conf (from puppet-0.24.5 to 0.24.6) mv /etc/puppet.old /etc/puppet 5.-) start puppetmaster: [gridinstall etc]# /etc/init.d/puppetmaster start

I''m using puppet 0.24.7-4. I have a situation where I have some very long running puppet runs in order to do upgrades (removing applications from load balancers gracefully, et cetera). My puppet runs triggered via puppetrun are finishing successfully: Jun 8 20:31:29 puppetd[10178]: Finished catalog run in 345.18 seconds Puppetrun itself is timing out: err: Connection timeout calling

> I''ve built a puppet solaris - package which is distributed via jumpstart > at installation time of a solaris 10 machine. > It''s postinstallation registers the puppetd into smf and starts puppetd > afterwards. Puppetd connects to puppetmasterd, gets ist certificate signed > (autosig on) and the configuration stuff. > Now the interesting part: a new solaris zone

Can anyone point me to a procedure to install only the Puppet Agent on a Solaris 10 system for which I do not have root access? Everything I have found online involves using pkgadd and/or pkgutil, both of which require root privileges to run. --Ken -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and

I have the following set up: schedule {nightly: period => daily, range => "18 - 23", repeat => 1 } define deadlypkg { tag("package") $pkgrepo="/staging/PRODUCTION/deadly" package{"$name": source => "$pkgrepo/$name.pkg", ensure => latest, adminfile

Nigel Kersten and I had previously worked on a plist provider spec for Mac OS X. Attached is a PDF of the current state. I would appreciate any input and criticisms. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To

The original blastwave.rb would store "no pkg-get in /usr/sbin /usr/ bin" into @@pkgget if pkg-get is not found in the PATH. The patch below modifies blastwave.rb to store the first matching binary in the user''s PATH, or if not found, check the default location (puppetd''s PATH may not be sane) and if still not present and executable, correctly store as nil.

I am trying to get puppet to manage my LDAP users but I don''t appear to be having much success. What I have in puppet.conf is this [puppetmasterd] ldapserver=ldap.myorg.company.com ldapbase=dc=myorg,dc=org ldapuser=cn=admin,dc=myorg,dc=org ldappassword=mysecret ldapparentattr=dc=myorg,dc=org I added the ldapparentattr in desperation and doubt if

I''m still tinkering, moving over code from CFE to Puppet in a test environment. One item I did with CfE was manage services. If something wasn''t running, it was restarted. Puppet''s service integration makes this easy. The flip side, is how do you guarantee Puppet''s running? I pulled some tricks with CfE to ensure it was always running. I made CfE a direct

Hi guys, Which puppet operations should i try to avoid? I know that probably the most time consuming operations are file copies, but, is there something from the code point of view that I should try to avoid? I''ve seen for example, that on Solaris, puppet will execute pkginfo quite alot of times - sometimes with a package name, some other times without (pkginfo -l), thats extremely time

Hi folks I know that has, to some degree, been run over the past year in different ways, but, I may have yet another instance of an issue on this. The puppetmaster system and the puppet system are both running 0.24.7-r1, on a gentoo system. Other puppet systems are running 0.24.4. The puppet system (not the puppetmaster system) that is running 0.24.7-r1 is showing multiple close_wait

$ puppet --help /opt/csw/lib/ruby/gems/1.8/gems/puppet-0.20.1/bin/puppet:103: undefined method `feature'' for Puppet:Module (NoMethodError) from /opt/csw/lib/ruby/1.8/getoptlong.rb:460:in `each'' from /opt/csw/lib/ruby/1.8/getoptlong.rb:457:in `each'' from /opt/csw/lib/ruby/gems/1.8/gems/puppet-0.20.1/bin/puppet:97 from /opt/csw/bin/puppet:18

Has the component/type defaults syntax changed for 0.22.x? I have a component: <snip> define remotefile($owner=root, $group=root, $mode, $source, $backup=false, $recurse=false, $groupname="default") { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup,

I have this config: # BL00070 - Disable NFS service {["nfs","nfslock","netfs","portmap"]: ensure => stopped, enable => false, } user {"rpc": ensure => absent, provider => "useradd" } user {"rpcuser": ensure => absent, provider => "useradd" } file