similar to: signing certs

Hello, I hope this has not been discussed very often previously, but I do not know how to search the archives, so I cannot prevent posting this. I installed puppet (and removed it andf installed it again, which gave me these error messages: when removing: puppetmaster: unknown service error: %preun(puppet-server-0.22.1-1.i386) scriptlet failed, exit status 1 when installing: puppet: unknown

Hi, I thought about changing the RPM package the guys of Redhat created, because I wanted an Init Script for SLES10 built-in. I started documenting the steps I took. Maybe it''s useful for someone else, although in German.. but the basic steps should be useable. My little Installating puppet Howto: http://wiki.njh.eu/Konfigurationsmanagement#Installation_3 The Init Script for SLES10:

hello, so today i started setting up a puppet server and client and am already having a problem (even before i started). the client tries to talk to the server for the first time to get a certificate. debug: Calling puppetca.getcert that is what it says as last line on the client. tcpdump says there are four packages transmitted between the hosts.. all coming from the client and going to the

I updated to 0.22.3-1 from the dlutter repo (CentOS 4.4) and I''m still having trouble adding new nodes as others saw from the previous version, though I believe the error is different now. The procedure I used was: <client> /etc/init.d/puppet once -v <server> /usr/sbin/puppetca --sign nodename <client> /etc/init.d/puppet once -v This used to work for new nodes, now I

Hi, I have been getting the below error for sometime now. Both master and client are using version 0.24.8. Output from /var/log/messages err: Could not call puppetmaster.getconfig: #<#<Class:0xb7b50a9c>: execution expired> err: Could not retrieve catalog: execution expired P.S- all of this was working absolutely fine and suddenly has started to misbehave. Regards, -- You

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

Hello, I try to install puppet on freebsd 6.X. All is well but i cannot get the certificte to install and be recognized. I run .19.3. I run the puppetd --test --waitforcert 60 then sign and then i got: err: No certificate; running with reduced functionality. info: Creating a new SSL key at /usr/local/.aqadmin/puppet/conf/ssl/private_keys/xxxxxxxxxxxxxx.pem info: Creating a new certificate

I recently had a working puppet server serving around 4-5 clients. One of the clients needed to be re-built and now only that client cannot connect. puppetca --clean hostname did not work So here is what I did on both the server/client I removed /var/lib/puppet/* Then I restarted the server via puppetmasterd --mkusers --verbose I then connect in via the client with /usr/bin/ruby

The Asterisk Development Team would like to announce security release Asterisk 21.0.1. The release artifacts are available for immediate download at https://github.com/asterisk/asterisk/releases/tag/21.0.1 and https://downloads.asterisk.org/pub/telephony/asterisk The following security advisories were resolved in this release: - [Path traversal via AMI GetConfig allows access to outside

The Asterisk Development Team would like to announce security release Asterisk 21.0.1. The release artifacts are available for immediate download at https://github.com/asterisk/asterisk/releases/tag/21.0.1 and https://downloads.asterisk.org/pub/telephony/asterisk The following security advisories were resolved in this release: - [Path traversal via AMI GetConfig allows access to outside

Hi all, My current conf splits 188 clients execution in one hour, and puppet runs as a cron job. My server (2cpu 2 GB RAM) runs with mongrel (with 8 puppetmasterd) and this conf works fine. We''d like puppet to run clients all at same time (force a change, i.e.), so we''re testing several things. (Previous conf do not support massive execution). First and most important, is

Hello, I just installed the latest version of puppet and puppetmaster on an up to date RHEL4 system. If I turn on ''storeconfigs'' on the puppetmaster server I get the following error: debug: Calling puppetmaster.getconfigerr: Could not retrieve configuration: Uncaught exception No such file to load -- sqlite3 in method puppetmaster.getconfig I have gems and rails installed

I''m using 0.24 with Webrick (in the process of migrating to 0.25 / passenger). Occasionally, the puppetmasterd becomes unavailable, and we see error messages along the lines of: Could not call puppetmaster.getconfig: #<Errno::ECONNRESET: Connection reset by peer> I believe the puppetmasterd does not completely die, so it is still in the process list. I''m wondering what

I see in the changelog that: You now must specify an environment and you are required to specify the valid environments for your site. (#911) Does this mean that the puppetmaster has to be updated before clients work correctly? I ask because I''m testing out a client upgrade to 0.24.0 (server is still 0.23.2) and this is what I''m seeing: [~]% sudo /foo/bin/puppetd

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I am rather new to puppet and set up a puppet server and some clients. during "puppetd --server=puppetmaster.example.com --verbose" I get the following error which says nothing to me: err: Could not retrieve configuration: Uncaught exception compile error (erb):241: syntax error, unexpected tIDENTIFIER, expecting $end

Can someone who uses SuSe Linux (I currently use 9.3) please tell me what I need toto to avoid the message configure: error: --with-x=yes (default) and X11 headers/libs are not available without setting --with-x=no currently my /usr/lib/X11 directory looks like this ls /usr/lib/X11 app-defaults fvwm2 nls twm XErrorDB Xmodmap Cards getconfig Options wmmount

Hello all, I have what is certainly a stupid problem on my part. I have setup puppet in a test environment and it''s been working wonderfully. I am now in the process of moving this to our production systems and I have rebuilt our puppetmaster completely from scratch using the same modules/manifests, etc. from my test system. Unfortunately I am running into an issue with what I

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

Hi all, I''ve followed http://reductivelabs.com/trac/puppet/wiki/UsingMongrel for configuring my puppet with mongrel. Al seems to work fine, except that, after a reinstall of 40 nodes atone time, I got many kind of errors like: ------------------------------------------------------------------------- err: Could not request certificate: Certificate retrieval failed: .tmp file already

flight 18243 qemu-upstream-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18243/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop fail never pass test-amd64-i386-xend-qemuu-winxpsp3 16 leak-check/check fail never pass test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 13