I''ve been trying to migrate from webrick to a clustered mongrel
implementation. The problem I''m seeing is that puppetmasterd seems to
be insisting on trying to bind the servers on port 8140 even if I''m
explicitly instructing it not to.
(root@sw178) conf.d > strace -o /tmp/suck puppetmasterd --
masterport=18142 --servertype=mongrel --pidfile=/var/run/puppet/
puppetmaster.18142.pid
Address already in use - bind(2)
(root@sw178) conf.d > tail -10 /tmp/suck
socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 4
setsockopt(4, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
bind(4, {sa_family=AF_INET, sin_port=htons(8140), sin_addr=inet_addr
("127.0.0.1")}, 16) = -1 EADDRINUSE (Address already in use)
close(4) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
write(2, "Address already in use - bind(2)", 32) = 32
write(2, "\n", 1) = 1
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigaction(SIGINT, {SIG_DFL}, {0x46fb10, [INT], SA_RESTORER|
SA_RESTART, 0x369f0301b0}, 8) = 0
exit_group(1) = ?
Is there something I''m missing as to why this is possible?
Thanks
Bill
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
The problem seemed to be that I had separated puppet.conf and puppetmasterd.conf. After fujin enlightened me, everything worked just as it''s supposed to. Thanks! On Dec 10, 12:43 am, Bill <hipt...@gmail.com> wrote:> I''ve been trying to migrate from webrick to a clustered mongrel > implementation. The problem I''m seeing is that puppetmasterd seems to > be insisting on trying to bind the servers on port 8140 even if I''m > explicitly instructing it not to. > > (root@sw178) conf.d > strace -o /tmp/suck puppetmasterd -- > masterport=18142 --servertype=mongrel --pidfile=/var/run/puppet/ > puppetmaster.18142.pid > Address already in use - bind(2) > > (root@sw178) conf.d > tail -10 /tmp/suck > socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 4 > setsockopt(4, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0 > bind(4, {sa_family=AF_INET, sin_port=htons(8140), sin_addr=inet_addr > ("127.0.0.1")}, 16) = -1 EADDRINUSE (Address already in use) > close(4) = 0 > rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 > write(2, "Address already in use - bind(2)", 32) = 32 > write(2, "\n", 1) = 1 > rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 > rt_sigaction(SIGINT, {SIG_DFL}, {0x46fb10, [INT], SA_RESTORER| > SA_RESTART, 0x369f0301b0}, 8) = 0 > exit_group(1) = ? > > Is there something I''m missing as to why this is possible? > > Thanks > Bill--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
FLEMING PETER-PRC368
2009-Feb-27 03:00 UTC
[Puppet Users] Re: puppetmasterd & mongrel port binding
I have the same problem but don''t have a puppet.conf just puppetmasterd.conf. Puppetmaster always tries to bind to the default port, here is the command I''m running: /usr/sbin/puppetmasterd --manifest=/etc/puppet/manifests/site.pp --servertype=mongrel --masterport=18140 --pidfile=/var/run/puppet/puppetmaster.18140.pid I get: Could not start WEBrick: Address already in use - bind(2) I followed the instructions on the wiki, do I need to install mongrel or is that part of the puppet install? Any suggestions? Thanks Pete -----Original Message----- From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On Behalf Of Bill Sent: Wednesday, December 10, 2008 2:29 AM To: Puppet Users Subject: [Puppet Users] Re: puppetmasterd & mongrel port binding The problem seemed to be that I had separated puppet.conf and puppetmasterd.conf. After fujin enlightened me, everything worked just as it''s supposed to. Thanks! On Dec 10, 12:43 am, Bill <hipt...@gmail.com> wrote:> I''ve been trying to migrate from webrick to a clustered mongrel > implementation. The problem I''m seeing is that puppetmasterd seems to > be insisting on trying to bind the servers on port 8140 even if I''m > explicitly instructing it not to. > > (root@sw178) conf.d > strace -o /tmp/suck puppetmasterd -- > masterport=18142 --servertype=mongrel --pidfile=/var/run/puppet/ > puppetmaster.18142.pid Address already in use - bind(2) > > (root@sw178) conf.d > tail -10 /tmp/suck socket(PF_INET, SOCK_STREAM, > IPPROTO_TCP) = 4 setsockopt(4, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0 > bind(4, {sa_family=AF_INET, sin_port=htons(8140), sin_addr=inet_addr > ("127.0.0.1")}, 16) = -1 EADDRINUSE (Address already in use) > close(4) = 0 > rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 write(2, "Address already > in use - bind(2)", 32) = 32 write(2, "\n", 1) = > 1 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 rt_sigaction(SIGINT, > {SIG_DFL}, {0x46fb10, [INT], SA_RESTORER| SA_RESTART, 0x369f0301b0}, > 8) = 0 > exit_group(1) = ? > > Is there something I''m missing as to why this is possible? > > Thanks > Bill--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
FLEMING PETER-PRC368
2009-Feb-27 21:12 UTC
[Puppet Users] Re: puppetmasterd & mongrel port binding
Anyone have any advice? I''m running the latest stable puppet on CentOS 5.2 x64. Thanks, Pete -----Original Message----- From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On Behalf Of FLEMING PETER-PRC368 Sent: Thursday, February 26, 2009 7:01 PM To: puppet-users@googlegroups.com Subject: [Puppet Users] Re: puppetmasterd & mongrel port binding I have the same problem but don''t have a puppet.conf just puppetmasterd.conf. Puppetmaster always tries to bind to the default port, here is the command I''m running: /usr/sbin/puppetmasterd --manifest=/etc/puppet/manifests/site.pp --servertype=mongrel --masterport=18140 --pidfile=/var/run/puppet/puppetmaster.18140.pid I get: Could not start WEBrick: Address already in use - bind(2) I followed the instructions on the wiki, do I need to install mongrel or is that part of the puppet install? Any suggestions? Thanks Pete -----Original Message----- From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On Behalf Of Bill Sent: Wednesday, December 10, 2008 2:29 AM To: Puppet Users Subject: [Puppet Users] Re: puppetmasterd & mongrel port binding The problem seemed to be that I had separated puppet.conf and puppetmasterd.conf. After fujin enlightened me, everything worked just as it''s supposed to. Thanks! On Dec 10, 12:43 am, Bill <hipt...@gmail.com> wrote:> I''ve been trying to migrate from webrick to a clustered mongrel > implementation. The problem I''m seeing is that puppetmasterd seems to > be insisting on trying to bind the servers on port 8140 even if I''m > explicitly instructing it not to. > > (root@sw178) conf.d > strace -o /tmp/suck puppetmasterd -- > masterport=18142 --servertype=mongrel --pidfile=/var/run/puppet/ > puppetmaster.18142.pid Address already in use - bind(2) > > (root@sw178) conf.d > tail -10 /tmp/suck socket(PF_INET, SOCK_STREAM, > IPPROTO_TCP) = 4 setsockopt(4, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0 > bind(4, {sa_family=AF_INET, sin_port=htons(8140), sin_addr=inet_addr > ("127.0.0.1")}, 16) = -1 EADDRINUSE (Address already in use) > close(4) = 0 > rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 write(2, "Address already > in use - bind(2)", 32) = 32 write(2, "\n", 1) > 1 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 rt_sigaction(SIGINT, > {SIG_DFL}, {0x46fb10, [INT], SA_RESTORER| SA_RESTART, 0x369f0301b0}, > 8) = 0 > exit_group(1) = ? > > Is there something I''m missing as to why this is possible? > > Thanks > Bill--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Frank Sweetser
2009-Feb-27 21:37 UTC
[Puppet Users] Re: puppetmasterd & mongrel port binding
FLEMING PETER-PRC368 wrote:> Anyone have any advice? I''m running the latest stable puppet on CentOS 5.2 x64. > > Thanks, > Pete > > -----Original Message----- > From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On Behalf Of FLEMING PETER-PRC368 > Sent: Thursday, February 26, 2009 7:01 PM > To: puppet-users@googlegroups.com > Subject: [Puppet Users] Re: puppetmasterd & mongrel port binding > > > I have the same problem but don''t have a puppet.conf just puppetmasterd.conf. Puppetmaster always tries to bind to the default port, here is the command I''m running: > > /usr/sbin/puppetmasterd --manifest=/etc/puppet/manifests/site.pp --servertype=mongrel --masterport=18140 --pidfile=/var/run/puppet/puppetmaster.18140.pid > > I get: > Could not start WEBrick: Address already in use - bind(2)That error message means that something else is already listening on that port. You can use the command (as root) lsof -i -P to see what processes are listening on what ports. -- Frank Sweetser fs at wpi.edu | For every problem, there is a solution that WPI Senior Network Engineer | is simple, elegant, and wrong. - HL Mencken GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
FLEMING PETER-PRC368
2009-Feb-27 22:09 UTC
[Puppet Users] Re: puppetmasterd & mongrel port binding
Thanks Frank,
Here is what''s running:
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
portmap 1329 rpc 3u IPv4 3026 UDP *:111
portmap 1329 rpc 4u IPv4 3027 TCP *:111 (LISTEN)
rpc.statd 1349 root 3u IPv4 3069 UDP *:680
rpc.statd 1349 root 6u IPv4 3059 UDP *:677
rpc.statd 1349 root 7u IPv4 3076 TCP *:683 (LISTEN)
sshd 1519 root 3u IPv6 3447 TCP *:22 (LISTEN)
ntpd 1532 ntp 16u IPv4 3482 UDP *:123
ntpd 1532 ntp 17u IPv6 3483 UDP *:123
ntpd 1532 ntp 18u IPv6 3484 UDP
localhost6.localdomain6:123
ntpd 1532 ntp 19u IPv6 3485 UDP
[fe80::219:7dff:fe67:1419]:123
ntpd 1532 ntp 20u IPv4 3489 UDP
localhost.localdomain:123
ntpd 1532 ntp 21u IPv4 3490 UDP
puppet01.domain123.com:123
nrpe 1542 nagios 4u IPv4 3515 TCP *:5666 (LISTEN)
sendmail 1561 root 4u IPv4 3590 TCP
localhost.localdomain:25 (LISTEN)
sshd 6002 root 3u IPv6 164165 TCP
puppet01.domain123.com:22->172.16.221.6:2062 (ESTABLISHED)
sshd 6004 dsmith 3u IPv6 164165 TCP
puppet01.domain123.com:22->172.16.221.6:2062 (ESTABLISHED)
puppetmas 6071 puppet 7u IPv4 165178 TCP *:8140 (LISTEN)
Then I ran "Kill 6071" and port 8140 was not in use anymore. Then the
command to start puppetmaster:
/usr/sbin/puppetmasterd --manifest=/etc/puppet/manifests/site.pp
--servertype=mongrel --masterport=18140
--pidfile=/var/run/puppet/puppetmaster.18140.pid
It works but listens on port 8140 not 18140? It seems it ignores the
port argument and mongrel completely. I also noticed when it says the
port is in use the message is coming from Webrick and not Mongrel. Does
Mongrel need to be installed or is it part of the Puppet install?
Thanks!
Pete
PS: below are my config files
[root@puppet01 ~]# cat /etc/sysconfig/puppet
# The puppetmaster server
PUPPET_SERVER=dev01.domain123.com
# If you wish to specify the port to connect to do so here
#PUPPET_PORT=8140
# Where to log to. Specify syslog to send log messages to the system
log.
PUPPET_LOG=/var/log/puppet/puppet.log
# You may specify other parameters to the puppet client here
#PUPPET_EXTRA_OPTS=--waitforcert=500
[root@puppet01 ~]# cat /etc/sysconfig/puppetmaster
# Location of the main manifest
PUPPETMASTER_MANIFEST=/etc/puppet/manifests/site.pp
PUPPETMASTER_PORTS=( [0]=18140 )
[root@puppet01 ~]# cat /etc/puppet/puppetmasterd.conf
[puppet]
# Where Puppet stores dynamic and growing data.
# The default value is ''/var/puppet''.
vardir = /var/lib/puppet
# The Puppet log directory.
# The default value is ''$vardir/log''.
logdir = /var/log/puppet
# Where Puppet PID files are kept.
# The default value is ''$vardir/run''.
rundir = /var/run/puppet
# Where SSL certificates are kept.
# The default value is ''$confdir/ssl''.
ssldir = $vardir/ssl
[puppetd]
# The file in which puppetd stores a list of the classes
# associated with the retrieved configuratiion. Can be loaded in
# the separate ``puppet`` executable using the ``--loadclasses``
# option.
# The default value is ''$confdir/classes.txt''.
classfile = $vardir/classes.txt
# Where puppetd caches the local configuration. An
# extension indicating the cache format is added automatically.
# The default value is ''$confdir/localconfig''.
localconfig = $vardir/localconfig
[puppetmasterd]
templatedir = /etc/puppet/templates
#reports = tagmail,daily,security
reports = tagmail,log
tagmap = /etc/puppet/tagmail.conf
reportfrom = report@puppet01.domain123.com
modulepath = /etc/puppet/modules
Installed Packages
Name : puppet
Arch : noarch
Version: 0.24.7
Release: 4.el5
-----Original Message-----
From: puppet-users@googlegroups.com
[mailto:puppet-users@googlegroups.com] On Behalf Of Frank Sweetser
Sent: Friday, February 27, 2009 1:37 PM
To: puppet-users@googlegroups.com
Subject: [Puppet Users] Re: puppetmasterd & mongrel port binding
FLEMING PETER-PRC368 wrote:> Anyone have any advice? I''m running the latest stable puppet on
CentOS
5.2 x64.>
> Thanks,
> Pete
>
> -----Original Message-----
> From: puppet-users@googlegroups.com
> [mailto:puppet-users@googlegroups.com] On Behalf Of FLEMING
> PETER-PRC368
> Sent: Thursday, February 26, 2009 7:01 PM
> To: puppet-users@googlegroups.com
> Subject: [Puppet Users] Re: puppetmasterd & mongrel port binding
>
>
> I have the same problem but don''t have a puppet.conf just
puppetmasterd.conf. Puppetmaster always tries to bind to the default
port, here is the command I''m running:>
> /usr/sbin/puppetmasterd --manifest=/etc/puppet/manifests/site.pp
> --servertype=mongrel --masterport=18140
> --pidfile=/var/run/puppet/puppetmaster.18140.pid
>
> I get:
> Could not start WEBrick: Address already in use - bind(2)
That error message means that something else is already listening on
that port. You can use the command (as root)
lsof -i -P
to see what processes are listening on what ports.
--
Frank Sweetser fs at wpi.edu | For every problem, there is a solution
that
WPI Senior Network Engineer | is simple, elegant, and wrong. - HL
Mencken
GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
FLEMING PETER-PRC368
2009-Feb-28 04:14 UTC
[Puppet Users] Re: puppetmasterd & mongrel port binding
Anyone?
-----Original Message-----
From: puppet-users@googlegroups.com
[mailto:puppet-users@googlegroups.com] On Behalf Of FLEMING PETER-PRC368
Sent: Friday, February 27, 2009 2:10 PM
To: puppet-users@googlegroups.com
Subject: [Puppet Users] Re: puppetmasterd & mongrel port binding
Thanks Frank,
Here is what''s running:
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
portmap 1329 rpc 3u IPv4 3026 UDP *:111
portmap 1329 rpc 4u IPv4 3027 TCP *:111 (LISTEN)
rpc.statd 1349 root 3u IPv4 3069 UDP *:680
rpc.statd 1349 root 6u IPv4 3059 UDP *:677
rpc.statd 1349 root 7u IPv4 3076 TCP *:683 (LISTEN)
sshd 1519 root 3u IPv6 3447 TCP *:22 (LISTEN)
ntpd 1532 ntp 16u IPv4 3482 UDP *:123
ntpd 1532 ntp 17u IPv6 3483 UDP *:123
ntpd 1532 ntp 18u IPv6 3484 UDP
localhost6.localdomain6:123
ntpd 1532 ntp 19u IPv6 3485 UDP
[fe80::219:7dff:fe67:1419]:123
ntpd 1532 ntp 20u IPv4 3489 UDP
localhost.localdomain:123
ntpd 1532 ntp 21u IPv4 3490 UDP
puppet01.domain123.com:123
nrpe 1542 nagios 4u IPv4 3515 TCP *:5666 (LISTEN)
sendmail 1561 root 4u IPv4 3590 TCP
localhost.localdomain:25 (LISTEN)
sshd 6002 root 3u IPv6 164165 TCP
puppet01.domain123.com:22->172.16.221.6:2062 (ESTABLISHED)
sshd 6004 dsmith 3u IPv6 164165 TCP
puppet01.domain123.com:22->172.16.221.6:2062 (ESTABLISHED)
puppetmas 6071 puppet 7u IPv4 165178 TCP *:8140 (LISTEN)
Then I ran "Kill 6071" and port 8140 was not in use anymore. Then the
command to start puppetmaster:
/usr/sbin/puppetmasterd --manifest=/etc/puppet/manifests/site.pp
--servertype=mongrel --masterport=18140
--pidfile=/var/run/puppet/puppetmaster.18140.pid
It works but listens on port 8140 not 18140? It seems it ignores the
port argument and mongrel completely. I also noticed when it says the
port is in use the message is coming from Webrick and not Mongrel. Does
Mongrel need to be installed or is it part of the Puppet install?
Thanks!
Pete
PS: below are my config files
[root@puppet01 ~]# cat /etc/sysconfig/puppet # The puppetmaster server
PUPPET_SERVER=dev01.domain123.com
# If you wish to specify the port to connect to do so here
#PUPPET_PORT=8140
# Where to log to. Specify syslog to send log messages to the system
log.
PUPPET_LOG=/var/log/puppet/puppet.log
# You may specify other parameters to the puppet client here
#PUPPET_EXTRA_OPTS=--waitforcert=500
[root@puppet01 ~]# cat /etc/sysconfig/puppetmaster # Location of the
main manifest PUPPETMASTER_MANIFEST=/etc/puppet/manifests/site.pp
PUPPETMASTER_PORTS=( [0]=18140 )
[root@puppet01 ~]# cat /etc/puppet/puppetmasterd.conf [puppet]
# Where Puppet stores dynamic and growing data.
# The default value is ''/var/puppet''.
vardir = /var/lib/puppet
# The Puppet log directory.
# The default value is ''$vardir/log''.
logdir = /var/log/puppet
# Where Puppet PID files are kept.
# The default value is ''$vardir/run''.
rundir = /var/run/puppet
# Where SSL certificates are kept.
# The default value is ''$confdir/ssl''.
ssldir = $vardir/ssl
[puppetd]
# The file in which puppetd stores a list of the classes
# associated with the retrieved configuratiion. Can be loaded in
# the separate ``puppet`` executable using the ``--loadclasses``
# option.
# The default value is ''$confdir/classes.txt''.
classfile = $vardir/classes.txt
# Where puppetd caches the local configuration. An
# extension indicating the cache format is added automatically.
# The default value is ''$confdir/localconfig''.
localconfig = $vardir/localconfig
[puppetmasterd]
templatedir = /etc/puppet/templates
#reports = tagmail,daily,security
reports = tagmail,log
tagmap = /etc/puppet/tagmail.conf
reportfrom = report@puppet01.domain123.com
modulepath = /etc/puppet/modules
Installed Packages
Name : puppet
Arch : noarch
Version: 0.24.7
Release: 4.el5
-----Original Message-----
From: puppet-users@googlegroups.com
[mailto:puppet-users@googlegroups.com] On Behalf Of Frank Sweetser
Sent: Friday, February 27, 2009 1:37 PM
To: puppet-users@googlegroups.com
Subject: [Puppet Users] Re: puppetmasterd & mongrel port binding
FLEMING PETER-PRC368 wrote:> Anyone have any advice? I''m running the latest stable puppet on
CentOS
5.2 x64.>
> Thanks,
> Pete
>
> -----Original Message-----
> From: puppet-users@googlegroups.com
> [mailto:puppet-users@googlegroups.com] On Behalf Of FLEMING
> PETER-PRC368
> Sent: Thursday, February 26, 2009 7:01 PM
> To: puppet-users@googlegroups.com
> Subject: [Puppet Users] Re: puppetmasterd & mongrel port binding
>
>
> I have the same problem but don''t have a puppet.conf just
puppetmasterd.conf. Puppetmaster always tries to bind to the default
port, here is the command I''m running:>
> /usr/sbin/puppetmasterd --manifest=/etc/puppet/manifests/site.pp
> --servertype=mongrel --masterport=18140
> --pidfile=/var/run/puppet/puppetmaster.18140.pid
>
> I get:
> Could not start WEBrick: Address already in use - bind(2)
That error message means that something else is already listening on
that port. You can use the command (as root)
lsof -i -P
to see what processes are listening on what ports.
--
Frank Sweetser fs at wpi.edu | For every problem, there is a solution
that
WPI Senior Network Engineer | is simple, elegant, and wrong. - HL
Mencken
GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---