hi everyone, i'm trying to roll out an .exe file for the puppet package
provider windows.
my manifest looks like this:
$package_source =
http://puppet.local.domain/base_check_mk/windows/check-mk-agent-1.2.3i1.exe;
$package_name = Check_MK Agent 1.2.3i1
package { $package_name:
On 04.08.2013 08:35, fuzzy186 wrote:
And I got this error:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid
resource type balancermember at
/etc/puppet/modules/apache/manifests/worker.pp:4 on node
Hi,
I assume that you have the exe file within your module in the files folder.
Adopt the source attribute to the following:
source = 'puppet:///modulename/filename
Put the exe in your module:
modulepath/modulename/files/exe filename
http://docs.puppetlabs.com/references/latest/type.html#file
I'm running puppet from vagrant, everything else runs as root so I guess
this also runs as root (is there a way to specifiy to run as root in the
puppet command?)
On Monday, August 5, 2013 1:06:52 AM UTC+3, denmat wrote:
Did you see this in the log?
Hi,
from the official documentation:
Additional Notes on Windows Packages
- The source parameter is required, and must refer to a local .msi
file, a file from a mapped drive, or a UNC path. You can distribute
packages as file resources. Puppet URLs are not currently supported
On Friday, August 2, 2013 10:03:19 AM UTC-5, cvv...@gmail.com wrote:
Version: puppet-3.2.3-1.el6.noarch.rpm
--
I just try to create a class as parameters container like this:
cat /etc/puppet/modules/ssh/manifests/params.pp EOF
class ssh::params {
Hello,
I want to add user with puppet. In my password string I have three times
the $.
The result is that in the password of the the /etc/shadow file everything
from $ until a . or / is missing.
password =
Could the problem be the variable name : group ?
That is a Puppet Type
Try changing it.
Hope this helps. Just a wild guess.
“Sometimes I think the surest sign that intelligent life exists elsewhere in
the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin
Here my init.pp
define useradd ( $name, $uid, $group, $gid, $password, $shell, $sshkeytype,
$sshkey) {
$homedir = $kernel ? {
'SunOS' = '/export/home',
default = '/home'
}
$username = $title
user { $username:
ensure = present,
comment = $name,
uid
On Friday, August 2, 2013 12:07:24 PM UTC-5, Jacob McCoy Wade wrote:
On Friday, August 2, 2013 6:43:01 AM UTC-7, jcbollinger wrote:
On Thursday, August 1, 2013 2:37:03 PM UTC-5, Jacob McCoy Wade wrote:
The closest I've come is to use:
$random_1 = generate('/bin/sh', '-c', '\/bin/cat
On 05.08.2013 15:16, Andreas Dvorak wrote:
Hello,
I want to add user with puppet. In my password string I have three times
the $.
The result is that in the password of the the /etc/shadow file
everything from $ until a . or / is missing.
password =
On Monday, August 5, 2013 3:04:08 AM UTC-5, Alon Nisser wrote:
I'm running puppet from vagrant, everything else runs as root so I guess
this also runs as root (is there a way to specifiy to run as root in the
puppet command?)
No. Mechanisms by which unprivileged processes can obtain
thank you,
single quotes solved it
regards,
Andreas
--
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
Having the same issue but not from an upgrade -- have not been able to get
the dashboard to get reports from puppet clients yarr
On Thursday, 20 June 2013 14:29:58 UTC-7, Joe Benson wrote:
I upgraded our puppetmaster from 2.7.20 to 2.7.22 and puppet dashboard
quit importing reports. I'm
With the risc I ask a queston answered a hunderd times before (which I
couldn't find)...
On node A I want to create a ssh key. For this I exec a ssh-keygen. Now I
want the generated public key added to the authorized key file of node B.
Probably I need the ssh_authorized_key resource for this.
On Mon, Aug 5, 2013 at 10:16 AM, Andreas Dvorak
andreas.dvo...@googlemail.com wrote:
Hello,
I want to add user with puppet. In my password string I have three times the
$.
The result is that in the password of the the /etc/shadow file everything
from $ until a . or / is missing.
Hello,
I'm looking for a running infrastructure with the combination of Hubot,
Puppet, Mcollective and Jenkins. I know about the Hubot setup from
Github, but I can't find any information of a successfully setup with
Mcollective.
I have some questions regarding the connections between the
Yes, I do intend to list all the files and their expected mode and
ownership, I just want to figure out the nicest, most succinct way to do
that.
Wildcards and recursive listings will do me no good -- these files are
scattered all over.
Thanks.
On Friday, August 2, 2013 3:33:57 PM UTC-4,
Nagios is restarted every time a host or service is added, but never when
removing hosts or services.
The client resources:
@@nagios_host { $::fqdn:
ensure= 'present',
alias = $::hostname,
address = $::ipaddress,
use = 'linux-server',
}
@@nagios_service {
It seems this statement is working for latest puppet+facter:
if($::processorcount25).
Before there was concern that puppet would not auto convert string to
number, is this still a concern here?
I am wondering if I should convert the facter string value to integer first
before comparing it ..
--
This is an extract from a defined type I use to create accounts:
code extract
define users::useraccount (
) {
..
File {
owner = $username,
group = $username,
mode = '0600',
}
..
Can anyone tell me why this is legal:
file { /etc/cron.d:
owner = root,
group = root,
mode = $operatingsystem ? {
'Solaris' = 0755,
default = 0700,
}
}
...And yet if I have any resource attributes below the mode selector
root writes:
Can anyone tell me why this is legal:
file { /etc/cron.d:
owner = root,
group = root,
mode = $operatingsystem ? {
'Solaris' = 0755,
default = 0700,
}
}
...And yet if I have any
Greetings:
I'm having trouble connecting to PuppetDB. When I execute *sudo puppet
agent --test* on a client node, I receive the following:
Warning: Unable to fetch my node definition, but the agent run will
continue:
Warning: Error 400 on SERVER: Could not retrieve facts for
Check your /etc/puppetdb/conf.d/jetty.ini file for the configuration
items ssl-host host. These should both be set to the IP address you
want PuppetDB to listen on, or 0.0.0.0 for all IP addresses. This is
probably set to 127.0.0.1 or something now, which might explain why
PuppetDB is not
Hi there,
On 05/08/13 10:51 AM, John Santana wrote:
When I remove the host from the database via
delete from fact_values where host_id='N';
delete from resources where host_id='N';
delete from hosts where id='N';
if you remove the host exported resource in the manifests and the DB,
then
Ken... you are a genius! I, for some reason, had entered the PuppetDB's
FQDN in there. The manual, found
herehttp://docs.puppetlabs.com/puppetdb/latest/configure.html#jetty-http-settings,
reads:
host
This sets the hostname to listen on for unencrypted HTTP traffic. If not
supplied, we bind
On Mon, Aug 05, 2013 at 04:22:41PM -0400, Gabriel Filion wrote:
you need to export the resource with ensure = absent and run puppet on
the host, then on the nagios server so that everything runs fine.
Dozens of VMs are routinely destroyed on a weekly basis and in an
automated fashion based on
On 06/26/2013 07:27 PM, Alessandro Franceschi wrote:
Good point.
In the doc I placed some possible examples on where to assign names, but
more (or remarks on the ones listed) cases are welcomed.
(Let me have your email for an invitation to edit)
Btw, comments and access to:
On 05/08/13 04:33 PM, puppetl...@downhomelinux.com wrote:
On Mon, Aug 05, 2013 at 04:22:41PM -0400, Gabriel Filion wrote:
you need to export the resource with ensure = absent and run puppet on
the host, then on the nagios server so that everything runs fine.
Dozens of VMs are routinely
That's quite nice, I like the reduced verbosity of the code and
essentiality of an all in one (init.pp) location for resources.
For better reusability I'd provide a *_template option to manage the
templates of all the different files you manage, leaving as the default
the currently hardcoded
Installing from a URL is a feature of msiexec rather than the puppet
provider. I think you're stuck using a file resource to download the .exe
and then installing from a local path (or serving directly from a UNC
path). It would be neat if the windows package provider could eat
puppet:///
Well, actually it is straight forward.
Just create a ssh_authorized_keys resource for an user for both nodes and
store the private key in .ssh/id_rsa or define Identity key file in
.ssh/config.
On Sat, Aug 3, 2013 at 7:12 AM, Mark Ruys mark.r...@gmail.com wrote:
With the risc I ask a
33 matches
Mail list logo
