> -- > 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<puppet-users%2Bunsubscribe@google groups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en.
-- Jason Koppe Jason.Robert.Ko...@gmail.com Cell (210) 445-8242
> On Fri, Feb 12, 2010 at 12:28 AM, Joe McDonagh < > joseph.e.mcdon...@gmail.com> wrote:
>> Daniel Kerwin wrote: >> > Hi list,
>> > i just enabled storeconfigs and cannot use puppetrun on more than 5 >> > hosts. When i try 6+ i get the error message:
>> > puppetmasterd[16209]: could not obtain a database connection within 5 >> > seconds. The max pool size is currently 5; consider increasing it.
>> > My Mysql setup allows a lot more connections (500). Any suggestions?
>> Do you have the proper rubygem for mysql installed? I think on >> deb/ubuntu it's something like libmysql-ruby1.8.
> I'm having the same problem with the mysql gem installed and the gem > appears to be in-use
The gem version is a bit of a red herring, so long are using the gem and not Ruby's own connector. As the warning suggests, ActiveRecord's pool option simply needs raising if it's to be put under any strain at all. There is a bug/feature ticket as #2568 [0] which exposes this option to Puppet's configuration. But it's not due to be delivered until 2.6/rowlf.
I've been slipstreaming the patch into 0.25 myself because storeconfigs grinds to a halt without it in my environment. Given the simplicity of the diff and that it seems to be affecting a number of people I think it probably warrants being brought forward to 0.25.
Queuing support from ActiveMQ doesn't even make a difference for me -- I thought the purpose of adding the queuing support was to queue the data in puppetqd's memory and let that flush out to the database when it could. I'm still seeing this error from the puppetmaster (not puppetqd).
err: could not obtain a database connection within 5 seconds. The max pool size is currently 5; consider increasing it.
Am I misunderstanding how puppetmasterd+puppetqd is supposed to function?
On Wed, Jun 9, 2010 at 3:51 AM, Dan Carley <dan.car...@gmail.com> wrote: > On 9 June 2010 06:09, Jason Koppe <jason.robert.ko...@gmail.com> wrote:
>> On Fri, Feb 12, 2010 at 12:28 AM, Joe McDonagh < >> joseph.e.mcdon...@gmail.com> wrote:
>>> Daniel Kerwin wrote:
>>> > Hi list,
>>> > i just enabled storeconfigs and cannot use puppetrun on more than 5 >>> > hosts. When i try 6+ i get the error message:
>>> > puppetmasterd[16209]: could not obtain a database connection within 5 >>> > seconds. The max pool size is currently 5; consider increasing it.
>>> > My Mysql setup allows a lot more connections (500). Any suggestions?
>>> Do you have the proper rubygem for mysql installed? I think on >>> deb/ubuntu it's something like libmysql-ruby1.8.
>> I'm having the same problem with the mysql gem installed and the gem >> appears to be in-use
> The gem version is a bit of a red herring, so long are using the gem and > not Ruby's own connector. As the warning suggests, ActiveRecord's pool > option simply needs raising if it's to be put under any strain at all. There > is a bug/feature ticket as #2568 [0] which exposes this option to Puppet's > configuration. But it's not due to be delivered until 2.6/rowlf.
> I've been slipstreaming the patch into 0.25 myself because storeconfigs > grinds to a halt without it in my environment. Given the simplicity of the > diff and that it seems to be affecting a number of people I think it > probably warrants being brought forward to 0.25.
> -- > 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<puppet-users%2Bunsubscribe@google groups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en.
-- Jason Koppe Jason.Robert.Ko...@gmail.com Cell (210) 445-8242
> Queuing support from ActiveMQ doesn't even make a difference for me -- I > thought the purpose of adding the queuing support was to queue the data in > puppetqd's memory and let that flush out to the database when it could. I'm > still seeing this error from the puppetmaster (not puppetqd).
> err: could not obtain a database connection within 5 seconds. The max pool > size is currently 5; consider increasing it.
> Am I misunderstanding how puppetmasterd+puppetqd is supposed to function?
> On Wed, Jun 9, 2010 at 3:51 AM, Dan Carley <dan.car...@gmail.com> wrote:
>> On 9 June 2010 06:09, Jason Koppe <jason.robert.ko...@gmail.com> wrote:
>>> On Fri, Feb 12, 2010 at 12:28 AM, Joe McDonagh < >>> joseph.e.mcdon...@gmail.com> wrote:
>>>> Daniel Kerwin wrote:
>>>> > Hi list,
>>>> > i just enabled storeconfigs and cannot use puppetrun on more than 5 >>>> > hosts. When i try 6+ i get the error message:
>>>> > puppetmasterd[16209]: could not obtain a database connection within 5 >>>> > seconds. The max pool size is currently 5; consider increasing it.
>>>> > My Mysql setup allows a lot more connections (500). Any suggestions?
>>>> Do you have the proper rubygem for mysql installed? I think on >>>> deb/ubuntu it's something like libmysql-ruby1.8.
>>> I'm having the same problem with the mysql gem installed and the gem >>> appears to be in-use
>> The gem version is a bit of a red herring, so long are using the gem and >> not Ruby's own connector. As the warning suggests, ActiveRecord's pool >> option simply needs raising if it's to be put under any strain at all. There >> is a bug/feature ticket as #2568 [0] which exposes this option to Puppet's >> configuration. But it's not due to be delivered until 2.6/rowlf.
>> I've been slipstreaming the patch into 0.25 myself because storeconfigs >> grinds to a halt without it in my environment. Given the simplicity of the >> diff and that it seems to be affecting a number of people I think it >> probably warrants being brought forward to 0.25.
>> -- >> 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<puppet-users%2Bunsubscribe@google groups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en.
> -- > 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<puppet-users%2Bunsubscribe@google groups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en.
I'm not sure, I can't seem to find README.queuing or much documentation about how it's supposed to work. I'll checkout the code this weekend if there aren't responses here.
On Thu, Jun 10, 2010 at 9:32 AM, Christopher Johnston <chjoh...@gmail.com>wrote:
> I have the same issue as well, seems puppetqd uses sqlite for caching....?
> On Wed, Jun 9, 2010 at 4:11 PM, Jason Koppe <jason.robert.ko...@gmail.com>wrote:
>> Queuing support from ActiveMQ doesn't even make a difference for me -- I >> thought the purpose of adding the queuing support was to queue the data in >> puppetqd's memory and let that flush out to the database when it could. I'm >> still seeing this error from the puppetmaster (not puppetqd).
>> err: could not obtain a database connection within 5 seconds. The max >> pool size is currently 5; consider increasing it.
>> Am I misunderstanding how puppetmasterd+puppetqd is supposed to function?
>> On Wed, Jun 9, 2010 at 3:51 AM, Dan Carley <dan.car...@gmail.com> wrote:
>>> On 9 June 2010 06:09, Jason Koppe <jason.robert.ko...@gmail.com> wrote:
>>>> On Fri, Feb 12, 2010 at 12:28 AM, Joe McDonagh < >>>> joseph.e.mcdon...@gmail.com> wrote:
>>>>> Daniel Kerwin wrote:
>>>>> > Hi list,
>>>>> > i just enabled storeconfigs and cannot use puppetrun on more than 5 >>>>> > hosts. When i try 6+ i get the error message:
>>>>> > puppetmasterd[16209]: could not obtain a database connection within 5 >>>>> > seconds. The max pool size is currently 5; consider increasing it.
>>>>> > My Mysql setup allows a lot more connections (500). Any suggestions?
>>>>> Do you have the proper rubygem for mysql installed? I think on >>>>> deb/ubuntu it's something like libmysql-ruby1.8.
>>>> I'm having the same problem with the mysql gem installed and the gem >>>> appears to be in-use
>>> The gem version is a bit of a red herring, so long are using the gem and >>> not Ruby's own connector. As the warning suggests, ActiveRecord's pool >>> option simply needs raising if it's to be put under any strain at all. There >>> is a bug/feature ticket as #2568 [0] which exposes this option to Puppet's >>> configuration. But it's not due to be delivered until 2.6/rowlf.
>>> I've been slipstreaming the patch into 0.25 myself because storeconfigs >>> grinds to a halt without it in my environment. Given the simplicity of the >>> diff and that it seems to be affecting a number of people I think it >>> probably warrants being brought forward to 0.25.
>>> -- >>> 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<puppet-users%2Bunsubscribe@google groups.com> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/puppet-users?hl=en.
>> -- >> 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<puppet-users%2Bunsubscribe@google groups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en.
> -- > 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<puppet-users%2Bunsubscribe@google groups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en.
-- Jason Koppe Jason.Robert.Ko...@gmail.com Cell (210) 445-8242
Any findings? From what I can tell it defaults to sqlite leaving me with an issue of my hosts bombing out when more then 6 runs are happening. I would prefer to have it use mysql for a cache then let the queuing daemon fwd its data to a central mysql server.
On Thu, Jun 10, 2010 at 1:39 PM, Jason Koppe <jason.robert.ko...@gmail.com>wrote:
> I'm not sure, I can't seem to find README.queuing or much documentation > about how it's supposed to work. I'll checkout the code this weekend if > there aren't responses here.
> On Thu, Jun 10, 2010 at 9:32 AM, Christopher Johnston <chjoh...@gmail.com>wrote:
>> I have the same issue as well, seems puppetqd uses sqlite for caching....?
>> On Wed, Jun 9, 2010 at 4:11 PM, Jason Koppe <jason.robert.ko...@gmail.com >> > wrote:
>>> Queuing support from ActiveMQ doesn't even make a difference for me -- I >>> thought the purpose of adding the queuing support was to queue the data in >>> puppetqd's memory and let that flush out to the database when it could. I'm >>> still seeing this error from the puppetmaster (not puppetqd).
>>> err: could not obtain a database connection within 5 seconds. The max >>> pool size is currently 5; consider increasing it.
>>> Am I misunderstanding how puppetmasterd+puppetqd is supposed to function?
>>> On Wed, Jun 9, 2010 at 3:51 AM, Dan Carley <dan.car...@gmail.com> wrote:
>>>> On 9 June 2010 06:09, Jason Koppe <jason.robert.ko...@gmail.com> wrote:
>>>>> On Fri, Feb 12, 2010 at 12:28 AM, Joe McDonagh < >>>>> joseph.e.mcdon...@gmail.com> wrote:
>>>>>> Daniel Kerwin wrote:
>>>>>> > Hi list,
>>>>>> > i just enabled storeconfigs and cannot use puppetrun on more than 5 >>>>>> > hosts. When i try 6+ i get the error message:
>>>>>> > puppetmasterd[16209]: could not obtain a database connection within >>>>>> 5 >>>>>> > seconds. The max pool size is currently 5; consider increasing it.
>>>>>> > My Mysql setup allows a lot more connections (500). Any suggestions?
>>>>>> Do you have the proper rubygem for mysql installed? I think on >>>>>> deb/ubuntu it's something like libmysql-ruby1.8.
>>>>> I'm having the same problem with the mysql gem installed and the gem >>>>> appears to be in-use
>>>> The gem version is a bit of a red herring, so long are using the gem and >>>> not Ruby's own connector. As the warning suggests, ActiveRecord's pool >>>> option simply needs raising if it's to be put under any strain at all. There >>>> is a bug/feature ticket as #2568 [0] which exposes this option to Puppet's >>>> configuration. But it's not due to be delivered until 2.6/rowlf.
>>>> I've been slipstreaming the patch into 0.25 myself because storeconfigs >>>> grinds to a halt without it in my environment. Given the simplicity of the >>>> diff and that it seems to be affecting a number of people I think it >>>> probably warrants being brought forward to 0.25.
>>>> -- >>>> 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<puppet-users%2Bunsubscribe@google groups.com> >>>> . >>>> For more options, visit this group at >>>> http://groups.google.com/group/puppet-users?hl=en.
>>> -- >>> 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<puppet-users%2Bunsubscribe@google groups.com> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/puppet-users?hl=en.
>> -- >> 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<puppet-users%2Bunsubscribe@google groups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en.
> -- > 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<puppet-users%2Bunsubscribe@google groups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en.
> Any findings? From what I can tell it defaults to sqlite leaving me with > an issue of my hosts bombing out when more then 6 runs are happening. I > would prefer to have it use mysql for a cache then let the queuing daemon > fwd its data to a central mysql server.
> On Thu, Jun 10, 2010 at 1:39 PM, Jason Koppe <jason.robert.ko...@gmail.com > > wrote:
>> I'm not sure, I can't seem to find README.queuing or much documentation >> about how it's supposed to work. I'll checkout the code this weekend if >> there aren't responses here.
>> On Thu, Jun 10, 2010 at 9:32 AM, Christopher Johnston <chjoh...@gmail.com >> > wrote:
>>> I have the same issue as well, seems puppetqd uses sqlite for >>> caching....?
>>> On Wed, Jun 9, 2010 at 4:11 PM, Jason Koppe < >>> jason.robert.ko...@gmail.com> wrote:
>>>> Queuing support from ActiveMQ doesn't even make a difference for me -- I >>>> thought the purpose of adding the queuing support was to queue the data in >>>> puppetqd's memory and let that flush out to the database when it could. I'm >>>> still seeing this error from the puppetmaster (not puppetqd).
>>>> err: could not obtain a database connection within 5 seconds. The max >>>> pool size is currently 5; consider increasing it.
>>>> Am I misunderstanding how puppetmasterd+puppetqd is supposed to >>>> function?
>>>> On Wed, Jun 9, 2010 at 3:51 AM, Dan Carley <dan.car...@gmail.com>wrote:
>>>>> On 9 June 2010 06:09, Jason Koppe <jason.robert.ko...@gmail.com>wrote:
>>>>>> On Fri, Feb 12, 2010 at 12:28 AM, Joe McDonagh < >>>>>> joseph.e.mcdon...@gmail.com> wrote:
>>>>>>> Daniel Kerwin wrote:
>>>>>>> > Hi list,
>>>>>>> > i just enabled storeconfigs and cannot use puppetrun on more than 5 >>>>>>> > hosts. When i try 6+ i get the error message:
>>>>>>> > puppetmasterd[16209]: could not obtain a database connection within >>>>>>> 5 >>>>>>> > seconds. The max pool size is currently 5; consider increasing it.
>>>>>>> > My Mysql setup allows a lot more connections (500). Any >>>>>>> suggestions?
>>>>>>> Do you have the proper rubygem for mysql installed? I think on >>>>>>> deb/ubuntu it's something like libmysql-ruby1.8.
>>>>>> I'm having the same problem with the mysql gem installed and the gem >>>>>> appears to be in-use
>>>>> The gem version is a bit of a red herring, so long are using the gem >>>>> and not Ruby's own connector. As the warning suggests, ActiveRecord's pool >>>>> option simply needs raising if it's to be put under any strain at all. There >>>>> is a bug/feature ticket as #2568 [0] which exposes this option to Puppet's >>>>> configuration. But it's not due to be delivered until 2.6/rowlf.
>>>>> I've been slipstreaming the patch into 0.25 myself because storeconfigs >>>>> grinds to a halt without it in my environment. Given the simplicity of the >>>>> diff and that it seems to be affecting a number of people I think it >>>>> probably warrants being brought forward to 0.25.
>>>>> -- >>>>> 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<puppet-users%2Bunsubscribe@google groups.com> >>>>> . >>>>> For more options, visit this group at >>>>> http://groups.google.com/group/puppet-users?hl=en.
>>>> -- >>>> 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<puppet-users%2Bunsubscribe@google groups.com> >>>> . >>>> For more options, visit this group at >>>> http://groups.google.com/group/puppet-users?hl=en.
>>> -- >>> 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<puppet-users%2Bunsubscribe@google groups.com> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/puppet-users?hl=en.
>> -- >> 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<puppet-users%2Bunsubscribe@google groups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en.
> -- > 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<puppet-users%2Bunsubscribe@google groups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en.
-- Jason Koppe Jason.Robert.Ko...@gmail.com Cell (210) 445-8242
Hey Jason, I ran into this problem myself. I switched to SQLite3, for my stored configs. No problems with it, and then I run PuppetDashboard (with a mysql backend as a secondary stored configs source just in case. Please let me know if you have any questions or if there is something I can help with. -Tom
Thomas A. McGonagle t...@dataero.com Google Voice: 617-229-5185
<jason.robert.ko...@gmail.com> wrote: > I didn't read anything over last weekend but I'm anxious to find out how to > fix this for my environment.
> What is the OS of your puppetmaster?
> I've got CentOS and there's another thread about CentOS5 leaking file > descriptors.... which seems to be related.
> On Mon, Jun 21, 2010 at 10:30 AM, Christopher Johnston <chjoh...@gmail.com> > wrote:
>> Any findings? From what I can tell it defaults to sqlite leaving me with >> an issue of my hosts bombing out when more then 6 runs are happening. I >> would prefer to have it use mysql for a cache then let the queuing daemon >> fwd its data to a central mysql server.
>> On Thu, Jun 10, 2010 at 1:39 PM, Jason Koppe >> <jason.robert.ko...@gmail.com> wrote:
>>> I'm not sure, I can't seem to find README.queuing or much documentation >>> about how it's supposed to work. I'll checkout the code this weekend if >>> there aren't responses here.
>>> On Thu, Jun 10, 2010 at 9:32 AM, Christopher Johnston >>> <chjoh...@gmail.com> wrote:
>>>> I have the same issue as well, seems puppetqd uses sqlite for >>>> caching....?
>>>> On Wed, Jun 9, 2010 at 4:11 PM, Jason Koppe >>>> <jason.robert.ko...@gmail.com> wrote:
>>>>> Queuing support from ActiveMQ doesn't even make a difference for me -- >>>>> I thought the purpose of adding the queuing support was to queue the data in >>>>> puppetqd's memory and let that flush out to the database when it could. I'm >>>>> still seeing this error from the puppetmaster (not puppetqd).
>>>>> err: could not obtain a database connection within 5 seconds. The max >>>>> pool size is currently 5; consider increasing it.
>>>>> Am I misunderstanding how puppetmasterd+puppetqd is supposed to >>>>> function?
>>>>> On Wed, Jun 9, 2010 at 3:51 AM, Dan Carley <dan.car...@gmail.com> >>>>> wrote:
>>>>>> On 9 June 2010 06:09, Jason Koppe <jason.robert.ko...@gmail.com> >>>>>> wrote:
>>>>>>> On Fri, Feb 12, 2010 at 12:28 AM, Joe >>>>>>> McDonagh <joseph.e.mcdon...@gmail.com> wrote:
>>>>>>>> Daniel Kerwin wrote: >>>>>>>> > Hi list,
>>>>>>>> > i just enabled storeconfigs and cannot use puppetrun on more than >>>>>>>> > 5 >>>>>>>> > hosts. When i try 6+ i get the error message:
>>>>>>>> > puppetmasterd[16209]: could not obtain a database connection >>>>>>>> > within 5 >>>>>>>> > seconds. The max pool size is currently 5; consider increasing >>>>>>>> > it.
>>>>>>>> > My Mysql setup allows a lot more connections (500). Any >>>>>>>> > suggestions?
>>>>>>>> Do you have the proper rubygem for mysql installed? I think on >>>>>>>> deb/ubuntu it's something like libmysql-ruby1.8.
>>>>>>> I'm having the same problem with the mysql gem installed and the gem >>>>>>> appears to be in-use
>>>>>> The gem version is a bit of a red herring, so long are using the gem >>>>>> and not Ruby's own connector. As the warning suggests, ActiveRecord's pool >>>>>> option simply needs raising if it's to be put under any strain at all. There >>>>>> is a bug/feature ticket as #2568 [0] which exposes this option to Puppet's >>>>>> configuration. But it's not due to be delivered until 2.6/rowlf. >>>>>> I've been slipstreaming the patch into 0.25 myself because >>>>>> storeconfigs grinds to a halt without it in my environment. Given the >>>>>> simplicity of the diff and that it seems to be affecting a number of people >>>>>> I think it probably warrants being brought forward to 0.25. >>>>>> [0] http://projects.puppetlabs.com/issues/2568
>>>>>> -- >>>>>> 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 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 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 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 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 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.
