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
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
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
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
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
}
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
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
On Wed, Oct 1, 2014 at 8:13 AM, jcbollinger john.bollin...@stjude.org
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
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
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
On 10/01/2014 03:35 PM, Jeffrey Watts wrote:
On Wed, Oct 1, 2014 at 8:13 AM, jcbollinger john.bollin...@stjude.org
mailto:john.bollin...@stjude.org wrote:
As for a link, the C++ Frequently Questioned Answers
http://yosefk.com/c++fqa/ helped me crystallize some of my
previously less-focused
On Wed, Oct 1, 2014 at 5:42 AM, Vaidik Kapoor kapoor.vai...@gmail.com
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.
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
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
On Wed, Oct 1, 2014 at 9:48 AM, jmp242 jp10...@gmail.com 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:
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
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:
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
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
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
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:
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
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
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 =
On Wed, Oct 1, 2014 at 10:05 AM, Wil Cooley wcoo...@nakedape.cc wrote:
On Wed, Oct 1, 2014 at 9:48 AM, jmp242 jp10...@gmail.com 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
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
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 =
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
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 =
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.
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
On Wed, Oct 1, 2014 at 10:47 AM, Bret Wortman b...@thewortmans.org 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
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
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
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 k...@puppetlabs.com wrote:
Hmm... I didn't even know this existed. Ironically, given your question,
it
sounds like something I'd
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 nan@gmail.com wrote:
On Wed, Oct 1, 2014 at 5:42 AM, Vaidik Kapoor kapoor.vai...@gmail.com
36 matches
Mail list logo
