similar to: Problem with storeconfigs

Displaying 20 results from an estimated 6000 matches similar to: "Problem with storeconfigs"

2009 Jul 21
0
new puppet config - fileserver issue
Hi I am a newbie to puppet. I have tried an initial config serving a simple file & dir from the puppetmaster, but the client will not mount. What obvious mistake am I making, I wonder? puppetmaster is a DNS alias for osiris3. Config files: [root@osiris3 puppet]# cat fileserver.conf [config] path /data/puppet/manifests/files allow *.pinnacle.co.uk [root@osiris3 puppet]# cat puppet.conf
2012 Aug 23
1
Puppet Agent VS User
Hello, Running into a problem when wanting to daemon-ize the agent. It doesnt seems to do anything: - cannot find any daemon process with (ps aux | grep puppet) - the config is not updated after editing some params on the master - /var/log/puppet stay empty... while, when logged as root, it is working without issue with $puppet agent --test. ##Conf Ubuntu 12.04 Puppet 2.7.11 ## Daemon is
2012 Jun 26
5
Next Problem: Puppet 2.7 + Passenger won't connect
OK. What did I booger up this time ? agent.myexample.org and puppetmaster.myexample.org are the same server. ---------------------------------------------------------------------------- # puppetd --no-daemonize --onetime --debug --noop debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not
2011 Jun 29
0
Setting up puppetmaster-passenger on Debian
I am at the end of my rope here so I pray to the gods that puppet-users can help. Using Debian apt-get install puppetmaster-passenger you get a fairly complete puppetmaster setup. I have the Pro Puppet book next to me and following Chapter 4 on setting up Puppet with Passenger I can see that apt has already done most of the ground work. For example the config.ru script is owned by puppet,
2012 Aug 29
4
troubleshooting resource collection
Hi, I''m new to Puppet. And I''m trying out an ssh module: https://github.com/saz/puppet-ssh. It collects ssh keys like this: class ssh::knownhosts { Sshkey <<| |>> { ensure => present, } notify{"knownhosts class: $fqdn $hostname $ipaddress ":} } I can see it echoes the host key of the host the puppet agent runs on. But the
2009 Jun 13
0
problems with puppetd on some of my solaris machines
I am having troubles with getting puppetd running on some of my Solaris10 update 7 (05/2009) boxes. I use Jumpstart to build my servers, so the installation is repeatable, consistent, and automated, so it is especially confusing that some boxes work, and others don''t. I can ssh into both of these machines, so the host certs should be OK. As part of my installation, I download the
2013 Oct 08
4
'puppet storeconfigs export' killed
Hi, I currently have a MySQL database containing all Puppet storeconfigs. My intention is to migrate to PuppetDB on a PostgreSQL server, so the first step is to use the ''storeconfigs'' face to export all the DB to a file PuppetDB can later consume. But the ''puppet storeconfigs export'' command always ends up being killed, I suspect due to some sort of OOM
2010 Dec 06
7
error running puppetrun
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
2012 Aug 09
4
Error 400 on Server: Another local or imported resource exists with the type and title Sshkey
I am attempting to remove an old ssh host key from /etc/ssh/ssh_known_hosts. In my manifest, I have the following: # add keys @@sshkey { $hostname: ensure => present, type => "rsa", key => $sshrsakey, } # remove key @@sshkey { "foohost": ensure => absent, type => "rsa", } Sshkey <<| |>> But I get this error on
2009 Oct 21
2
Bug #2617(?) in Puppet 0.25.1rc2
When I use the latest puppet 0.25.1 I got the same problem. This is what I do: 0. Install the Ubuntu 8.04 server with ssh, ruby, rdoc, libopenssl- ruby and git-core (which gets removed after clone). 1. Install the latest puppet from git repositories on both machines using git clone «git clone git://github.com/reductivelabs/puppet» and «git clone git://github.com/reductivelabs/facter» 2. Install it
2010 Aug 02
1
wrong facts going into storeconfigs, 0.25+2.6
I''m re-posting this because I''m not sure that it got through the first time. If someone could at least echo back that this is reaching the list, I''d appreciate it. (I''m new to the list.) Sometimes (with variable frequency) storeconfigs stores the wrong data in the fact_values table. This has the end result that exported resources, when collected, have
2002 Aug 24
1
Virtual servers - multiple sambas
New to this list. Running samba 2.2.4 set up as a PDC. We've recently added another department to our office network. Ideally, I don't want either department to see each others shares - just to be aware of the shares in their own workgroups. The documentation says that you can set up virtual servers using the "netbios aliases" and the "%L" options in the
2011 Dec 15
0
Using stored configs brakes on client update
Hi, We''re using puppet from longer time, but now want to switch into stored configs. When I ran locally puppet on puppetmaster server, ie: puppet /var/lib/puppet/manifests/nodes.pp --debug it works smooth. When running client with debug I get message: root@puppet-client:~# puppet agent -v --fqdn=puppet-client.ig.local -- waitforcert 60 --onetime --no-daemonize --logdest console --test
2007 Apr 17
7
Still having factsync trouble ...
Some time ago i sent to the list a problem i was having with facts on fedora core 6 and wasn''t able to find a solution at that time, but with the release of RHEL5 and CentOS 5 based on fc6 i have hit the problem again. i have written several facts to collect information about a clients network and i am also using the vmware fact from the wiki. i have separated my original fact into
2013 Oct 09
6
Could not retrieve catalog from remote server: Error 400 on SERVER: cannot generate tempfile `/var/lib/puppet/yaml/facts/vagrant1.localdomain.yaml20131009-16545-8oie5i-9'
Hi, i''m a newbie about Puppet( 1 month ~) i got error on generate temp file, i''ll explain my situation: -i have a puppetmaster(version: 3.3.0),executed on root and a puppet agent(version 2.7) provisioning by vagrant,executed on root -my site.pp, where webserv is a parametrized class, and typews is a parameter to choice nginx or lamp module, -i have my Enc node with path
2010 Jun 09
4
Could not retrieve catalog from remote server: certificate verify failed
Hi guys, I''m trying to setup my first puppet installation and I''m running into problems. I''ve got the puppetmaster running on a fresh install of Centos 5.4. The puppet client is also on another Centos 5.4 server. Once I''ve signed the client certificate on the puppetmaster, the client seems to break. See below for the debug output from the client. Any clue as
2010 Aug 18
0
info: Retrieving plugin, err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate': undefined method `closed?' for nil:NilClass
I''m not really sure the problem is a Plugin problem!! Note than a puppet client was installed, i change the setting of ip/hosname and try to re inscription the node to puppetmaster. I would like to understand what happen. The errors/warnings messages are not very easy to understand and sometime i''m lost. thank you for you advice. Eric Puppet version: 0.25.4-2ubuntu6
2006 Aug 31
4
crashes
I just started playing with puppet. Unfortunately, it keeps crashing in a variety of places. I don''t have much experience with Ruby yet, so any tips in tracking down these problems would be appreciated. I''m using the Debian package 0.18.4-1. Here''s the output of a couple runs: www01:/home/cwarden# puppetd --verbose --onetime info: Caching configuration at
2009 Sep 09
0
puppet 0.25 client on xen / EC2
Trying to get an EC2 AMI running puppet 0.25 and i''m hitting a problem. After installing the rpms and starting puppet it was just quitting with only: puppetd[3313]: Reopening log files In the log file. When running it with the following I get some more output. -bash-3.1# puppetd -D -d -t --trace debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug:
2013 Aug 07
1
puppet-3.2.2 runs fine - but doesn't work. 2.7.22 works fine.
Hi, I''ve setup a puppet-3.2.2 master, on a new server, and I''ve updated 1 server (agent) to 3.2.2 as well - and when I run that against the new master (where I''ve copied my /etc/puppet folder over incl. modules etc.), the client removes all facts etc. and does absolutely nothing. I''ve tried to change the manifest - but nothing is done anyways. I''m