similar to: "Mounts without paths are not usable"

Hello, I try config puppet with foreman frontend. Into puppetmasterd I create modules "test" and create init.pp: # Create "/tmp/testfile" if it doesn''t exist. class test_class { file { "/tmp/testfile": ensure => present, mode => 644, owner => root, group => root } } Configure nodes in site.pp and import

Bunch of weird stuff after a power failure here this morning. One of my virtual servers, managed through puppet, seems to not be talking to the master any more. And I can''t get it to reconnect. I did puppetca --clean on the master, cleaned off certs on the client, started puppetd manually on the client, and got this: sh-3.2# rm -rf /var/lib/puppet/ssl/ sh-3.2# puppetd --server

Here is my class class puppetconf { file { "/etc/puppet/puppetd.conf": mode => 644, owner => root, group => root, source => "puppet://puppet/cci/etc/puppet/puppetd.conf", notify => exec[puppet_restart] } file { "/etc/init.d/puppet": mode => 755, owner => root, group => root,

Hi, I''m trying to use Puppet ability to export and collect resources using PuppetDB. My PuppetDB and Puppet Master are running on the same host and I used the PuppetDB puppet module to install PuppetDB and configure the Puppet master. Each time the puppet agent runs on a client, the facts and the catalog are being pushed in PuppetDB and I can query the PuppetDB server to get

All- Poking around in the bug database it looks like storeconfigs is being actively worked on. I am using 2.7.6 on my master as well as all the clients. I have clients boot , start puppet and get a signed cert via auto signing. The nagios module (and currently the only thing puppet does) complains a lot during compile time about not having storeconfigs enabled, which is not the case in my

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

Just upgraded to 2.7.6 and the yumrepo type does not write out our yum configs correctly, anyone experiencing this? Documentation hasn''t changed from what I can tell for this type. # facter -version 1.6.2 # puppetd --version 2.7.6 # facter architecture x86_64 # facter operatingsystem Fedora # facter operatingsystemrelease 14 ==== My manifest ==== yumrepo {

I''ve ran into a strange issue today while using my development environment I was receiving some errors about modules that shouldn''t have been used. After looking it looks like my agent (or master) isn''t respecting the environment I specify and is actually using the main (master) environment. This used to work and I haven''t had any changes beyond a upgrade ..

I''m playing around with foreman for the moment. I can''t seem to figure out how to make the dashboard look like in this screenshot http://theforeman.org/wiki/foreman/Screenshots#Dashboard In order for those statistics to work what should be done? I have activated the rrdgraph reports in puppetd, uncommented the line ":rrd_report_url: report/" in config/settings.yaml

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,

Greetings- Is it possible to mount multiple block devices (or network devices over NFS/CIFS) such that the contents of the mounts appear in one location? For example, lets say I have these shares available: \\server1\volume1\ \\server1\volume2\ \\server1\volume3\ All three contain a directory called data, with different subdirectories. Typically, these would be mounted like so: mount

puppet maser conf: [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl [master] classfile = $vardir/classes.txt localconfig = $vardir/localconfig user = root group = root fileserverconfig = /etc/puppet/fileserver.conf reportdir = /home/logs/puppet/reports masterhttplog = /home/logs/puppet/masterhttp.log masterlog =

Hello All, I don''t seem to be able to get reports to display on the foreman interface. I copied extras/puppet/foreman/files/foreman-report.rb to / usr/lib/ruby/site_ruby/1.8/puppet/reportsforeman.rb, instead of /usr/ lib/ruby/1.8/puppet/reports/foreman.rb. Config: Centos5.4, Apache/ Passenger, Puppet 0.25.4. The reports are coming from the clients, because I can see them in

Hello! I try to use foreman. It''s successfuly import current nodes from puppet storeconfig. Nodes hostname stored in short form, without domain. After that, i run puppet on newly created additional 5 nodes. They shows in foreman with full fqdn. Os, environment, architecture for this nodes not shown. How can i fix this issue? -- You received this message because you are subscribed to

Ok, the file definition was missing. Now i''ve put that: ## services/ssh.pp class ssh { file { sshd_config: name => "/etc/ssh/sshd_config" } service { ssh: name => $operatingsystem ? { Debian => ssh, default => sshd }, ensure =>

I have a similar line in my network script, for the same reason. THIS problem is different. I cannot umount those shares after the windows machine goes down, no matter what commands I try. Joel On Mon, Dec 03, 2001 at 02:49:01PM -0800, Bill Parker wrote: > > Joel, > > I used to have the same problem with smbfs type mounts hanging > until I modified /etc/rc.d/init.d/network to add

Hi, is there a way to make sure a file is installed only if a certain package is installed on the client? e.g. I want to distribute the client key for NX via puppet. However I only want to install these files if package ''freenx'' is installed on the client. I tried adding ''require => package["freenx"]'' but then puppetd complains it

Hi all, I''d like to comment my puppetd --debug output with some expert or other admin cause I see some thing that I don''t understand. 1.-) Defaults. I define my defaults in site.pp like: case $operatingsystem { ''RedHat'' , ''CentOS'' : { [...] Package { provider => yum,

I''ve been using PuppetDB as an ENC for a while, but I haven''t really utilized it for stored configs or anything. I was mostly interested in replacing Dashboard''s reporting capabilities, but PuppetDB doesn''t yet do anything (that I can see) with reports. So I''m currently looking into setting up a separate Foreman server. I saw the script mentioned

Hi I am new in Puppet and i have one error when i test Postgresql module in infrastructure mode. I''m using Puppet 3.1.0 in Debian squeeze or 6.0.7 i tape the next command puppetd -t -v and this is the error info: Retrieving plugin info: Loading facts in pe_version info: Loading facts in postgres_default_version info: Loading facts in iptables info: Loading facts in puppet_vardir