Hello,
Puppet 0.24.8 on both the client and server, CentOS5.3.
It is applied repeatedly when puppetrun is executed,
and a lot of report mails are transmitted.
There is host repeatedly applied,
and is host applied only once.
Every time, it is different.
Is the setting somewhere wrong?
-----
# puppetrun -p 10 --tag cron_www_g1 --host devel03.devel.local --host
devel04.devel.local --host devel05.devel.local --host
devel06.devel.local
-----
puppetmaster server''s /var/log/messages:
(Devel05 was pulled out as an example.)
Oct 20 12:22:29 devel-111 puppetmasterd[14811]: Expiring the node
cache of devel05.devel.local
Oct 20 12:22:29 devel-111 puppetmasterd[14811]: Not using expired node
for devel05.devel.local from cache; expired at Tue Oct 20 12:21:29
+0900 2009
Oct 20 12:22:29 devel-111 puppetmasterd[14811]: Caching node for
devel05.devel.local
Oct 20 12:22:29 devel-111 puppetmasterd[14811]: Compiled catalog for
devel05.devel.local in 0.13 seconds
Oct 20 12:22:33 devel-111 puppetmasterd[14811]: Expiring the node
cache of devel05.devel.local
Oct 20 12:22:33 devel-111 puppetmasterd[14811]: Not using expired node
for devel05.devel.local from cache; expired at Tue Oct 20 12:21:33
+0900 2009
Oct 20 12:22:33 devel-111 puppetmasterd[14811]: Caching node for
devel05.devel.local
Oct 20 12:22:33 devel-111 puppetmasterd[14811]: Compiled catalog for
devel05.devel.local in 0.04 seconds
Oct 20 12:22:34 devel-111 puppetmasterd[14811]: Expiring the node
cache of devel05.devel.local
Oct 20 12:22:34 devel-111 puppetmasterd[14811]: Not using expired node
for devel05.devel.local from cache; expired at Tue Oct 20 12:21:34
+0900 2009
Oct 20 12:22:34 devel-111 puppetmasterd[14811]: Caching node for
devel05.devel.local
Oct 20 12:22:34 devel-111 puppetmasterd[14811]: Compiled catalog for
devel05.devel.local in 0.04 seconds
Oct 20 12:22:38 devel-111 puppetmasterd[14811]: (mount[data])
Sending /
data/bw_base/var/spool/cron/www-g1 to devel05.devel.local
Oct 20 12:22:39 devel-111 puppetmasterd[14811]: (mount[data])
Sending /
data/bw_base/var/spool/cron/www-g1 to devel05.devel.local
Oct 20 12:22:40 devel-111 puppetmasterd[14811]: (mount[data])
Sending /
data/bw_base/var/spool/cron/www-g1 to devel05.devel.local
Oct 20 12:22:40 devel-111 puppetmasterd[14811]: (mount[data])
Sending /
data/bw_base/var/spool/cron/www-g1 to devel05.devel.local
Oct 20 12:22:41 devel-111 puppetmasterd[14811]: (mount[data])
Sending /
data/bw_base/var/spool/cron/www-g1 to devel05.devel.local
Oct 20 12:22:42 devel-111 puppetmasterd[14811]: (mount[data])
Sending /
data/bw_base/var/spool/cron/www-g1 to devel05.devel.local
Oct 20 12:22:43 devel-111 puppetmasterd[14811]: (mount[data])
Sending /
data/bw_base/var/spool/cron/www-g1 to devel05.devel.local
Oct 20 12:22:44 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 20 12:22:45 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 20 12:22:46 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 20 12:22:47 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 20 12:22:48 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 20 12:22:49 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 20 12:22:50 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 20 12:22:50 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 20 12:22:51 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 20 12:22:51 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 20 12:22:52 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 20 12:22:52 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 20 12:22:53 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 20 12:22:54 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 20 12:22:55 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 20 12:22:56 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 20 12:22:56 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 20 12:22:57 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 20 12:22:58 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 20 12:22:58 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
-----
puppet client''s /var/log/messages:
Oct 20 12:22:24 devel05 puppetd[28835]: devel-111.devel.local
(172.25.195.111) triggered run
Oct 20 12:22:34 devel05 puppetd[28835]: Starting catalog run
Oct 20 12:22:43 devel05 puppetd[28835]: (//cron_www_g1/File[/var/
spool/
cron/www]) Filebucketed to with sum ef042c30a04a3f8b892e4be3a1009c53
Oct 20 12:22:43 devel05 puppetd[28835]: (//cron_www_g1/File[/var/
spool/
cron/www]/source) replacing from source
puppet://devel-111.devel.local/data/bw_base/var/spool/cron/www-g1 with
contents {md5}7b2f019b56fa8593d4e3973edc89d83c
Oct 20 12:22:58 devel05 puppetd[28835]: Finished catalog run in 24.22
seconds
-----
puppetmaster server''s
puppet.conf
[main]
vardir = /var/lib/puppet
logdir = /var/log/puppet
rundir = /var/run/puppet
ssldir = $vardir/ssl
[puppetmasterd]
reports = tagmail, log
reportfrom = ***@***.***
tagmail.conf
all: ***@***.***
fileserver.conf
[data]
path /var/lib/puppet/data
allow *
site.pp
$fileserver = ''devel-111.devel.local''
node ''devel05.devel.local'' {
include ''cron_www_g1''
}
class cron_www_g1 {
file {
''/var/spool/cron/www'':
source => "puppet://$fileserver/data/bw_base/var/spool/cron/www-
g1",
mode => 600, owner => ''www'', group =>
''root'';
}
}
-----
puppet client''s
puppet.conf
[main]
vardir = /var/lib/puppet
logdir = /var/log/puppet
rundir = /var/run/puppet
ssldir = $vardir/ssl
[puppetd]
configtimeout = 300
server = devel-111.devel.local
daemonize = true
listen = true
report = true
namespaceauth.conf
[puppetrunner]
allow devel-111.devel.local
/etc/sysconfig/puppet
PUPPET_EXTRA_OPTS="--no-client"
// kyawai
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
On Oct 19, 2009, at 9:24 PM, kyawai wrote:> > Hello, > > Puppet 0.24.8 on both the client and server, CentOS5.3. > > It is applied repeatedly when puppetrun is executed, > and a lot of report mails are transmitted. > There is host repeatedly applied, > and is host applied only once. > Every time, it is different. > > Is the setting somewhere wrong?You might have encountered a bug - you''ve told it to parallelize by 10, but only provided 3 hosts, so it might be triggering each of them more than once. That wouldn''t explain this many runs, though; are they all the same host or something? And even then, the runs are taking 24 seconds, so you can''t be running them concurrently on a single machine. So, um, no, I''ve no idea what''s going on, but more below.> ----- > # puppetrun -p 10 --tag cron_www_g1 --host devel03.devel.local --host > devel04.devel.local --host devel05.devel.local --host > devel06.devel.local > > ----- > puppetmaster server''s /var/log/messages: > (Devel05 was pulled out as an example.) > > Oct 20 12:22:29 devel-111 puppetmasterd[14811]: Expiring the node > cache of devel05.devel.local > Oct 20 12:22:29 devel-111 puppetmasterd[14811]: Not using expired node > for devel05.devel.local from cache; expired at Tue Oct 20 12:21:29 > +0900 2009 > Oct 20 12:22:29 devel-111 puppetmasterd[14811]: Caching node for > devel05.devel.local > Oct 20 12:22:29 devel-111 puppetmasterd[14811]: Compiled catalog for > devel05.devel.local in 0.13 seconds > Oct 20 12:22:33 devel-111 puppetmasterd[14811]: Expiring the node > cache of devel05.devel.local > Oct 20 12:22:33 devel-111 puppetmasterd[14811]: Not using expired node > for devel05.devel.local from cache; expired at Tue Oct 20 12:21:33 > +0900 2009 > Oct 20 12:22:33 devel-111 puppetmasterd[14811]: Caching node for > devel05.devel.local > Oct 20 12:22:33 devel-111 puppetmasterd[14811]: Compiled catalog for > devel05.devel.local in 0.04 seconds > Oct 20 12:22:34 devel-111 puppetmasterd[14811]: Expiring the node > cache of devel05.devel.local > Oct 20 12:22:34 devel-111 puppetmasterd[14811]: Not using expired node > for devel05.devel.local from cache; expired at Tue Oct 20 12:21:34 > +0900 2009 > Oct 20 12:22:34 devel-111 puppetmasterd[14811]: Caching node for > devel05.devel.local > Oct 20 12:22:34 devel-111 puppetmasterd[14811]: Compiled catalog for > devel05.devel.local in 0.04 seconds > Oct 20 12:22:38 devel-111 puppetmasterd[14811]: (mount[data]) > Sending / > data/bw_base/var/spool/cron/www-g1 to devel05.devel.local > Oct 20 12:22:39 devel-111 puppetmasterd[14811]: (mount[data]) > Sending / > data/bw_base/var/spool/cron/www-g1 to devel05.devel.local > Oct 20 12:22:40 devel-111 puppetmasterd[14811]: (mount[data]) > Sending / > data/bw_base/var/spool/cron/www-g1 to devel05.devel.local > Oct 20 12:22:40 devel-111 puppetmasterd[14811]: (mount[data]) > Sending / > data/bw_base/var/spool/cron/www-g1 to devel05.devel.local > Oct 20 12:22:41 devel-111 puppetmasterd[14811]: (mount[data]) > Sending / > data/bw_base/var/spool/cron/www-g1 to devel05.devel.local > Oct 20 12:22:42 devel-111 puppetmasterd[14811]: (mount[data]) > Sending / > data/bw_base/var/spool/cron/www-g1 to devel05.devel.local > Oct 20 12:22:43 devel-111 puppetmasterd[14811]: (mount[data]) > Sending / > data/bw_base/var/spool/cron/www-g1 to devel05.devel.local > Oct 20 12:22:44 devel-111 puppetmasterd[14811]: Processing reports > tagmail, log for devel05.devel.local > Oct 20 12:22:45 devel-111 puppetmasterd[14811]: Processing reports > tagmail, log for devel05.devel.local > Oct 20 12:22:46 devel-111 puppetmasterd[14811]: Processing reports > tagmail, log for devel05.devel.local > Oct 20 12:22:47 devel-111 puppetmasterd[14811]: Processing reports > tagmail, log for devel05.devel.local > Oct 20 12:22:48 devel-111 puppetmasterd[14811]: Processing reports > tagmail, log for devel05.devel.local > Oct 20 12:22:49 devel-111 puppetmasterd[14811]: Processing reports > tagmail, log for devel05.devel.local > Oct 20 12:22:50 devel-111 puppetmasterd[14811]: Processing reports > tagmail, log for devel05.devel.local > Oct 20 12:22:50 devel-111 puppetmasterd[14811]: Processing reports > tagmail, log for devel05.devel.local > Oct 20 12:22:51 devel-111 puppetmasterd[14811]: Processing reports > tagmail, log for devel05.devel.local > Oct 20 12:22:51 devel-111 puppetmasterd[14811]: Processing reports > tagmail, log for devel05.devel.local > Oct 20 12:22:52 devel-111 puppetmasterd[14811]: Processing reports > tagmail, log for devel05.devel.local > Oct 20 12:22:52 devel-111 puppetmasterd[14811]: Processing reports > tagmail, log for devel05.devel.local > Oct 20 12:22:53 devel-111 puppetmasterd[14811]: Processing reports > tagmail, log for devel05.devel.local > Oct 20 12:22:54 devel-111 puppetmasterd[14811]: Processing reports > tagmail, log for devel05.devel.local > Oct 20 12:22:55 devel-111 puppetmasterd[14811]: Processing reports > tagmail, log for devel05.devel.local > Oct 20 12:22:56 devel-111 puppetmasterd[14811]: Processing reports > tagmail, log for devel05.devel.local > Oct 20 12:22:56 devel-111 puppetmasterd[14811]: Processing reports > tagmail, log for devel05.devel.local > Oct 20 12:22:57 devel-111 puppetmasterd[14811]: Processing reports > tagmail, log for devel05.devel.local > Oct 20 12:22:58 devel-111 puppetmasterd[14811]: Processing reports > tagmail, log for devel05.devel.local > Oct 20 12:22:58 devel-111 puppetmasterd[14811]: Processing reports > tagmail, log for devel05.devel.local > > ----- > puppet client''s /var/log/messages: > > Oct 20 12:22:24 devel05 puppetd[28835]: devel-111.devel.local > (172.25.195.111) triggered run > Oct 20 12:22:34 devel05 puppetd[28835]: Starting catalog run > Oct 20 12:22:43 devel05 puppetd[28835]: (//cron_www_g1/File[/var/ > spool/ > cron/www]) Filebucketed to with sum ef042c30a04a3f8b892e4be3a1009c53 > Oct 20 12:22:43 devel05 puppetd[28835]: (//cron_www_g1/File[/var/ > spool/ > cron/www]/source) replacing from source > puppet://devel-111.devel.local/data/bw_base/var/spool/cron/www-g1 with > contents {md5}7b2f019b56fa8593d4e3973edc89d83c > Oct 20 12:22:58 devel05 puppetd[28835]: Finished catalog run in 24.22 > seconds > > > ----- > puppetmaster server''s > puppet.conf > [main] > vardir = /var/lib/puppet > logdir = /var/log/puppet > rundir = /var/run/puppet > ssldir = $vardir/ssl > [puppetmasterd] > reports = tagmail, log > reportfrom = ***@***.*** > > tagmail.conf > all: ***@***.*** > > fileserver.conf > [data] > path /var/lib/puppet/data > allow * > > site.pp > $fileserver = ''devel-111.devel.local'' > > node ''devel05.devel.local'' { > include ''cron_www_g1'' > } > > class cron_www_g1 { > file { > ''/var/spool/cron/www'': > source => "puppet://$fileserver/data/bw_base/var/spool/cron/www- > g1", > mode => 600, owner => ''www'', group => ''root''; > } > } > > > ----- > puppet client''s > > puppet.conf > [main] > vardir = /var/lib/puppet > logdir = /var/log/puppet > rundir = /var/run/puppet > ssldir = $vardir/ssl > > [puppetd] > configtimeout = 300 > server = devel-111.devel.local > daemonize = true > listen = true > report = true > > namespaceauth.conf > [puppetrunner] > allow devel-111.devel.local > > /etc/sysconfig/puppet > PUPPET_EXTRA_OPTS="--no-client"Why is this set? -- Ours is the age that is proud of machines that think and suspicious of men who try to. -- H. Mumford Jones --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Thank you for reply.
Sorry, value ''10'' of the parallelize is not so significant,
because even if the value is changed, it becomes a same deal.
It became a same deal when not specifying it.
It is using report mail to information share a manifest application
result
because multiple people manage the server.
For instance, when the same manifest as 10 clients is applied,
puppetrun is executed with the devel-111 server by which puppetmasterd
does run.
# puppetrun --tag cron_www_g1 -p 10 --host devel01.devel.local --host
devel02.devel.local \
--host devel03.devel.local --host devel04.devel.local --host
devel05.devel.local \
--host devel06.devel.local --host devel07.devel.local --host
devel08.devel.local \
--host devel09.devel.local --host devel10.devel.local
Failed to load ruby LDAP library. LDAP functionality will not be
available
Triggering devel01.devel.local
Triggering devel02.devel.local
Triggering devel03.devel.local
devel01.devel.local finished with exit code 0
devel03devel.local finished with exit code 0
devel02.devel.local finished with exit code 0
Triggering devel05.devel.local
Triggering devel07.devel.local
Triggering devel04.devel.local
Triggering devel09.devel.local
Triggering devel10.devel.local
Triggering devel08.devel.local
Triggering devel06.devel.local
devel108.devel.local finished with exit code 0
devel09.devel.local finished with exit code 0
devel10.devel.local finished with exit code 0
devel04.devel.local finished with exit code 0
devel06.devel.local finished with exit code 0
devel05.devel.local finished with exit code 0
devel07.devel.local finished with exit code 0
Finished
Then, the following logs remain in devel-111.
Oct 21 16:47:24 devel-111 puppetmasterd[14811]: Expiring the node
cache of devel05.devel.local
Oct 21 16:47:24 devel-111 puppetmasterd[14811]: Not using expired node
for devel05.devel.local from cache; expired at Wed Oct 21 16:46:24
+0900 2009
Oct 21 16:47:24 devel-111 puppetmasterd[14811]: Caching node for
devel05.devel.local
Oct 21 16:47:24 devel-111 puppetmasterd[14811]: Compiled catalog for
devel05.devel.local in 0.03 seconds
Oct 21 16:47:24 devel-111 puppetmasterd[14811]: Expiring the node
cache of devel05.devel.local
Oct 21 16:47:25 devel-111 puppetmasterd[14811]: Not using expired node
for devel05.devel.local from cache; expired at Wed Oct 21 16:46:24
+0900 2009
Oct 21 16:47:25 devel-111 puppetmasterd[14811]: Caching node for
devel05.devel.local
Oct 21 16:47:25 devel-111 puppetmasterd[14811]: Compiled catalog for
devel05.devel.local in 0.11 seconds
Oct 21 16:47:26 devel-111 puppetmasterd[14811]: Expiring the node
cache of devel05.devel.local
Oct 21 16:47:26 devel-111 puppetmasterd[14811]: Not using expired node
for devel05.devel.local from cache; expired at Wed Oct 21 16:46:26
+0900 2009
Oct 21 16:47:26 devel-111 puppetmasterd[14811]: Caching node for
devel05.devel.local
Oct 21 16:47:26 devel-111 puppetmasterd[14811]: Compiled catalog for
devel05.devel.local in 0.15 seconds
Oct 21 16:47:27 devel-111 puppetmasterd[14811]: Expiring the node
cache of devel05.devel.local
Oct 21 16:47:27 devel-111 puppetmasterd[14811]: Not using expired node
for devel05.devel.local from cache; expired at Wed Oct 21 16:46:27
+0900 2009
Oct 21 16:47:28 devel-111 puppetmasterd[14811]: Caching node for
devel05.devel.local
Oct 21 16:47:28 devel-111 puppetmasterd[14811]: Compiled catalog for
devel05.devel.local in 0.05 seconds
Oct 21 16:47:30 devel-111 puppetmasterd[14811]: (mount[data]) Sending /
data/bw_base/var/spool/cron/www-g1 to devel05.devel.local
Oct 21 16:47:33 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 21 16:47:33 devel-111 puppetmasterd[30242]: Sending report to
***@***.***
Oct 21 16:47:33 devel-111 puppetmasterd[14811]: (//cron_www_g1/File[/
var/spool/cron/www]) Filebucketed to with sum
7b2f019b56fa8593d4e3973edc89d83c
Oct 21 16:47:33 devel-111 puppetmasterd[14811]: (//cron_www_g1/File[/
var/spool/cron/www]/source) replacing from source
puppet://devel-111.devel.local/data/bw_base/var/spool/cron/www-g1 with
contents {md5}ef042c30a04a3f8b892e4be3a1009c53
Oct 21 16:47:34 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 21 16:47:34 devel-111 puppetmasterd[30251]: Sending report to
***@***.***
Oct 21 16:47:34 devel-111 puppetmasterd[14811]: (//cron_www_g1/File[/
var/spool/cron/www]) Filebucketed to with sum
7b2f019b56fa8593d4e3973edc89d83c
Oct 21 16:47:34 devel-111 puppetmasterd[14811]: (//cron_www_g1/File[/
var/spool/cron/www]/source) replacing from source
puppet://devel-111.devel.local/data/bw_base/var/spool/cron/www-g1 with
contents {md5}ef042c30a04a3f8b892e4be3a1009c53
Oct 21 16:47:35 devel-111 puppetmasterd[14811]: Processing reports
tagmail, log for devel05.devel.local
Oct 21 16:47:35 devel-111 puppetmasterd[30257]: Sending report to
***@***.***
Oct 21 16:47:35 devel-111 puppetmasterd[14811]: (//cron_www_g1/File[/
var/spool/cron/www]) Filebucketed to with sum
7b2f019b56fa8593d4e3973edc89d83c
Oct 21 16:47:35 devel-111 puppetmasterd[14811]: (//cron_www_g1/File[/
var/spool/cron/www]/source) replacing from source
puppet://devel-111.devel.local/data/bw_base/var/spool/cron/www-g1 with
contents {md5}ef042c30a04a3f8b892e4be3a1009c53
.........
And, only the following logs remain in the client.
Oct 21 16:47:16 devel05 puppetd[31054]: devel-111.devel.local
(172.25.195.111) triggered run
Oct 21 16:47:28 devel05 puppetd[31054]: Starting catalog run
Oct 21 16:47:31 devel05 puppetd[31054]: (//cron_www_g1/File[/var/spool/
cron/www]) Filebucketed to with sum 7b2f019b56fa8593d4e3973edc89d83c
Oct 21 16:47:16 devel05 puppetd[31054]: devel-111.devel.local
(172.25.195.111) triggered run
Oct 21 16:47:28 devel05 puppetd[31054]: Starting catalog run
Oct 21 16:47:31 devel05 puppetd[31054]: (//cron_www_g1/File[/var/spool/
cron/www]) Filebucketed to with sum 7b2f019b56fa8593d4e3973edc89d83c
Oct 21 16:47:31 devel05 puppetd[31054]: (//cron_www_g1/File[/var/spool/
cron/www]/source) replacing from source
puppet://devel-111.devel.local/data/bw_base/var/spool/cron/www-g1 with
contents {md5}ef042c30a04a3f8b892e4be3a1009c53
Oct 21 16:48:06 devel05 puppetd[31054]: Finished catalog run in 38.22
seconds
The log from which the manifest is repeatedly applied in devel-111
until "Finished catalog run" is written, and report is transmitted is
written.
Other client is also similar.
1 or two or more reports of each of the clients are transmitted.
It is likely to reach 30 per server at times.
It happens when option "--host" is used with puppetrun in plurals.
But, it doesn''t happen in case of one.
The relation seem not to be in the value of "-p", and
"--tag".
It thinks whether there is a problem in the part of the notification
from puppetd between "16:48:06"-"16:47:31"
because there is an access from devel05 many times
when tcpdump is executed with devel-111.
It is anxious that "Compiled catalog" happens many times by
puppetmasterd.
Besides, it acquires it when there is necessary information.
// kyawai
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
On Oct 21, 2009, at 2:50 AM, kyawai wrote:> > Thank you for reply. > > Sorry, value ''10'' of the parallelize is not so significant, > because even if the value is changed, it becomes a same deal. > It became a same deal when not specifying it. > > It is using report mail to information share a manifest application > result > because multiple people manage the server. > > For instance, when the same manifest as 10 clients is applied, > puppetrun is executed with the devel-111 server by which puppetmasterd > does run. > [...] > The log from which the manifest is repeatedly applied in devel-111 > until "Finished catalog run" is written, and report is transmitted is > written. > Other client is also similar. > > 1 or two or more reports of each of the clients are transmitted. > It is likely to reach 30 per server at times. > > It happens when option "--host" is used with puppetrun in plurals. > But, it doesn''t happen in case of one. > The relation seem not to be in the value of "-p", and "--tag". > > > It thinks whether there is a problem in the part of the notification > from puppetd between "16:48:06"-"16:47:31" > because there is an access from devel05 many times > when tcpdump is executed with devel-111. > > It is anxious that "Compiled catalog" happens many times by > puppetmasterd. > Besides, it acquires it when there is necessary information.I''m missing something in this large amount of data, I think. So, if you specify multiple hosts then you get duplication, right? Are the actual runs being duplicated, or just the logs, or just the reports, or what? -- Good judgment comes from experience, and experience comes from bad judgment. --Barry LePatner --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Yes, for example, the correct operation that I think about, 1. Three host is executed with puppetrun specifying it. serverA serverB serverC 2. The manifest is applied. 3. One report mail of each server is received. serverA:1 serverB:1 serverC:1 However, an actual result has the problem in the part of the report mail. 3. The report mail is received. serverA: 5 serverB: 1 serverC: 20 Every time, this figure is different. I''m sorry for being not able to explain well. // kyawai --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Hi,
We use puppet to manage our ssh accounts and I want to extract this data
into a database or other format. It there an existing way to extract
this data without writing a parser to read the files? Here is an example
of what we have.
Thanks,
Pete
class users::vsdba {
@group { "sdba":
ensure => present,
gid => 12345,
}
@user { "xxxxx":
ensure => present,
uid => 12346,
gid => 12345,
groups => ["sdba"],
password => ''xxxxxxxxxxxxxxxxxxxxxxxxx'',
comment => ''xxxxxxxxxx'',
managehome => true,
shell => "/bin/bash",
}
@user { "yyyyy":
ensure => present,
uid => 12347,
gid => 12345,
groups => ["sdba"],
password => ''xxxxxxxxxxxxxxxxxxxxxxxxx'',
comment => ''xxxxxxxxxx'',
managehome => true,
shell => "/bin/bash",
}
}
class users::sdba inherits users::vsdba {
realize(
Group["sdba"],
User["xxxxx"],
User["yyyyy"]
)
}
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
You can use stored configs. http://reductivelabs.com/trac/puppet/wiki/UsingStoredConfiguration Insteading of having virtual resources you''ll have exported resources that you than collect (vs realizing). http://reductivelabs.com/trac/puppet/wiki/ExportedResources These exported resources will be stored in the database that you can then query. On Oct 23, 2009, at 12:29 PM, FLEMING PETER-PRC368 wrote:> > Hi, > > We use puppet to manage our ssh accounts and I want to extract this > data > into a database or other format. It there an existing way to extract > this data without writing a parser to read the files? Here is an > example > of what we have. > > Thanks, > Pete > > class users::vsdba { > @group { "sdba": > ensure => present, > gid => 12345, > } > > @user { "xxxxx": > ensure => present, > uid => 12346, > gid => 12345, > groups => ["sdba"], > password => ''xxxxxxxxxxxxxxxxxxxxxxxxx'', > comment => ''xxxxxxxxxx'', > managehome => true, > shell => "/bin/bash", > } > > @user { "yyyyy": > ensure => present, > uid => 12347, > gid => 12345, > groups => ["sdba"], > password => ''xxxxxxxxxxxxxxxxxxxxxxxxx'', > comment => ''xxxxxxxxxx'', > managehome => true, > shell => "/bin/bash", > } > > } > > > class users::sdba inherits users::vsdba { > > realize( > Group["sdba"], > User["xxxxx"], > User["yyyyy"] > ) > > } > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
It returns it based on the title. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---