Re: [Puppet Users] useradd question
Hi Peter,
Have you tried --debug --noop, looking for lines like these:
debug: /Stage[main]/Git/File[dirrights]/require: requires User[git]
notice: /Stage[main]/Git::User/User[git]/ensure: current_value absent,
should be present (noop)
debug: /Stage[main]/Git::User/User[git]: The container
Class[Git::User] will propagate my refresh event
This little test seems to run ok here.
test.pp
class git::user {
user {'git':
name= 'git',
ensure = present,
comment = 'Git user for puppet',
}
}
class git {
file {'dirrights':
path= '/home/ahendry/temp',
owner = 'git',
require = User['git'],
}
}
include git::user
include git
$ puppet apply --noop test.pp
warning: Could not retrieve fact fqdn
notice: /Stage[main]/Git::User/User[git]/ensure: current_value absent,
should be present (noop)
err: /Stage[main]/Git/File[dirrights]: Could not evaluate: Could not
find user git
notice: Class[Git::User]: Would have triggered 'refresh' from 1 events
notice: Stage[main]: Would have triggered 'refresh' from 1 events
notice: Finished catalog run in 0.05 seconds
On Tue, Nov 1, 2011 at 3:16 PM, Peter Horvath
peter.horvat...@googlemail.com wrote:
I call them here.
/etc/puppet/manifests/site.pp
#Puppet Node configurationsnode eurwebtest01 { include apache2
include apache2::mods include apache2::vhost-eurwebtest}
node eurwebtest02 { include apache2 include
apache2::mods include apache2::vhost-eurwebtest include
system include git include git::ssh include
git::user include git::sudoers}
node eurwebtest03 { include apache2 include
apache2::mods include apache2::vhost-eurwebtest include
system
include git include git::ssh include git::user
include git::sudoers}
On 1 November 2011 01:19, Andrew Hendry andrew.hen...@gmail.com wrote:
Hi Peter,
Where do you call git::user and git::ssh from?
Maybe the spots where you have require = User['git'], should they be
require = Class['Git::User']?
Andrew.
On Tue, Nov 1, 2011 at 1:21 AM, Peter Horvath
peter.horvat...@googlemail.com wrote:
I am using Ubuntu LTS 10.04 with the backported puppet
2.6.1-0ubuntu2~lucid1
I am trying to create user with the following manifests but at the end
always getting the Could not find user git error message:
What am i missing, seems the manifest not creating the missing git
user.
/etc/modules/git/manifests/user.pp
class git::user {
user{'install':
name = 'install',
ensure = absent,
}
user{'git':
name = 'git',
password = 'x',
ensure = present,
comment = 'Git user for puppet',
managehome = true,
shell = '/bin/bash',
uid = '1000',
require = User['install'],
provider = 'useradd',
}
Some other classes uses this as requirement:
/etc/modules/git/manifests/ssh.pp
class git::ssh {
package{'ssh':
ensure = installed,
}
file{'dir':
ensure = directory,
path = '/home/git/.ssh',
require = User['git'],
}
file{'authkey':
path = '/home/git/.ssh/authorized_keys',
ensure = file,
source = '/etc/puppet/modules/git/files/
authorized_keys',
owner = 'git',
group = 'git',
mode = '600',
recurse = true,
require = User['git'],
}
/etc/modules/git/manifests/init.pp
class git {
package{'git-core':
ensure = installed,
}
file{'config':
path = '/etc/puppet/.git/config',
ensure = file,
source = '/etc/puppet/modules/git/files/config',
}
file{'post_receive':
path = '/etc/puppet/.git/hooks/post-receive',
ensure = file,
source = '/etc/puppet/modules/git/files/post-
receive',
}
file{'dirrights':
path = '/etc/puppet',
owner = 'git',
group = 'root',
mode = '755',
recurse = true,
require = User['git'],
}
}
Thank you
Peter
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
Re: [Puppet Users] useradd question
I have other classes and require between classes pps working perfectly puppet apply --trace --debug /etc/puppet/site.pp debug: importing '/etc/puppet/modules/apache2/manifests/init.pp' in environment production debug: Automatically imported apache2 from apache2 into production debug: importing '/etc/puppet/modules/apache2/manifests/mods.pp' in environment production debug: Automatically imported apache2::mods from apache2/mods into production debug: importing '/etc/puppet/modules/apache2/manifests/vhost-eurwebtest.pp' in environment production debug: Automatically imported apache2::vhost-eurwebtest from apache2/vhost-eurwebtest into production debug: Scope(Class[Apache2::Vhost-eurwebtest]): Retrieving template /etc/puppet/modules/apache2/templates/vhost.erb debug: template[/etc/puppet/modules/apache2/templates/vhost.erb]: Bound template variables for /etc/puppet/modules/apache2/templates/vhost.erb in 0.00 seconds debug: template[/etc/puppet/modules/apache2/templates/vhost.erb]: Interpolated template /etc/puppet/modules/apache2/templates/vhost.erb in 0.00 seconds debug: importing '/etc/puppet/modules/system/manifests/init.pp' in environment production debug: Automatically imported system from system into production debug: importing '/etc/puppet/modules/git/manifests/init.pp' in environment production debug: Automatically imported git from git into production debug: importing '/etc/puppet/modules/git/manifests/ssh.pp' in environment production debug: Automatically imported git::ssh from git/ssh into production debug: importing '/etc/puppet/modules/git/manifests/user.pp' in environment production debug: Automatically imported git::user from git/user into production debug: importing '/etc/puppet/modules/git/manifests/sudoers.pp' in environment production debug: Automatically imported git::sudoers from git/sudoers into production debug: Puppet::Type::Package::ProviderPortage: file /usr/bin/emerge does not exist debug: Puppet::Type::Package::ProviderPkg: file /usr/bin/pkg does not exist debug: Puppet::Type::Package::ProviderSun: file /usr/sbin/pkgrm does not exist debug: Puppet::Type::Package::ProviderSunfreeware: file pkg-get does not exist debug: Puppet::Type::Package::ProviderAptrpm: file rpm does not exist debug: Puppet::Type::Package::ProviderYum: file yum does not exist debug: Puppet::Type::Package::ProviderUrpmi: file urpmi does not exist debug: Puppet::Type::Package::ProviderOpenbsd: file pkg_add does not exist debug: Puppet::Type::Package::ProviderAix: file /usr/bin/lslpp does not exist debug: Puppet::Type::Package::ProviderNim: file /usr/sbin/nimclient does not exist debug: Puppet::Type::Package::ProviderUp2date: file /usr/sbin/up2date-nox does not exist debug: Puppet::Type::Package::ProviderFink: file /sw/bin/fink does not exist debug: Puppet::Type::Package::ProviderPortupgrade: file /usr/local/sbin/pkg_deinstall does not exist debug: Puppet::Type::Package::ProviderFreebsd: file /usr/sbin/pkg_add does not exist debug: Puppet::Type::Package::ProviderRug: file /usr/bin/rug does not exist debug: Puppet::Type::Package::ProviderPorts: file /usr/local/sbin/pkg_deinstall does not exist debug: Puppet::Type::Package::ProviderHpux: file /usr/sbin/swinstall does not exist debug: Puppet::Type::Package::ProviderZypper: file /usr/bin/zypper does not exist debug: Puppet::Type::Package::ProviderRpm: file rpm does not exist debug: Puppet::Type::File::ProviderMicrosoft_windows: feature microsoft_windows is missing debug: Puppet::Type::Service::ProviderLaunchd: file /bin/launchctl does not exist debug: Puppet::Type::Service::ProviderRunit: file /usr/bin/sv does not exist debug: Puppet::Type::Service::ProviderDaemontools: file /usr/bin/svc does not exist debug: Puppet::Type::Service::ProviderGentoo: file /sbin/rc-update does not exist debug: Puppet::Type::Service::ProviderRedhat: file /sbin/chkconfig does not exist debug: Service[apache](provider=debian): Executing 'ps -ef' debug: Service[apache](provider=debian): PID is 1191 debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist debug: Puppet::Type::User::ProviderUser_role_add: file roledel does not exist debug: Puppet::Type::User::ProviderLdap: true value when expecting false /usr/lib/ruby/1.8/puppet/type/file/owner.rb:37:in `retrieve' /usr/lib/ruby/1.8/puppet/type/file/owner.rb:32:in `collect' /usr/lib/ruby/1.8/puppet/type/file/owner.rb:32:in `retrieve' /usr/lib/ruby/1.8/puppet/type.rb:695:in `retrieve' /usr/lib/ruby/1.8/puppet/type.rb:690:in `each' /usr/lib/ruby/1.8/puppet/type.rb:690:in `retrieve' /usr/lib/ruby/1.8/puppet/type/file.rb:634:in `retrieve' /usr/lib/ruby/1.8/puppet/type.rb:703:in `retrieve_resource' /usr/lib/ruby/1.8/puppet/type.rb:1861:in `to_trans' /usr/lib/ruby/1.8/puppet/type/file.rb:701:in `to_trans' /usr/lib/ruby/1.8/puppet/type.rb:1886:in `to_resource' /usr/lib/ruby/1.8/puppet/type.rb:203:in `uniqueness_key'
[Puppet Users] What's the canonical way to enforce permissions/ownership on a directory subtree?
I've just tried this (we assume /opt/jetty-6.1.26 already exists):
file { /opt/jetty-6.1.26:
owner = jetty,
group = users,
recurse = true,
}
... but it's taking an *age*. What's the Right Way?
Cheers, Robert.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet client starting problem !!
Hi, On 10/31/2011 07:47 AM, Swati Longia wrote: I don't even have normal linux commands like useradd or groupadd in this OS. is this a requirement? Because: /err: Could not create resources for managing Puppet's files and directories in sections [:main, :agent, :ssl]: Could not find a default provider for user/ Puppet doesn't seem to be able to work in this environment. Your basic installation should really comprise the most basic toolchain, including useradd. HTH, Felix -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Phasewise run of puppet
- Original Message -
Hi All,
I have a requirement to initiate puppet runs of different services
in a phase wise manner. I have the following setup in my nodes.pp
you seem to be on roughly the right track
node /^(host1|host2)\.domain\.local$/ inherits basenode {
include role_service1
}
node /^(host3|host4)\.domain\.local$/ inherits basenode {
include role_service2
}
I'd make these a module and do something like roles::services1 and
roles::services2
Now i want to run puppet on host1 and host3 and then on host2 and
host4. In short i would like to group the hosts into phases
phase1 - host1|host3
phase2 - host2|host4
alternatively you can create a custom fact that sets which phase a node
is in
I would like to make a class something like phase1 and phase2 and
then use mcollective to initiate a puppet run:
mco puppetd -Wphase1 runonce.
with your 2 includes above you can just do: mco puppetd -W role_service1 runonce
or if you went the fact route do;
mco puppetd -W phase=1 runonce
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Rules for numerical variable use
On 10/31/11 2:04 AM, Henrik Lindberg wrote: Need help with Geppetto issue #226 regarding rules for numerical variables - https://github.com/cloudsmith/geppetto/issues/226 This is to allow geppetto to correctly validate their use. Help much appreciated. Regards - henrik Thanks everyone who chimed in on this issue. This has now been fixed in Geppetto and will be available in the next update. Regards - henrik -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: What's the canonical way to enforce permissions/ownership on a directory subtree?
how big is the directory structure?
we've had incredibly painful experiences trying to manage directory
perms/ownerships on large directory trees...
so much so that we only set the perms on a few of the top level
directories and left the rest
it's something to do with needing to do an md5 and stat on every file
in the tree that slows it down
how important is it that the permissions are forced?
we decided eventually that the file attr wouldn't necessarily change
unless someone had access to the directory via ssh..
and only the sys admins do to the server in question anyway
hopefully there's a better way of doing it ... calling all gurus?
cheers,
Andrew
On Nov 1, 11:15 am, Robert Atkins snikta.tre...@gmail.com wrote:
I've just tried this (we assume /opt/jetty-6.1.26 already exists):
file { /opt/jetty-6.1.26:
owner = jetty,
group = users,
recurse = true,
}
... but it's taking an *age*. What's the Right Way?
Cheers, Robert.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] organizing Ruby DSL manifests
I am trying to understand Puppet's Ruby DSL. I have tried it in server-less mode using 'puppet apply' and it worked fine. But I am not sure how to organize it in the server. It is a simple manifest file without any modules and classes in it. Should it go in the regular manifests directory (which already contains few manifests in Puppet DSL)? - thanks, neuby.r -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] organizing Ruby DSL manifests
This might help you: http://docs.puppetlabs.com/learning/ Lots of people seem to have a structure so that /etc/puppet/manifests/site.pp does this: import nodes/* And then your node definitions are in separate files in /etc/puppet/manifests/nodes. Of course, each to their own. Maybe you like a different system. On Tue, Nov 01, 2011 at 09:46:56AM -0500, neubyr wrote: I am trying to understand Puppet's Ruby DSL. I have tried it in server-less mode using 'puppet apply' and it worked fine. But I am not sure how to organize it in the server. It is a simple manifest file without any modules and classes in it. Should it go in the regular manifests directory (which already contains few manifests in Puppet DSL)? - thanks, neuby.r -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] 2.7.6 yumrepo not working
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 {
'EWT-Base':
descr= 'Base Repository',
baseurl =
http://repo:80/$operatingsystem-$operatingsystemrelease-$architecture;,
gpgcheck = 0,
enabled = 1,
priority = 1;
= What gets written out
[Base]
name=Base Repository
baseurl=http://repo:80/x86_64
enabled=1
gpgcheck=0
priority=1
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] 2.7.6 yumrepo not working
You probably need to escape some of this, part of ours-
.repo/\$releasever/\$basearch
puppet/factor shouldn't resolve these variables, they go to the repo file
and are resolved by yum or whatever.
On Tue, Nov 1, 2011 at 10:45 AM, Christopher Johnston chjoh...@gmail.comwrote:
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 {
'EWT-Base':
descr= 'Base Repository',
baseurl =
http://repo:80/$operatingsystem-$operatingsystemrelease-$architecture;,
gpgcheck = 0,
enabled = 1,
priority = 1;
= What gets written out
[Base]
name=Base Repository
baseurl=http://repo:80/x86_64
enabled=1
gpgcheck=0
priority=1
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] 2.7.6 yumrepo not working
It's the dashes at the end of variable names problem. Try
...${operatingsystem}-${operatingsystemrelease}-${architecture} instead.
On 2011-11-01 09:07 , Len Rugen wrote:
You probably need to escape some of this, part of ours-
.repo/\$releasever/\$basearch
puppet/factor shouldn't resolve these variables, they go to the repo
file and are resolved by yum or whatever.
On Tue, Nov 1, 2011 at 10:45 AM, Christopher Johnston
chjoh...@gmail.com mailto:chjoh...@gmail.com wrote:
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 {
'EWT-Base':
descr= 'Base Repository',
baseurl =
http://repo:80/$operatingsystem-$operatingsystemrelease-$architecture;,
gpgcheck = 0,
enabled = 1,
priority = 1;
= What gets written out
[Base]
name=Base Repository
baseurl=http://repo:80/x86_64
enabled=1
gpgcheck=0
priority=1
signature.asc
Description: OpenPGP digital signature
Re: [Puppet Users] Re: Clearing delayed job failures in dashboard
I don't think this will help. I do report cleanup daily to keep only the last 14 days and it hasn't touched the number of delayed job failures reported. On 10/31/2011 12:26 AM, Evgeny wrote: this will clean all reports, I don't know how to clean only delayed job failures but it may help rake RAILS_ENV=production reports:prune upto=0 unit=day On Oct 28, 9:32 pm, Steven L. Seedslseed1...@gmail.com wrote: I have a ton of delayed job failures in my dashboard under background tasks. They are mostly failed imports of report yaml files that were deleted. There are over 4 of them so I can't use the Mark all as read button because it causes dashboard to hang forever. Anyone know how I can clear these from the command line? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] git hooks for pre-commit in puppet 2.7?
Hi All, Does anyone have a good git pre-commit hook that's compatible with Puppet 2.7? The example pre-commit hook on the PuppetLabs wiki[1] no longer works, because the puppet binary no longer seems to accept stdin. [1] http://projects.puppetlabs.com/projects/1/wiki/Puppet_Version_Control -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Intermittent Error 400 catalog failure
Len, I would be very interested in the details of your Puppet Master system running 2.7.5. Any configs you are willing to share would be appreciated. Also, it would be most helpful if you can reproduce one of the failed runs using from a Puppet client using: puppet agent --test --debug Thanks! On Tue, Nov 1, 2011 at 6:27 AM, Len Rugen lenru...@gmail.com wrote: I have one host, the only one using this class, where it occasionally gets the following error. I'd guess this happens 1/3 of the time, but seems to work for several runs, then fail for several runs. Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class server::e1 for e1.xxx.xxx on node e1.xxx.xxx This started when we installed 2.7.5, upgrading from 2.6.8 or .9. Foreman 0.3 is also in use, but to me, this doesn't look like foreman. I also upgraded the client to 2.7.6 but it didn't change the symptoms. Any thoughts? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Dominic Maraglia QA Engineer Puppet Labs -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] 2.7.6 yumrepo not working
That worked, for some reason back referencing did not. My foolishness I
was overlooking normal variable semantic (like in shell). Strange thing my
prior setup worked fine in 2.6, 2.7 broke it.
-Chris
On Tue, Nov 1, 2011 at 12:40 PM, Jacob Helwig ja...@puppetlabs.com wrote:
It's the dashes at the end of variable names problem. Try
...${operatingsystem}-${operatingsystemrelease}-${architecture} instead.
On 2011-11-01 09:07 , Len Rugen wrote:
You probably need to escape some of this, part of ours-
.repo/\$releasever/\$basearch
puppet/factor shouldn't resolve these variables, they go to the repo
file and are resolved by yum or whatever.
On Tue, Nov 1, 2011 at 10:45 AM, Christopher Johnston
chjoh...@gmail.com mailto:chjoh...@gmail.com wrote:
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 {
'EWT-Base':
descr= 'Base Repository',
baseurl =
http://repo:80/$operatingsystem-$operatingsystemrelease-$architecture;,
gpgcheck = 0,
enabled = 1,
priority = 1;
= What gets written out
[Base]
name=Base Repository
baseurl=http://repo:80/x86_64
enabled=1
gpgcheck=0
priority=1
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] 2.7.6 yumrepo not working
There was a change in 2.7 to allow dashes in variable names. There's an
issue open in Redmine around this very issue[0]
[0] http://projects.puppetlabs.com/issues/10146
On 2011-11-01 10:29 , Christopher Johnston wrote:
That worked, for some reason back referencing did not. My foolishness I
was overlooking normal variable semantic (like in shell). Strange thing
my prior setup worked fine in 2.6, 2.7 broke it.
-Chris
On Tue, Nov 1, 2011 at 12:40 PM, Jacob Helwig ja...@puppetlabs.com
mailto:ja...@puppetlabs.com wrote:
It's the dashes at the end of variable names problem. Try
...${operatingsystem}-${operatingsystemrelease}-${architecture}
instead.
signature.asc
Description: OpenPGP digital signature
[Puppet Users] parameterized module and flow control
Hi guys, For a project I'm working on for my studies we need to create a demo setup of a small enterprise environment. The linux-part of this is now managed by puppet. However, I'm running into something I can't exactly figure to how to fix. I've read the docs a few times but I can't find a clear indication on how to solve this and what would be the recommended way, Google left me out in the cold too. What I basically need is flow control for my installation. In the current state I want to create an nginx-module that handles a few things. My main issue is that I want this parameterized. Depending on a parameter fed to that module I want to change the packages installed and additional classes being called upon. I'd like to be able to do something like this: nginx(type=default), install nginx, call nginx::conf nginx(type=ruby), install nginx-extras, call nginx::conf, call nginx::conf::passenger nginx(type=php), install nginx, php5-fpm, call nginx::conf, call nginx::conf::php And so forth. I'd rather not split this up into different modules, imho that's ugly but I can't figure out how to do it this way in puppet either. Can anyone point me in the right direction? Kind regards, -- Daenney -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/7sMpz4YucOEJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Puppet client starting problem !!
On Oct 31, 1:47 am, Swati Longia swati.lon...@gmail.com wrote: Hi, I have installed puppet 2.7.5 from tar on open suse 10.1. My ruby version is 1.8.5 and facter version is 1.6.2. The opensuse OS is pretty minimalistic. I don't even have normal linux commands like useradd or groupadd in this OS. Surely this distro has *some* command for managing system users. The documentation I find seems to indicate that OpenSUSE does indeed have useradd for this purpose. Perhaps you have performed an extremely minimalistic install that does not include the user management commands; in that case, manually install the needed package before trying to fire up the Puppet client. Your alternatives are to write a new provider class for the User resource type that works with the available tools, or to script a replacement for useradd that employs the available tools. Either is likely to be much more difficult and error-prone than would be just finding and installing the needed package. John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Intermittent Error 400 catalog failure
On Tue, Nov 1, 2011 at 6:27 AM, Len Rugen lenru...@gmail.com wrote: I have one host, the only one using this class, where it occasionally gets the following error. I'd guess this happens 1/3 of the time, but seems to work for several runs, then fail for several runs. Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class server::e1 for e1.xxx.xxx on node e1.xxx.xxx This started when we installed 2.7.5, upgrading from 2.6.8 or .9. Foreman 0.3 is also in use, but to me, this doesn't look like foreman. I also upgraded the client to 2.7.6 but it didn't change the symptoms. A change from 2.6 to 2.7 was that ENC-specified classes now fail if they can't be found, just like classes that you've included via manifests. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Clearing delayed job failures in dashboard
On Fri, Oct 28, 2011 at 11:32 AM, Steven L. Seed slseed1...@gmail.comwrote: I have a ton of delayed job failures in my dashboard under background tasks. They are mostly failed imports of report yaml files that were deleted. There are over 4 of them so I can't use the Mark all as read button because it causes dashboard to hang forever. Anyone know how I can clear these from the command line? 'rake -T' is very useful for looking for rake tasks. # rake -T jobs rake jobs:clear # Clear the delayed_job queue. rake jobs:work# Start a delayed_job worker. The first one looks like the one you want. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Intermittent Error 400 catalog failure
It could be this issue if you are using imports in your Puppet code. https://projects.puppetlabs.com/issues/8433 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Intermittent Error 400 catalog failure
Yes, this fits. I'll change my structure and see if it goes away. (Still, would it work sometimes but not always?) On Tue, Nov 1, 2011 at 2:55 PM, Chuck cssc...@gmail.com wrote: It could be this issue if you are using imports in your Puppet code. https://projects.puppetlabs.com/issues/8433 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Seattle Meetup - November 8th
Join me 11/8 at Brouwers Cafe in Fremont at 6pm for drinks and discussions on Puppet, DevOps, system administration, etc. http://www.meetup.com/Seattle-Puppet-Meetup/ -g -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] help with err: Could not find node
I'm running Ubuntu 10.04 LTS and I just installed Puppet and puppetmasterd (both 0.25.4) along with the puppet-dashboard v1.2.0 and Foreman 0.3. Puppet and the dashboard were working fine with just the master server and a separate client until I installed and configured Foreman. Now I keep getting the following errors... On the puppet master server: debug: Executing '/usr/bin/env PUPPET_DASHBOARD_URL=http://localhost: 3000 /root/puppet-dashboard/bin/external_node puppet.mydomain.com' err: Failed to find puppet.mydomain.com via exec: Execution of '/usr/ bin/env PUPPET_DASHBOARD_URL=http://localhost:3000 /root/puppet- dashboard/bin/external_node puppet.mydomain.com' returned 126: /usr/ bin/env: /root/puppet-dashboard/bin/external_node: Permission denied err: Could not find node 'puppet.mydomain.com'; cannot compile On the client, doing puppetd -vtd: debug: Failed to load library 'selinux' for feature 'selinux' debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does not exist debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/ dscl does not exist debug: Failed to load library 'ldap' for feature 'ldap' debug: Puppet::Type::User::ProviderLdap: feature ldap is missing debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: /File[/var/lib/puppetmaster/ssl/certs/puppet.mydomain.com.pem]: Autorequiring File[/var/lib/puppetmaster/ssl/certs] debug: /File[/var/lib/puppetmaster/state/classes.txt]: Autorequiring File[/var/lib/puppetmaster/state] debug: /File[/var/lib/puppetmaster/state/state.yaml]: Autorequiring File[/var/lib/puppetmaster/state] debug: /File[/var/lib/puppetmaster/facts]: Autorequiring File[/var/lib/ puppetmaster] debug: /File[/var/lib/puppetmaster/ssl]: Autorequiring File[/var/lib/ puppetmaster] debug: /File[/var/lib/puppetmaster/ssl/crl.pem]: Autorequiring File[/ var/lib/puppetmaster/ssl] debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet] debug: /File[/var/lib/puppetmaster/ssl/certs]: Autorequiring File[/var/ lib/puppetmaster/ssl] debug: /File[/var/run/puppetmaster/puppetd.pid]: Autorequiring File[/ var/run/puppetmaster] debug: /File[/var/lib/puppetmaster/puppetmaster]: Autorequiring File[/ var/lib/puppetmaster] debug: /File[/var/lib/puppetmaster/state]: Autorequiring File[/var/lib/ puppetmaster] debug: /File[/var/lib/puppetmaster/ssl/public_keys]: Autorequiring File[/var/lib/puppetmaster/ssl] debug: /File[/var/lib/puppetmaster/client_yaml]: Autorequiring File[/ var/lib/puppetmaster] debug: /File[/var/lib/puppetmaster/ssl/private]: Autorequiring File[/ var/lib/puppetmaster/ssl] debug: /File[/var/lib/puppetmaster/ssl/certs/ca.pem]: Autorequiring File[/var/lib/puppetmaster/ssl/certs] debug: /File[/var/lib/puppetmaster/ssl/public_keys/ puppet.mydomain.com.pem]: Autorequiring File[/var/lib/puppetmaster/ssl/ public_keys] debug: /File[/var/lib/puppetmaster/ssl/private_keys]: Autorequiring File[/var/lib/puppetmaster/ssl] debug: /File[/var/lib/puppetmaster/lib]: Autorequiring File[/var/lib/ puppetmaster] debug: /File[/var/lib/puppetmaster/ssl/private_keys/ puppet.mydomain.com.pem]: Autorequiring File[/var/lib/puppetmaster/ssl/ private_keys] debug: /File[/var/lib/puppetmaster/clientbucket]: Autorequiring File[/ var/lib/puppetmaster] debug: /File[/var/lib/puppetmaster/state/graphs]: Autorequiring File[/ var/lib/puppetmaster/state] debug: /File[/var/lib/puppetmaster/ssl/certificate_requests]: Autorequiring File[/var/lib/puppetmaster/ssl] debug: Finishing transaction 70213661363800 with 0 changes debug: Using cached certificate for ca, good until Sun Oct 23 19:49:36 UTC 2016 debug: Using cached certificate for puppet.mydomain.com, good until Sun Oct 23 20:00:26 UTC 2016 debug: Loaded state in 0.00 seconds debug: Executing '/etc/puppet/etckeeper-commit-pre' debug: Using cached certificate for ca, good until Sun Oct 23 19:49:36 UTC 2016 debug: Using cached certificate for puppet.mydomain.com, good until Sun Oct 23 20:00:26 UTC 2016 debug: Using cached certificate_revocation_list for ca, good until debug: catalog supports formats: b64_zlib_yaml marshal pson raw yaml; using pson err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find node 'puppet-client0.mydomain.com'; cannot compile warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run My puppet.conf: [main] logdir=$vardir/puppetmaster vardir=/var/lib/puppetmaster ssldir=$vardir/puppetmaster/ssl rundir=/var/run/puppetmaster factpath=$vardir/lib/facter pluginsync=false templatedir=$confdir/templates prerun_command=/etc/puppet/etckeeper-commit-pre postrun_command=/etc/puppet/etckeeper-commit-post reports=log, foreman [puppetmasterd] modulepath = /etc/puppet/modules certname=puppet reports = store, puppet_dashboard node_terminus = exec external_nodes = /usr/bin/env PUPPET_DASHBOARD_URL=http://localhost: 3000 /root/puppet-dashboard/bin/external_node [puppetd] server=puppet vardir=/var/lib/puppetmaster ssldir=$vardir/ssl report = true
Re: [Puppet Users] help with err: Could not find node
At the top of your email:
Could not find node 'puppet.mydomain.com'
At the bottom of your email:
node default {
}
node basenode {
}
node 'puppet-client0.mydomain.com' inherits basenode {
}
Does it work when you explicitly define this node?
node 'puppet.mydomain.com' {
}
On Tue, Nov 01, 2011 at 01:27:40PM -0700, weloki wrote:
I'm running Ubuntu 10.04 LTS and I just installed Puppet and
puppetmasterd (both 0.25.4) along with the puppet-dashboard v1.2.0 and
Foreman 0.3. Puppet and the dashboard were working fine with just the
master server and a separate client until I installed and configured
Foreman. Now I keep getting the following errors...
On the puppet master server:
debug: Executing '/usr/bin/env PUPPET_DASHBOARD_URL=http://localhost:
3000 /root/puppet-dashboard/bin/external_node puppet.mydomain.com'
err: Failed to find puppet.mydomain.com via exec: Execution of '/usr/
bin/env PUPPET_DASHBOARD_URL=http://localhost:3000 /root/puppet-
dashboard/bin/external_node puppet.mydomain.com' returned 126: /usr/
bin/env: /root/puppet-dashboard/bin/external_node: Permission denied
err: Could not find node 'puppet.mydomain.com'; cannot compile
On the client, doing puppetd -vtd:
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does
not exist
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/
dscl does not exist
debug: Failed to load library 'ldap' for feature 'ldap'
debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: /File[/var/lib/puppetmaster/ssl/certs/puppet.mydomain.com.pem]:
Autorequiring File[/var/lib/puppetmaster/ssl/certs]
debug: /File[/var/lib/puppetmaster/state/classes.txt]: Autorequiring
File[/var/lib/puppetmaster/state]
debug: /File[/var/lib/puppetmaster/state/state.yaml]: Autorequiring
File[/var/lib/puppetmaster/state]
debug: /File[/var/lib/puppetmaster/facts]: Autorequiring File[/var/lib/
puppetmaster]
debug: /File[/var/lib/puppetmaster/ssl]: Autorequiring File[/var/lib/
puppetmaster]
debug: /File[/var/lib/puppetmaster/ssl/crl.pem]: Autorequiring File[/
var/lib/puppetmaster/ssl]
debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppetmaster/ssl/certs]: Autorequiring File[/var/
lib/puppetmaster/ssl]
debug: /File[/var/run/puppetmaster/puppetd.pid]: Autorequiring File[/
var/run/puppetmaster]
debug: /File[/var/lib/puppetmaster/puppetmaster]: Autorequiring File[/
var/lib/puppetmaster]
debug: /File[/var/lib/puppetmaster/state]: Autorequiring File[/var/lib/
puppetmaster]
debug: /File[/var/lib/puppetmaster/ssl/public_keys]: Autorequiring
File[/var/lib/puppetmaster/ssl]
debug: /File[/var/lib/puppetmaster/client_yaml]: Autorequiring File[/
var/lib/puppetmaster]
debug: /File[/var/lib/puppetmaster/ssl/private]: Autorequiring File[/
var/lib/puppetmaster/ssl]
debug: /File[/var/lib/puppetmaster/ssl/certs/ca.pem]: Autorequiring
File[/var/lib/puppetmaster/ssl/certs]
debug: /File[/var/lib/puppetmaster/ssl/public_keys/
puppet.mydomain.com.pem]: Autorequiring File[/var/lib/puppetmaster/ssl/
public_keys]
debug: /File[/var/lib/puppetmaster/ssl/private_keys]: Autorequiring
File[/var/lib/puppetmaster/ssl]
debug: /File[/var/lib/puppetmaster/lib]: Autorequiring File[/var/lib/
puppetmaster]
debug: /File[/var/lib/puppetmaster/ssl/private_keys/
puppet.mydomain.com.pem]: Autorequiring File[/var/lib/puppetmaster/ssl/
private_keys]
debug: /File[/var/lib/puppetmaster/clientbucket]: Autorequiring File[/
var/lib/puppetmaster]
debug: /File[/var/lib/puppetmaster/state/graphs]: Autorequiring File[/
var/lib/puppetmaster/state]
debug: /File[/var/lib/puppetmaster/ssl/certificate_requests]:
Autorequiring File[/var/lib/puppetmaster/ssl]
debug: Finishing transaction 70213661363800 with 0 changes
debug: Using cached certificate for ca, good until Sun Oct 23 19:49:36
UTC 2016
debug: Using cached certificate for puppet.mydomain.com, good until
Sun Oct 23 20:00:26 UTC 2016
debug: Loaded state in 0.00 seconds
debug: Executing '/etc/puppet/etckeeper-commit-pre'
debug: Using cached certificate for ca, good until Sun Oct 23 19:49:36
UTC 2016
debug: Using cached certificate for puppet.mydomain.com, good until
Sun Oct 23 20:00:26 UTC 2016
debug: Using cached certificate_revocation_list for ca, good until
debug: catalog supports formats: b64_zlib_yaml marshal pson raw yaml;
using pson
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Could not find node 'puppet-client0.mydomain.com'; cannot
compile
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
My puppet.conf:
[main]
logdir=$vardir/puppetmaster
vardir=/var/lib/puppetmaster
ssldir=$vardir/puppetmaster/ssl
rundir=/var/run/puppetmaster
factpath=$vardir/lib/facter
pluginsync=false
templatedir=$confdir/templates
[Puppet Users] Custom fact not set with mc-puppetd
Hello, I've mcollective 1.2.1 with puppet 2.6.12 on rhel5.6, facter 1.6.2 setup from http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML. Now I've create a custom fact in /usr/lib/ruby/site_ruby/1.8/facter/ customer_status.rb. On the client; Running facter customer_status works. Running 'puppet agent --test' works, customer_status is set in /etc/ mcollective/facts.yaml On the server; But running 'mc-puppetd --wi client runonce' doesn't set the customer_status in /etc/mcollective/facts.yaml. Anyone an idea why? Thanks, Stefan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: help with err: Could not find node
When I put that line in nodes.pp I get:
err: Could not retrieve catalog from remote server: Connection refused
- connect (2)
On Nov 1, 4:38 pm, Christopher Wood christopher_w...@pobox.com
wrote:
At the top of your email:
Could not find node 'puppet.mydomain.com'
At the bottom of your email:
node default {}
node basenode {
}
node 'puppet-client0.mydomain.com' inherits basenode {
}
Does it work when you explicitly define this node?
node 'puppet.mydomain.com' {
}
On Tue, Nov 01, 2011 at 01:27:40PM -0700, weloki wrote:
I'm running Ubuntu 10.04 LTS and I just installed Puppet and
puppetmasterd (both 0.25.4) along with the puppet-dashboard v1.2.0 and
Foreman 0.3. Puppet and the dashboard were working fine with just the
master server and a separate client until I installed and configured
Foreman. Now I keep getting the following errors...
On the puppet master server:
debug: Executing '/usr/bin/env PUPPET_DASHBOARD_URL=http://localhost:
3000 /root/puppet-dashboard/bin/external_node puppet.mydomain.com'
err: Failed to find puppet.mydomain.com via exec: Execution of '/usr/
bin/env PUPPET_DASHBOARD_URL=http://localhost:3000/root/puppet-
dashboard/bin/external_node puppet.mydomain.com' returned 126: /usr/
bin/env: /root/puppet-dashboard/bin/external_node: Permission denied
err: Could not find node 'puppet.mydomain.com'; cannot compile
On the client, doing puppetd -vtd:
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does
not exist
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/
dscl does not exist
debug: Failed to load library 'ldap' for feature 'ldap'
debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: /File[/var/lib/puppetmaster/ssl/certs/puppet.mydomain.com.pem]:
Autorequiring File[/var/lib/puppetmaster/ssl/certs]
debug: /File[/var/lib/puppetmaster/state/classes.txt]: Autorequiring
File[/var/lib/puppetmaster/state]
debug: /File[/var/lib/puppetmaster/state/state.yaml]: Autorequiring
File[/var/lib/puppetmaster/state]
debug: /File[/var/lib/puppetmaster/facts]: Autorequiring File[/var/lib/
puppetmaster]
debug: /File[/var/lib/puppetmaster/ssl]: Autorequiring File[/var/lib/
puppetmaster]
debug: /File[/var/lib/puppetmaster/ssl/crl.pem]: Autorequiring File[/
var/lib/puppetmaster/ssl]
debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppetmaster/ssl/certs]: Autorequiring File[/var/
lib/puppetmaster/ssl]
debug: /File[/var/run/puppetmaster/puppetd.pid]: Autorequiring File[/
var/run/puppetmaster]
debug: /File[/var/lib/puppetmaster/puppetmaster]: Autorequiring File[/
var/lib/puppetmaster]
debug: /File[/var/lib/puppetmaster/state]: Autorequiring File[/var/lib/
puppetmaster]
debug: /File[/var/lib/puppetmaster/ssl/public_keys]: Autorequiring
File[/var/lib/puppetmaster/ssl]
debug: /File[/var/lib/puppetmaster/client_yaml]: Autorequiring File[/
var/lib/puppetmaster]
debug: /File[/var/lib/puppetmaster/ssl/private]: Autorequiring File[/
var/lib/puppetmaster/ssl]
debug: /File[/var/lib/puppetmaster/ssl/certs/ca.pem]: Autorequiring
File[/var/lib/puppetmaster/ssl/certs]
debug: /File[/var/lib/puppetmaster/ssl/public_keys/
puppet.mydomain.com.pem]: Autorequiring File[/var/lib/puppetmaster/ssl/
public_keys]
debug: /File[/var/lib/puppetmaster/ssl/private_keys]: Autorequiring
File[/var/lib/puppetmaster/ssl]
debug: /File[/var/lib/puppetmaster/lib]: Autorequiring File[/var/lib/
puppetmaster]
debug: /File[/var/lib/puppetmaster/ssl/private_keys/
puppet.mydomain.com.pem]: Autorequiring File[/var/lib/puppetmaster/ssl/
private_keys]
debug: /File[/var/lib/puppetmaster/clientbucket]: Autorequiring File[/
var/lib/puppetmaster]
debug: /File[/var/lib/puppetmaster/state/graphs]: Autorequiring File[/
var/lib/puppetmaster/state]
debug: /File[/var/lib/puppetmaster/ssl/certificate_requests]:
Autorequiring File[/var/lib/puppetmaster/ssl]
debug: Finishing transaction 70213661363800 with 0 changes
debug: Using cached certificate for ca, good until Sun Oct 23 19:49:36
UTC 2016
debug: Using cached certificate for puppet.mydomain.com, good until
Sun Oct 23 20:00:26 UTC 2016
debug: Loaded state in 0.00 seconds
debug: Executing '/etc/puppet/etckeeper-commit-pre'
debug: Using cached certificate for ca, good until Sun Oct 23 19:49:36
UTC 2016
debug: Using cached certificate for puppet.mydomain.com, good until
Sun Oct 23 20:00:26 UTC 2016
debug: Using cached certificate_revocation_list for ca, good until
debug: catalog supports formats: b64_zlib_yaml marshal pson raw yaml;
using pson
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Could not find node 'puppet-client0.mydomain.com'; cannot
compile
warning: Not using cache on failed
Re: [Puppet Users] Re: help with err: Could not find node
On Tue, Nov 01, 2011 at 01:56:53PM -0700, weloki wrote:
When I put that line in nodes.pp I get:
err: Could not retrieve catalog from remote server: Connection refused
- connect (2)
So what dit he puppetmaster say about this agent run?
Also, keep digging into your own email. You may have file permission issues:
returned 126: /usr/bin/env: /root/puppet-dashboard/bin/external_node:
Permission denied
On Nov 1, 4:38 pm, Christopher Wood christopher_w...@pobox.com
wrote:
At the top of your email:
Could not find node 'puppet.mydomain.com'
At the bottom of your email:
node default {}
node basenode {
}
node 'puppet-client0.mydomain.com' inherits basenode {
}
Does it work when you explicitly define this node?
node 'puppet.mydomain.com' {
}
On Tue, Nov 01, 2011 at 01:27:40PM -0700, weloki wrote:
I'm running Ubuntu 10.04 LTS and I just installed Puppet and
puppetmasterd (both 0.25.4) along with the puppet-dashboard v1.2.0 and
Foreman 0.3. Puppet and the dashboard were working fine with just the
master server and a separate client until I installed and configured
Foreman. Now I keep getting the following errors...
On the puppet master server:
debug: Executing '/usr/bin/env PUPPET_DASHBOARD_URL=http://localhost:
3000 /root/puppet-dashboard/bin/external_node puppet.mydomain.com'
err: Failed to find puppet.mydomain.com via exec: Execution of '/usr/
bin/env PUPPET_DASHBOARD_URL=http://localhost:3000/root/puppet-
dashboard/bin/external_node puppet.mydomain.com' returned 126: /usr/
bin/env: /root/puppet-dashboard/bin/external_node: Permission denied
err: Could not find node 'puppet.mydomain.com'; cannot compile
On the client, doing puppetd -vtd:
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does
not exist
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/
dscl does not exist
debug: Failed to load library 'ldap' for feature 'ldap'
debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: /File[/var/lib/puppetmaster/ssl/certs/puppet.mydomain.com.pem]:
Autorequiring File[/var/lib/puppetmaster/ssl/certs]
debug: /File[/var/lib/puppetmaster/state/classes.txt]: Autorequiring
File[/var/lib/puppetmaster/state]
debug: /File[/var/lib/puppetmaster/state/state.yaml]: Autorequiring
File[/var/lib/puppetmaster/state]
debug: /File[/var/lib/puppetmaster/facts]: Autorequiring File[/var/lib/
puppetmaster]
debug: /File[/var/lib/puppetmaster/ssl]: Autorequiring File[/var/lib/
puppetmaster]
debug: /File[/var/lib/puppetmaster/ssl/crl.pem]: Autorequiring File[/
var/lib/puppetmaster/ssl]
debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppetmaster/ssl/certs]: Autorequiring File[/var/
lib/puppetmaster/ssl]
debug: /File[/var/run/puppetmaster/puppetd.pid]: Autorequiring File[/
var/run/puppetmaster]
debug: /File[/var/lib/puppetmaster/puppetmaster]: Autorequiring File[/
var/lib/puppetmaster]
debug: /File[/var/lib/puppetmaster/state]: Autorequiring File[/var/lib/
puppetmaster]
debug: /File[/var/lib/puppetmaster/ssl/public_keys]: Autorequiring
File[/var/lib/puppetmaster/ssl]
debug: /File[/var/lib/puppetmaster/client_yaml]: Autorequiring File[/
var/lib/puppetmaster]
debug: /File[/var/lib/puppetmaster/ssl/private]: Autorequiring File[/
var/lib/puppetmaster/ssl]
debug: /File[/var/lib/puppetmaster/ssl/certs/ca.pem]: Autorequiring
File[/var/lib/puppetmaster/ssl/certs]
debug: /File[/var/lib/puppetmaster/ssl/public_keys/
puppet.mydomain.com.pem]: Autorequiring File[/var/lib/puppetmaster/ssl/
public_keys]
debug: /File[/var/lib/puppetmaster/ssl/private_keys]: Autorequiring
File[/var/lib/puppetmaster/ssl]
debug: /File[/var/lib/puppetmaster/lib]: Autorequiring File[/var/lib/
puppetmaster]
debug: /File[/var/lib/puppetmaster/ssl/private_keys/
puppet.mydomain.com.pem]: Autorequiring File[/var/lib/puppetmaster/ssl/
private_keys]
debug: /File[/var/lib/puppetmaster/clientbucket]: Autorequiring File[/
var/lib/puppetmaster]
debug: /File[/var/lib/puppetmaster/state/graphs]: Autorequiring File[/
var/lib/puppetmaster/state]
debug: /File[/var/lib/puppetmaster/ssl/certificate_requests]:
Autorequiring File[/var/lib/puppetmaster/ssl]
debug: Finishing transaction 70213661363800 with 0 changes
debug: Using cached certificate for ca, good until Sun Oct 23 19:49:36
UTC 2016
debug: Using cached certificate for puppet.mydomain.com, good until
Sun Oct 23 20:00:26 UTC 2016
debug: Loaded state in 0.00 seconds
debug: Executing '/etc/puppet/etckeeper-commit-pre'
debug: Using cached certificate for ca, good until Sun Oct 23 19:49:36
UTC 2016
debug: Using cached certificate for
Re: [Puppet Users] Custom fact not set with mc-puppetd
- Original Message - Hello, I've mcollective 1.2.1 with puppet 2.6.12 on rhel5.6, facter 1.6.2 setup from http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML. Now I've create a custom fact in /usr/lib/ruby/site_ruby/1.8/facter/ customer_status.rb. you should be using pluginsync to copy out custom facts: http://docs.puppetlabs.com/guides/plugins_in_modules.html On the client; Running facter customer_status works. Running 'puppet agent --test' works, customer_status is set in /etc/ mcollective/facts.yaml On the server; But running 'mc-puppetd --wi client runonce' doesn't set the customer_status in /etc/mcollective/facts.yaml. this could only really be down to some environment change, maybe its not picking up those fact or your custom fact only works based on some set of stuff in the environment etc? all runonce does is do: puppetd --onetime which will spawn off a copy of puppet into the background and let it do a normal run, with pluginsync enabled in puppet.conf etc it should all work fine. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] organizing Ruby DSL manifests
On Tue, Nov 1, 2011 at 9:53 AM, Christopher Wood christopher_w...@pobox.com wrote: This might help you: http://docs.puppetlabs.com/learning/ Lots of people seem to have a structure so that /etc/puppet/manifests/site.pp does this: import nodes/* And then your node definitions are in separate files in /etc/puppet/manifests/nodes. Of course, each to their own. Maybe you like a different system. Thanks Chris, that's helpful. I am wondering if I should be mixing Ruby DSL manifests with the Puppet DSL manifests. Is there any recommended practice for keeping both styles together? Also, does Ruby DSL get converted into Puppet DSL before execution? On Tue, Nov 01, 2011 at 09:46:56AM -0500, neubyr wrote: I am trying to understand Puppet's Ruby DSL. I have tried it in server-less mode using 'puppet apply' and it worked fine. But I am not sure how to organize it in the server. It is a simple manifest file without any modules and classes in it. Should it go in the regular manifests directory (which already contains few manifests in Puppet DSL)? - thanks, neuby.r -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] organizing Ruby DSL manifests
On Tue, Nov 01, 2011 at 04:17:41PM -0500, neubyr wrote: On Tue, Nov 1, 2011 at 9:53 AM, Christopher Wood christopher_w...@pobox.com wrote: This might help you: http://docs.puppetlabs.com/learning/ Lots of people seem to have a structure so that /etc/puppet/manifests/site.pp does this: import nodes/* And then your node definitions are in separate files in /etc/puppet/manifests/nodes. Of course, each to their own. Maybe you like a different system. Thanks Chris, that's helpful. I am wondering if I should be mixing Ruby DSL manifests with the Puppet DSL manifests. Is there any recommended practice for keeping both styles together? Also, does Ruby DSL get converted into Puppet DSL before execution? I couldn't tell you since I've only used Puppet DSL. I thought everything was rendered into ruby before execution. I could be wrong. On Tue, Nov 01, 2011 at 09:46:56AM -0500, neubyr wrote: I am trying to understand Puppet's Ruby DSL. I have tried it in server-less mode using 'puppet apply' and it worked fine. But I am not sure how to organize it in the server. It is a simple manifest file without any modules and classes in it. Should it go in the regular manifests directory (which already contains few manifests in Puppet DSL)? - thanks, neuby.r -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Custom fact not set with mc-puppetd
On Nov 1, 10:00 pm, R.I.Pienaar r...@devco.net wrote: - Original Message - you should be using pluginsync to copy out custom facts: http://docs.puppetlabs.com/guides/plugins_in_modules.html Ok, enabled pluginsync, customer_status.rb is now copied to the client in /var/lib/puppet/lib/facts. this could only really be down to some environment change, maybe its not picking up those fact or your custom fact only works based on some set of stuff in the environment etc? Correct, customer_status.rb was picking up an environment variable set from a file in /etc/profile.d/ I've changed customer_status.rb to get the value directly from this file. 'mc-puppetd --wi client runonce' doens't work with customer_status.rb in /var/lib/puppet/lib/facts but it does work with customer_status.rb in /usr/lib/ruby/site_ruby/ 1.8/facter. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Puppet 2.7.7rc1 available
Puppet 2.7.7rc1 is available. This release fixes several issues with Mongrel and Puppet 2.7.x, Windows fixes and updates, test fixes, documentation updates and more. Release Notes for 2.7.7 series -- https://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes This release is available for download at: http://downloads.puppetlabs.com/puppet/ See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected version of 2.7.7rc1 http://projects.puppetlabs.com/projects/puppet Documentation is available at: http://docs.puppetlabs.com/index.html Highlights for 2.7.7rc1 ## (10269) Search bit not set on newly created directories Previously, puppet would not set the user, group, or other execute/search bits for newly created directories. This was a regression introduced in 2.7.6 in commit 22bfd9ce83ff52d909a43c370ba71112ed4961a4. This was caused because the dirmask'ing was occurring when munging the mode property, but that was occurring prior to the ensure property being synced, which is when the directory is actually created. And since the directory did not exist, the executable bits were never added. Similar failures would occur if the path referred to a non-executable file or link that we wanted to change to a directory. This commit reverts the changes to the dirmask and munge methods, and moves the call to dirmask back to the retrieve method. This way we can be sure that the directory has been created by the time we call dirmask. Ideally, we could know at munge time whether we are going to create a directory as opposed to a file or link. But the logic for that depends on many other properties, e.g. source, target, etc. The easiest thing is to just revert the change. ## Maint: Revise reference text for most types and providers This documentation-only commit makes edits for wording, clarity, accuracy, and formatting to the description strings in 64 type and provider files, with the aim of improving the type reference (http://docs.puppetlabs.com/references/latest/type.html). ## (7601) Use instead of += in references This commit refactors some reference code to use the string append operator instead of the slower-but-equivalent += operator. (Offending instances left in lib/puppet/reference/metaparameter.rb and lib/puppet/reference/indirection.rb are slated for deletion in a subsequent commit.) ## (9109) Retrieve request parameters from the request body for POSTs When using Puppet with Mongrel, the facts were being lost with 2.7.0+ clients, since they were switched over to using POST requests for fact submission. This was happening because the request parameters were only being retrieved from the query parameters of the URL, which will not include the POSTed data. We now merge the body of the post together with the query parameters when dealing with POST requests. We also rewind the request body after reading it, since retrieving the request body multiple times would return an empty string after the first time. ## (10244) Restore Mongrel XMLRPC functionality This code was over-eagerly removed, when it turns out to actually still be necessary for backward compatibility with XMLRPC clients. ## (10161) Parenthesize method arguments Ruby 1.8.6 issues warnings when arguments to nested methods are not parenthesized, e.g. f.puts(YAML.dump metadata) results in: warning: parenthsize arguments(s) for future versions These warnings were introduced during Windows development, but not noticed on that platform due to using ruby 1.8.7, which doesn't issue a warning. This commit just wraps the arguments in parenthesis. In addition to the items mentioned above, there were a slew a testing/spec improvements around order dependent tests, and testing on Windows. 2.7.7rc1 === 674068a (#10269) Make directories executable so they can be cleaned up fd747cc (#10365) Add pending test when file overwrites an executable directory fe30d8f (#10315) Add pending tests when following symlinks a22c7aa Maint: Fix test breakage 8576e86 (#10269) Search bit not set on newly created directories 428e08c Stub File.open to not touch the disk a97337f (#10346) Fix storeconfigs spec failures when run alone 5c4daa4 (#7601) Use definition lists in indirection references 7df46a2 (#7601) Use definition lists in type references ad97dc9 (#7601) Add markdown_definitionlist method to reference.rb 455c9aa Maint: Revise reference text for most types and providers ced8e19 (#7601) Remove unnecessarily abstracted paramwrap method a6957ac (#7601) Rename h method to markdown_header 7a0ade6 (#7601) Use instead of += in references 7d65796 (#9109) Retrieve request parameters from the request
[Puppet Users] Re: Help using puppetlabs-mysql
On Oct 31, 3:09 pm, Dan Bode d...@puppetlabs.com wrote:
On Mon, Oct 31, 2011 at 12:44 PM, treydock treyd...@gmail.com wrote:
On Oct 31, 1:56 pm, treydock treyd...@gmail.com wrote:
On Oct 31, 1:05 pm, Dan Bode d...@puppetlabs.com wrote:
On Mon, Oct 31, 2011 at 10:55 AM, treydock treyd...@gmail.com wrote:
On Oct 31, 12:26 pm, Dan Bode d...@puppetlabs.com wrote:
you are running into a documentation issue. All of the
configuration was
moved to a new parameter called: config_hash. I can submit a patch
On Mon, Oct 31, 2011 at 10:01 AM, treydock treyd...@gmail.com
wrote:
I'm working to begin managing MySQL with the puppetlabs-mysql
provided
module, but am not able to get very far with the README
documentation.
So far, simply trying to add the server module and define the
root_password is failing like so,
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Invalid parameter root_password at /etc/puppet/manifests/
nodes.pp:882 on node puppetnode1.tld
The definition looks like this,
node 'puppetnode1.tld' {
class { 'mysql::server':
root_password = 'test'
}
should be changed to:
class { 'mysql::server':
config_hash = { root_password = 'test'}
}
database_user { 'treydock@localhost':
password_hash = mysql_password('pass')
}
database_grant { 'treydock@localhost/*':
privileges = ['ALL'],
}
mysql::db { 'zabbix':
user = 'zabbix',
password = 'zabbix',
host = 'localhost',
grant = ['ALL'],
}
}
The database_user and _grant thus far haven't actually done
anything.
I'm assuming it's because mysql::server isn't working or being
applied.
There's likely something very obvious I'm missing. This is also
my
first time using parameterized classes.
Thanks
- Trey
--
You received this message because you are subscribed to the
Google
Groups
Puppet Users group.
To post to this group, send email to
puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Ah that was it! Thanks.
Is there a way to similuate or run the equivilant of
mysql_secure_installation within this module? I tried an initial
attempt with the following...but once it's added to the mysql::server
class it never seems to get called...
what failed? How did you add it to the mysql::server class?
class mysql::server::secure {
database_user {
'':
ensure = absent,
require = Service['mysqld'];
root@${fqdn}:
ensure = absent,
require = Service['mysqld'];
}
database {
test:
ensure = absent,
require = Service['mysqld'];
}
}
Would the easier route be to just modify the
mysql_secure_installation
script to be more puppet friendly?
Thanks
- Trey
--
You received this message because you are subscribed to the Google
Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
It didn't fail, it just simply did nothing.
This is it's inclusion in mysql::server
class mysql::server(
$service_name = $mysql::params::service_name,
$config_hash = {},
$package_name = 'mysql-server'
) inherits mysql::params {
include mysql::server::secure
# automatically create a class to deal with
# configuration
$hash = {
mysql::config = $config_hash
}
I am doing it via Exec now anyways. Though I'd prefer to do it with
the new type and provider
- Trey
Slightly different question...is there a way to pass / store the hash
for the root password rather than the plain text password? Similar to
how the puppet user resource works?
I am not quite sure if mysql supports that. Could you open a ticket
here:http://projects.puppetlabs.com/projects/modulesand explain what the
implementation would look like?
thanks
Thanks
- Trey
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
[Puppet Users] ERB templates and escaping Apache virtual hosts
Is any special escaping necessary for URLs in ERB templates? For example, Puppet complains: bad URI(is not URI?) about the :80 and http:/// lines in a template like this: VirtualHost *:80 [...] RewriteRule ^/+(.*) http://example.com/$1 [L,R=permanent] /VirtualHost Ruby's uri.split() is the only place that raises this error, so I'm guessing it's some kind of URL escaping/quoting ERB wants to do. john -- John Morrissey _o/\ __o j...@horde.net_- \_ / \ \, www.horde.net/__(_)/_(_)/\___(_) /_(_)__ -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] minimize catalog to ensure upgrade?
we are having problems with incompatibility between older clients and newer
configuration syntax.
(in specific, user resource system attribute was added somewhere between
2.6.6 and 2.6.11)
It seems the right thing to do for older clients when they attach is to give
them a very short manifest that immediately upgrades them. I'm trying to
figure out how to do this. I want something like this at the top of site.pp
if $puppetversion == '2.6.6' {
class { upgradepuppet: }
stop-parsing-here
}
I'd rather avoid putting all the rest of site.pp inside an else statement if I
can.
--
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source and other
randomness
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] git hooks for pre-commit in puppet 2.7?
On Tue, Nov 1, 2011 at 12:50 PM, Rob Terhaar rob...@robbyt.net wrote: Hi All, Does anyone have a good git pre-commit hook that's compatible with Puppet 2.7? The example pre-commit hook on the PuppetLabs wiki[1] no longer works, because the puppet binary no longer seems to accept stdin. In 2.7 'puppet manifest.pp' is no longer supported (which is puppet apply manifest.pp), and --parseonly option has it's own face which you can find out more about via: puppet help parser I think you just need to change from: syntax_check=puppet --color=false --confdir=/tmp --vardir=/tmp --parseonly --ignoreimport syntax_check=puppet parser validate Thanks, Nan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
