similar to: Not using expired node for targethost from cache; expired

I also made the changes below in the puppet.conf file to tell puppet where to look for the the modules and manifests. I then restart the puppet master then ran puppet command to apply changes to a puppet client it did not find anything to change just got these three lines "info: Caching catalog for pdlnx-adpt03.kareoprod.ent, info: Applying configuration version

Hi, I''ve got some problems with setting up environments. On the master: [main] [...] manifestdir = /etc/puppet/manifests modulepath = /etc/puppet/modules [...] environments = production,staging [production] manifestdir = /etc/puppet/manifests modulepath = /etc/puppet/modules [staging] manifestdir = /opt/puppet-staging/manifests modulepath = /opt/puppet-staging/modules [puppetmasterd]

Hi, I am trying to install puppet enterprise on a fresh Debian Squeeze machine, but I am getting an error midway with no information on what went wrong. How do I troubleshoot or look for more debugging information? This is what the screen output for installation is: thanks for your help in advance! Setting up pe-rubygem-fog (1.0.0e-1puppet2) ... Setting up pe-cloud-provisioner (1.0.1-puppet1)

Hi, Software in use: OpenSSH-Version: 4.5p1 OpenSSL-Version: 0.98d zlib-Version: 1.2.3 OS-Platform: AIX 5.3 ML4 Problem: when issuing following command on an AIX host: $ ssh -2 -n -f -x -L6666:localhost:6666 -o BatchMode=yes targethost sleep 500000 $ exit the shell is waiting for the finish of issued command (sleep). The expected behaviour of above command should be, that the shell would

Hi, I wonder why the puppet agent on the server itself will not run: ---snip--- # puppet agent --test Error: Could not run Puppet configuration client: Puppet::Node does not respond to from_s; can not intern instances from text/plain Error: Could not run: can''t convert Puppet::Util::Log into Integer ---pins--- whereas the client on a test box tells me: ---snip--- # puppet agent --test

Hi all, We have a number of server on which user "admin" exists, and that have manual modifications to its bashrc and bash_profile files. What I''d like to do is to host its user password from puppet master, but not the bash-files. I tries this (we''re running Puppet Enterprise 2): -- code start -- pe_accounts::user { ''admin'': password =>

I know this comes up periodically, and I''ve read through the wiki (including the Best Practices page) & list archives, but still can''t quite get my head around it. I see lots of references to /modules and $MODULE_PATH, but am not sure what these refer to. Here''s a basic setup I have. Let me know if this looks correct: /etc/puppet/ |-- autosign.conf |--

Hello, I am installing Puppet Enterprise agent (puppet-enterprise-1.2.1- solaris-10-sparc) on a Solaris 10 64bit SPARC system. When I view the logs for the agent I see: puppet-agent[14680]: [ID 702911 daemon.error] Could not run Puppet configuration client: Could not retrieve local facts: private method `split'' called for nil:NilClass The client successfully initiates a cert exchange

Hello, when I do: /opt/rsync/bin/rsync /etc/hosts targethost::bkp/ I get: cannot create .hosts.b0WX1x : File exists I check the targethost and I get empty file .hosts.b0WX1x When trying with other targethost-s it works, but on this one it doesn't. On the other targethosts I have exactly the same LinuX distribution, permissions and users than on the problem targethost. I have exactly the

My company uses a certain product which forces me to use a jumphost / ssh proxy. When connecting to a server I have to type "ssh myuser at technicaluser@targethost at jumphost" everytime. I tried to simplify this by editing my ssh_config and putting this into the file: Host targethost ProxyJump technicaluser at jumphost These lines are recognized but don't work like intended

**Hi Darren, thanks for the information. I've applied the mentioned patch for openssh 4.5p1 the patch itself contains a minor typo (closing bracket) for line 1455 (I've attached a corrected version of your patch to bug http://bugzilla.mindrot.org/show_bug.cgi?id=52). The patch itself resolves the issue of hang-on-exit on AIX when executing a 'ssh -f ...' thanks for your great

I have these three modules with the following structure: |-- modules | |-- create_resources | | |-- LICENSE | | |-- Modulefile | | |-- README | | |-- lib | | | `-- puppet | | | `-- parser | | | `-- functions | | | `-- create_resources.rb | | |-- spec | | | |-- spec.opts | | | |-- spec_helper.rb | | | `-- unit

When I deploy a module I wrote with couple of custom facts, those facts do not show up in factor. But when I point FACTORLIB to the directory with those factor, they work just fine. I am running a masterless puppet version 2.7.22 and factor 1.7.1 The module structure looks like so: -license ---lib -----facter -------license.rb -------hardware_serial.rb -----puppet Any idea what is causing

Hi, I''ve been trying to pass the http_proxy_host option to puppet but it''s not taking. I have tried the following: sudo puppet apply --debug --verbose --http_proxy_host http://user:pass@fqdn.com.au --modulepath ''/tmp/vagrant-puppet/modules-0'' /tmp/vagrant-puppet/manifests/default.pp sudo puppet apply --debug --verbose

Hi! as I just noted, after scp the connection does not shut down properly. When I do a "scp file targethost:path", on targethost a "sshd" process is left running. I do use --with-default-path="/usr/local/openssh/bin:/usr/bin:/usr/local/bin" to assure, that the corrensponding openssh-scp is used. It also seems, that normal sessions are not always closed properly.

Warning - Puppet newby here. I am trying to set up a puppetmaster 3.3.2 and have run into a snag right out of the box. I want to add a new directory to modulepath= in /etc/puppet/puppet.conf So I added the following line in the [main] header modulepath = /etc/puppet/modules:/opt/our-repo/puppetmaster/modules And populated new new directory with modules I have written. I then run puppet

Hello everyone... I have configured the puppetmaster to use Apache/Passenger. However, executing a configprint (puppet --configprint all) from either the puppetmaster or an agent shows servertype = Webbrick Has anyone else seen this? What do I need to do to correct this? Thanks! JA -- You received this message because you are subscribed to the Google Groups "Puppet Users" group.

Hi All I have a requirement to consume a 3rd party web service from my Rails application. I am doing this in my action require ''soap/wsdlDriver'' factory = SOAP::WSDLDriverFactory.new(TRANSIDIOM_WSDL_URL) soap = factory.create_rpc_driver soap.wiredump_file_base="#{RAILS_ROOT}/log/transidiom.log" param = %(<Request

# cat /etc/redhat-release CentOS release 6.4 (Final) # puppet --version 3.2.3 # rpm -q puppetdb puppetdb-1.3.2-1.el6.noarch I am now receiving "Not collecting exported resources without storeconfigs" for my opsview module. It was working fine on puppet 2.7 with Activerecord/MySQL. I am still new to puppetdb so maybe I am missing something. This is from puppet.conf: storeconfigs

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