Ed, It sound correct. The tag/facter value @uptime_seconds changes each
time you run the puppet on agent machine.
During the puppet catalog run, puppet first fetch the facter value and then
apply the puppet manifests. So whatever the value of facter are set before
the puppet manifests deployment.
Y
- Original Message -
> Hi,
>
> is this puppet 3? I shall suppose it is.
>
> With the parameter name of "bar", you likely trigger the automagic hiera
> lookup of foo::bar, which is (naturally) not done using hiera_array.
> Apparently, this overrides the explicit call to hiera_array.
>
>
... and $name is the default variable given to you by puppet, so you don't
have to define it. Works like $_ in perl.
On Wed, Aug 21, 2013 at 7:18 PM, Peter Bukowinski wrote:
> You define an array-containing variable like this:
>
> $mounts = [ 'directory1', 'directory2', 'directory3' ]
>
>
Thanks. These are good pointers.
--
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
Ok. Thanks a lot!
--
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@go
Do you see any active connections? A query like this in pgsql might
give you some information:
SELECT datname,procpid,current_query FROM pg_stat_activity;
On Thu, Aug 22, 2013 at 9:54 AM, Miguel Angel Coa Morales
wrote:
> My setting for db I've the next:
>
> […..]
> [root@master puppet]# cat
Correct! That way the Master doesn't have to know the specifics, it just
queues the mail locally.
On Thu, Aug 22, 2013 at 10:51 AM, ytmp123 wrote:
> Ah ok,
>
> So I've to install and configure an SMTP-Server on the local-machine, on
> which the puppetmaster is installed. This local SMTP-Server
Ah ok,
So I've to install and configure an SMTP-Server on the local-machine, on
which the puppetmaster is installed. This local SMTP-Server then has to
connect to the real SMTP-Server out there in the Internet. Is that right?
thanks
--
You received this message because you are subscribed to t
My setting for db I've the next:
[…..]
[root@master puppet]# cat /etc/puppetdb/conf.d/config.ini | grep -v ^#
[global]
vardir = /var/lib/puppetdb
logging-config = /etc/puppetdb/log4j.properties
resource-query-limit = 2
[command-processing]
[database]
classname = org.postgresql.Driver
su
Regarding that fqdn and uptime_seconds are facts, that is understood.
The agent node updating the file and triggered the content change may be
obvious to you, but I'm a puppet beginner, and I yet don't have a solid
understanding of the catalog run or how, when or where the tags get
updated.
This is something you should be configuring on the Puppet master's local
MTA, be it Sendmail or Postfix or whatever. Then Puppet will just attempt
to send email through localhost, and the MTA can determine how to route it
and with what authentication methods.
On Thursday, August 22, 2013 8:21:2
Check your /etc/puppetdb/database.ini, it may be configured for
hsqldb. If in doubt provide the file here and we can take a look.
Instructions for configuring this specifically for PostgreSQL are
here: http://docs.puppetlabs.com/puppetdb/1.4/configure.html#using-postgresql
On Thu, Aug 22, 2013 at
Ok, I've got a workaround. if I return some valid YAML in addition to the
0 return value, everything works like poptarts:
*null_obj = { 'vars' : { 'emptyvar': '0'}}*
*print yaml.dump(null_obj, Dumper = yaml.SafeDumper)*
*exit(0)*
then the node definitions (including defa
On 22/08/13 16:39, Ed Young wrote:
Thanks for the response. There doesn't seem to be another process
updating the files on before the puppet run. I believe the issue was the
presence of a dynamic tag on the template file.
The problem appears to be that the tag <%= @uptime_seconds %> was in
some
Yes I can connect but when i list tables i have the next message "No relations
found."
1. Connect from my node: [root@node1 ~]# psql -h 10.0.0.132 puppetdb puppetdb
2. Show tables: puppetdb=> \d
No relations found.
3. My databases are:
puppetdb=> \l puppetdb
Li
Hi,
is this puppet 3? I shall suppose it is.
With the parameter name of "bar", you likely trigger the automagic hiera
lookup of foo::bar, which is (naturally) not done using hiera_array.
Apparently, this overrides the explicit call to hiera_array.
I'm not sure wether that's as designed, you may
Thanks for the response. There doesn't seem to be another process updating
the files on before the puppet run. I believe the issue was the presence of
a dynamic tag on the template file.
The problem appears to be that the tag <%= @uptime_seconds %> was in some
of the configuration files. When
I have a weird issue. I'm using puppet 3.2.3 and I have a simple module to
install an msi (module below).
If I run manually (from the start menu, or cmd using puppet agent - it
works fine and installs. If I let the 30 minute scheduled run happen - I
get "Storage to process this request is not
Hi guys,
I want the Puppet-Master to notify the admin via E-Mail: SMTP, SSL &
Authentification is required.
How can I do that with the help of "tagmail"?
Have you some clue for me?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscri
Hi folks,
I just managed to reproduce on a very small scale an issue
that's I've debugged for hours yesterday.
if we have a class:
class foo (
$bar = hiera_array('foo::bar', $foo::params::bar),
) inherits foo::params {
notify{ "foo::bar: ${bar}": }
}
class foo::param
Take a look at the last paragraph here:
http://docs.puppetlabs.com/puppet/3/reference/lang_variables.html#assignment
$role = 'nameserver'
assigns a variable within the 'role::nameserver' namespace (allowed), while
$::role = 'nameserver'
assigns a top level variable (not allowed).
Eric
On T
Hi,
I had faced the same issue when I was configuring puppet.
what are the contents of your /etc/puppet/auth.conf file ?
Wikram
On Thursday, August 22, 2013 1:25:27 PM UTC+5:30, Salvador Priego Sácnhez
wrote:
>
> Hi,
>
> I'm having some troubles related with reports.
> Catalogs are updated be
We're trying to set a role variable in one of our role classes i.e.
class role::nameserver {
$::role = 'nameserver'
include profile::baseline
}
however we get the following error
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not parse for environment p
Hi,
I'm having some troubles related with reports.
Catalogs are updated between server and clients but I cannot submit reports
because of the 401 error. All is caused by the security that I had to put
and I don't know how to solve it.
Anybody knows how to fix it?
Thanks in advance.
--
You r
Hi Stuart,
I think you have to downgrade your rubygems version- 2.0.6 and try to
install puppet this might work.
Refer Following link for supported version of ruby,
http://docs.puppetlabs.com/guides/platforms.html#ruby-versions
Thanks and Regards,
Rahul Khengare,
NTT DATA OSS-Center, Pune,
Hi Mathias,
I'm experiencing a similar problem. did you manage to resolve it?
Thanks,
Michael
On Saturday, 20 July 2013 00:35:42 UTC+10, Mathias Kaufmann wrote:
>
> Hi,
>
> I've tested puppet on Debian 7, 64bit. When I run "puppet node classify" I
> get an error as shown below. Is this a conf
26 matches
Mail list logo