[Puppet Users] Windows woes.....how to send a refresh event to an array of services, with one service depending on one other?

[Stephen Wallace]

Hi,

I'm using PE 3.1.1 on Win2k8R2.

I'm sending a refresh event to a class containing this declaration.

   service { ['Sentinel RMS License Manager', 'Micro Focus XDB Server for 
ETD 2.2', 'Micro Focus CES daemon']:
 ensure => 'running',
 enable => 'true',
   }

This results in the follow Windows error embedded in the puppet debug 
output.

*
Error: /Stage[main]/Mf_ent_test_server::Init2/Service[Sentinel RMS License 
Manager]: Cannot stop Sentinel RMS License Manager, error was: Execution of 
'C:/Windows/system32/net.exe stop Sentinel RMS License Manager' returned 
4294967295: The following services are dependent on the Sentinel RMS 
License Manager service.
Stopping the Sentinel RMS License Manager service will also stop these 
services.

   Micro Focus CES daemon

Do you want to continue this operation? (Y/N) [N]:
No valid response was provided.
**

i.e. To refresh the License Manager, I also need to refresh "Micro Focus 
CES daemon"

I suppose chaining each service in turn ensure => stopped, then chaining 
each again ensure => running would do the trick. Bit messy however.

Any ideas on this one would be appreciated. Lovin' Windoze.(probably!)

Regs

Stephen

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/4a13d87f-1563-4994-a24e-322146eac348%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Exit Puppet when a custom Hiera backend is not found

[Vaidik Kapoor]

Thanks for the suggestion. Looking for a non-existent key sounds like a
decent work around for now. Thanks a lot for the help! :)

Vaidik Kapoor
vaidikkapoor.info

On 1 October 2014 21:27, Nan Liu  wrote:

> On Wed, Oct 1, 2014 at 5:42 AM, Vaidik Kapoor 
> wrote:
>
>> Hi Guys,
>>
>> I am using masterless Puppet. And My situation is that I am using a
>> custom Hiera backend called hiera-regex. The process of using it is that
>> you have to have hiera-regex installed on your target machine.
>>
>> If sometime for some reason, hiera-regex is not installed, hiera still
>> looks up for the key in hierarchy and starts using that key which it was
>> not suppose to use in the presence of hiera-regex. Ideally, I would want
>> Puppet to exit when it does not find hiera-regex backend installed. But
>> as of now, Puppet only prints a notice() which can be easily missed and can
>> leave your node in an unwanted state.
>>
>> Is it possible to somehow configure Puppet/hiera for masterless setup to
>> not continue at all if hiera is configured to use a custom backend and that
>> backend is not installed?
>>
>> Here is my hiera.yaml file:
>>
>> ---
>> :backends:
>> - regex  # this is the custom backend (hiera-regex)
>> - yaml
>>
>> :regex:
>> :datadir: /etc/puppet/hiera
>>
>> :yaml:
>> :datadir: /etc/puppet/hiera
>>
>> :hierarchy:
>> - "%{fqdn}"
>> - base
>>
>>
>> Expecting some help on this. I have posted the same question on
>> stackoverflow as well:
>> http://stackoverflow.com/questions/26133604/exit-puppet-when-hiera-backend-is-not-found
>>
>
> Perform a data lookup for a non relevant key that only exists in the
> hiera-regex backend or fail the catalog.
>
> if !hiera('hiera::regex') { fail('hiera-regex backend does not appear to
> be loaded') }
>
> Nan
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CACqVBqCf%2BnF9wFp-5Q4rWMZ%2B5wHNjxeLbdpxr_G%2BMRTkUMTM8A%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CACWtv5%3DPAmrp9C_UAbS_JSvztitFVdn7e4q9THEA7TG2p9pEfg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Puppet facts uploading to PuppetDB

[Erik Dalén]

We do this, but could probably live without it. But we do it using the
facts indirector and setting it up to cache to puppetdb.
On 27 Sep 2014 15:28, "Ken Barber"  wrote:

> > Hmm... I didn't even know this existed. Ironically, given your question,
> it
> > sounds like something I'd want to use. But if it's going away, I guess
> I'll
> > just totally forget that I heard it...
>
> Oh to be clear Jason, the functionality is of course still staying for
> PuppetDB :-). Its just the transmission via the master that has been
> removed. There are a number of future architecture cases that might
> allow this via an alternate path, that are being debated however - but
> we don't want to rush into something like this, or make promises we
> can't keep :-). Understanding the use-cases in the real world is
> obviously important to these considerations.
>
> > Use case: We still have a bunch of legacy systems that aren't puppetized
> and
> > probably never will be (lots of "base" stuff that we do on "every" host
> that
> > would break these snowflakes). For everything else, PuppetDB is our one
> and
> > only inventory system. These legacy boxes exist only in a...
> spreadsheet. If
> > I knew there was a way to get facts from them into PuppetDB without
> risking
> > what would happen with a full puppet run, I probably would've done it by
> > now...
>
> So this sounds like you could just get away with something that
> doesn't require the Puppet runtime, that can submit facts directly to
> PuppetDB. At the moment this is completely possible with our commands
> submission API, but afaik tooling is generally done by users only in a
> bespoke way, at least I don't know anything that has been published.
>
> Truth is its actually dead easy to do this, (*hint hint* for those who
> have been looking for a personal project to work on, I'm sure we'd
> love to see such a thing - and would happily promote it here:
> https://docs.puppetlabs.com/puppetdb/2.2/community_add_ons.html). I
> have something ~10 lines that already does this for example in Ruby
> (using the Facter class from the facter gem/library), but since we're
> moving to a cfacter world, might be good to consider doing it
> different for future compatibility (not to mention a C++11 based
> facter will provide more portability opportunities).
>
> The main complication as ever, is the SSL authentication and the PKI
> handling of keys/certs etc. Obviously with Puppet you get the key/cert
> signing baked in - although one might consider yet another tool or
> bespoke methodology to make this work as an alternate to the Puppet
> client.
>
> ken.
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAE4bNT%3DKfbj-4f4BUgX2PgrM%3DKbcNt6RXxhTKfHL%3D4xpyrpSxA%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAAAzDLdjwJT2DAFpzWUGZ9LeytunwthyGEuWHiO_8ZHm-tU3hw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: PuppetDB 2.2 and pg_trgm extension

[Ellison Marks]

If you're using ubuntu, It would probably just be 

sudo apt-get install postgresql-contrib

You might need to restart postgres after that, not sure.


On Wednesday, October 1, 2014 2:10:40 PM UTC-7, Taylor Leese wrote:
>
> Ken - I'm using Ubuntu 14 and I installed PuppetDB via 
> https://forge.puppetlabs.com/puppetlabs/puppetdb. I also should have 
> noted that I got this error while upgrading from PuppetDB 2.1 to 2.2. 
> Postgres is version 9.3.5 if I remember correctly. Admittedly, I'm not very 
> familiar with Postgres.
>
> Ellison - How would I go about installing this "contrib" package to see if 
> that helps?
>
> - Taylor
>
> On Wednesday, October 1, 2014 10:39:07 AM UTC-7, Ellison Marks wrote:
>>
>> As a note, I installed from the postgres yum repositories, as the version 
>> in stock centos 6 was getting too old. I had to install the -contrib 
>> package to get that extension.
>>
>> On Wednesday, October 1, 2014 7:11:17 AM UTC-7, Ken Barber wrote:
>>>
>>> > I tried the same thing and got the error below. Any ideas? 
>>> > 
>>> > puppetdb=# create extension pg_trgm; 
>>> > 
>>> > ERROR:  could not open extension control file 
>>> > "/usr/share/postgresql/9.3/extension/pg_trgm.control": No such file or 
>>> > directory 
>>>
>>> Seems odd, pg_trgm should be shipped with PostgreSQL. Maybe its a bug 
>>> in that package or pg_trgm is shipped separately? 
>>>
>>> I can probably take a look here. What distro and distro release is 
>>> this exactly? Is this the PG shipped with the distro or is it from 
>>> PGDG upstream? 
>>>
>>> ken. 
>>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/d4c48b05-badf-4891-8193-acdf6507767d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: How do I install Websphere MQ using WS_MQ_SOL_ON_X86_64_7.5.0.2_IMG.tar files in a puppet master? or are there any available deb or rpm packages which puppet can recognize?

[Brian Morris]

This is what I use to deploy VMTools, which is packaged similarly. First I 
place the tar.gz file within the manifest's "files" dir, and here is the 
code:

if ( $::virtual == vmware ) {
  
  File["/home/someuser/vmtools_package.tgz"] -> Exec["vmtools_install"]
  
file {"/home/someuser/vmtools_package.tgz":
  source=> 
"puppet:///modules/vmtools_install/VMwareTools-9.0.5-1283433.tar.gz",
  schedule  => 'hourly',
}
  exec {"vmtools_install":
command   => '/bin/sh -c "killall vmtoolsd; cd /home/someuser && tar 
xzf vmtools_package.tgz && cd vmware-tools-distrib && ./vmware-install.pl 
-d && cd .. && rm -rf vm* && /usr/sbin/vmtoolsd &"',
schedule  => 'hourly',
}
  }

Notice that the handling and installing of the packaged file all happens in 
one line. The hourly schedule insures that a client doesn't try to start 
this process again while another one is running, as the compile during 
installation can take a while. It also cleans up the installation files 
when done.

I hope this helps,
Brian



On Wednesday, October 1, 2014 9:18:55 AM UTC-7, Chayce wrote:
>
> Hi,
>
> Actually, I am trying to install Websphere MQ on agents by using puppet 
> master. I think there are two ways. One is from available .tar files, and 
> other is using rpm/deb. I also want to use rpm, but how do I create a 
> manifest to use rpm packages. I found modules for activemq, and rabbitmq 
> but not for web sphere mq in puppet forge. or What I am missing here? Thank 
> you.
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/35da9354-2cb9-48cb-a770-34eb6ca07590%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Could not retrieve catalog from remote server: end of file reached

[Josh Cooper]

On Wed, Oct 1, 2014 at 10:47 AM, Bret Wortman  wrote:

> I guess not. I upgraded the server to match but the problem persists.
>
>
> On Wednesday, October 1, 2014 1:38:16 PM UTC-4, Bret Wortman wrote:
>>
>> We're running through Passenger and Apache. Puppetdb back-end. Puppet
>> 3.6.2-1 on F20 on the server, Puppet 3.7.1-1 C6.5 on the client. H.
>> Could the newer client be the problem?
>>
>> On Wednesday, October 1, 2014 1:31:00 PM UTC-4, Henrik Lindberg wrote:
>>>
>>> On 2014-01-10 19:21, Bret Wortman wrote:
>>> > This is happening on some of my clients. It'll happen about 1 out of
>>> 20
>>> > runs, but it's really getting to be a problem. There's nothing
>>> > indicative in /var/log/messages or any other server-side log that I
>>> can
>>> > find, and this is all the output I'm seeing on the client:
>>> >
>>> > # puppet agent - t
>>> > Info: Retrieving pluginfacts
>>> > Info: Retrieving plugin
>>> > Info: Loading facts
>>> > Error: Could not retrieve catalog from remote server: end of file
>>> reached
>>> > Warning: Not using cache on failed catalog
>>> > Error: Could not retrieve catalog; skipping run
>>> > #
>>> >
>>> > Any guidance on how to get more details out of Puppet about what's
>>> going
>>> > wrong here? It's persistent, but again, doesn't happen 100% of the
>>> time.
>>> > And it's only happening on certain agents, so I'm pretty sure it's
>>> > related to a module somewhere that's doing something wrong, but for
>>> the
>>> > life of me, I can't suss out which module is causing the problem.
>>> >
>>> >
>>> > Bret Wortman
>>> >
>>>
>>> Are you using Webrick ? If so, there are versions of Puppet 3x that have
>>> issues with concurrent operation (more than one agent at the same time)
>>> that can cause all kinds of weird behavior - typically resulting in
>>> truncated streams.
>>>
>>> Try latest 3.6, or 3.7. The best fix is to stop using Webrick in favor
>>> of Passenger. Webrick is really not for production use.
>>>
>>> - henrik
>>>
>>> --
>>>
>>> Visit my Blog "Puppet on the Edge"
>>> http://puppet-on-the-edge.blogspot.se/
>>>
>>>  --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/f159d59a-aa57-4648-8e34-cb39686469fa%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

You may be running into https://tickets.puppetlabs.com/browse/PUP-3238. Is
the passenger KeepAliveTimeout shorter than the the puppet agent's timeout?
If so, the server may close an idle connection, e.g. while the agent is
running facter.

See also
https://docs.puppetlabs.com/puppet/3.7/reference/release_notes.html#performance-improvements

Josh

-- 
Josh Cooper
Developer, Puppet Labs

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CA%2Bu97un7%3DTJYSc04tK%2B2H7CkJL%2BT9ydX8W0HYC69_5R%3DMGOBpA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: PuppetDB 2.2 and pg_trgm extension

[Taylor Leese]

Ken - Also, to be even more specific I'm using the following version of the 
puppetdb module:

mod 'puppetlabs/puppetdb',   
  :git => 'g...@github.com:puppetlabs/puppetlabs-puppetdb.git',   
  :ref => 'ba3049796f89aec8fb2857cb04d7f6b4dd71c4dc'

On Wednesday, October 1, 2014 2:10:40 PM UTC-7, Taylor Leese wrote:
>
> Ken - I'm using Ubuntu 14 and I installed PuppetDB via 
> https://forge.puppetlabs.com/puppetlabs/puppetdb. I also should have 
> noted that I got this error while upgrading from PuppetDB 2.1 to 2.2. 
> Postgres is version 9.3.5 if I remember correctly. Admittedly, I'm not very 
> familiar with Postgres.
>
> Ellison - How would I go about installing this "contrib" package to see if 
> that helps?
>
> - Taylor
>
> On Wednesday, October 1, 2014 10:39:07 AM UTC-7, Ellison Marks wrote:
>>
>> As a note, I installed from the postgres yum repositories, as the version 
>> in stock centos 6 was getting too old. I had to install the -contrib 
>> package to get that extension.
>>
>> On Wednesday, October 1, 2014 7:11:17 AM UTC-7, Ken Barber wrote:
>>>
>>> > I tried the same thing and got the error below. Any ideas? 
>>> > 
>>> > puppetdb=# create extension pg_trgm; 
>>> > 
>>> > ERROR:  could not open extension control file 
>>> > "/usr/share/postgresql/9.3/extension/pg_trgm.control": No such file or 
>>> > directory 
>>>
>>> Seems odd, pg_trgm should be shipped with PostgreSQL. Maybe its a bug 
>>> in that package or pg_trgm is shipped separately? 
>>>
>>> I can probably take a look here. What distro and distro release is 
>>> this exactly? Is this the PG shipped with the distro or is it from 
>>> PGDG upstream? 
>>>
>>> ken. 
>>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/0379f579-de92-410f-83f6-33aa0e8fc37b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: PuppetDB 2.2 and pg_trgm extension

[Taylor Leese]

Ken - I'm using Ubuntu 14 and I installed PuppetDB 
via https://forge.puppetlabs.com/puppetlabs/puppetdb. I also should have 
noted that I got this error while upgrading from PuppetDB 2.1 to 2.2. 
Postgres is version 9.3.5 if I remember correctly. Admittedly, I'm not very 
familiar with Postgres.

Ellison - How would I go about installing this "contrib" package to see if 
that helps?

- Taylor

On Wednesday, October 1, 2014 10:39:07 AM UTC-7, Ellison Marks wrote:
>
> As a note, I installed from the postgres yum repositories, as the version 
> in stock centos 6 was getting too old. I had to install the -contrib 
> package to get that extension.
>
> On Wednesday, October 1, 2014 7:11:17 AM UTC-7, Ken Barber wrote:
>>
>> > I tried the same thing and got the error below. Any ideas? 
>> > 
>> > puppetdb=# create extension pg_trgm; 
>> > 
>> > ERROR:  could not open extension control file 
>> > "/usr/share/postgresql/9.3/extension/pg_trgm.control": No such file or 
>> > directory 
>>
>> Seems odd, pg_trgm should be shipped with PostgreSQL. Maybe its a bug 
>> in that package or pg_trgm is shipped separately? 
>>
>> I can probably take a look here. What distro and distro release is 
>> this exactly? Is this the PG shipped with the distro or is it from 
>> PGDG upstream? 
>>
>> ken. 
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/7cfee753-494f-4df6-9696-95c15dc6b4bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Migrate from config file environments to directory environments

[Barry Gestwicki]

Hi jmp252!

I recently made the very same transition and banged my head against a wall 
for a while, but finally got it working, and perhaps this isn't the only 
solution or appropriate approach, but it's what's worked for me.  At a bare 
minimum, you should have "environmentpath = $confdir/environments" in 
puppet.conf (which it sounds like you already have), and the directory 
structure $confdir/environments/production/{manifests,modules}, as 
"production" is the default environment used for all hosts in 
Puppet/Foreman.  Of course, you can add environments in Foreman, and then 
you would just need a 
$confdir/environments/**/{manifests,modules} 
directory structure for each additional one.  

Furthermore, I have an *environment.conf* file in each environment's 
directory (i.e /etc/puppet/environments/production/) that specifies a path 
for the manifests and modules, akin to the following, going along with the 
*production 
*example :

manifest = $confdir/environments/production/manifests
modulepath = $confdir/environments/production/modules

Of course, you will need a site.pp in each environment's "manifests" 
directory and at least one class in the "modules" directory that's being 
declared for a Puppet run to actually do anything.  Hopefully this helps, 
but feel free to let me know if you need any additional info or assistance!

## Example Structure ##
/etc/puppet/environments/production
/etc/puppet/environments/production/environment.conf
/etc/puppet/environments/production/manifests
/etc/puppet/environments/production/manifests/site.pp
/etc/puppet/environments/production/modules
/etc/puppet/environments/production/modules/ntp
/etc/puppet/environments/production/modules/ntp/{blah, blah, blah}

*BG*

On Wednesday, October 1, 2014 7:35:43 AM UTC-5, jmp242 wrote:
>
> Ok, I use TheForeman, and recently updated from puppet 3.4.3 to 3.7.1. I 
> also updated TheForeman to 1.6.0. I have had config file environments. One 
> wrinkle was I had modules as $confdir/environments/dev - and all the 
> modules are under here, no sub modules dir. I tried to migrate to directory 
> environments by moving my modules to $confdir/environments/dev/modules for 
> instance, and removing the config definitions in puppet.conf and adding 
> environmentpath=$confdir/environments to puppet.conf.I restarted apache, 
> but my clients could no longer find their modules. I've poured over the 
> docs, but can't see what I did wrong. Is there a doc with step by step 
> example of converting the type of environments to be puppet4 compatible?
>
>
> Because of TheForeman, I don't have anything in site.pp... But maybe I 
> need blank site.pp in each environment? Can Puppet work without a default 
> manifest? The docs imply it should process a blank one if one doesn't 
> exist... Do I have to have an environment.conf that specifies an empty 
> site.pp? It is really not clear from the docs.
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/148ec11a-02b8-4776-bc17-7d9c41d2bb70%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Best way to deploy the Puppet client to a large set of Windows servers?

[Brian Morris]

Hello all,

There may come a need for me to perform a wide deployment of the Puppet 
client to Windows servers. I am curious to know how others have 
accomplished this.

Concerns I have:

- No other tools are in place that readily come to mind for pushing the 
client out. VCM is in play, but is difficult at best to deploy other 
applications with. The client could certainly be placed on a central file 
share, but pulling rather than pushing sounds like it will require direct 
Sysadmin involvement.

- To ease the pain I could set the Puppet Master to auto-sign certificates 
for a small window of time, but am unsure if this would be worthwhile.

- I can imagine a "patch party" where a bunch of Sysadmins each get a list 
of servers to go hand perform the installation on, but I am hoping for 
something much cleaner than this.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/0cb53cf7-6e6e-41c3-8855-8217cfaae923%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Migrate from config file environments to directory environments

[jmp242]

Ok, so some more reading, and ignoring what seemed to be wrong one liners 
in the documentation, I found out I needed to have the setup like this:

environment/modules

environment/manifests

environment/manifests/site.pp <- which I did need some settings in, namely  
Package 
{  allow_virtual => false, } (or true) and a path definition so all my 
short paths could work. I may in fact want to edit this to split path for 
windows and linux, but for now it seems to work with that structure. 3.7.1 
does not, in fact, seem to work with a non-existant site.pp inside the 
directory environments... 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/23b104f9-594f-485d-8527-1369eb585318%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: facter error message - what does this mean?

[jmp242]

Ok, thanks, it turns out restarting the puppet service fixes this error.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/11fe1507-71fc-477d-9fa0-f5bc3c2ea1c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: facter error message - what does this mean?

[Kylo Ginsberg]

On Wed, Oct 1, 2014 at 10:05 AM, Wil Cooley  wrote:

> On Wed, Oct 1, 2014 at 9:48 AM, jmp242  wrote:
>
>> I also see this on 3.7.1... Same symptoms.
>>
>
>> On Wednesday, September 24, 2014 8:16:54 AM UTC-4, JonY wrote:
>>>
>>> I'm seeing this error appear on a client machine (/var/log/syslog):
>>>
>>>  puppet-agent[17158]: Failed to apply catalog: Could not retrieve local
>>> facts: Invalid facter option(s) type
>>>
>>> If I run 'puppet agent --test' it runs fine.
>>>
>>> If I run 'puppet agent --test --debug' there is no mention of this error.
>>>
>>> Yet if I wait until the next scheduled run the error will reappear.
>>>
>>>
>>> What's going on?
>>>
>>
> You've restarted the agent I presume? In the past I've seen errors that
> would show up only in the scheduled agent runs but not when running it from
> the command line after upgrading Facter.
>

Or do any of the affected parties have two versions of facter installed? If
so the difference between standalone and daemonized agent runs might be
about ruby load path.

I ask because the "Invalid facter option(s)" message was in the 1.7 series
and is gone in 2.x. One of the reports above mentioned that they were
running 2.x, but seeing that message, which suggests multiple facter
installs.

You could get this if, say, you had done a 'gem install facter' and also a
package-based install of facter. (Among various scenarios.)

Kylo
-- 
Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CALsUZFEYZqDStPNvBtKxUjo%3D918XU6aSj3gw7LChcArZn-0BSQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] subscribe and refreshonly - expected behavior

[Mike Reed]

Hello all,

My thanks in advance to anybody with thoughts on this.  I have a module in 
which I would like two resources to be applied/refreshed based on the 
change of their parent resource.  

The code looks something like this:

exec {'assume_default_domain':
  command => "${pbis_bin_path}/config AssumeDefaultDomain true",
  subscribe   => Exec['create_home_dir'],
  refreshonly => true,
}

exec {'user_domain_prefix':
  command => "${pbis_bin_path}/config UserDomainPrefix \"\" ",
  subscribe   => Exec['assume_default_domain'],
}

When running a 'puppet agent -tvd' I get the following:

Notice: /Stage[main]/Pbis::Config/Exec[assume_default_domain]: Triggered 
'refresh' from 1 events
Info: /Stage[main]/Pbis::Config/Exec[assume_default_domain]: Scheduling 
refresh of Exec[user_domain_prefix]
Debug: /Stage[main]/Pbis::Config/Exec[assume_default_domain]: The container 
Class[Pbis::Config] will propagate my refresh event
Debug: Exec[user_domain_prefix](provider=posix): Executing 
'/opt/pbis/bin/config UserDomainPrefix "" '
Debug: Executing '/opt/pbis/bin/config UserDomainPrefix "" '
Notice: /Stage[main]/Pbis::Config/Exec[user_domain_prefix]/returns: 
executed successfully
Debug: /Stage[main]/Pbis::Config/Exec[user_domain_prefix]: The container 
Class[Pbis::Config] will propagate my refresh event
Debug: Exec[user_domain_prefix](provider=posix): Executing 
'/opt/pbis/bin/config UserDomainPrefix "" '
Debug: Executing '/opt/pbis/bin/config UserDomainPrefix "" '
Notice: /Stage[main]/Pbis::Config/Exec[user_domain_prefix]: Triggered 
'refresh' from 1 events
Debug: /Stage[main]/Pbis::Config/Exec[user_domain_prefix]: The container 
Class[Pbis::Config] will propagate my refresh event
Debug: Class[Pbis::Config]: The container Stage[main] will propagate my 
refresh event
Debug: Class[Pbis::Config]: The container Class[Pbis] will propagate my 
refresh event
Debug: Class[Pbis]: The container Stage[main] will propagate my refresh 
event
Debug: Finishing transaction 25871380
Debug: Storing state
Debug: Stored state in 0.06 seconds

As you can see, the 'user_domain_prefix' resource is firing twice and I'm 
not sure why.  If I change the resource and add a 'refreshonly', I get the 
desired result (resource only being applied once):

exec {'user_domain_prefix':
  command => "${pbis_bin_path}/config UserDomainPrefix \"\" ",
  subscribe   => Exec['assume_default_domain'],
  refreshonly => true,

Notice: /Stage[main]/Pbis::Config/Exec[assume_default_domain]: Triggered 
'refresh' from 1 events
Info: /Stage[main]/Pbis::Config/Exec[assume_default_domain]: Scheduling 
refresh of Exec[user_domain_prefix]
Debug: /Stage[main]/Pbis::Config/Exec[assume_default_domain]: The container 
Class[Pbis::Config] will propagate my refresh event
Debug: Exec[user_domain_prefix](provider=posix): Executing 
'/opt/pbis/bin/config UserDomainPrefix "" '
Debug: Executing '/opt/pbis/bin/config UserDomainPrefix "" '
Notice: /Stage[main]/Pbis::Config/Exec[user_domain_prefix]: Triggered 
'refresh' from 1 events
Debug: /Stage[main]/Pbis::Config/Exec[user_domain_prefix]: The container 
Class[Pbis::Config] will propagate my refresh event
Debug: Class[Pbis::Config]: The container Stage[main] will propagate my 
refresh event
Debug: Class[Pbis::Config]: The container Class[Pbis] will propagate my 
refresh event
Debug: Class[Pbis]: The container Stage[main] will propagate my refresh 
event
Debug: Finishing transaction 29272600
Debug: Storing state
Debug: Stored state in 0.06 seconds

My understanding is that 'subscribe' will both create a dependency and will 
require the refreshing of the dependent object, based on the subscribed 
objects' state.  I also understand 'refreshonly' to be a mechanism used 
when a dependent object is changed (sounds almost the same as subscribe 
except it doesn't create a dependency).  Based on my example above, I would 
expect 'subscribe' alone to satisfy my needs and I don't understand why I 
get duplicate refresh events when something is simply 'subscribed' but only 
one refresh event when a resource is set to both 'subscribe' and 
'refreshonly'.

Would anybody have a quick explanation for this one?

Thanks again for your help in advance.

Cheers,

Mike

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/adad7980-adc0-48eb-8ffa-d3b151f4a911%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Could not retrieve catalog from remote server: end of file reached

[Bret Wortman]

I guess not. I upgraded the server to match but the problem persists.

On Wednesday, October 1, 2014 1:38:16 PM UTC-4, Bret Wortman wrote:
>
> We're running through Passenger and Apache. Puppetdb back-end. Puppet 
> 3.6.2-1 on F20 on the server, Puppet 3.7.1-1 C6.5 on the client. H. 
> Could the newer client be the problem?
>
> On Wednesday, October 1, 2014 1:31:00 PM UTC-4, Henrik Lindberg wrote:
>>
>> On 2014-01-10 19:21, Bret Wortman wrote: 
>> > This is happening on some of my clients. It'll happen about 1 out of 20 
>> > runs, but it's really getting to be a problem. There's nothing 
>> > indicative in /var/log/messages or any other server-side log that I can 
>> > find, and this is all the output I'm seeing on the client: 
>> > 
>> > # puppet agent - t 
>> > Info: Retrieving pluginfacts 
>> > Info: Retrieving plugin 
>> > Info: Loading facts 
>> > Error: Could not retrieve catalog from remote server: end of file 
>> reached 
>> > Warning: Not using cache on failed catalog 
>> > Error: Could not retrieve catalog; skipping run 
>> > # 
>> > 
>> > Any guidance on how to get more details out of Puppet about what's 
>> going 
>> > wrong here? It's persistent, but again, doesn't happen 100% of the 
>> time. 
>> > And it's only happening on certain agents, so I'm pretty sure it's 
>> > related to a module somewhere that's doing something wrong, but for the 
>> > life of me, I can't suss out which module is causing the problem. 
>> > 
>> > 
>> > Bret Wortman 
>> > 
>>
>> Are you using Webrick ? If so, there are versions of Puppet 3x that have 
>> issues with concurrent operation (more than one agent at the same time) 
>> that can cause all kinds of weird behavior - typically resulting in 
>> truncated streams. 
>>
>> Try latest 3.6, or 3.7. The best fix is to stop using Webrick in favor 
>> of Passenger. Webrick is really not for production use. 
>>
>> - henrik 
>>
>> -- 
>>
>> Visit my Blog "Puppet on the Edge" 
>> http://puppet-on-the-edge.blogspot.se/ 
>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/f159d59a-aa57-4648-8e34-cb39686469fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: PuppetDB 2.2 and pg_trgm extension

[Ellison Marks]

As a note, I installed from the postgres yum repositories, as the version 
in stock centos 6 was getting too old. I had to install the -contrib 
package to get that extension.

On Wednesday, October 1, 2014 7:11:17 AM UTC-7, Ken Barber wrote:
>
> > I tried the same thing and got the error below. Any ideas? 
> > 
> > puppetdb=# create extension pg_trgm; 
> > 
> > ERROR:  could not open extension control file 
> > "/usr/share/postgresql/9.3/extension/pg_trgm.control": No such file or 
> > directory 
>
> Seems odd, pg_trgm should be shipped with PostgreSQL. Maybe its a bug 
> in that package or pg_trgm is shipped separately? 
>
> I can probably take a look here. What distro and distro release is 
> this exactly? Is this the PG shipped with the distro or is it from 
> PGDG upstream? 
>
> ken. 
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/1c86ca76-59e1-4b0e-85f7-503ce18a4a21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Could not retrieve catalog from remote server: end of file reached

[Bret Wortman]

We're running through Passenger and Apache. Puppetdb back-end. Puppet 
3.6.2-1 on F20 on the server, Puppet 3.7.1-1 C6.5 on the client. H. 
Could the newer client be the problem?

On Wednesday, October 1, 2014 1:31:00 PM UTC-4, Henrik Lindberg wrote:
>
> On 2014-01-10 19:21, Bret Wortman wrote: 
> > This is happening on some of my clients. It'll happen about 1 out of 20 
> > runs, but it's really getting to be a problem. There's nothing 
> > indicative in /var/log/messages or any other server-side log that I can 
> > find, and this is all the output I'm seeing on the client: 
> > 
> > # puppet agent - t 
> > Info: Retrieving pluginfacts 
> > Info: Retrieving plugin 
> > Info: Loading facts 
> > Error: Could not retrieve catalog from remote server: end of file 
> reached 
> > Warning: Not using cache on failed catalog 
> > Error: Could not retrieve catalog; skipping run 
> > # 
> > 
> > Any guidance on how to get more details out of Puppet about what's going 
> > wrong here? It's persistent, but again, doesn't happen 100% of the time. 
> > And it's only happening on certain agents, so I'm pretty sure it's 
> > related to a module somewhere that's doing something wrong, but for the 
> > life of me, I can't suss out which module is causing the problem. 
> > 
> > 
> > Bret Wortman 
> > 
>
> Are you using Webrick ? If so, there are versions of Puppet 3x that have 
> issues with concurrent operation (more than one agent at the same time) 
> that can cause all kinds of weird behavior - typically resulting in 
> truncated streams. 
>
> Try latest 3.6, or 3.7. The best fix is to stop using Webrick in favor 
> of Passenger. Webrick is really not for production use. 
>
> - henrik 
>
> -- 
>
> Visit my Blog "Puppet on the Edge" 
> http://puppet-on-the-edge.blogspot.se/ 
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/6dd97f89-ce31-4455-a81b-b1e53f0cd928%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Could not retrieve catalog from remote server: end of file reached

[Henrik Lindberg]

On 2014-01-10 19:21, Bret Wortman wrote:

This is happening on some of my clients. It'll happen about 1 out of 20
runs, but it's really getting to be a problem. There's nothing
indicative in /var/log/messages or any other server-side log that I can
find, and this is all the output I'm seeing on the client:

# puppet agent - t
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: end of file reached
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
#

Any guidance on how to get more details out of Puppet about what's going
wrong here? It's persistent, but again, doesn't happen 100% of the time.
And it's only happening on certain agents, so I'm pretty sure it's
related to a module somewhere that's doing something wrong, but for the
life of me, I can't suss out which module is causing the problem.


Bret Wortman



Are you using Webrick ? If so, there are versions of Puppet 3x that have 
issues with concurrent operation (more than one agent at the same time) 
that can cause all kinds of weird behavior - typically resulting in 
truncated streams.


Try latest 3.6, or 3.7. The best fix is to stop using Webrick in favor 
of Passenger. Webrick is really not for production use.


- henrik

--

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/m0hdnd%2448h%241%40ger.gmane.org.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: facter error message - what does this mean?

[jmp242]

And here's the trace=true output:

Oct 1 13:04:16 lnx7179 puppet-agent[18029]: Local environment: "production" 
doesn't match server specified node environment "dev", switching agent to 
"dev".
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: Could not retrieve local facts: 
Invalid facter option(s) type
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/collection.rb:60:in `add'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter.rb:128:in `add'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/os.rb:31
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:95:in `load'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:95:in `load_file'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:46:in `load_all'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:41:in `each'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:41:in `load_all'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:38:in `each'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:38:in `load_all'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/collection.rb:87:in `fact'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter.rb:150:in `method_missing'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/gce.rb:3
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:95:in `load'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:95:in `load_file'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:46:in `load_all'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:41:in `each'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:41:in `load_all'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:38:in `each'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:38:in `load_all'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/collection.rb:87:in `fact'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter.rb:150:in `method_missing'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/ec2.rb:20
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:95:in `load'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:95:in `load_file'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:46:in `load_all'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:41:in `each'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:41:in `load_all'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:38:in `each'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:38:in `load_all'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter/util/collection.rb:114:in `load_all'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/facter.rb:118:in `to_hash'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/facts/facter.rb:23:in `find'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:201:in `find'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/puppet/configurer/fact_handler.rb:15:in 
`find_facts'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/puppet/configurer/fact_handler.rb:31:in 
`facts_for_uploading'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:96:in `get_facts'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:195:in `run_internal'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:132:in `run'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/puppet/context.rb:64:in `override'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/puppet.rb:244:in `override'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:131:in `run'
Oct 1 13:04:17 lnx7179 puppet-agent[18029]: 
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:47:i

Re: [Puppet Users] Re: Puppet 3.7.1 parse problems with resource overrides.

[Henrik Lindberg]

On 2014-23-09 13:25, Stefan Heijmans wrote:

Hi,

Received the same kind of error with a different message, using Puppet
3..7.2 with future parser;
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Syntax error at '[' at
/etc/puppet/environments/tst/modules/managesoft/manifests/install.pp:41:23
on node 

Had the following in my require statement;
require => [ File ['/var/tmp/mgsft_rollout_response'], File
['/var/tmp/ux.npl'] ]
fixed by removing spaces to;
require => [File['/var/tmp/mgsft_rollout_response'],File['/var/tmp/ux.npl']]

Stefan


Posting this to clarify for those that google for problems...

This is a legit error message, you basically ended up with something 
similar to this:


require => [File , File ]

which is a syntax error since you cannot simply list entries in an array 
without commas. You fixed it the correct way by removing the spaces 
thereby making the [...] part into an access operation on the File type 
instead of being a separate expression.


- henrik

--

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/m0hddv%24vcq%241%40ger.gmane.org.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Could not retrieve catalog from remote server: end of file reached

[Bret Wortman]

This is happening on some of my clients. It'll happen about 1 out of 20 
runs, but it's really getting to be a problem. There's nothing indicative 
in /var/log/messages or any other server-side log that I can find, and this 
is all the output I'm seeing on the client:

# puppet agent - t
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: end of file reached
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
#

Any guidance on how to get more details out of Puppet about what's going 
wrong here? It's persistent, but again, doesn't happen 100% of the time. 
And it's only happening on certain agents, so I'm pretty sure it's related 
to a module somewhere that's doing something wrong, but for the life of me, 
I can't suss out which module is causing the problem.


Bret Wortman

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/fe84700f-8b4b-4676-a20a-13bd41a9a90c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: can't find node definition puppet 3.7.1

[Henrik Lindberg]

On 2014-30-09 15:35, jcbollinger wrote:



On Tuesday, September 30, 2014 3:29:23 AM UTC-5, Benjamin Priestman wrote:

I've always used import, not include to get my node definitions into
site.pp. the new way of doing it, I believe, is to use a manifest
directory. See
https://docs.puppetlabs.com/puppet/latest/reference/lang_import.html




Yes. 'include' is for declaring classes; it does not apply directly to
whole manifests.  'import'ing node definitions is about the only use of
'import' that is any more accepted as good practice.  The point of the
new(ish) "manifest directory" feature seems primarily to remove any need
for that use of 'import'.  Deprecation of 'import' will surely follow,
if it hasn't been deprecated already.



It is already deprecated, and you get an error if you try to use import 
with --parser future. In Puppet 4.0, the import is gone, but you get a 
specific error message that it has been discontinued.


- henrik
--

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/m0hd27%24pjb%241%40ger.gmane.org.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: facter error message - what does this mean?

[Wil Cooley]

On Wed, Oct 1, 2014 at 9:48 AM, jmp242  wrote:

> I also see this on 3.7.1... Same symptoms.
>

> On Wednesday, September 24, 2014 8:16:54 AM UTC-4, JonY wrote:
>>
>> I'm seeing this error appear on a client machine (/var/log/syslog):
>>
>>  puppet-agent[17158]: Failed to apply catalog: Could not retrieve local
>> facts: Invalid facter option(s) type
>>
>> If I run 'puppet agent --test' it runs fine.
>>
>> If I run 'puppet agent --test --debug' there is no mention of this error.
>>
>> Yet if I wait until the next scheduled run the error will reappear.
>>
>>
>> What's going on?
>>
>
You've restarted the agent I presume? In the past I've seen errors that
would show up only in the scheduled agent runs but not when running it from
the command line after upgrading Facter.

Wil

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAMmm3r4cBDmxn4efHsPbBrgLxKR25vLPQSPzYm_jq24usyEF-w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: facter error message - what does this mean?

[jmp242]

I also see this on 3.7.1... Same symptoms. 

On Wednesday, September 24, 2014 8:16:54 AM UTC-4, JonY wrote:
>
> I'm seeing this error appear on a client machine (/var/log/syslog):
>
>  puppet-agent[17158]: Failed to apply catalog: Could not retrieve local 
> facts: Invalid facter option(s) type
>
> If I run 'puppet agent --test' it runs fine. 
>
> If I run 'puppet agent --test --debug' there is no mention of this error.
>
> Yet if I wait until the next scheduled run the error will reappear.
>
>
> What's going on?
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/c96471b9-4d65-4caa-9787-8b4c12403093%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] How do I install Websphere MQ using WS_MQ_SOL_ON_X86_64_7.5.0.2_IMG.tar files in a puppet master? or are there any available deb or rpm packages which puppet can recognize?

[Chayce]

Hi,

Actually, I am trying to install Websphere MQ on agents by using puppet 
master. I think there are two ways. One is from available .tar files, and 
other is using rpm/deb. I also want to use rpm, but how do I create a 
manifest to use rpm packages. I found modules for activemq, and rabbitmq 
but not for web sphere mq in puppet forge. or What I am missing here? Thank 
you.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/68cfc903-93a3-455d-b14e-2f4bf3419d09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Exit Puppet when a custom Hiera backend is not found

[Nan Liu]

On Wed, Oct 1, 2014 at 5:42 AM, Vaidik Kapoor 
wrote:

> Hi Guys,
>
> I am using masterless Puppet. And My situation is that I am using a custom
> Hiera backend called hiera-regex. The process of using it is that you
> have to have hiera-regex installed on your target machine.
>
> If sometime for some reason, hiera-regex is not installed, hiera still
> looks up for the key in hierarchy and starts using that key which it was
> not suppose to use in the presence of hiera-regex. Ideally, I would want
> Puppet to exit when it does not find hiera-regex backend installed. But
> as of now, Puppet only prints a notice() which can be easily missed and can
> leave your node in an unwanted state.
>
> Is it possible to somehow configure Puppet/hiera for masterless setup to
> not continue at all if hiera is configured to use a custom backend and that
> backend is not installed?
>
> Here is my hiera.yaml file:
>
> ---
> :backends:
> - regex  # this is the custom backend (hiera-regex)
> - yaml
>
> :regex:
> :datadir: /etc/puppet/hiera
>
> :yaml:
> :datadir: /etc/puppet/hiera
>
> :hierarchy:
> - "%{fqdn}"
> - base
>
>
> Expecting some help on this. I have posted the same question on
> stackoverflow as well:
> http://stackoverflow.com/questions/26133604/exit-puppet-when-hiera-backend-is-not-found
>

Perform a data lookup for a non relevant key that only exists in the
hiera-regex backend or fail the catalog.

if !hiera('hiera::regex') { fail('hiera-regex backend does not appear to be
loaded') }

Nan

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CACqVBqCf%2BnF9wFp-5Q4rWMZ%2B5wHNjxeLbdpxr_G%2BMRTkUMTM8A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Announce: Puppet Server 0.2.0

[Felix Frank]

On 10/01/2014 03:35 PM, Jeffrey Watts wrote:
> On Wed, Oct 1, 2014 at 8:13 AM, jcbollinger  > wrote:
> As for a link, the C++ Frequently Questioned Answers
>  helped me crystallize some of my
> previously less-focused distaste for C++.
>
> There's a reason there are dozens (hundreds?) of general purpose
> programming languages - people can't agree on which is the best tool
> for a job.  Using C++ as the underlying language won't be the end of
> the world.  :)

No, it won't, and let's not go to war about it.

Still, as long as the dev team is in the process of choosing the way
forward, let the record show that there is two community voices (thanks
for that link John, that was exactly what I had skimmed back in the day)
that recommend considering alternatives.

Cheers,
Felix

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/542C10E8.403%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Git Repo Strategy

[Clayton O'Neill]

On Tuesday, September 30, 2014 7:17:51 PM UTC-4, Tom Tucker wrote:
>
>
> I just got back from PuppetConf last week and several presenters mentioned 
> using more than one Git repo with Puppet.  Some even recommend having a 
> repo per module.  For our initial Puppet deployment this seems a bit 
> excessive.  My plan was to have three repos for each of our environments 
> (Dev, QA and Production).  The contents of these repos would contain Puppet 
> Enterprise directory of /etc/puppetlabs/puppet.
>
I'll echo what other people have said here about single repo vs multiple 
repo.  You might be fine with a single repo if you have pretty basic 
configurations, but it has definite limits.  

One thing I'd *strongly* recommend against is having different repositories 
for different environments.  Assuming you're using Git, you should at most 
have these be separate branches in the same repository.  Longer term, you 
may want to move to using tags and (maybe) release branches for QA and Prod 
environments.  Having 3 branches will give you a lot more tools for moving 
changes between branches and for comparing differences between them. 
 Personally I think this is a lot more important than all modules in one 
repo vs a repo per module. 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/496a0d42-999a-4d42-915c-3eb95b3e7f16%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: PuppetDB 2.2 and pg_trgm extension

[Ken Barber]

> I tried the same thing and got the error below. Any ideas?
>
> puppetdb=# create extension pg_trgm;
>
> ERROR:  could not open extension control file
> "/usr/share/postgresql/9.3/extension/pg_trgm.control": No such file or
> directory

Seems odd, pg_trgm should be shipped with PostgreSQL. Maybe its a bug
in that package or pg_trgm is shipped separately?

I can probably take a look here. What distro and distro release is
this exactly? Is this the PG shipped with the distro or is it from
PGDG upstream?

ken.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAE4bNTm4-2Yb5aOFcgxLha2AyRJD2HkJrL%3DqDA_Arj1TJsfBvQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Dependency cycle using tidy with puppet 3

[jcbollinger]

On Tuesday, September 30, 2014 10:55:32 AM UTC-5, Chris Lee wrote:
>
> Hi all,
>
> We are busy migrating out puppet 2.7 code to puppet 3 and have run into a 
> problem where we are getting dependency cycles when using tidy.
> This mostly happens with stages (and yes, I completely understand why we 
> should avoid them).
>
> As an example we have a defined class that we use to create our cron jobs, 
> and then a tidy to clean up anything that isn't defined.
>
> class crond::cleanup {
> tidy {
> "/etc/cron.d":
> age => 0, recurse => true,
> matches => "*.puppet.cron"
> }
> }
>
> define crond::job($jobs,$comment,$mail="root") {
> include crond::cleanup
> file {
> "/etc/cron.d/${name}.puppet.cron":
> owner=>root,group=>root,
> content=>template("crond/job.erb")
> } 
> }
>
>
> and we get a dependency as follows:
>
> (File[/etc/cron.d/puppetcheck.puppet.cron] => Tidy[/etc/cron.d] => 
> Class[Crond::Cleanup] => Stage[main] => Stage[apps] => Stage[apps] => 
> Stage[post] => Class[Puppet::Service] => Crond::Job[puppetcheck] => 
> File[/etc/cron.d/puppetcheck.puppet.cron])
>
> Does anyone know of a workaround?
>
>

Yes.  Stop using run stages.

That's somewhat tongue-in-cheek, but it is certainly the case that your use 
of run stages is a significant factor in this problem, and that use of run 
stages is prone to this kind of problem in general.  That doesn't 
necessarily mean you shouldn't use run stages at all, but I usually 
discourage it.  There is nothing you can express via stages that you cannot 
also express (albeit more verbosely) via ordinary resource relationships, 
and although stages are not inherently bad, but they are trickier to use 
and more dangerous than their documentation might lead you to believe.

If you feel compelled to use stages, then I recommend that you at least 
tread lightly: as much as possible should go in Stage[main], and there 
should be no more than three stages altogether (up to one preceding main 
and up to one following it).

As for the specifics of your case, not all of the relationships in that 
cycle are coming from the code you presented, and the reasons for some of 
them are unclear to me.  In addition to the run stage assignments, it is 
unclear

   - whether Class[Puppet::Service] actually needs the specified 
   relationship with Crond::Job[puppetcheck];
   - where the relationship File[/etc/cron.d/puppetcheck.puppet.cron] -> 
   Tidy[/etc/cron.d] is coming from; it could in principle be an autorequire, 
   but no such autorequire is documented in the type reference, and neither 
   the code for the File type nor the code for the Tidy type appears to have 
   such an autorequire
   - why Crond::Job[puppetcheck] needs to be applied in Stage[post], or 
   after Class[Puppet::Service] specifically

If any of those is wrong or unneeded, then getting rid of it will probably 
help.

I cannot explain why this issue did not appear under Puppet 2.7.  Is it 
possible that a change applied as part of your migration process is 
contributing?


John

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/9db57030-8527-447a-a0a7-434d425c27ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Announce: Puppet Server 0.2.0

[Jeffrey Watts]

On Wed, Oct 1, 2014 at 8:13 AM, jcbollinger 
wrote:

>
> I'm fine with C (which I use a lot), and I love Java, JVM and all.  I'm
> satisfied with a wide variety of scripting languages.  Although it's not
> chic, I even like Fortran for certain uses.  But I hate C++.
>
> As for a link, the C++ Frequently Questioned Answers
>  helped me crystallize some of my previously
> less-focused distaste for C++.
>

Whenever I hear programmers argue about the merits and failings of
different programming languages I remember this old joke:

"At the beginning of the week, we sealed ten BSD programmers into a
computer room with a single distribution of BSD Unix.  Upon opening the
room after seven days, we found all ten programmers dead, clutching each
others' throats, and thirteen new flavors of BSD."

There's a reason there are dozens (hundreds?) of general purpose
programming languages - people can't agree on which is the best tool for a
job.  Using C++ as the underlying language won't be the end of the world.
 :)

Jeffrey.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAMvPdm2bJdSH8ZamhcdXncoYK5tgMRyHD-3pJVTLhC%2BYwcbjow%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Exit Puppet when a custom Hiera backend is not found

[Vaidik Kapoor]

Hi Guys,

I am using masterless Puppet. And My situation is that I am using a custom
Hiera backend called hiera-regex. The process of using it is that you have
to have hiera-regex installed on your target machine.

If sometime for some reason, hiera-regex is not installed, hiera still
looks up for the key in hierarchy and starts using that key which it was
not suppose to use in the presence of hiera-regex. Ideally, I would want
Puppet to exit when it does not find hiera-regex backend installed. But as
of now, Puppet only prints a notice() which can be easily missed and can
leave your node in an unwanted state.

Is it possible to somehow configure Puppet/hiera for masterless setup to
not continue at all if hiera is configured to use a custom backend and that
backend is not installed?

Here is my hiera.yaml file:

---
:backends:
- regex  # this is the custom backend (hiera-regex)
- yaml

:regex:
:datadir: /etc/puppet/hiera

:yaml:
:datadir: /etc/puppet/hiera

:hierarchy:
- "%{fqdn}"
- base


Expecting some help on this. I have posted the same question on
stackoverflow as well:
http://stackoverflow.com/questions/26133604/exit-puppet-when-hiera-backend-is-not-found

Thanks,
Vaidik Kapoor
vaidikkapoor.info

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CACWtv5%3DmGJUBXpstgU6%3D2n5ZaZnZ0U_TpcsqRx8eBC%2BNoSf9CA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Announce: Puppet Server 0.2.0

[jcbollinger]

On Tuesday, September 30, 2014 8:29:42 AM UTC-5, Felix.Frank wrote:
>
>  On 09/29/2014 05:19 AM, Kylo Ginsberg wrote:
>  
>  I'm good with JVM, but C++ feels like a backward step in many regards. 
>> My judgment here may be clouded by reading too many blogpost of them 
>> naysayers.
>>  
>
>  C++ should be a forward step from a performance/footprint perspective. 
> I'm guessing your backward step is from an ease of devel/debug perspective 
> for core? But say more so the concern is clear.
>
>  Keep in mind that this would just be C++ for the client *core*. Puppet 
> very much needs to continue to support its existing Ruby API for extensions 
> (e.g. type and providers, custom facts). And yes this implies that the API 
> needs to be *defined* better than it is today (which is undoubtedly going 
> to take some collective rolling up of sleeves).
>
>
> Hi,
>
> well I did read some arguments for C++ being quite flawed from a language 
> design perspective. I found those very compelling, but sadly cannot find 
> the link.
>


I'm fine with C (which I use a lot), and I love Java, JVM and all.  I'm 
satisfied with a wide variety of scripting languages.  Although it's not 
chic, I even like Fortran for certain uses.  But I hate C++.

As for a link, the C++ Frequently Questioned Answers 
 helped me crystallize some of my previously 
less-focused distaste for C++.


John

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/91faa7cf-b1b2-4b23-97e2-8c564f9f648c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] schedule whole class and not only resources

[Andreas Dvorak]

Dear all,

I have a class with many resource that should only run at one certain time. 
I could add a schedule to every resource, but that is the same line at all 
the resources.
Is there a solution to schedule the whole class at one place.

something like this

include abc {
 schedule 
}

Best 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/674857d1-bc31-4de7-ade7-2f51632b4316%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Migrate from config file environments to directory environments

[jmp242]

Ok, I use TheForeman, and recently updated from puppet 3.4.3 to 3.7.1. I 
also updated TheForeman to 1.6.0. I have had config file environments. One 
wrinkle was I had modules as $confdir/environments/dev - and all the 
modules are under here, no sub modules dir. I tried to migrate to directory 
environments by moving my modules to $confdir/environments/dev/modules for 
instance, and removing the config definitions in puppet.conf and adding 
environmentpath=$confdir/environments to puppet.conf.I restarted apache, 
but my clients could no longer find their modules. I've poured over the 
docs, but can't see what I did wrong. Is there a doc with step by step 
example of converting the type of environments to be puppet4 compatible?


Because of TheForeman, I don't have anything in site.pp... But maybe I need 
blank site.pp in each environment? Can Puppet work without a default 
manifest? The docs imply it should process a blank one if one doesn't 
exist... Do I have to have an environment.conf that specifies an empty 
site.pp? It is really not clear from the docs.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/68d765ab-ac8a-442a-bb38-0ae0c6933d59%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] installation and upgradation of puppet on SLES/OpenSuse

[shashank]

Hi,

My puppet master and agent version is 3.6.2 running perfectly on rhel and 
centos.
Now we have included the SUSE linux as some compute/agent nodes.
The problem I am facing is with the up-gradation/installation of 
puppet-3.6.2 and its dependencies on SUSE,I did few things which didn't 
worked.
1)From the suse repo,It will keeps the latest version of puppet i.e puppet 
3.7 which is greater than the puppet master's version 
//download.opensuse.org/repositories/systemsmanagement:/puppet/SLE_11_SP3/systemsmanagement:puppet.repo
2)Also tried to install from compling through the source code i.e 
installation through .tar file.
3)Also used yast manager
 Since the above process didn't solve the problem. 

So,the simple query is "How can I install a specific puppet version (as of 
now 3.6.2) on SLES client with all dependencies".Better to get the RPM 
repos.

Please suggest any links,forums or process.

Thanks


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/4e5516b2-e41b-4820-8d42-a28331e786ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] installation and upgradation of puppet on SLES/OpenSuse

[shashank]

Hi,

My puppet master and agent version is 3.6.2 running perfectly on rhel and 
centos.
Now we have included the SUSE linux as some compute/agent nodes.
The problem I am facing is with the up-gradation/installation of 
puppet-3.6.2 and its dependencies on SUSE,I did few things which didn't 
worked.
1)From the suse repo,It will keeps the latest version of puppet i.e puppet 
3.7 which is greater than the puppet master's version 
//download.opensuse.org/repositories/systemsmanagement:/puppet/SLE_11_SP3/systemsmanagement:puppet.repo
2)Also tried to install from compling through the source code i.e 
installation through .tar file.
3)Also used yast manager
 Since the above process didn't solve the problem. 

So,the simple query is "How can I install a specific puppet version (as of 
now 3.6.2) on SLES client with all dependencies".Better to get the RPM 
repos.

Please suggest any links,forums or process.

Thanks


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/15b0bd7c-0ca8-4e6e-ac18-d50591d83ef2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: PuppetDB 2.2 and pg_trgm extension

[Taylor Leese]

I tried the same thing and got the error below. Any ideas?

puppetdb=# create extension pg_trgm;

ERROR:  could not open extension control file 
"/usr/share/postgresql/9.3/extension/pg_trgm.control": No such file or 
directory

- Taylor

On Saturday, August 30, 2014 12:42:30 AM UTC-7, Paul Seymour wrote:
>
> Ignore me didn't add the extension to the PuppetDB database.
>
> Added it to the puppetdb DB and hey presto:-
> 2014-08-30 08:40:27,935 INFO  [c.p.p.s.migrate] Creating additional index 
> `fact_paths_path_trgm`
>
> Too early in the morning for this sh..
>
> Cheers
> Paul
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/01038d48-d73b-4394-95e3-d2b75c925e3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.