Re: [Puppet Users] Re: class + each do
On Thu, Mar 03, 2011 at 11:59:25PM -0800, aleksey_k wrote: # puppet agent --test Throw a --debug on the end, and it should be a whole more talkative! puppetmaster: #grep -i keys node/test-nodes.pp include keys You made a class for it? As it sounds like it's not getting called at all. -- Ben Hughes || http://www.puppetlabs.com/ -- 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] Trying to write a visudo checker
On Thu, 03 Mar 2011, Rich Rauenzahn wrote: It seems someone got clever and decided to look at exec's and look for managed filenames in argument lists and create implicit dependencies from them? Argh! Yes, the unwanted dependencies are very annoying. Using file names like /dir/subdir/./file instead of /dir/subdir/file is enough to fool the code that adds implicit dependencies. --apb (Alan Barrett) -- 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: class + each do
On 4 мар, 13:08, Ben Hughes b...@puppetlabs.com wrote:
On Thu, Mar 03, 2011 at 11:59:25PM -0800, aleksey_k wrote:
# puppet agent --test
Throw a --debug on the end, and it should be a whole more talkative!
Outpu here - http://pastebin.com/0GHfkH63
You made a class for it? As it sounds like it's not getting called at all.
Yes.I did a class for this:
class keys {
define userkey() {
file { /etc/file/keys/${name}_keys:
#ensure = ,
owner = $name,
group = root,
mode= 440,
replace = true,
source = puppet://server/files/file/keys/${name}
_keys,
require = User[$name],
}
userkey{ [user1,user2,user3]:
}
}
--
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: Darned PSON Message!
Sorry Jed I didn't realise that you didn't know about .puppet directories. A .puppet directory is created in your home directory if you accidentally run puppet as yourself and not as root. The problem that I had was that sometimes puppetd was correctly reading SSL settings from /var/lib/puppet/ssl and sometimes from ~/.puppet/ssl (I started puppet sudo'ed from my account). But I don't think that this is Douglas' problem as he is only getting his error occasionally whereas mine was happening once every three or four runs at the beginning and then increased in frequency. But still my experience might help a bit as I found that, at least in my case, no PSON meant actually meant no content at all was fetched from the puppetmaster. And the place to look to see if that is the case is the web server log on the master (in /var/log/puppet or whatever). I hope that this helps. On Mar 4, 4:55 am, Jed jedbl...@gmail.com wrote: Hi doug, I've been getting this as well , someone suggested searching the entire filesystem on the client for a directory called .puppet and delete any found. I haven't tried this yet though On Mar 3, 2:36 pm, Douglas Garstang doug.garst...@gmail.com wrote: I'm sure it must already be a known bug, but I've been getting this message frequently on the clients: Could not retrieve catalog from remote server: Could not intern from pson: source did not contain any PSON! Happens erratically but it's frequency seems to have increased with my upgrade from 2.6.3 to 2.6.4. Getting rather sick of it because I have to restart the client multiple times to get it to stop. Doug. -- 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: class + each do
On 03/04/2011 09:08 AM, Ben Hughes wrote: On Thu, Mar 03, 2011 at 11:59:25PM -0800, aleksey_k wrote: # puppet agent --test Throw a --debug on the end, and it should be a whole more talkative! puppetmaster: #grep -i keys node/test-nodes.pp include keys You made a class for it? As it sounds like it's not getting called at all. On such occasions, I prefer --test --evaltrace over --debug. Your files should show up in there. If not, your manifest is probably erronous. 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.
[Puppet Users] Storeconfigs: facts not updated
Hi, I run the Puppetmaster with storeconfigs = true thin_storeconfigs = true dbadapter = mysql So far, this has been working perfectly, but today I noticed something odd. Yesterday, I upgraded one of my nodes from Ubuntu Jaunty to Lucid, but the facts from this node aren't updated in the database. For example, the database still said (and notice the timestamps, they are current!): 2011-03-04 11:39:05 kernelrelease 2.6.28-17-server 2011-03-04 11:39:05 lsbdistcodename jaunty 2011-03-04 11:39:05 lsbdistdescription Ubuntu 9.04 While 'facter' on the machine itself correctly reports: kernelrelease = 2.6.32-29-generic-pae lsbdistcodename = lucid lsbdistdescription = Ubuntu 10.04.2 LTS Then I thought I'd just remove all the facts from the database, to have Puppet refresh them, so I did delete FROM `fact_values` where host_id=27. On the next Puppet run, I got: err: Could not retrieve catalog from remote server: Error 400 on SERVER: No matching value for selector param 'undef' at /etc/puppet/manifests/site.pp:37 on node abcxyz. This error refers to a selector that uses the fact $operatingsystem, which now appears to be 'undef'. Now, if I completely disable storeconfigs on the master, a Puppet run succeeds like ever before, but as soon as storeconfigs is re-enabled, the 'undef' error returns. What could be the cause of this? One thing possibly worth mentioning: this node runs the Puppetmaster. No idea if that makes a difference. Everything is version 2.6.3. Regards, Martijn. -- 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] Storeconfigs: facts not updated
After completely deleting the node from the database's 'host' table and resources that referenced its host_id, a following catalog run refreshed the database, adding all facts with their current values... Best regards, Martijn. On 04-03-11 12:43, Martijn Grendelman wrote: Hi, I run the Puppetmaster with storeconfigs = true thin_storeconfigs = true dbadapter = mysql So far, this has been working perfectly, but today I noticed something odd. Yesterday, I upgraded one of my nodes from Ubuntu Jaunty to Lucid, but the facts from this node aren't updated in the database. For example, the database still said (and notice the timestamps, they are current!): 2011-03-04 11:39:05 kernelrelease 2.6.28-17-server 2011-03-04 11:39:05 lsbdistcodename jaunty 2011-03-04 11:39:05 lsbdistdescriptionUbuntu 9.04 While 'facter' on the machine itself correctly reports: kernelrelease = 2.6.32-29-generic-pae lsbdistcodename = lucid lsbdistdescription = Ubuntu 10.04.2 LTS Then I thought I'd just remove all the facts from the database, to have Puppet refresh them, so I did delete FROM `fact_values` where host_id=27. On the next Puppet run, I got: err: Could not retrieve catalog from remote server: Error 400 on SERVER: No matching value for selector param 'undef' at /etc/puppet/manifests/site.pp:37 on node abcxyz. This error refers to a selector that uses the fact $operatingsystem, which now appears to be 'undef'. Now, if I completely disable storeconfigs on the master, a Puppet run succeeds like ever before, but as soon as storeconfigs is re-enabled, the 'undef' error returns. What could be the cause of this? One thing possibly worth mentioning: this node runs the Puppetmaster. No idea if that makes a difference. Everything is version 2.6.3. Regards, Martijn. -- 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: postfix module problems
On Mar 3, 10:38 pm, Ramin K ramin.khat...@gmail.com wrote:
source = puppet:///postfix/aliases.db; --- I don't think you need
the ; anywhere. You've got a a few of them.
They are not necessary in that context, but they are valid and
harmless. They are needed when you want to put multiple resources
into the same declaration, like so:
package {
my-package1: ensure = latest;
my-package2: ensure = 0.42;
your-package3: ensure = absent;
# The last semicolon is optional
}
Of course, you can specify as many properties as you like for each
resource.
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] postfix module problems
On 03/03/11 21:14, Tim Dunphy wrote: hello list!! I am having some trouble with a postfix module I am attempting to implement. as always, your input is extremely valuable and would be appreciated here's what's going on: ## errors err: //postfix/Package[postfix-pflogsum.x86_64]/ensure: change from absent to present failed: Could not find package postfix-pflogsum.x86_64 notice: //postfix/Cron[pflogsum]: Dependency package[postfix-pflogsum.x86_64] has 1 failures warning: //postfix/Cron[pflogsum]: Skipping because of failed dependencies err: //postfix/Service[postfix]/ensure: change from stopped to running failed: Could not start Service[postfix]: Execution of '/sbin/service postfix start' returned 1: at /etc/puppet/modules/postfix/manifests/init.pp:35 err: //postfix/File[/etc/aliases.db]: Failed to retrieve current state of resource: Error 400 on SERVER: Permission denied - /etc/puppet/modules/postfix/files/aliases.db Could not retrieve file metadata for puppet:///postfix/aliases.db: Error 400 on SERVER: Permission denied - /etc/puppet/modules/postfix/files/aliases.db at /etc/puppet/modules/postfix/manifests/init.pp:17 As you can see pflogsum is not being installed and the postfix service is not starting. also the aliases.db file that I am attempting to share doesn't get transferred. although ## ls of files [root@puppet ~]# ls -l /etc/puppet/modules/postfix/files/aliases.db -rw-r- 1 root root 12288 Mar 2 16:18 /etc/puppet/modules/postfix/files/aliases.db Is your puppetmaster running as root? It's unlikely. You either want to change the owner or chmod o+r. HTH, Dan -- 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] postfix module problems
Hi Dan, the puppetmaster daemon is not running as root, however I have other modules running on this machine and a files directory in each that all have the same exact ownership and permissions and are being shared without any problems. tim On Fri, Mar 4, 2011 at 9:18 AM, Daniel Piddock dgp-g...@corefiling.co.uk wrote: On 03/03/11 21:14, Tim Dunphy wrote: hello list!! I am having some trouble with a postfix module I am attempting to implement. as always, your input is extremely valuable and would be appreciated here's what's going on: ## errors err: //postfix/Package[postfix-pflogsum.x86_64]/ensure: change from absent to present failed: Could not find package postfix-pflogsum.x86_64 notice: //postfix/Cron[pflogsum]: Dependency package[postfix-pflogsum.x86_64] has 1 failures warning: //postfix/Cron[pflogsum]: Skipping because of failed dependencies err: //postfix/Service[postfix]/ensure: change from stopped to running failed: Could not start Service[postfix]: Execution of '/sbin/service postfix start' returned 1: at /etc/puppet/modules/postfix/manifests/init.pp:35 err: //postfix/File[/etc/aliases.db]: Failed to retrieve current state of resource: Error 400 on SERVER: Permission denied - /etc/puppet/modules/postfix/files/aliases.db Could not retrieve file metadata for puppet:///postfix/aliases.db: Error 400 on SERVER: Permission denied - /etc/puppet/modules/postfix/files/aliases.db at /etc/puppet/modules/postfix/manifests/init.pp:17 As you can see pflogsum is not being installed and the postfix service is not starting. also the aliases.db file that I am attempting to share doesn't get transferred. although ## ls of files [root@puppet ~]# ls -l /etc/puppet/modules/postfix/files/aliases.db -rw-r- 1 root root 12288 Mar 2 16:18 /etc/puppet/modules/postfix/files/aliases.db Is your puppetmaster running as root? It's unlikely. You either want to change the owner or chmod o+r. HTH, Dan -- 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. -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B -- 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: NFS mount problem
I manually created the mount points and incorrectly assumed the mount process would automatically create the point if it didn't exist. Once a managed mount point is no longer needed, we want the NFS mount its directory removed from the client -- if we need them again, I can just keep them commented out in the code. Can you explain the wrap you were talking about? Thanks! -- 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: plusignment to add values to a resource several times
I have hit a similar issue. Does anybody know if this is going to be fixed or some workaround present? -- 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: NFS mount problem
I manually created the mount points and incorrectly assumed the mount process would automatically create the point if it didn't exist. Once a managed mount point is no longer needed, we want the NFS mount its directory removed from the client -- if we need them again, I can just keep them commented out in the code. Can you explain the wrap you were talking about? Thanks! -- 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: NFS mount problem
On Thu, Mar 03, 2011 at 07:38:28PM -0800, Forrie wrote:
I'm trying to figure out how to manage the NFS mounts, then 'unmanage'
them when we're done -- ie: remove the NFS mount (ensure = absent)
and make sure the mount point on the client is removed.
I thought for the mount{} portion of this and loop over it. But it's
not a big deal, I don't mind editing them manually for now.
So are you saying for the absent items, we'll need to include a
file{} directive to remove the mount point, too?
yes. And remember to put a require in there because you don't want to
purge the mountpoint when umounting failed. Can turn out pretty bad
for NFS mounts you need elsewhere ;-)
# Creation
file { '/mnt/foo': ensure = directory }
mount { '/mnt/foo':
device = ...,
ensure = mounted,
require = File['/mnt/foo'],
}
# Delete (i think force is needed here)
file { '/mnt/foo': ensure = absent, force = true}
mount { '/mnt/foo':
ensure = absent,
before = File['/mnt/foo'],
}
-Stefan
pgppY0mGvvljw.pgp
Description: PGP signature
[Puppet Users] Puppet dsl
Is the puppet dsl a complete Turing capable language? As I understand it, the chain is dsl - compiled thing - actions. What language is the compiled thing in? Ruby? -- 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: class + each do
On Fri, Mar 04, 2011 at 02:24:59AM -0800, aleksey_k wrote:
On 4 мар, 13:08, Ben Hughes b...@puppetlabs.com wrote:
On Thu, Mar 03, 2011 at 11:59:25PM -0800, aleksey_k wrote:
# puppet agent --test
Throw a --debug on the end, and it should be a whole more talkative!
Outpu here - http://pastebin.com/0GHfkH63
You made a class for it? As it sounds like it's not getting called at all.
Yes.I did a class for this:
Your code
01 class keys {
02 define userkey() {
03file { /etc/file/keys/${name}_keys:
04 #ensure = ,
05 owner = $name,
06 group = root,
07 mode= 440,
08 replace = true,
09 source = puppet://server/files/file/keys/${name}_keys,
10 require = User[$name],
11}
12
13 userkey{ [user1,user2,user3]: }
14
15 }
My comments
04: Use `ensure = file` so it is clear that something will be created
08: replace = true is the default so I wont specify it
09: Are you using modules? Maybe you're specifying an incorrect path. Have
a look at http://docs.puppetlabs.com/guides/modules.html and
http://docs.puppetlabs.com/guides/file_serving.html
10: When you specify the owner of the file, puppet will create an
implicit require you dont dont need that explicit require
12: There is a missing closing bracket for the define
-Stefan
pgpIGlyfZy6Uf.pgp
Description: PGP signature
Re: [Puppet Users] Puppet dsl
On Fri, Mar 4, 2011 at 8:50 AM, Kevin Beckford lazy...@gmail.com wrote: Is the puppet dsl a complete Turing capable language? Puppet is not a general purpose programming language, it is a tool that manages infrastructure, you could probably mathematically prove that it is Turing complete, but its end result is a single data format. Perhaps it would be better to ask can Puppet do X As I understand it, the chain is dsl - compiled thing - actions. Architecturally, it is better to think of Puppet as a system that can transform between various data formats: Code that creates data: Data: Facts Terminus (Facter) Facts: Node Terminus Nodes Catalog Terminus (compiler) Catalog Resource Abstraction Layer Events What language is the compiled thing in? Ruby? The compiled artifact is not code, it is data that describes the desired state of your system, in the above chart, the artifact you are asking about is the catalog. -- 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] Re: Darned PSON Message!
Bill Proud wrote: Sorry Jed I didn't realise that you didn't know about .puppet directories. A .puppet directory is created in your home directory if you accidentally run puppet as yourself and not as root. The problem that I had was that sometimes puppetd was correctly reading SSL settings from /var/lib/puppet/ssl and sometimes from ~/.puppet/ssl (I started puppet sudo'ed from my account). But I don't think that this is Douglas' problem as he is only getting his error occasionally whereas mine was happening once every three or four runs at the beginning and then increased in frequency. But still my experience might help a bit as I found that, at least in my case, no PSON meant actually meant no content at all was fetched from the puppetmaster. And the place to look to see if that is the case is the web server log on the master (in /var/log/puppet or whatever). Check the /var/log/puppet/masterhttp.log. Regards James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 -- 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] Trying to write a visudo checker
On 3/4/2011 12:23 AM, Alan Barrett wrote: On Thu, 03 Mar 2011, Rich Rauenzahn wrote: It seems someone got clever and decided to look at exec's and look for managed filenames in argument lists and create implicit dependencies from them? Argh! Yes, the unwanted dependencies are very annoying. Using file names like /dir/subdir/./file instead of /dir/subdir/file is enough to fool the code that adds implicit dependencies. Ah, what I did instead was just do exec = diff /.$path1 /.$path2. I was imagining doing much more invasive methods last night. Thanks! -- 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] dashboard packaging issue: private copy of ruby gem
Hello. I'm trying to make a dashboard package for mandriva linux, but I'm having some issues with the private copy of rack ruby gem shipped with dashboard. When installed on the same host as the puppetmaster, running itself with passenger, it conflicts with the system version of this gem, required by puppetmaster: can't activate rack (~ 1.0.1, runtime) for [], already activated rack-1.1.0 for [passenger-2.2.9] I had to comment the line forcing the rack version in lib/action_controller.rb to make it work with system wide version. Shipping private copies is usually considered a bad practice by packagers, because of the difficulties to ensure updating, here it seems to be even harmful. So, is there an actual reason to force this version ? -- BOFH excuse #23: improperly oriented keyboard -- 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] learning, but puppet does not detect change
Hi,
My site.pp:
[root@S manifests]# cat /etc/puppet/manifests/site.pp
import nodes.pp
[root@S manifests]#
I copied ntp.pp into init.pp as you've suggested:
[root@S manifests]# cp ntp.pp init.pp
[root@S manifests]# diff ntp.pp init.pp
[root@S manifests]#
I started the server as follows:
[root@S training]# puppet master --debug
The results of running the command normally:
[root@S ~]# puppet agent --test --server=S.domain.com
info: Caching catalog for S.domain.com
info: Applying configuration version '1299265059'
notice: Finished catalog run in 0.07 seconds
[root@S ~]#
with the (master) output in the log file as:
Mar 4 14:07:50 S puppet-master[5716]: Expiring the node cache of
S.domain.com
Mar 4 14:07:50 S puppet-master[5716]: Not using expired node for
S.domain.com from cache; expired at Fri Mar 04 14:06:50 -0500 2011
Mar 4 14:07:50 S puppet-master[5716]: Caching node for S.domain.com
Mar 4 14:07:51 S puppet-master[5716]: Compiled catalog for S.domain.com in
environment production in 0.24 seconds
Mar 4 14:07:51 S puppet-agent[7169]: Caching catalog for S.domain.com
Mar 4 14:07:51 S puppet-agent[7169]: Applying configuration version
'1299265059'
Mar 4 14:07:51 S puppet-agent[7169]: Finished catalog run in 0.07 seconds
The output from your suggested command (with -d -v) provided as an
attachment.
root@S manifests]# puppet agent --test --server=S.domain.com -d -v
/tmp/bar.txt
[root@S manifests]# wc -l /tmp/bar.txt
214 /tmp/bar.txt
[root@S manifests]#
Thanks very much for any help,
Mark
On Sat, Feb 26, 2011 at 10:15 PM, yzhk...@gmail.com yzhk...@gmail.com
wrote:
1、site.pp: import nodes.pp
2、ntp.ppshould be $module_path/manifests/init.pp
3、puppet agent --test --server=S -d -v
Have a look
at
http://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Best_Practice
On Sun, Feb 27, 2011 at 8:01 AM, mark bradley gopearl...@gmail.com
wrote:
Hi,
I've just installed Puppet on two CentOS 5.5 servers, S for A. A
does not have the ntp package installed nor of course ntp running.
The Puppet server is started on S with the ntp class from this
tutorial: http://bitfieldconsulting.com/puppet-tutorial (included
below) however when I run the agent on A it don't produce a notice
that a change needs to be applied:
root@A ~]# puppet agent --test --server=S
info: Caching catalog for A.domain.com
info: Applying configuration version '1298756440'
notice: Finished catalog run in 0.07 seconds
[root@A ~]#
Apparently it should not notifying me that ntp needs to be installed
and started.
ntp.pp on S:
class ntp {
package { ntp:
ensure = installed
}
service { ntp:
ensure = running
}
}
nodes.pp on S:
node A {
include ntp
}
Did I miss some crucial set in the installation or configuration? I
know it's seeing the files since if I introduce syntax errors into
them Puppet complains.
Thanks for any help,
Mark
--
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.
--
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.
debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does not exist
debug: Puppet::Type::User::ProviderPw: file pw 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::ProviderDirectoryservice: file /usr/bin/dscl does
not exist
debug: Failed to load library 'rubygems' for feature 'rubygems'
debug: Puppet::Type::File::ProviderMicrosoft_windows: feature microsoft_windows
is missing
debug: /File[/etc/puppet/ssl/private_keys/S.domain.com.pem]/seluser: Found
seluser default 'system_u' for /etc/puppet/ssl/private_keys/S.domain.com.pem
debug: /File[/etc/puppet/ssl/private_keys/S.domain.com.pem]/selrole: Found
selrole default 'object_r' for /etc/puppet/ssl/private_keys/S.domain.com.pem
debug: /File[/etc/puppet/ssl/private_keys/S.domain.com.pem]/seltype: Found
seltype default 'etc_t' for /etc/puppet/ssl/private_keys/S.domain.com.pem
debug:
[Puppet Users] Re: Puppet dsl
On Mar 4, 9:18 am, Dan Bode d...@puppetlabs.com wrote: What language is the compiled thing in? Ruby? The compiled artifact is not code, it is data that describes the desired state of your system, in the above chart, the artifact you are asking about is the catalog. *nods.* The catalog is just a directed acyclic graph describing resources and dependencies, which then gets serialized via a common text data format. It isn't code; it's a document, which gets consumed by code that knows how to generate events from resources. -- 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] Role-based access in Dashboard
Denmat wrote: Very high level but I would like to see the following: • to be able to create roles such as viewer, editor, administrator • these roles be ldap groups Den, will you tell me more about roles being LDAP groups? To my perception that could mean: * Manually creating a role in Dashboard and associating it with an LDAP group, * Importing groups from LDAP to then manipulate as roles in Dashboard, * LDAP groups being read-only in Dashboard and represented as roles, * something else I've not considered. Thank you, 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.
