search for: vagnscott

I''m running Puppet 2.7.1 on the master as well as the agent and just received a new error which doesn''t actually reference a module or a file, so I''m somewhat stuck as to how to debug this. Any pointers? The error is err: Could not retrieve catalog from remote server: Could not intern from pson: Could not convert from pson: Could not find relationship target

I''ve got this: file { ''/opt/sugarsync/tomcat/tomcat-home/current'': ensure => "tomcat-$config[''tomcat_version_server'']"; where $config[''tomcat_version_server''] was set with extlookup (the yaml one), by loading: --- tomcat_config: tomcat_version_server: 6.0.20-1 tomcat_version_libs: 1.0-1

Hi, I''m quite new to Puppet.. I''m wondering if someone could point me in the right direction regarding the best way to manage a temporary requirement within Puppet? The scenario is, every server in our estate of Debian machines requires some monitoring software which is not provided as a Debian package. So we have a Puppet class, monitor::install which we include to distribute

This may have been asked before, if so, please excuse me and point me to the right direction. What I want to do is to define a hash table with multiple key->value pairs. I would like to pass this variable to a file template and generate a result file with all the mappings listed. Based on what I read, I need to do it in a definition. But does Puppet supports loop over a hash? Any help would

Dear all, I''m trying to do this. Say for example, I want this link: "liblcgdm.so -> liblcgdm.so.1.8.0" to be present on the client only if "lcgdm- libs-1.8.0-1sec.sl5" is already listed. I already have this to create the link: file { ''liblcgdm.so'': ensure => symlink, name => ''/opt/lcg/lib/liblcgdm.so'',

prep for 2.8: scopes and variables: nodes are not classes I have been preparing for 2.8 by experimenting with 2.7.X and seeing what it takes to get rid of the warnings. I would like to share my results in a number of upcoming posts. Begin with the simple question of hard-wiring scopes. the ''shocking'' revelation is that variables defined in nodes are no longer visible