[Puppet Users] Custom ensure instead of ensurable in type provider
Hi, I'm currently writing a custom type for managing Windows environment variables. A variable should be (re-)created if it doesn't exist or the value doesn't match the desired value. So exists? checks exactly this. It returns true only if the variable exists and the value matches. This, however, creates a problem when the variable should be destroyed. When destroying a variable, I don't care for the value anymore. I just need to know wether it exists or not. So I need to different tests (existswithvalue? and exists?). My problem now is that I don't know how to implement "ensure" for this case, as I cannot use "ensurable" in the type. Thanks... Dirk -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Custom ensure instead of ensurable in type provider
Am Mittwoch, 13. März 2013 17:00:18 UTC+1 schrieb jcbollinger:
>
>
> My problem now is that I don't know how to implement "ensure" for this
>> case, as I cannot use "ensurable" in the type.
>>
>
> Your problem is that you are conflating distinct (for your purposes)
> aspects of your resource's state. If you care at times whether the
> variable is declared at all or not, and at other times what its value is,
> then those should be separate properties. Your resource declarations will
> then look like this:
>
> env_var { 'AWESOMENESS':
> value => 'meh',
> # optional:
> ensure => present
> }
>
> or
>
> env_var { 'AWESOMENESS':
> ensure => absent
> }
>
I've changed the logic of exists? a bit to reflect this, and it works.
However, one has to remember not to provide a value if "ensure => absent"
was specified. Or is there a way to check this in the provider?
Thanks...
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] exec resource not refreshed when subscribed resource changes
Hello,
I've created a little class which should unpack a 7z archive on Windows.
The class has a parameter for passing in the archive version, so that I can
trigger an update when a new version of the archive is available. A
simplyfied version looks like this (requires 7z):
class my_archive ($version = undef) {
file { 'version':
path => 'C:/the_version',
content => $version,
ensure => present,
mode => 0666,
}
# Extracting archive creates C:/some/dir
exec { 'unpack_archive':
command => "cmd /c rmdir /S /Q C:\some/dir & 7z x -oC:/some
C:/path/to/archive-${version}.7z",
creates => 'C:/some/dir/a_file',
require => File['version'],
path => $::path,
subscribe => File['version'],
}
}
I trigger this from site.pp like so:
class { 'my_archive':
version => '1.2.3'
}
The initial unpacking of (an older version of) the archive works fine, but
when I change the version, I see that this change is recognized by the
agent and a refresh is triggered, but the command isn't executed:
Info: /Stage[main]/My_archive/File[version]: Filebucketed C:/the_version to
puppet with sum 185910a1e94c599dc6541266286675bc
Notice: /Stage[main]/My_archive/File[version]/content: content changed
'{md5}185910a1e94c599dc6541266286675bc' to
'{md5}d0cdd9a6594750ea1063643fcda90d3b'
Debug: /Stage[main]/My_archive/File[version]: The container
Class[My_archive] will propagate my refresh event
Info: /Stage[main]/My_archive/File[version]: Scheduling refresh of
Exec[unpack_archive]
Debug: /Schedule[weekly]: Skipping device resources because running on a
host
Debug: Prefetching windows resources for package
Notice: /Stage[main]/My_archive/Exec[unpack_archive]: Triggered 'refresh'
from 1 events
Debug: /Stage[main]/My_archive/Exec[unpack_archive]: The container
Class[My_archive] will propagate my refresh event
Debug: Class[My_archive]: The container Stage[main] will propagate my
refresh event
Debug: /Schedule[puppet]: Skipping device resources because running on a
host
Debug: Finishing transaction 144533424
Debug: Storing state
Debug: Stored state in 0.06 seconds
Notice: Finished catalog run in 0.75 seconds
I tried to omit "creates => ...", but this only makes the agent run the
resource every time. I also tried adding "refreshonly => true", but this
doesn't help. I even tried adding "refresh => ..." with the exact same
command without any change in behaviour.
Any hints what could be wrong?
Puppet Agent version on Windows is 3.1.0.
Thanks...
Dirk
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: exec resource not refreshed when subscribed resource changes
Am Donnerstag, 14. März 2013 08:56:31 UTC+1 schrieb dirk.he...@altum.de:
>
> Hello,
>
> I've created a little class which should unpack a 7z archive on Windows.
> The class has a parameter for passing in the archive version, so that I can
> trigger an update when a new version of the archive is available. A
> simplyfied version looks like this (requires 7z):
>
> class my_archive ($version = undef) {
> file { 'version':
> path => 'C:/the_version',
> content => $version,
> ensure => present,
> mode => 0666,
> }
>
> # Extracting archive creates C:/some/dir
> exec { 'unpack_archive':
> command => "cmd /c rmdir /S /Q C:\some/dir & 7z x -oC:/some
> C:/path/to/archive-${version}.7z",
> creates => 'C:/some/dir/a_file',
> require => File['version'],
> path => $::path,
> subscribe => File['version'],
> }
> }
>
> I trigger this from site.pp like so:
>
> class { 'my_archive':
> version => '1.2.3'
> }
>
> The initial unpacking of (an older version of) the archive works fine, but
> when I change the version, I see that this change is recognized by the
> agent and a refresh is triggered, but the command isn't executed:
>
> Info: /Stage[main]/My_archive/File[version]: Filebucketed C:/the_version
> to puppet with sum 185910a1e94c599dc6541266286675bc
> Notice: /Stage[main]/My_archive/File[version]/content: content changed
> '{md5}185910a1e94c599dc6541266286675bc' to
> '{md5}d0cdd9a6594750ea1063643fcda90d3b'
> Debug: /Stage[main]/My_archive/File[version]: The container
> Class[My_archive] will propagate my refresh event
> Info: /Stage[main]/My_archive/File[version]: Scheduling refresh of
> Exec[unpack_archive]
> Debug: /Schedule[weekly]: Skipping device resources because running on a
> host
> Debug: Prefetching windows resources for package
> Notice: /Stage[main]/My_archive/Exec[unpack_archive]: Triggered 'refresh'
> from 1 events
> Debug: /Stage[main]/My_archive/Exec[unpack_archive]: The container
> Class[My_archive] will propagate my refresh event
> Debug: Class[My_archive]: The container Stage[main] will propagate my
> refresh event
> Debug: /Schedule[puppet]: Skipping device resources because running on a
> host
> Debug: Finishing transaction 144533424
> Debug: Storing state
> Debug: Stored state in 0.06 seconds
> Notice: Finished catalog run in 0.75 seconds
>
> I tried to omit "creates => ...", but this only makes the agent run the
> resource every time. I also tried adding "refreshonly => true", but this
> doesn't help. I even tried adding "refresh => ..." with the exact same
> command without any change in behaviour.
>
> Any hints what could be wrong?
>
> Puppet Agent version on Windows is 3.1.0.
>
Got it: Omitting "creates" AND adding "refreshonly => true" makes the class
work as desired.
Bye...
Dirk
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Windows Puppet waits for , then warns "Facter::Util::Resolution.exec with a shell built-in is deprecated"
On Fri, Apr 12, 2013 at 12:23:45PM -0700, Larry Fast wrote:
> Windows NuBQ:
> I'm running windows with a clean install of puppet and an empty node
> definition. puppet agent -t pauses with no prompt. When I hit enter, I
> get this warning:
>
> Using Facter::Util::Resolution.exec with a shell built-in is deprecated.
> Most built-ins can be replaced with native ruby commands. If you really
> have to run a built-in, pass "cmd /c your_builtin" as a command
>
> How do I fix/disable this warning?
I'm facing a similar problem, on one single Windows machine out of
more than 100. If I run any puppet command, I get above warning.
Additionally, it can't execute the following simple class to update the
puppet.conf file:
class puppetconf {
service { 'PuppetAgent':
name => 'puppet',
ensure => 'running',
enable => 'true',
subscribe => File['puppet.conf'],
}
file { 'puppet.conf':
path => 'C:/ProgramData/PuppetLabs/puppet/etc/puppet.conf',
ensure => file,
source => 'puppet:///modules/puppetconf/puppet.conf',
}
}
It fails with the following error:
Error: /Service[PuppetAgent]: Could not evaluate: Could not find init script
for 'puppet'
It looks like it somehow thinks it isn't running on a Windows machine.
I've read this thread but the solution given here doesn't apply to my
setup. There are no custom facts added, and the few modules installed
from PuppetForge work fine on all the other machines.
Anything else I could do to resolve this issue?
Thanks...
Dirk
--
Dirk Heinrichs
Tel: +49 (0)2471 209385 | Mobil: +49 (0)176 34473913
GPG Public Key C2E467BB | Jabber: dirk.heinri...@altum.de
signature.asc
Description: Digital signature
Re: [Puppet Users] Windows Puppet waits for , then warns "Facter::Util::Resolution.exec with a shell built-in is deprecated"
On Sat, Apr 20, 2013 at 01:55:46PM +0200, Stefan Schulte wrote:
> We'll first try to get a clearer error message. Please go to your facter
> installation directory on your agent and modify the file
> `util/resolution.rb`. Change
>
> Facter.warnonce 'Using Facter::Util::Resolution.exec with a shell built-in is
> deprecated. Most built-ins can be replaced with native ruby commands. If you
> really have to run a built-in, pass "cmd /c your_builtin" as a command'
> unless expanded_code
>
> to
>
> Facter.warnonce "Using Facter::Util::Resolution.exec with a shell built-in
> (here: #{code}) is deprecated. Most built-ins can be replaced with native
> ruby commands. If you really have to run a built-in, pass \"cmd /c
> your_builtin\" as a command" unless expanded_code
>
> Then run your agent again. This way you should see the command that
> puppet complains about.
It's actually three commands:
C:\Program Files (x86)\Puppet Labs\Puppet\bin>puppet agent -t
Using Facter::Util::Resolution.exec with a shell built-in (here: hostname) is
deprecated. Most built-ins can be replaced with native ruby commands. If you
really have to run a built-in, pass "cmd /c your_builtin" as a command
Info: Retrieving plugin
Using Facter::Util::Resolution.exec with a shell built-in (here: arp -a) is
deprecated. Most built-ins can be replaced with native ruby commands. If you
really have to run a built-in, pass "cmd /c your_builtin" as a command
Info: Loading facts in
C:/ProgramData/PuppetLabs/puppet/var/lib/facter/facter_dot_d.rb
Info: Loading facts in
C:/ProgramData/PuppetLabs/puppet/var/lib/facter/pe_version.rb
Info: Loading facts in
C:/ProgramData/PuppetLabs/puppet/var/lib/facter/puppet_vardir.rb
Info: Loading facts in
C:/ProgramData/PuppetLabs/puppet/var/lib/facter/root_home.rb
Using Facter::Util::Resolution.exec with a shell built-in (here: whoami) is
deprecated. Most built-ins can be replaced with native ruby commands. If you
really have to run a built-in, pass "cmd /c your_builtin" as a command
Info: Caching catalog for
Info: Applying configuration version '1366367977'
Error: /Service[PuppetAgent]: Could not evaluate: Could not find init script
for 'puppet'
Notice: Finished catalog run in 0.43 seconds
> > Error: /Service[PuppetAgent]: Could not evaluate: Could not find init
> > script for 'puppet'
>
> Can you provide the output of your agent when you run with `--debug`?
> This way we should be able to see the actual provider the agent picks
> for the service resource.
See attachment.
> Also the output of the following command would be helpful
>
> facter operatingsystem
>
> the above command should return "windows"
Prints: windows
> net.exe
>
> the above command should be found. If not please check your path
> (try running `facter path`)
Ah, it's not found. But the path looks good to me (I'm not a Windows
expert, though):
C:\Program Files (x86)\Puppet Labs\Puppet\bin>facter path
C:\Program Files (x86)\Puppet Labs\Puppet\puppet\bin;C:\Program Files
(x86)\Puppet Labs\Puppet\facter\bin;C:\Program Files (x86)\Puppet
Labs\Puppet\hiera\bin;C:\Program Files (x86)\Puppet Labs\Puppet\bin;C:\Program
Files (x86)\Puppet Labs\Puppet\sys\ruby\bin;C:\Program Files (x86)\Puppet
Labs\Puppet\sys\tools\bin;C:\Program Files (x86)\Puppet
Labs\Puppet\puppet\bin;C:\Program Files (x86)\Puppet
Labs\Puppet\facter\bin;C:\Program Files (x86)\Puppet
Labs\Puppet\hiera\bin;C:\Program Files (x86)\Puppet Labs\Puppet\bin;C:\Program
Files (x86)\Puppet Labs\Puppet\sys\ruby\bin;C:\Program Files (x86)\Puppet
Labs\Puppet\sys\tools\bin;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0;%SystemRoot%\System32\Wbem;%SystemRoot%\system32;D:\Recommind\program\bin64;D:\Recommind\program\bin32\minicygwin;D:\Recommind\program\bin32;D:\Recommind\program\bat\system;D:\Recommind\program\bat;D:\Recommind\jdk\bin;D:\Recommind\jdk32\bin;D:\Recommind\JRuby\bin;D:\Recommind\Downloads\bat;%PATH%
Bye...
Dirk
--
Dirk Heinrichs
Tel: +49 (0)2471 209385 | Mobil: +49 (0)176 34473913
GPG Public Key C2E467BB | Jabber: dirk.heinri...@altum.de
Using Facter::Util::Resolution.exec with a shell built-in (here: hostname) is
deprecated. Most built-ins can be replaced with native ruby commands. If you
really have to run a built-in, pass "cmd /c your_builtin" as a command
[0;36mDebug: Failed to load library 'syslog' for feature 'syslog'[0m
[0;36mDebug: Failed to load library 'selinux' for feature 'selinux'[0m
[0;36mDebug: Using settings: adding file resource 'lastrunfile':
'File[C:/ProgramData/PuppetLabs/puppet/var/state/last_run_summary.yaml]{:loglevel=>:debug,
:ensure=>:file, :links=>:follow, :backup=>false, :mode=
Re: [Puppet Users] Windows Puppet waits for , then warns "Facter::Util::Resolution.exec with a shell built-in is deprecated"
On Mon, Apr 22, 2013 at 08:58:31AM +0200, Dirk Heinrichs wrote: > C:\Program Files (x86)\Puppet Labs\Puppet\bin>facter path > C:\Program Files (x86)\Puppet Labs\Puppet\puppet\bin;C:\Program Files > (x86)\Puppet Labs\Puppet\facter\bin;C:\Program Files (x86)\Puppet > Labs\Puppet\hiera\bin;C:\Program Files (x86)\Puppet > Labs\Puppet\bin;C:\Program Files (x86)\Puppet > Labs\Puppet\sys\ruby\bin;C:\Program Files (x86)\Puppet > Labs\Puppet\sys\tools\bin;C:\Program Files (x86)\Puppet > Labs\Puppet\puppet\bin;C:\Program Files (x86)\Puppet > Labs\Puppet\facter\bin;C:\Program Files (x86)\Puppet > Labs\Puppet\hiera\bin;C:\Program Files (x86)\Puppet > Labs\Puppet\bin;C:\Program Files (x86)\Puppet > Labs\Puppet\sys\ruby\bin;C:\Program Files (x86)\Puppet > Labs\Puppet\sys\tools\bin;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0;%SystemRoot%\System32\Wbem;%SystemRoot%\system32;D:\Recommind\program\bin64;D:\Recommind\program\bin32\minicygwin;D:\Recommind\program\bin32;D:\Recommind\program\bat\system;D:\Recommind\program\bat;D:\Recommind\jdk\bin;D:\Recommind\jdk32\bin;D:\Recommind\JRuby\bin;D:\Recommind\Downloads\bat;%PATH% Found it: The two occurrences of %SystemRoot% should really be %SYSTEMROOT%. Fixed it, works now. Bye... Dirk -- Dirk Heinrichs Tel: +49 (0)2471 209385 | Mobil: +49 (0)176 34473913 GPG Public Key C2E467BB | Jabber: dirk.heinri...@altum.de signature.asc Description: Digital signature
Re: [Puppet Users] Windows Puppet waits for , then warns "Facter::Util::Resolution.exec with a shell built-in is deprecated"
On Mon, Apr 22, 2013 at 12:45:35AM -0700, Paul Tötterman wrote: > Shouldn't environment variables be case-insensitive? What code is > responsible for expanding those environment variables? This is Windows, so I'd say: "It depends". I can do this: C:\Program Files (x86)\Puppet Labs\Puppet\bin>echo %SYSTEMROOT% C:\Windows C:\Program Files (x86)\Puppet Labs\Puppet\bin>echo %SYSTEMRoot% C:\Windows But, as seen, expanding %SYSTEMROOT% in %PATH% only seems to work when it's all uppercase... And I still hear people whining how complicated this Linux thing is... Bye... Dirk -- Dirk Heinrichs Tel: +49 (0)2471 209385 | Mobil: +49 (0)176 34473913 GPG Public Key C2E467BB | Jabber: dirk.heinri...@altum.de signature.asc Description: Digital signature
Re: [Puppet Users] dynamic /etc/hosts
Am 20.01.2014 07:52, schrieb Peter Romfeld:
> I am using the puppet example42/hosts module to have a dynamic
> /etc/hosts file.
> Its working fine so far but i have one more requirement, i need to
> force update on all other nodes if one node changes or get added.
This is what it is: an example. In the real world, you'd rather setup a
DNS server instead of messing with /etc/hosts.
HTH...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/52DCC8D8.6020602%40recommind.com.
For more options, visit https://groups.google.com/groups/opt_out.
<>
Re: [Puppet Users] dynamic /etc/hosts
Am 21.01.2014 03:37, schrieb Peter Romfeld: > I have a cluster where all nodes must use hostnames, so we use > /etc/hosts. I want to configure autoscaling for this cluster, but my > biggest problem is the hosts file, so when a new node comes up all > other nodes need to be notify that the hosts file changed, so the make > pull the new file. Opposed to what Felix is thinking, my previous message was meant seriously. I don't see a trivial solution to your problem that involves Puppet and /etc/hosts. You'd need to: 1) Have the new node update the hosts file that Puppet delivers. What is two noeds come up at the same time? You'd need proper locking. 2) Puppet agents only run every 30 minutes, so you'll have a delay until all other nodes know the new one. 3) What happens when a node goes down? OTOH, what you want to do can be achieved with DHCP and DNS, such that the DHCP server updates DNS when a new client comes up. Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52DE1692.1060703%40recommind.com. For more options, visit https://groups.google.com/groups/opt_out. <>
Re: [Puppet Users] dynamic /etc/hosts
Am 21.01.2014 08:25, schrieb Jose Luis Ledesma: > I think this could be accomplished with exported resources, on every node > export a file with his IP, and collect the other ones. Then with a custom > script you could verify if the entry is on the hosts file. But still, how do you cope with nodes going away? > About the offtopic dhcp vs hosts file, most clusters like to have the ips > defined on the hosts file, f.e. in Hacmp cluster it is mandatory. Also, imho, > it is not a good idea to have dhcp for cluster nodes. Why is it a bad idea? DHCP can give each node the same address and name everytime, based on the MAC address. It's like a static IP, with the benefit of automatic DNS updates. Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52DE256A.7060009%40recommind.com. For more options, visit https://groups.google.com/groups/opt_out. <>
Re: [Puppet Users] Reg : Pushing files from Puppet Master to Agent node
Am 28.01.2014 08:09, schrieb krishna bhaskara rao:
> I have installed puppetmaster in ubuntu machine and i have installed
> puppet in all my clients using apt-get. I have joined all my puppet
> clients with puppet master. Is it possible to copy a file to all these
> puppet clients from puppet master instead of going into agent and
> issue the command to pull?
No. The master does not actively push stuff to the agents. However, you
also don't need to "go into agent and issue the command to pull". The
agent runs as a daemon and queries the master every 30 minutes, so all
you need to do is to provide a manifest containing a "file" resource
which puts your file in place.
For example, a simple approach to change the agents puppet.conf could
look like this:
/etc/puppet/modules/puppetconf/manifests/init.pp
class puppetconf {
service { 'PuppetAgent':
name => 'puppet',
ensure => 'running',
enable => 'true',
subscribe => File['puppet.conf'],
}
file { 'puppet.conf':
path => '/etc/puppet/puppet.conf',
ensure => file,
source => 'puppet:///modules/puppetconf/puppet.conf',
}
}
You would then put the puppet.conf file that should be copied to your
agents into /etc/puppet/modules/puppetconf/files.
HTH...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/52E75A61.7080703%40recommind.com.
For more options, visit https://groups.google.com/groups/opt_out.
<>
[Puppet Users] hiera-eyaml-gpg gives strange error
Hi, I'm trying to store some encrypted values in hiera, using either hiera-eyaml or hiera-eyaml-gpg. While hiera-eyaml (PKCS7 encryption) works fine, the agent gives the following error message when using hiera-eyaml-gpg: Could not retrieve catalog from remote server: Error 400 on SERVER: Error from DataBinding 'hiera' while looking up 'the_secret_field': can't convert nil into String on node the_machine.example.com Any ideas what could be wrong or how to debug this? Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52E9138A.5050306%40recommind.com. For more options, visit https://groups.google.com/groups/opt_out. <>
[Puppet Users] Re: hiera-eyaml-gpg gives strange error
Am 29.01.2014 17:27, schrieb Simon Hildrew: > On Wednesday, 29 January 2014 14:43:22 UTC, Dirk Heinrichs wrote: > > Hi, > > I'm trying to store some encrypted values in hiera, using either > hiera-eyaml or hiera-eyaml-gpg. While hiera-eyaml (PKCS7 > encryption) works fine, the agent gives the following error > message when using hiera-eyaml-gpg: > > Could not retrieve catalog from remote server: Error 400 on > SERVER: Error from DataBinding 'hiera' while looking up > 'the_secret_field': can't convert nil into String on node > the_machine.example.com <http://the_machine.example.com> > > Any ideas what could be wrong or how to debug this? > > > I've not seen that before. > > What versions of puppet/hiera/hiera-eyaml/hiera-eyaml-gpg are you > using? Is there anything in the log on the puppetmaster? Puppet is 3.4.2 on both master and agent, agent is Windows, though. Hiera is 1.3.1, hiera-eyaml 2.0.0 and hiera-eyaml-gpg is 0.4. Server log (/var/log/messages) contains the same message as above. > Can you raise an issue on the github project > at https://github.com/sihil/hiera-eyaml-gpg with details on how you > produced the error? Sure. Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52E9F9AB.8030706%40recommind.com. For more options, visit https://groups.google.com/groups/opt_out. <>
Re: [Puppet Users] Re: hiera-eyaml-gpg gives strange error
Am 30.01.2014 08:05, schrieb Dirk Heinrichs: > Am 29.01.2014 17:27, schrieb Simon Hildrew: > >> Can you raise an issue on the github project >> at https://github.com/sihil/hiera-eyaml-gpg with details on how you >> produced the error? > > Sure. https://github.com/sihil/hiera-eyaml-gpg/issues/11 Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52EA06A5.5030308%40recommind.com. For more options, visit https://groups.google.com/groups/opt_out. <>
Re: [Puppet Users] Rebooting all agents simultaneously
Am 06.02.2014 13:13, schrieb Bas van Weelde:
> Administering a large number of hosts (100>) I am in need of a way to
> reboot them all at the same time or in groups. Just a reboot or after
> the change of a config file. Are there any pre-baked solutions for
> that, and if not, do you guyes have any experience in that? I am
> thinking of a way to check if there's a file existing that works as a
> trigger to exec the reboot.
You could use an "exec" resource which is subscribed to a file and has
"refreshonly => true", like:
class reboot ($reason = undef) {
file { 'reboot_trigger':
path => '/.reboot',
ensure => present,
content => "${reason}",
}
exec { 'reboot':
command => "/sbin/shutdown -r now",
subscribe => File['reboot_trigger'],
refreshonly => true,
}
}
Your agents will now reboot whenever you change $reason.
HTH...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/52F39D7C.7020502%40recommind.com.
For more options, visit https://groups.google.com/groups/opt_out.
<>
Re: [Puppet Users] Best practices: client/server VS Git
Am 20.02.2014 16:15, schrieb Julien Deloubes: > For the moment i see 2 ways for Puppet to synchronize nodes: > -Puppet client/server way with a puppetmaster node > -Decentralized way, with node pull their configuration from a Git repo > and make a puppet apply on their own. > > Can you told me what is the pro/cons for this two methods? > And for a large scale of node which is the preferred one? It depends on your use case. We, for example, use a mixture of both in a software development project. All nodes are connected to the master to receive their basic configuration. But we have certain software on certain nodes which should only be updated on demand, so we use the "puppet apply" approach for this in addition to the standard configuration. HTH... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/53070A26.4080100%40recommind.com. For more options, visit https://groups.google.com/groups/opt_out. <>
[Puppet Users] Windows: Can't create/update file in user's home directory using template
Hi,
I've created a simple class for creating/updating a file in a user's
home directory on Windows like so:
class put_file ($user = undef, $group = undef) {
file { 'user_dir':
path => "C:/Users/${user}",
ensure => directory,
owner => "${user}",
}
file { 'some_file':
path=> "C:/Users/${user}/somefile",
ensure => file,
content => template('put_file/somefile.erb'),
owner => "${user}",
group => "${group}",
mode=> '0666',
require => File['user_dir'],
}
}
The home directory exists as the user has been logged in before.
However, when I try to apply this class (via agent), I get the following
error message:
Error: ReplaceFile(C:/Users/the_user/somefile,
C:/Users/the_user/somefile20140303-1756-qjll80): The system cannot find
the file specified.
Any idea what's going wrong here? Both master and agent are running
Puppet 3.4.2.
Thanks...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/53148A0A.5020604%40recommind.com.
For more options, visit https://groups.google.com/groups/opt_out.
<>
Re: [Puppet Users] Windows: Can't create/update file in user's home directory using template
Am 05.03.2014 01:14, schrieb Rob Reynolds:
> This appears to be PUP-1389[1]. We've fixed a found issue with Windows
> 2012 and ruby and how they handle the double line terminator. Note
> that the description is somewhat misleading, this can happen with any
> file name. We've fixed the issue, you will want to evaluate 3.4.3 to
> get it. This bug became more prominent once we applied a CVE fix for
> 3.4.1.
Yes, updating to 3.4.3 fixes the problem.
The description of PUP-1389 was indeed misleading as I checked the
release notes before posting to the list and found that none of the
fixed issues seemed to apply to my problem. Thanks for pointing me into
the right direction.
BTW: I had this problem on Windows Server 2008R2.
Bye...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/5316DCE8.9040507%40recommind.com.
For more options, visit https://groups.google.com/groups/opt_out.
<>
[Puppet Users] Problem with custom facts and hiera
Hi,
I'm trying to categorize our Puppet agent nodes via custom facts. To do
this, I've placed a simple text file "custom_facts.txt" into
C:\ProgramData\PuppetLabs\facter\facts.d with content
[facts]
role = PuppetDev
When I call facter on the agent node, I can see the new fact.
On the server, I've added a line
- "role/%{::role}"
into /etc/hiera.yaml, below the :hierarchy: line and restarted the master.
Finally, I've added /etc/puppet/hiera/role/PuppetDev.yaml with content
---
puppet_agent::version: 3.4.3
while /etc/puppet/hiera/common.yaml has
puppet_agent::version: 3.4.2
To verify that the correct version is delivered, I run
hiera puppet_agent::version ::role=PuppetDev
and get the correct version (3.4.3) back.
However, when I run the puppet agent on the node, it has role unset and
thus it doesn't try to update the puppet agent.
What am I doing wrong here?
Master is 3.4.3, agents are 3.4.2.
Thanks...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/531ED4B8.5060001%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
<>
Re: [Puppet Users] Problem with custom facts and hiera
Am 11.03.2014 10:31, schrieb Craig Dunn:
> Drop the :: from your hiera.yaml, it's being taken literally as
> '::role' rather than defining scope.
That doesn't help, unfortunately. OTOH, using a predefined fact works
fine. For example, I also have a line
- "node/%{::fqdn}"
in hiera.yaml and I can overwrite values from common.yaml with values
taken from node/myhost.recommind.com.yaml without problem.
To me it looks like facter is reading the file containing the custom
fact, while the agent does not.
Bye...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/531EE38C.6020604%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
<>
Re: [Puppet Users] Problem with custom facts and hiera (solved)
Am 11.03.2014 10:17, schrieb Dirk Heinrichs: > To do this, I've placed a simple text file "custom_facts.txt" into > C:\ProgramData\PuppetLabs\facter\facts.d with content > > [facts] > role = PuppetDev Got it to work by removing the blanks: role=PuppetDev Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/531EF73A.6060204%40recommind.com. For more options, visit https://groups.google.com/d/optout. <>
Re: [Puppet Users] Re: mount point directory permissions
Am 23.03.2014 09:57, schrieb Stefan Schulte:
> That's what I'd do, too. But you can use `creates` paramter to do the
> check, there is no need to invoke an external command.
>
> exec { 'create_mntpoint_/mnt/foo':
> command => '/bin/mkdir -m 0755 /mnt/foo',
> creates => '/mnt/foo',
> }
But that's not the OP's problem. Creating the mount point can be
perfectly accomplished with a file resource. The problem is to adjust
permissions AFTER mounting something there w/o having to wait for the
next agent run.
If the permissions of the mount point and the mounted directory are
different, that would lead to a permission change ping-pong, unless one
leaves the permission and ownership attributes of the mount point file
resource untouched and uses an exec with appropriate conditions and
"refreshonly=>true", triggered by the mount resource.
HTH...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/532FD65E.5000402%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
<>
Re: [Puppet Users] Re: mount point directory permissions
Am 21.03.2014 18:48, schrieb Peter Bukowinski:
> exec { 'fix_mount_perms':
> command => 'chmod 2755 /app_dir && chown root:root /app_dir',
> refreshonly => true,
> }
>
> Setting the exec's refreshonly parameter to true prevents it from
> running every time, but it will run any time the mount resource changes.
Shouldn't you add "subscribe=>Mount['/app_dir']", then? Otherwise,
there's nothing that triggers the refresh.
Bye...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/532FFD22.9040502%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
<>
Re: [Puppet Users] Re: mount point directory permissions
Am 24.03.2014 12:10, schrieb Peter Bukowinski:
> That's what the notify parameter in the mount resource does.
Yes, you're right. I always use subscribe instead of notify and didn't
even recognize you use the latter ;)
Bye...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/53301A81.5080606%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
<>
Re: [Puppet Users] How to remove a directory?
Am 06.04.2014 01:27, schrieb Swit Zerland: > I am writing a site.pp to automate some tasks performed on a Windows > VM puppet agent and I would like to know how to remove recursively a > directory. Either use an exec, which includes an "onlyif" attribute to remove the tree with an OS command, or one file resource (with "ensure => absent") for each directory in the tree. The latter needs more wotk to set up, but has the advantage of being OS independent. Finally, you could write a new "dirtree" module which provides a new resource for managing directory trees and make it available on Github ;) HTH... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5342387D.902%40recommind.com. For more options, visit https://groups.google.com/d/optout. <>
Re: [Puppet Users] Re: Getting latest agent on debian for ARM?
Am 08.04.2014 12:29, schrieb JonY:
> Not sure. The devices are fanless PCs called 'dream plugs'. How would
> I determine the chip id?
I've got a Guruplug, which is the predecessor. It's armv5tel, running on
Marvel Feroceon CPU.
% cat /proc/cpuinfo
processor : 0
model name : Feroceon 88FR131 rev 1 (v5l)
Features: swp half thumb fastmult edsp
CPU implementer : 0x56
CPU architecture: 5TE
CPU variant : 0x2
CPU part: 0x131
CPU revision: 1
Hardware: Marvell Kirkwood (Flattened Device Tree)
Revision:
Serial :
% uname -a
Linux rohan 3.13-1-kirkwood #1 Debian 3.13.7-1 (2014-03-25) armv5tel
GNU/Linux
HTH...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/5343E698.1090708%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
<>
[Puppet Users] Hiera lookups in Ruby code
Hi, is it possible to do Hiera lookups inside Ruby code, for example in a provider for a new resource type? If so, how? Thanks... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/534BCC99.20102%40recommind.com. For more options, visit https://groups.google.com/d/optout. <>
Re: [Puppet Users] How to make sure a config file haven't changed in an OS upgrade?
Am 21.04.2014 00:17, schrieb Trevor Vaughan: > Also, doing upgrades between major releases is not generally > recommended and may cause unforseen issues in the future. A fresh kick > is best if possible. ... if running RHEL/CentOS (or upgrade by booting from CD/DVD). Debian derivatives, OTOH, support in-place upgrades. Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5357BA06.9080704%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] "locking" puppet runs
Am 08.05.2014 15:34, schrieb Jonathan Gazeley: > I suppose it would be possible to disable the agent from running as a > daemon and use cron, and the cron job could easily use a MySQL handle > as a locking device. But it still doesn't stop me from simply sshing > to each of the nodes and forcing a puppet run, and breaking the cluster. > > Has anyone done anything like this before? Hope to have some > interesting ideas from you all :) You could 1. enable splay on the client node 2. use mcollective to orchestrate the agent runs. For example: "Update config file on all MariaDB servers, but only one at a time." See http://www.slideshare.net/PuppetLabs/presentation-16281121 for some more information. HTH... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/536B8D9C.5010305%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] btsync (was: Module for lsyncd - multiple syncs to be configured, but only one config file)
Am 15.05.2014 21:25, schrieb Ugo Bellavance:
> I wrote my first puppet module and it is for lsyncd.
Just looked into lsyncd and what it can achieve. While I like rsync and
use it quite often, there's a better way to mirror directories to
multiple destinations: BitTorrent Sync (btsync). btsync uses the
BitTorrent algorithm to distribute the contents of a directory to an
arbitrary number of other machines, where every other machine starts
participating in the distribution process as soon as they have some
chunks of the added file(s) available locally, thus producing less load
on the originating machine.
There are some btsync modules available on Puppetforge, and I've also
written one myself which provides a new resource type "btsync" which
allows for adding/removing new sync folders to a running btsync
instance, for example:
btsync { 'test':
secret => hiera('btsync::test::secret'),# The secret for this
sync folder
path => 'path/to/test_folder',# Where the sync folder should
be stored on disc
login=> hiera('btsync::login'),# Username for btsync
password => hiera('btsync::password'),# Password
ensure => absent,# Removes the sync folder from btsync AND on
disc.
require => Exec['run_btsync'], # Make sure btsync is installed
and running.
}
Bye...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/537600C7.2040301%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] puppet kick as sudo fails
Am 16.05.2014 12:26, schrieb Andy Adman:
> Shit now it fails. I checked my sudoers rules and ok there is written:
Your $HOME is different than foreman's. Puppet looks into $HOME/.puppet
for it's certs.
HTH...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/53760A6A.2000306%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] puppet kick as sudo fails
Am 16.05.2014 12:26, schrieb Andy Adman: > /Warning: Puppet kick is deprecated./ Maybe mcollective is what you want. Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/53760AFF.2050003%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] pass a command output as another command's parameter
Am 26.05.2014 15:09, schrieb cheniour ghassen: > but puppet seems to not understand $2. Because it's an awk variable. You need to escape it somehow (\$2, maybe). HTH... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/53833E5D.8060503%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] pass a command output as another command's parameter
Am 26.05.2014 15:18, schrieb cheniour ghassen: > i tried to escape but this doesn't work . Hmm, try awk \'...\', like shown here <https://ask.puppetlabs.com/question/3020/execs-onlyif-not-playing-nicely-with-test/>. Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/53834070.9030207%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] pass a command output as another command's parameter
Am 26.05.2014 15:24, schrieb Dirk Heinrichs: > Am 26.05.2014 15:18, schrieb cheniour ghassen: > >> i tried to escape but this doesn't work . > > Hmm, try awk \'...\', like shown here > <https://ask.puppetlabs.com/question/3020/execs-onlyif-not-playing-nicely-with-test/>. There's another solution here <http://projects.puppetlabs.com/projects/1/wiki/Firmware_Password_Patterns>, which suggests to escape the subshell call (id = \$(...) in your case). And, you can always put all the commands into an external script and call that. Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/53834209.4050805%40recommind.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Hiera lookup bug?
Hi, I'm facing a strange problem with Hiera, where a trailing 0 (zero) is cut off a value, for example: myclass::version: 1.10 resolves to 1.1 when the class is applied on an agent. The agent runs Puppet 3.4.3 with Hiera 1.3.1 on Windows Server 2008R2. As a workaround I'm now passing the value to the class as a default parameter instead of through hiera. Any ideas how to fix this? Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/53842A30.9000306%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Hiera lookup bug?
Am 27.05.2014 10:15, schrieb R.I.Pienaar: > Quote the number, 1.10 is a string Ah, OK. Thought that everything is a string in hiera. Thanks... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/53844B49.7020203%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] PostgreSQL INSERT
Am 27.05.2014 13:42, schrieb zerozerouno...@gmail.com:
> Of course I could manage it through an Exec resource, but isn't there
> a more "elegant" solution?
> I would also need to be sure the line isn't already there, before
> inserting it...
I wonder what's wrong with exec? I use for example:
exec { 'create_app_schema':
command => 'psql -t -A -q -c "create schema app authorization
someuser" somedb pg_admin',
path=> ["${installdir}/bin", $::path],
unless => 'cmd /C psql -t -A -q -c "select nspname from
pg_catalog.pg_namespace where nspname = \'app\';" somedb pg_admin | find
"app"',
require => [Windows_env['PGPASSWORD'], Service['postgres'],
Exec['create_db']],
environment => ["PGPASSWORD=${password}"],
}
This executes the command for creating a schema, if it doesn't exist
already.
Of course, you could try to write your own resource type and provider
for db queries, but I doubt it won't buy you anything except for a
cleaner syntax and maybe platform independence.
HTH...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/53847CE6.7050603%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] PostgreSQL INSERT
Am 27.05.2014 14:01, schrieb Felix Frank: > Exec is mainly a crutch for places in which no provider is yet > available. It can be worthwile in some instances, of course, but in the > majority of applications, there is a strong case for type support. While I surely agree with you here, the problem from my PoV is that such a type provider would be pretty complex. Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5385D159.4030108%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Ability to "wait" for dotnet to complete installation
Am 04.06.2014 08:15, schrieb Stephen Wallace: > Short of writing a new function called "go for a cup of tea" feeding > it the required number of sleep seconds(!), does anybody have any > experiences or ideas around this one?? There's a nice little "wait_for" resource available on Github <https://github.com/basti1302/puppet-wait-for>. HTH... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/538EBA7D.3060804%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] puppetlabs-java: installing oracle-jdk on ubuntu trusty 14.04
Am 10.06.2014 07:35, schrieb Milan Simonović:
> I'm still trying to figure out how to install java *just using*
> puppetlabs-java module.
You can't. There is no package "oracle-jdk" on Ubuntu.
Bye...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/5396A1B0.9010202%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] how to change root password for all nodes
Am Mittwoch 09 Juli 2014, 08:21:30 schrieb mahesh vijapure: > I want to update root password for all vms registered with Puppet. Please > someone assist me here. Did you think about closing the root account in favour of using sudo for all admin tasks? That way, you only need to distribute new /etc/sudoers file to your VMs. Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com[1] <_mailto:dhs@recommind.com_> *Skype*: dirk.heinrichs.recommind www.recommind.com[2] <_http://www.recommind.com_> [1] mailto:d...@recommind.com [2] http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/3316244.GE7I965knB%40gondor. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] how to change root password for all nodes
Am Mittwoch 09 Juli 2014, 08:21:30 schrieb mahesh vijapure: > I want to update root password for all vms registered with Puppet. Please > someone assist me here. Did you think about closing the root account in favour of using sudo for all admin tasks? That way, you only need to distribute new /etc/sudoers file to your VMs. Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/14661472.9DAMugu5PL%40gondor. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] puppet agent upgrade on windows
Am 05.12.2014 um 19:03 schrieb Rob Reynolds: > Trying to upgrade Puppet with Puppet on Windows is harder because > Windows locks files that are in use instead of letting you replace > them in place. That's not true. Upgrading Puppet with Puppet on Windows works just fine. Downgrade is a different story, depending on the versions involved. I've alread done upgrades from 3.2.1 to 3.4.3 and I'm currently in the process of upgrading ~150 Windows agents from 3.4.3 (32bit) to 3.7.3 (64bit) and I don't see any problems related to file locks. Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5485B666.6030505%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] puppet agent upgrade on windows
Am 08.12.2014 um 15:52 schrieb Jason Chinsen: > Thanks of the update, this is great news. If you do not mind, please > can you share your puppet manifests and chocolatey package? I don't use chocolatey. I use the .msi from Puppetlabs (this is not PE, btw.). However, I've attached my module. You may need to remove/replace the "puppetstore" parts. > More over how do you, if you have to, deal with the .net4 issue that I > posted? No, I don't have that issue. HTH... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/54869DD3.2030204%40recommind.com. For more options, visit https://groups.google.com/d/optout. puppet_agent.tgz Description: Binary data
Re: [Puppet Users] puppet agent restarting everyday?
Am 12.12.2014 um 13:17 schrieb Suresh P: > Why puppet agent restarting everyday at 00:01 hours? > > [2014-11-29 00:01:02] INFO WEBrick::HTTPServer#start: pid=31285 port=8139 > [2014-11-30 00:01:01] INFO WEBrick::HTTPServer#start done. That's not the agent, it's the master. Logrotate cronjob (/etc/cron.daily)? HTH... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/548AEF97.9000207%40recommind.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Bug: Exec resource executes although dependencies have failed
Hi, on Puppet 3.7.3 (Windows) I currently see the following strange behaviour: Notice: /Stage[main]/Myclass/Exec[myexec]: Dependency Exec[myotherexec] has failures: true Warning: /Stage[main]/Myclass/Exec[myexec]: Skipping because of failed dependencies Debug: Exec[myexec](provider=windows): Executing 'cmd /C somecommand.exe' Debug: Executing 'cmd /C somecommand.exe' So it says "Skipping because of failed dependencies", but then executes it anyway. Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/548FF759.8010504%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] puppet agent restarting everyday?
Am 16.12.2014 um 15:26 schrieb Suresh P:
> This is configured to run daily by puppet installation itself. Does
> this restart puppet agent?
>
> /var/log/puppet/*log {
> missingok
> notifempty
> create 0644 puppet puppet
> sharedscripts
> postrotate
> pkill -USR2 -u puppet -f 'puppet master' || true
> [ -e /etc/init.d/puppet ] && /etc/init.d/puppet reload > /dev/null
> 2>&1 || true
> endscript
> }
Yes, it does, although it shouldn't. "/etc/init.d/puppet reload" sends a
SIGHUP signal to the puppet agent, which restarts it. However, according
to puppet-agent(8), this action should better be sending a SIGUSR2
("Close file descriptors for log files and reopen them. Used with
logrotate."), which wouldn't trigger an agent restart.
Should this be considered a bug in /etc/init.d/puppet?
Bye...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/5490443B.1010001%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Installing multiple versions of a ZIP archive
Hi,
lets say I have a small class that simply extracts a given ZIP archive
into a destination directory, using a version string passed in as class
parameter to identify both the archive and the destination:
class foo ($version = undef) {
...
}
If the archive is extracted manually, I can easily extract multiple
different versions next to each other, so that I get (for example):
/opt/foo/1/
/opt/foo/2/
...
/opt/foo/n/
However, in Puppet, I can't do this for the same node:
class {'foo': version => '1'}
class {'foo': version => '2'}
class {'foo': version => '3'}
to get multple versions extracted.
I currently achieve this by doing multiple sequential Puppet runs with
different values for $version.
There must be a better way to do this. I thought about passing in the
versions as an array, but Puppet has no loops. Do I really need to write
a custom type and provider for this?
Thanks...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/54A6561F.7020707%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Installing multiple versions of a ZIP archive
Am 02.01.2015 um 09:26 schrieb Dirk Heinrichs: > There must be a better way to do this. I thought about passing in the > versions as an array, but Puppet has no loops. Found it. Defined types is the way to go. Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/54A66CF2.90800%40recommind.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] MCollective: Problem on CentOS6
Hi, I've installed MCollective 2.7.0 incl. facter plugin from packages on two Ubuntu 14.04 and two Centos 6.6 machines. server.cfg is identical on all 4 machines. However, while initial "mco ping" commands receive replies from all 4 hosts, the Centos 6 hosts stop replying as soon as any other command is sent: # mco ping aaatime=6.72 ms bbb time=7.16 ms ccc time=7.53 ms ddd time=29.64 ms ping statistics 4 replies max: 29.64 min: 6.72 avg: 12.76 # mco facts fqdn warn 2015/01/14 11:29:38: client.rb:251:in `rescue in start_receiver' Could not receive all responses. Expected : 4. Received : 2 Report for fact: fqdn aaa.domain.com found 1 times bbb.domain.com found 1 times Finished processing 2 / 4 hosts in 12003.22 ms No response from: ccc ddd # mco ping aaatime=7.04 ms bbb time=9.29 ms ping statistics 2 replies max: 9.29 min: 7.04 avg: 8.17 Any idea what could be wrong on those Centos hosts? Thanks... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/54B645DF.2010404%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Upgrade
Am 20.01.2015 um 13:39 schrieb Don Dorman:
> Has anyone found documentation on upgrading Puppet 3.4.3 to Puppet
> 3.6.2. running on RHEL 6.4
First update the server, then agent nodes. You can use Puppet to update
the agents (I've written myself a small module to do that).
> I have found some documents, but nothing simple and clearly defined.
Server: yum upgrade
Agents:
Manual: yum upgrade
Automatic: Use (custom) puppet module, maybe with a version
parameter. Then to update, just increase the version number and wait for
the next automatic agent run.
Feel free to ask for my module ;).
HTH...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/54BE4E31.90307%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Upgrade
Am 20.01.2015 um 13:53 schrieb Don Dorman: > So respectively on the Puppet Master I have copied Puppet 3.6.2 to > /var/data/Puppet. I have the RHEL 6.4.iso mounted to /mnt > > So I am guessing to upgrade the Master it should be as simple as yum > upgrade puppet-server-3.6.2-1.el6.noarch.rpm > > and yum upgrade puppetdb-2.0.0-1.el6.noarch.rpm > > and the obvious yum upgrade puppet-3.6.2-1.el6.noarch.rpm Yes (could also be one command). "yum upgrade", as I suggested, would update ALL packages to their LATEST versions. Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/54BE5182.90803%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] puppet agent is not reflecting my changes
Am 18.02.2015 um 14:19 schrieb Raj Raju: > I created the manifest file /etc/puppetlabs/puppet/manifests/sites.pp > with the following content on puppet server.|| > |[...]| > ||Puppet node does not pick any changes from master. Because it needs to be named "site.pp", not "sites.pp". HTH... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/54E49501.3090802%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] My puppet code is not idempotent (Windows package provider)
Am 19.02.2015 um 10:29 schrieb cko: > But on every puppet run, the "package" resource gets applied. Example > tagmail output: > > /Thu Feb 19 09:48:28 +0100 2015 /Stage[main]/[ .. module > ]/Package[signotec WinUSB]/ensure (notice): created > Thu Feb 19 10:16:59 +0100 2015 /Stage[main]/[ .. module > ]/Package[signotec WinUSB]/ensure (notice): created > / > /./ > > Any ideas? Is 'signotec WinUSB' exactly the name of the package as reported by Windows in Control Panel\All Control Panel Items\Programs and Features? dito for the version? HTH... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/54E5B7B3.9050807%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Strategies for "boring" packages
Am 19.04.2016 um 02:47 schrieb J.T. Conklin:
> What strategies do you use for "boring" modules so you're not
> overwhelmed by hundreds of small boilerplate modules?
I use a simple module with one class for mass-installing packages and
another one for mass-uninstalling, like:
class linux_base::install ($packages = undef) {
$packages.each |String $pkg| {
package { $pkg: ensure => latest, }
}
}
where $packages is an array of package names (strings), which can easily
be provided for each (group of) host(s) via Hiera.
The ::uninstall class has "purge" instead of "latest". Of course, input
array for both classes must be mutually exclusive, if both are used at
the same time.
HTH...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/57178BA2.6020801%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Migration to PuppetDB and Apache/Passenger setup
Am 20.05.2016 um 11:36 schrieb christg76:
> Lastly, are there any packages for Puppet 4 available to use in a
> APache/passenger setup? I'm running Debian, and from Puppetlabs it
> looks everything is for PuppetServer.
Puppet 4 has no PuppetMaster running in Apache/Passenger anymore.
There's only PuppetServer, which is standalone.
HTH...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/7a470c71-071a-69ef-0f29-c46221fc0459%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] How does Puppet Push Model works
Am 17.08.2016 um 05:14 schrieb megha sharma:
> How does puppet push model works for application deployment. It should
> be done in such a way that deployment happens only when required and
> the same should be initiated from puppet master.
It's not really push. Puppet agent runs on each node and connects to the
master every 30 minutes (default), asking for its configuration. So you
need to change the nodes configuration on the master, so that it gets it
next time it connects.
To simulate a push, you'd need to setup mcollective on both master and
nodes. You can then initiate an agent run remotely, from the master.
HTH...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/4ac46dcb-9957-0d14-93f2-72775868e45a%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Influence hiera file selection from within hiera
Am 07.09.2016 um 13:50 schrieb Marc Haber:
> I would like to be able to influence which files hiera reads from with
> in hiera.
You can use facts in :datadir:, like for example:
:datadir: '/etc/puppetlabs/code/environments/%{::environment}/hiera'
While the :hierarchy: stays the same, we checkout different branches of
a hiera repository in each environment to get different file content.
HTH...
Dirk
--
*Dirk Heinrichs* | Senior Systems Engineer, Delivery Pipeline
http://mimage.opentext.com/alt_content/binary/images/email-signature/recommind-ot.png
<http://www.opentext.com>
*Tel*: +49 2226 159666 (Ansage) 1149
*Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com>
*Skype*: dirk.heinrichs.recommind
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon
Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer
HRB 10646
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese
E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den
Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie
die unbefugte Weitergabe dieser Mail sind nicht gestattet.
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/d8710093-96c2-541b-9a95-16e85783a8ea%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Hiera changes on specific node
Am 18.11.2016 um 12:56 schrieb Amber Mehra:
> Please advise what to write on hiera so i can push custom
> configuration of httpd.conf on specific node only.
That depends on your setup.
In general, say you have the following class definition:
class foo ($bar = undef) {}
and your hierarchy in hiera.yaml looks like this:
:hierarchy:
- "node/%{::fqdn}"
- common
You would then put common values for $bar into hiera's common.yaml like so:
foo::bar: common_value
and values for specific nodes would go into node/.yaml,
overwriting what is defined in common.yaml:
foo::bar: node_specific_value
HTH...
Dirk
--
*Dirk Heinrichs* | Senior Systems Engineer, Delivery Pipeline
http://mimage.opentext.com/alt_content/binary/images/email-signature/recommind-ot.png
<http://www.opentext.com>
*Tel*: +49 2226 159666 (Ansage) 1149
*Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com>
*Skype*: dirk.heinrichs.recommind
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon
Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer
HRB 10646
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese
E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den
Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie
die unbefugte Weitergabe dieser Mail sind nicht gestattet.
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/80d74096-9170-7c93-c87d-60a14bd552ca%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Problem with Puppet reinstalling Windows APPs
Am 08.12.2016 um 20:09 schrieb ratatapa:
> I have a package that install Adobe Reader DC on my nodes, the issue
> is that each time i run puppet agent -t it always reinstall Adobe Reader.
>
> Is there any way to tell puppet to ignore if program is already installed?
Yes. On Windows (and only on Windows), the resource title of a package
resource must match exactly what Windows shows in the "Name" column when
you open "Control Panel\All Control Panel Items\Programs and Features".
So in your case, it should look like
package { 'Adobe Acrobat Reader DC':
...
}
HTH...
Dirk
--
*Dirk Heinrichs* | Senior Systems Engineer, Delivery Pipeline
http://mimage.opentext.com/alt_content/binary/images/email-signature/recommind-ot.png
<http://www.opentext.com>
*Tel*: +49 2226 159666 (Ansage) 1149
*Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com>
*Skype*: dirk.heinrichs.recommind
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon
Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer
HRB 10646
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese
E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den
Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie
die unbefugte Weitergabe dieser Mail sind nicht gestattet.
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/0fd20414-b62f-d3bb-c3e2-cb59d731282f%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Problem with Puppet reinstalling Windows APPs
Am 09.12.2016 um 14:05 schrieb ratatapa: > Thanks, but that would seem to be an issue for updates then No, that would be the version, not the name. Just read the docs <https://docs.puppet.com/puppet/4.8/resources_package_windows.html#package-name-must-be-the-displayname>: "The title (or |name|) of the package must match the value of the package’s |DisplayName| property in the registry, which is also the value displayed in the “Add/Remove Programs” or “Programs and Features” control panel. If the provided name and the installed name don’t match, Puppet will believe the package is not installed and try to install it again." HTH... Dirk -- *Dirk Heinrichs* | Senior Systems Engineer, Delivery Pipeline http://mimage.opentext.com/alt_content/binary/images/email-signature/recommind-ot.png <http://www.opentext.com> *Tel*: +49 2226 159666 (Ansage) 1149 *Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com> *Skype*: dirk.heinrichs.recommind Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer HRB 10646 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet. http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/eb55769f-a375-6b88-b38c-191423990ef4%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Problem with Puppet reinstalling Windows APPs
Am 09.12.2016 um 15:35 schrieb Rob Nelson:
> I think in this case it's an issue because Adobe puts version numbers
> in the product name - it's not Acrobat Reader anymore, it's Acrobat
> Reader DC or Acrobat Reader X, which leads to having to change two
> strings. Definitely not a fan of their versioning scheme.
Nope. At least on my system, the name is "Adobe Acrobat Reader DC" and
the version is "15.020.20042". However, you're right in that some
packages add the version to the name, for example Git for Windows, where
the name looks like "Git version 2.11.0". In that case, one can either do:
class git ($version = undef) {
package { "Git version ${version}":
...
}
}
or use the chocolatey package provider from PuppetForge, like
class git {
package { 'git':
provider => 'chocolatey',
ensure => latest,
...
}
}
Note that in the 2nd example, one could also add the $version paramater
and use that instead of latest. Depends on your needs.
Bye...
Dirk
--
*Dirk Heinrichs* | Senior Systems Engineer, Delivery Pipeline
http://mimage.opentext.com/alt_content/binary/images/email-signature/recommind-ot.png
<http://www.opentext.com>
*Tel*: +49 2226 159666 (Ansage) 1149
*Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com>
*Skype*: dirk.heinrichs.recommind
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon
Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer
HRB 10646
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese
E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den
Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie
die unbefugte Weitergabe dieser Mail sind nicht gestattet.
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/6abc1208-db6f-d484-c7b2-d487ec6a4094%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Problem with Puppet reinstalling Windows APPs
Am 09.12.2016 um 16:20 schrieb Rob Nelson: > This is not fun when there isn't a chocolate package to use instead. https://chocolatey.org/packages/adobereader https://chocolatey.org/packages/adobereader-update Bye... Dirk -- *Dirk Heinrichs* | Senior Systems Engineer, Delivery Pipeline http://mimage.opentext.com/alt_content/binary/images/email-signature/recommind-ot.png <http://www.opentext.com> *Tel*: +49 2226 159666 (Ansage) 1149 *Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com> *Skype*: dirk.heinrichs.recommind Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer HRB 10646 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet. http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/edaec258-674b-4099-8a32-30198e1318c5%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Urgent Help Required | Puppet run is dead slow
Am 12.12.2016 um 17:34 schrieb Harish Kothuri:
> I have a puppet master v3.8.7 and having 300+ nodes running fine till
> last week.
>
> All the agents are running very slow since last week and sometimes it
> started complaining that puppet master is running on heavy load.
Two possible reasons come to my mind:
1. Memory leak, causing the machine to start swapping
2. Thundering herd problem: Too many agents accessing the server at the
same time, maybe also trying to download somthing large from builtin
fileserver.
If 1: Try restarting Puppet server processes.
If 2: Try adding some splay to the agent configuration:
splay = true
splaylimit = 2m
HTH...
Dirk
--
*Dirk Heinrichs* | Senior Systems Engineer, Delivery Pipeline
http://mimage.opentext.com/alt_content/binary/images/email-signature/recommind-ot.png
<http://www.opentext.com>
*Tel*: +49 2226 159666 (Ansage) 1149
*Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com>
*Skype*: dirk.heinrichs.recommind
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon
Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer
HRB 10646
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese
E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den
Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie
die unbefugte Weitergabe dieser Mail sind nicht gestattet.
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/e265f378-a09b-96b5-6492-00bde371bb73%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Over-engineering rant
Am 08.01.2017 um 11:04 schrieb Fabrice Bacchella: >> And, on the other hand - all this complexity to manage a NTP? > And that's for something that for a given environment never change, > have no options. So dropping a standard file that is hand made once in > a lifetime is enough for the vast majority of people. And it doesn't even support Windows. > That's why I don't use standard or references modules. I can do in 10 > lines written in 10 minutes what they did in 100 written in many days. > I don't care that they don't run on some exotic plate from that I > never heard of or are not good for stratum 1 servers. They are > tailored for my need, that's enough for me. They never brake, never > warn, works almost unchanged from puppet 2.7 time and it take me the > same amount of time that it would have taken to download, understand > and check them. Ack. Bye... Dirk -- *Dirk Heinrichs* Senior Systems Engineer, Delivery Pipeline OpenText^TM Discovery | Recommind *Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com> *Website*: www.recommind.de <http://www.recommind.de> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer HRB 10646 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet. http://www.recommind.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/426fe64e-e1f9-8455-26cd-b3a7bc6699e2%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] writing custom fact -> return value not as expected
Am 10.01.2017 um 22:29 schrieb Stefan Schulte:
> % LC_ALL=de_DE.utf8 /usr/bin/who -b |awk '{print $3}'
> 19:34
> % LC_ALL=en_US.utf8 /usr/bin/who -b |awk '{print $3}'
> 2017-01-10
Interesting. On my system, there's no difference between them (left out
the awk part for clarity):
% LC_ALL=en_US.UTF-8 who -b
system boot 2017-01-02 11:10
% LC_ALL=de_DE.UTF-8 who -b
system boot 2017-01-02 11:10
> % LC_ALL=C /usr/bin/who -b |awk '{print $3}'
> Jan
Only here:
% LC_ALL=C who -b
system boot Jan 2 11:10
Bye...
Dirk
--
*Dirk Heinrichs*
Senior Systems Engineer, Delivery Pipeline
OpenText^TM Discovery | Recommind
*Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com>
*Website*: www.recommind.de <http://www.recommind.de>
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon
Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer
HRB 10646
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese
E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den
Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie
die unbefugte Weitergabe dieser Mail sind nicht gestattet.
http://www.recommind.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/0196a5ed-4c5c-6f55-5feb-fd3bfdea69b9%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] syntax issue over puppet_4
Am 22.02.2017 um 14:28 schrieb Ren:
> *Error: Failed to apply catalog: Could not find dependency
> Package[openssh-server] for File[/etc/ssh/sshd_config] at
> modules/sshd/manifests/init.pp:14*
It's not declared (package {$ssh_pkg: ...}). Wondering why it worked in
P3...
Bye...
Dirk
--
*Dirk Heinrichs*
Senior Systems Engineer, Delivery Pipeline
OpenText^TM Discovery | Recommind
*Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com>
*Website*: www.recommind.de <http://www.recommind.de>
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon
Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer
HRB 10646
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese
E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den
Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie
die unbefugte Weitergabe dieser Mail sind nicht gestattet.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/29547df0-51c6-cf64-d01e-d75fd4e68d0a%40opentext.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Puppet4 $facts syntax
Am 10.03.2017 um 14:02 schrieb R.I.Pienaar:
> the first is just wrong
OTOH, I mostly use $::facts['fact_name'].
Bye...
Dirk
--
*Dirk Heinrichs*
Senior Systems Engineer, Delivery Pipeline
OpenText^TM Discovery | Recommind
*Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com>
*Website*: www.recommind.de <http://www.recommind.de>
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon
Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer
HRB 10646
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese
E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den
Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie
die unbefugte Weitergabe dieser Mail sind nicht gestattet.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/e972e522-387f-bbc4-1c01-e3dc2feb0e8e%40opentext.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Puppet4 $facts syntax
On 10.03.2017 14:10, R.I.Pienaar wrote: > You can never cause the problem that raised the need for $::facts to > exist, you can just use $facts and it's all sweet and > In general with Puppet 4 the needs for all the :: stuff is almost all gone Ah, good to know. Thanks for clarifying. Bye... Dirk -- *Dirk Heinrichs* Senior Systems Engineer, Delivery Pipeline OpenText^TM Discovery | Recommind *Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com> *Website*: www.recommind.de <http://www.recommind.de> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer HRB 10646 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5c563e06-4b4b-32b5-1c44-c6aad00980eb%40opentext.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] The repository 'http://apt.puppetlabs.com xenial Release' is not signed.
Hi, I'm currently facing this error when I try to apt-get update after installing puppetlabs-release-pc1-xenial.deb (also tried the latest one from the pool: puppetlabs-release-pc1_1.1.0-4xenial_all.deb). Please fix. Thanks a lot, Dirk -- *Dirk Heinrichs* Senior Systems Engineer, Delivery Pipeline OpenText^TM Discovery | Recommind *Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com> *Website*: www.recommind.de <http://www.recommind.de> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer HRB 10646 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/13e3ab42-9941-3063-ebe5-88a3567f8620%40opentext.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] The repository 'http://apt.puppetlabs.com xenial Release' is not signed.
On 27.04.2017 18:38, Morgan Rhodes wrote: > Looks like we had some bad metadata cached in our CDN, but this should > be resolved now. There's more information in this > ticket: https://tickets.puppetlabs.com/browse/CPR-419 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__tickets.puppetlabs.com_browse_CPR-2D419&d=DwMFaQ&c=ZgVRmm3mf2P1-XDAyDsu4A&r=TsKycyisPP_6FVCeETRooIdY_8hdAsXoxwbvHso_TaI&m=fVbRecTIOve70lQBAD1KhDc7eBikXQ3uXNM4Gizr0Mg&s=R4WHWNsDmvZ6MHIHz6f_ACwAMYeGs40bhz641ca6ozI&e=> Yep, works again. Thanks a lot... Dirk -- *Dirk Heinrichs* Senior Systems Engineer, Delivery Pipeline OpenText^TM Discovery | Recommind *Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com> *Website*: www.recommind.de <http://www.recommind.de> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer HRB 10646 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/b7eb7e53-7ec0-9cdc-8b80-988c12c67206%40opentext.com. For more options, visit https://groups.google.com/d/optout.
Re: [EXTERNAL] - [Puppet Users] Need to put iterative value in a file
On 04.05.2017 09:26, Quentin lenglet wrote:
> $demofiles = "/root/.ssh/test"
> $lpsc::ssh_keys.each | String $value | {
> file {$demofiles:
This will not work, since the loop potentially creates multiple file
resources with the same name ("/root/.ssh/test"), which is not allowed.
The resource names inside the loop must be unique (for each resource
type). They're best coupled with the loop counter variable ($value in
this case).
HTH...
Dirk
--
*Dirk Heinrichs*
Senior Systems Engineer, Delivery Pipeline
OpenText^TM Discovery | Recommind
*Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com>
*Website*: www.recommind.de <http://www.recommind.de>
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon
Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer
HRB 10646
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese
E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den
Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie
die unbefugte Weitergabe dieser Mail sind nicht gestattet.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/41db1be9-1ab1-252d-51ee-aa717818950b%40opentext.com.
For more options, visit https://groups.google.com/d/optout.
Re: [EXTERNAL] - [Puppet Users] Missing puppet-agent package on Debian Jessie
Am 13.06.2017 um 10:56 schrieb Fairouz el ouazi: > I installed > https://apt.puppetlabs.com/puppetlabs-release-pc1-jessie.deb > <https://urldefense.proofpoint.com/v2/url?u=https-3A__apt.puppetlabs.com_puppetlabs-2Drelease-2Dpc1-2Djessie.deb&d=DwMFaQ&c=ZgVRmm3mf2P1-XDAyDsu4A&r=TsKycyisPP_6FVCeETRooIdY_8hdAsXoxwbvHso_TaI&m=F-QvVRy0rm-lKM8Qgr1ZG7ehqfhS6ZEdPHL2IlD78mU&s=sLj9ErvKn2fh-dFDoNC9m_ulPsCbc1CYFaHIt9QhxEg&e=> > on an [ Raspbian GNU/Linux 8.0 (jessie) ] and ran `apt-get update` > and when I run `apt-get install puppet-agent` (or `puppetmaster`) I > get this error: > Package puppet-agent is not available, but is referred to by another > package. There are no arm packages available in this repository (see https://apt.puppetlabs.com/pool/jessie/PC1/p/puppet-agent/). It only contains packages for i386 and amd64. You could try to get the source package and build one for amr yourself. HTH... Dirk -- *Dirk Heinrichs* Senior Systems Engineer, Delivery Pipeline OpenText^TM Discovery | Recommind *Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com> *Website*: www.recommind.de <http://www.recommind.de> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer HRB 10646 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7ffc2f75-3854-7b41-75d8-c26ee5959f0f%40opentext.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Missing puppet-agent package on Debian Jessie
Am 13.06.2017 um 11:04 schrieb Fairouz el ouazi: [Oh, just noticed that I already misspelled the architecture. It's arm of course, not amr] > So how much time can take me to build one for Amr ? Don't know. Depends on your Raspi's speed. However, I just found out that PuppetLabs doesn't provide source packages for puppet-agent (only for puppetserver). So it seems you're out of luck here. You could try to write a bug report and ask them to provide the needed packages. Bye... Dirk -- *Dirk Heinrichs* Senior Systems Engineer, Delivery Pipeline OpenText^TM Discovery | Recommind *Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com> *Website*: www.recommind.de <http://www.recommind.de> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer HRB 10646 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/65aff43c-ca74-f08b-4776-1135fea8248e%40opentext.com. For more options, visit https://groups.google.com/d/optout.
Re: [EXTERNAL] - [Puppet Users] Every run puppet notices package install created
Am 21.09.2017 um 11:33 schrieb Lars Van Steenbergen: > So every run i get this notice: > /Stage[main]/Icinga::Install/Package[icinga*]/ensure created > Please, don't provide any more details, someone could be able to help, then. *SCNR* Bye... Dirk -- *Dirk Heinrichs* Senior Systems Engineer, Delivery Pipeline OpenText^TM Discovery | Recommind *Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com> *Website*: www.recommind.de <http://www.recommind.de> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer HRB 10646 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/32d76553-03fb-260f-7c3b-223a974fbb43%40opentext.com. For more options, visit https://groups.google.com/d/optout.
Re: [EXTERNAL] - [Puppet Users] Notice: package install ensured on every run
Am 21.09.2017 um 11:35 schrieb Lars Van Steenbergen:
> package {'icinga*':
> ensure =>installed,
> provider => 'yum',
> before => Package['openssh-clients','ftp','wget']
> }
Guess there's no package named "icinga*" in your distribution. You need
to provide the exact package name(s), either as array or as several
package resources.
Array example:
package { ['some', 'packages', 'to', 'install']:
...
}
HTH...
Dirk
--
*Dirk Heinrichs*
Senior Systems Engineer, Delivery Pipeline
OpenText^TM Discovery | Recommind
*Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com>
*Website*: www.recommind.de <http://www.recommind.de>
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon
Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer
HRB 10646
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese
E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den
Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie
die unbefugte Weitergabe dieser Mail sind nicht gestattet.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/f53ace6f-2bcd-c4c6-d0a2-0f6569e373e1%40opentext.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Set environment variable for Service resource
Am 07.11.2017 um 02:10 schrieb Andrei Iacob: > is there a way to configure a set of environment variables to be > available to a Service resource similar to what Exec supports? > > Looking at the documentation this doesn't seem to fit (except probably > from the Manifest attribute but still can't figure out how) so is > there a workaround for this such as exporting an environment variable > globally? What I want to avoid doing is writing a bash script to > export them and run it prior to the Service's actual start script. Which OS (flavour, version)? Bye... Dirk -- *Dirk Heinrichs* Senior Systems Engineer, Delivery Pipeline OpenText^TM Discovery | Recommind *Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com> *Website*: www.recommind.de <http://www.recommind.de> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer HRB 10646 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/2b26b366-3c6a-3c09-b648-a92a81e4ce1b%40opentext.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Set environment variable for Service resource
Am 07.11.2017 um 16:24 schrieb Peter Faller: > or if the service is managed by systemd, in the relevant '???.service' > file. Or, if the service file is shipped as part of a distribution package, in a '*.conf' file in the corresponding '???.service.d' directory (to be created), to avoid messing with distribution provided files. Bye... Dirk -- *Dirk Heinrichs* Senior Systems Engineer, Delivery Pipeline OpenText^TM Discovery | Recommind *Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com> *Website*: www.recommind.de <http://www.recommind.de> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer HRB 10646 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/39fe0247-e6cc-f858-8a77-e62ead9bf4b3%40opentext.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Duplicate declaration error - what's the correct approach to avoid this?
Am 23.11.2017 um 15:47 schrieb buoyant_puppy:
> That's is a simplified version of my actual use case:
> $mythings.each | String $x | { # for each x in list 'mythings'
> notify { "gonna do something with $x": }
>
Not sure, but I think you need to use ${x} in the resource declaration
to actually have the variable interpolated.
HTH...
Dirk
--
*Dirk Heinrichs*
Senior Systems Engineer, Delivery Pipeline
OpenText^TM Discovery | Recommind
*Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com>
*Website*: www.recommind.de <http://www.recommind.de>
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon
Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer
HRB 10646
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese
E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den
Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie
die unbefugte Weitergabe dieser Mail sind nicht gestattet.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/0ff870ae-131f-a044-9565-744f54224fbe%40opentext.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Duplicate declaration error - what's the correct approach to avoid this?
Am 24.11.2017 um 10:14 schrieb buoyant_puppy:
> Code:
> $dns[resolvers].each | String $resolver | {
> file_line { 'adding ns $resolver': path => '/etc/resolv.conf',
> line => 'nameserver $resolver', }
> notify { "just added $resolver to /etc/resolv.conf": }
> }
There are a few errors in this code, related to string interpolation:
* You need to use ", not ' when you want to interpolate a variable
inside a string
* Inside strings, the variables need to be written as ${variable}, not
$variable
Your code produces 2 resources with the name "adding ns $resolver"
instead of one resource named "adding ns 4.4.4.4" and one named "adding
ns 8.8.8.8".
HTH...
Dirk
--
*Dirk Heinrichs*
Senior Systems Engineer, Delivery Pipeline
OpenText^TM Discovery | Recommind
*Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com>
*Website*: www.recommind.de <http://www.recommind.de>
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon
Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer
HRB 10646
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese
E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den
Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie
die unbefugte Weitergabe dieser Mail sind nicht gestattet.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/bb209013-e626-079a-9f14-59d60a847752%40opentext.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Duplicate declaration error - what's the correct approach to avoid this?
Am 23.11.2017 um 15:47 schrieb buoyant_puppy:
> That's is a simplified version of my actual use case:
> $mythings.each | String $x | { # for each x in list 'mythings'
> notify { "gonna do something with $x": }
>
Not sure, but I think you need to use ${x} in the resource declaration
to actually have the variable interpolated.
HTH...
Dirk
--
*Dirk Heinrichs*
Senior Systems Engineer, Delivery Pipeline
OpenText^TM Discovery | Recommind
*Email*: dirk.heinri...@recommind.com <mailto:dirk.heinri...@recommind.com>
*Website*: www.recommind.de <http://www.recommind.de>
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon
Davies, Roger Illing, Registergericht Amtsgericht Bonn, Registernummer
HRB 10646
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese
E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den
Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie
die unbefugte Weitergabe dieser Mail sind nicht gestattet.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/9022423f-007b-a7a8-a615-98686e8721e7%40opentext.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Custom fact for linux service
From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On
Behalf Of Bill Sirinek
> I'm not sure you need a custom fact for this. Can you just check to see if,
> for example, Service['autofs'] or Service['autofs.service'] are defined?
Don't think so. Service is for *controlling* existing services, so using the
fact seems ok to me in case the service
file doesn't come as part of a package, in which case one could simply assume
that if that package is installed,
the service must also be there:
package { 'mypkg':
...
}
service { 'myservice':
...
require => Package['mypkg'],
}
OTOH, if it is a custom service, one could as well manage the service file with
Puppet, so that you can be sure it
exists when you want to manage it, like
file { '/etc/init.d/myservice':
...
}
service { 'myservice':
...
require => File['/etc/init.d/myservice'],
}
HTH...
Dirk
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/DM3PR15MB08803CD16A85DF5CF1F29414AACD0%40DM3PR15MB0880.namprd15.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Custom function that requires a Ruby library module
Hi,
I'm trying to write a custom function to get the primary group of a given user.
The following works in plain Ruby:
def primary_group_of(user:)
require 'etc'
return Etc.getgrgid(Etc.getpwnam(user).gid).name
end
puts primary_group_of(user: 'username' )
Translated into a Puppet function, it looks like:
Puppet::Functions.create_function(:'mylib::primary_group_of') do
dispatch :primary_group_of do
param 'String', :user
end
def primary_group_of(user)
require 'etc'
return Etc.getgrgid(Etc.getpwnam(user).gid).name
end
end
But this, when executed from within a simple file resource like this
class testing {
file { '/tmp/test':
content => 'foo',
owner => 'username',
group => mylib::primary_group_of('username'),
}
}
Only yields: "...Error while evaluating a Function Call, undefined method `gid'
for nil:NilClass..."
Any hints as to what could be wrong here? Seems it doesn't do the "require",
but I'm not sure. Documentation doesn't say anything about using Ruby library
modules.
Thanks...
Dirk
Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText (tm) Discovery | Recommind
Email: dhein...@opentext.com<mailto:dhein...@opentext.com>
Website: www.recommind.de<http://www.recommind.de/>
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon Davies,
Roger Illing, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are
not the intended recipient (or have received this e-mail in error) please
notify the sender immediately and destroy this e-mail. Any unauthorized
copying, disclosure or distribution of the material in this e-mail is strictly
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht
gestattet.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/BYAPR15MB2405BBEF9F2C108F0B2D54D0AADE0%40BYAPR15MB2405.namprd15.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Custom function that requires a Ruby library module
Von: zu...@puzzle.ch [mailto:zu...@puzzle.ch] > Is this user on the Puppet server/master? Because Puppet functions are > evaluated there > and never on the agent. OK, that's my mistake, then. So I'd better use a fact... Thanks for the hint. Bye... Dirk -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/SN6PR15MB24165FB2BC6DB39F8E77AD81AADE0%40SN6PR15MB2416.namprd15.prod.outlook.com. For more options, visit https://groups.google.com/d/optout.
RE: [Puppet Users] Module needed to update kernel
From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On
Behalf Of samarth saxena
> Need some pointers to write a puppet module to update kernel to latest
> update.
> "yum update kernel"
package {'kernel':
ensure => latest, # or some specific version
}
> if one error comes during the update of kernel certificate error w.r.t
> googlecloud rpms then run,
> sudo tee /etc/yum.repos.d/google-cloud.repo << EOM
file {'cloud_repo':
path => '...',
source => '...',
before => Package['kernel']
}
HTH...
Dirk
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mailto:puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_msgid_puppet-2Dusers_784afc3f-2D50b3-2D432e-2D9ec7-2D518783c82689-2540googlegroups.com-3Futm-5Fmedium-3Demail-26utm-5Fsource-3Dfooter&d=DwMFaQ&c=ZgVRmm3mf2P1-XDAyDsu4A&r=TsKycyisPP_6FVCeETRooIdY_8hdAsXoxwbvHso_TaI&m=6fiUYk9fl-oZSu5UumOQNgtP_oM11umkJybN7-AeSF8&s=tQuCv1ytod005fM07pALd5i4MdRhz-Y6OHARshoDfRw&e=.
For more options, visit
https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout&d=DwMFaQ&c=ZgVRmm3mf2P1-XDAyDsu4A&r=TsKycyisPP_6FVCeETRooIdY_8hdAsXoxwbvHso_TaI&m=6fiUYk9fl-oZSu5UumOQNgtP_oM11umkJybN7-AeSF8&s=r19p4dhX-koMUpIBdY1QitCUqxXl-bwsbZNvM_t2X9s&e=.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/SN6PR15MB24169C9667BAB037E8F87627AAB70%40SN6PR15MB2416.namprd15.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Advice on Puppet update to 4
Am 24.07.2015 um 12:59 schrieb Felix Frank: > If you need a good ENC, look at Foreman. If you need reporting, look at > puppetboard or Puppet Explorer. Is any of those ready for Puppet 4? At least Foreman 1.9 (current development version) doesn't seem to be. There is an open ticket, though... Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/55B22B4C.9090909%40recommind.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Custom Type: Error 400 on SERVER: Invalid parameter
Hi, I'm trying to take a new version of a custom type into use, but keep getting the following error message when doing an agent run: "Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter seconds on Wait_for[40 seconds] at /etc/puppet/environments/development/modules/test/manifests/init.pp:7 on node rm-puppet-dev03.recommind.com" I've already restarted the puppetserver process on the master as well as the agent. The agent also shows that there is a difference between the old and the new version of that custom type, but then doesn't use it. Applying the test class with "puppet apply" also works fine. This is on Puppet 3.8.1 (Master and Agent) using puppetserver 1.1.1. Doesn't matter whether the agent runs on Linux or Windows. Any further hints? Thanks... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/55C1F485.9060803%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Custom Type: Error 400 on SERVER: Invalid parameter
Am 05.08.2015 um 13:33 schrieb Dirk Heinrichs: > I've already restarted the puppetserver process on the master as well > as the agent. Nevermind, another server restart seems to have fixed the problem. Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/55C1FB0E.9090807%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Debian Testing and Debian Stable leaving apt.puppetlabs.com
Am 13.08.2015 um 20:13 schrieb Melissa Stone: > We will continue to support and ship packages associated with current > supported Debian codenames (i.e. Debian Wheezy and Debian Jessie). Please also continue to provide packages for Stretch (aka Testing). BTW: Are there any plans to deliver systemd service descriptions with the packages (Debian has decided to switch from sysvinit to systemd). Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/55CD979A.3000903%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Puppet dashboard Debian Jessie
Am 28.08.2015 um 02:42 schrieb Marcos Renato:
> I try to install puppet-dashboard from Debian respository, but see the
> error :
> puppet-dashboard depends on ruby1.8 (>= 1.8.7); however:
> Package ruby1.8 is not installed.
> puppet-dashboard depends on libdbd-mysql-ruby; however:
> Package libdbd-mysql-ruby is not installed.
Don't give too much details, people may be able to help you.
So, how do you try to install it (please provide exact command plus its
complete output)?
Bye...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/55E000F1.1090900%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Puppet dashboard Debian Jessie
Am 28.08.2015 um 13:58 schrieb marcos.ata1...@gmail.com: > apt-get install puppet-dashboard > > Lendo listas de pacotes... Pronto Try again please with LC_ALL=C apt-get install puppet-dashboard so that I can actually understand the language ;) Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/55E04DB7.6040106%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Puppet dashboard Debian Jessie
Am 28.08.2015 um 02:42 schrieb Marcos Renato: > I try to install puppet-dashboard from Debian respository, but see the > error : > > puppet-dashboard depends on ruby1.8 (>= 1.8.7); however: Package > ruby1.8 is not installed. > > puppet-dashboard depends on libdbd-mysql-ruby; however: Package > libdbd-mysql-ruby is not installed. Guess you tried to use the Wheezy repository on Jessie. Jessie doesn't have ruby1.8 anymore. Bye... dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/55E04FD7.6020202%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Puppet dashboard Debian Jessie
Am 28.08.2015 um 02:42 schrieb Marcos Renato:
> I try to install puppet-dashboard
Puppet Dashboard is also deprecated, I'd recommend you use The Foreman
<http://theforeman.org/> instead.
HTH...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/55E05082.7030007%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Puppet dashboard Debian Jessie
Am 28.08.2015 um 14:12 schrieb marcos.ata1...@gmail.com: > /etc/apt/sources.list.d/puppetlabs.list > > deb http://apt.puppetlabs.com wheezy main > deb-src http://apt.puppetlabs.com wheezy main > deb http://apt.puppetlabs.com wheezy dependencies > deb-src http://apt.puppetlabs.com wheezy dependencies > > jessie does not have puppet-dashboard. Yep, because it's deprecated. And Jessie doesn't have ruby1.8 anymore. Try The Foreman <http://theforeman.org/> instead of Dashboard. HTH... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/55E05120.3030409%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Announce: Puppet-Agent 1.2.4, Puppet 4.2.2, Facter 3.1.0
Am 14.09.2015 um 22:00 schrieb Eric Sorenson: > Puppet Agent 1.2.4 is out! This is a new minor release of the all-in-one > agent bundle which incorporates updates to Puppet, Facter, Hiera, and > Mcollective. I'm using a self-written class to manage the Puppet agent package on agent nodes. It works fine on any Linux and Windows Server 2008R2, but fails reproducably on Windows Server 2012R2 when trying to upgrade the agent package. The following message appears in the report: "change from 1.2.2 to 1.2.4 failed: Could not update: Failed to install: The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance." The agent service is running under the local system account on both Windows versions. Any idea what could be wrong here? Thanks... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/55FA6798.2060303%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Announce: Puppet-Agent 1.2.4, Puppet 4.2.2, Facter 3.1.0
Am 17.09.2015 um 12:53 schrieb Francois Lafont: > It's a curious situation where there is an execution of a software > during its upgrade. No, that's quite normal. Think "yum upgrade" upgrading yum itself on Linux. > Finally, it seems to me a not reasonable situation, and we can't hope > a normal behavior during a such situation. I did this for quite some time now, let various 3.x versions upgrade themselves to their successors w/o problems on both Linux and Win 2008. The self-upgrade from agent 1.2.2 to 1.2.4 also works fine on Win 2008. It just seems to be special to Win 2012. Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/55FA9D84.5030406%40recommind.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Announce: Puppet-Agent 1.2.4, Puppet 4.2.2, Facter 3.1.0
Am 17.09.2015 um 16:03 schrieb Rob Reynolds:
> It /can/ work, it's just not deterministic. As you are seeing.
That's not what I'm seeing. I'm seeing that it HAS worked fine on
Windows 2008 for the past 2 years or so (and still does), but doesn't on
Windows 2012.
Bye...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/55FBA789.8060007%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Announce: Puppet-Agent 1.2.4, Puppet 4.2.2, Facter 3.1.0
Am 18.09.2015 um 07:56 schrieb Dirk Heinrichs: > Am 17.09.2015 um 16:03 schrieb Rob Reynolds: > >> It /can/ work, it's just not deterministic. As you are seeing. > > That's not what I'm seeing. I'm seeing that it HAS worked fine on > Windows 2008 for the past 2 years or so (and still does), but doesn't > on Windows 2012. I'm also seeing that it's not a problem DURING upgrade, but a problem STARTING the installer (at least according to the error message). Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com <mailto:d...@recommind.com> *Skype*: dirk.heinrichs.recommind www.recommind.com <http://www.recommind.com> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/55FBAFC1.4050700%40recommind.com. For more options, visit https://groups.google.com/d/optout.
