similar to: Re: [puppet] #779: access to inherited variables from within a template

Displaying 20 results from an estimated 1000 matches similar to: "Re: [puppet] #779: access to inherited variables from within a template"

2011 Jun 27
12
Ruby script to download files without 'puppet agent'
We have often the Problem that some files need to be checked for updates faster than the cycle of the puppet agent. I try to solve this with a script which tries to download the files directly from the fileserver of the puppetmaster. So far i couldn''t get it to work. I don''t know if i got the URL right, i did not find any examples on the REST API documentation for the
2010 Jun 28
4
Error 400 : could not find template
Hello, I did make a stupid fault: not commiting changes to version control :-( After the installation of puppet-dashboard, I added a recipe to add report = true to puppet config files on clients. Now all Puppet clients don''t update because of an error... What can be the various reasons for an ''400'' error?? I guess it has something to do with rights. Jun 28 09:52:36 pm
2013 Feb 01
11
Change the location of puppet.conf
Hey guys, Does anyone know how to change the location of puppet.conf? In my situation, I don''t want to store it under /etc/puppet/puppet.conf or ~/.puppet/puppet.conf -- I''d like to store it under /opt/puppet/puppet.conf in this example. Is there a method without having to symlink, perhaps with an environment variable like PUPPET_CONF=.... ? Thanks for your time, Jason --
2007 Jan 01
5
File configuration difficulty
Hi, I''ve been using puppet to manage a small Linux network fairly successfully for a while now - thanks. I''ve hit a spot of bother in managing some files, though. There are a number of folders in /usr/local that I want to manage efficiently using puppet - for example /usr/local/share/templates. I want to copy the contents of a number of source folders on the puppet fileserver
2008 May 27
12
Puppetting the puppetmaster problems
Hi, installing puppet at my first site was quite easy (not w/o problems, but still). At the second site, I''ve run into something more serious. First things first - I install puppetmaster on existing server, used to keep LDAP db (my puppetmaster DOES NOT use LDAP, it just tries to coexist on the same machine). The thing is, I need to puppet this baby, so I''m running into a
2000 Mar 11
3
TEST RELEASE: openssh-1.2.3pre1
I have just uploaded a test release of 1.2.3. It includes numerous fixes from the OpenBSD team and should fix the stupid configure bugs of 1.2.2p1. http://violet.ibs.com.au/openssh/files/test/ A detailed ChangeLog is in the directory. Please report successes and failures. Regards, Damien Miller -- | "Bombay is 250ms from New York in the new world order" - Alan Cox | Damien Miller -
2000 Mar 23
1
Found a bug in the OpsnSSH configuration script
[I'm cc:ing openssl-users at openssl.org, because questions about this are getting there over and over...] There's a problem that several people who installed OpenSSL to be able to uyse OpenSSH have faced: Could not find working SSLeay / OpenSSL libraries, please install I don't recall how SSLeay was installed, but for OpenSSL, there's a glitch in the way it tries to find
2011 Mar 31
5
puppetca and /etc/puppet/ssl
All, I have --confdir=/etc/puppet/common in my /etc/init.d/puppetmaster and /etc/init.d/puppet files, vardir set to /var/lib/puppet in /etc/puppet/common/puppet.conf, and yet, every time I run puppetca it creates /etc/puppet/ssl. Anyone know why? Doug. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email
2001 Feb 16
7
OpenSSH 2.5.0p1
Known issues: 1) Linux 'sleep 20' -- Unfixable before 2.5.0 (known work around) 2) HP/UX signal issue -- Patched and HP/UX 11 works in v2 3) SCO 2/ Native Compiler -- Unfixable before 2.5.0 (known work around) 4) NeXTStep -- Resynced, MAX_GROUPS vs NGROUPS unresolved (not major) 5) DG/UX regcomp/regexec -- Fixed. 6) Cray signal issues -- ??? 7) Solaris '$PATH' issue -- ??
2001 Feb 22
11
Lets try this push again.. 2.5.1p2 bugs left.
Things that are still outstanding: 1) Solaris/Redhat/HPUX session.c patch. I've not seen a ya or na on Kevin's pam patch from the Solaris group. 2) Odd Redhat/Debian scp/ssh issues. .. I'm baffled, and I can't replicate the bug. Nor have I seen anything remotely like it reported. 3) SCO.. Is it happy yet for compiling? =) Completed: 1) mdoc2man.pl .. Commited into
2007 Jul 03
7
CA migration
Anyone ever migrated the puppetca to a different host? What are the steps that are involved?
2007 Nov 28
7
puppetrun failing: "connect'': tlsv1 alert unknown ca"
I''m trying to get puppetrun to work, without luck so far. I have my puppetmaster and clients working fine with the clients polling the master. Now I want to be able to force an update. Using version 0.23.2 On the client I set listen=true and created the namespaceauth.conf file. Restarted puppetd and it appears fine. On the master I run puppetrun as root and get root@plane:/etc/puppet#
2007 Oct 09
9
puppetca is unable to sign certificate
Hi - I a ran puppetd -vt against a brand newly build host (which is what I normally do for a new host) and got the usual message: err: No certificate; running with reduced functionality. info: Creating a new certificate request for sega-dev-1. info: Requesting certificate On the puppetmaster, I then list the waiting host with: puppetca --list then sign the key. In this case, I decided that the
2013 Oct 30
4
Warning: Local environment: "42A" doesn't match server specified node environment "production", switching agent to "production"
Hi, When I run puppet agent --test --environment 42A, I have the following warning : Warning: Local environment: "42A" doesn''t match server specified node environment "production", switching agent to "production". ... The puppet manifest for the environment "42A" isn''t applied. The puppet version is 3.3.1-1puppetlabs1 on agent and
2010 Aug 19
7
External CA: Could not run: Could not retrieve certificate for puppetsrv and not running on a valid certificate authority
Hi Experts, I''m trying to generate my own certificates (all of them, including certs for CA, server and client) for puppet to use. and I''m getting "Could not run: Could not retrieve certificate for puppetsrv and not running on a valid certificate authority" Just wondering what the problem could be? What I did is: 1. generate a self signed CA cert, and save the
2000 Mar 12
2
Trouble building 1.2.2p1 on Solaris 2.7
I installed OpenSSL 0.9.5 in the default location (/usr/local/ssl) on my Solaris 2.7 box, and then tried to install OpenSSH 1.2.2p1. Configure (with no arguments) complains that it can't find working OpenSSL libraries. The last few lines of config.log show a whole bunch of attempts to compile the test code, all failing of course. My /usr/local/ssl DOES have an include/openssl directory
2007 Feb 22
33
Scaling Puppet 0.22.1 to hunderdes of nodes.
Hi, My environment is composed of ~250 workstations hitting a single puppetmaster server, which has been working fairly well up until now. The most recent change has been a migration of a lot of remote file copy objects which were previously handled with cfengine. client side puppetd calls to the puppetmaster.getconfig method are taking unreasonably long, on the order of 2-3 minutes. It
2010 Apr 05
5
Problem syncing custom fact
I am trying to get a custom fact to sync. The fact is in a module. It will sync if I run puppet with "--pluginsync" but not otherwise. I have "pluginsync=true" in my puppet.conf. Shouldn''t the command line option and puppet.conf option have the same results? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group.
2010 Aug 10
4
Certificat Outlook 2003
Hi, next problem with outlook 2003 On the IMAP Server (dovecot.x86_64 1.0.7-7.el5) I created a certificate with "mkcert_dovecot.sh". Some entries as be written to "/etc/pki/dovecot/dovecot-openssl.cnf". plaintext paswords are disables. IMAP Serverport: 993 Server needs SSL Now the outlook 2003 clients meens "the server uses a security certificate, which could not be
2007 Dec 03
3
certificate issue with Branch Testing
Hello All, I''m using the "Branch Testing" approach documented at https://reductivelabs.com/trac/puppet/wiki/BranchTesting and am seeing an issue with certificates. On all clients, I can run puppetd --masterport=8141 successfully but see the following error when I run against the default (8140) port: err: Could not retrieve configuration: Certificates were not trusted: