Hi guys,
I am running puppet-dashboard with apache web server but when i am using
following command in one of my model file:-
`puppet parser validate #{module}`
I am not getting any error if module has syntax error. But it gives error
when it is running with webrick web server not with apache.
I try include different .pp for my systems. site.pp like:
if $operatingsystem == 'debian' {
import '../my/os/linux/debian.pp'
}
elsif $operatingsystem == 'windows' {
import '../my/os/windows/windows.pp'
}
else {
import '../my/os/default/default.pp'
}
and I try CASE:
case $operatingsystem {
import 'some.pp'
среда, 13 февраля 2013 г., 13:03:15 UTC+4 пользователь yarlagadda ramya
написал:
>
> Hi all,
>
> I have 3 different manifests. How can i call one manifest from another
> manifest?
>
> Please do help me with this.
>
--
You received this message because you are subscribed to the
Hello Emily,
I am reasonably sure you put your yaml files in /etc/facter/facts.d
On 14 February 2013 06:19, Emily Marx wrote:
> Hello,
>
> I am a new puppet user and I am trying to have my agent use facts defined
> in /etc/facts.d. I followed the instructions in the facter-dot-d readme and
>
I have a class that looks like this:
class java {
package { "java-1.6.0-sun.x86_64":
ensure => '1.6.0.39-1jpp.4.el5_9',
}
}
...but it gives me this error:
err: /Stage[main]/Java/Package[java-1.6.0-sun.x86_64]/ensure: change from
1.6.0.33-1jpp.1.el5_8 to 1.6.0.39-1jpp.4.el5_9 failed: Could n
Hello,
I am a new puppet user and I am trying to have my agent use facts defined
in /etc/facts.d. I followed the instructions in the facter-dot-d readme and
did the following:
1. Included stdlib in the node
2. agent -t --pluginsync (confirmed that facter-dot-d was run)
3. created a test.txt file
On 13 February 2013 19:41, Matthias Viehweger
wrote:
> Hi Oliver!
>
> On Tue, Feb 12, 2013 at 07:53:55PM -0800, oliver zhang wrote:
> > How do I do this in puppet:
> >
> > if process A is running, do nothing.
> >
> > else mount share and install package A
> >
> > I couldn't find any reference abou
Security vulnerabilities have been disclosed in Ruby on Rails, Rack,
the JSON rubygem, and certain cryptographic protocols used in OpenSSL,
assigned CVEs CVE-2013-0277, CVE-2013-0263, CVE-2013-0269 and
CVE-2013-0169, respectively. These vulnerabilities affect Puppet
Enterprise.
CVE-2013-0277 affe
We have rebuilt Windows packages for Puppet 2.7.20 and 3.1.0 in
response to CVE-2013-0169
(http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0169). The
packages include ruby 1.8.7-p371 compiled against openssl 1.0.0k. They
are available at http://downloads.puppetlabs.com/windows
Here's a brie
Will this help?
http://docs.puppetlabs.com/puppet/3/reference/lang_variables.html#parser-set-variables
--
Brian Lalor
bla...@bravo5.org
On Feb 13, 2013, at 6:17 PM, Chad Huneycutt wrote:
> I have been following the various blog posts about the roles and
> profiles pattern for classifying hosts
I have been following the various blog posts about the roles and
profiles pattern for classifying hosts, and I like it. It doesn't
provide a perfect fit for our infrastructure, but it is much better
than the ad-hoc classification we do now. I have a couple of
questions for those that use it, thou
[master] has been used for a while now. At least 2.6 up.
On Feb 13, 2013, at 12:52 PM, vioilly wrote:
> Hi,
>
> Does this still apply in puppet 3.0.2 in the puppet.conf file on the puppet
> master?
>
> [puppetmasterd]
>
> ssl_client_header = SSL_CLIENT_S_DN
>
> ssl_client_verify_head
There may be, but when we want to upgrade an application and minimize downtime,
a well-defined window of a checkin period is not sufficient. For example, given
10 machines, we need to upgrade 5, validate them, then upgrade the remaining 5.
The 5 being upgraded will get pulled out of the load bal
On Tuesday, February 12, 2013 8:37:56 PM UTC-6, blalor wrote:
>
> I'd like to use Puppet for the "last-mile" deployment of our applications,
> starting from a bare VM and ending up with a server that is running a
> specific version of an application. We're using a Puppet master already,
> whi
Hi,
Does this still apply in puppet 3.0.2 in the puppet.conf file on the puppet
master?
[puppetmasterd]
ssl_client_header = SSL_CLIENT_S_DN
ssl_client_verify_header = SSL_CLIENT_VERIFY
If yes, is puppetmasterd correct or should it be something else, like
[main] or [master]?
Cheer
On Wed, Feb 13, 2013 at 11:47 AM, Ellison Marks wrote:
> Just checking if anyone's made an attempt to update the puppetlabs nginx
> module, or could point me to one they like. Last version in forge was
> uploaded in june of 2011, and while the github version is more recent (two
> months ago), it'
This release of Puppet Dashboard addresses CVE-2013-0277 and
CVE-2013-0269. These are vulnerabilities that affect Ruby on Rails,
specifically around YAML serialization and JSON handling. They expose
vulnerable systems to SQL Injection, Denial of Service Attacks, and
arbitrary YAML deserialization.
Just checking if anyone's made an attempt to update the puppetlabs nginx
module, or could point me to one they like. Last version in forge was
uploaded in june of 2011, and while the github version is more recent (two
months ago), it's doesn't seem quite together, given that the comments are
di
I think there might be a bug buried here. I hit this before a demo this
morning - the problem was that the pid files at
/opt/puppet/share/puppet-dashboard/tmp/pids/delayed_job.{0,1}.pid were
present but there was no PID in them (and the background workers weren't
running). Removing the pidfiles
On Wednesday, February 13, 2013 12:00:40 PM UTC-6, Ken Barber wrote:
>
> Hi all,
>
> I've been looking at a potential problem, as documented here:
>
> http://projects.puppetlabs.com/issues/19241
>
> To do with a leak within the KahaDB persistence layer of ActiveMQ.
> Specifically, there are r
Hi all,
I've been looking at a potential problem, as documented here:
http://projects.puppetlabs.com/issues/19241
To do with a leak within the KahaDB persistence layer of ActiveMQ.
Specifically, there are reports of the db.data file growing unbounded:
https://issues.apache.org/jira/browse/AMQ-3
Hi Nick,
My biggest concern is that nodes can access other nodes resources stored in
PuppetDB, which effectively means that parameters like passwords and other
sensitive information is exposed.
I also wonder if PuppetDB has any sense of environments? What I mean, does
it separate data in envir
Yes, it is exactly the cause of the problem!
"
certificate_signer.rb
# Take care of signing a certificate in a FIPS 140-2 compliant manner.
#
# @see http://projects.puppetlabs.com/issues/17295
#
# @api private
class Puppet::SSL::CertificateSigner
def initialize
if OpenSSL::Digest.con
You should be versioning all your puppet manifests and modules. You
can then write a simple script to pull down the changes. Once you have
the files you can have the manfiests and modules folder look exactly
like the puppet master and then type something like this to test.
puppet apply /etc/puppet
Without fully understanding your modules and how they interact you can
always take a copy of the site manifest and modules with the node and
then do something like this
puppet apply /etc/puppet/manifests/site.pp --modulepath=/etc/puppet/modules
I typically do something similar when testing a modu
Yes because as part of the fix it checks on the CA, when its signing
the cert, whether it can support 256 or not. If it does not it drops
down to a lower SHA.
If you look at the pull request that is part of the ticket,
specifically the changes. If you scroll down to the
certificate_signer.rb chang
You would have to run your agent daemon wiht '--no-client' parameter. See
'man puppet.conf'.
On Wednesday, 13 February 2013 13:49:06 UTC, Andriy Yurchuk wrote:
>
> I need puppet agent daemon running because I need to access agent's REST
> API (http://docs.puppetlabs.com/guides/rest_api.html#the-
Matthew, you are right, this explain ALMOST everything
"Puppet is using the Solaris-provided OpenSSL as part of the Ruby install
in this case, which runs version 0.9.7 with patches and doesn’t support
sha256. I don’t mind the idea of compiling 1.0.x but the issue still seems
to stand that you can’
Vaidas and Matt - thats perfect information. Yum it is for me...
Thanks for your posts!
--
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...
Hi Oli,
I strongly recommend packaging everything up. It makes your life a lot
easier in the long term. Package systems like RPM with Yum give you a lot
of benefits, like package verification, easy updates, dependency resolution
across your system, easy way to uninstall packages etc.
The other
On Wed, Feb 13, 2013 at 3:07 PM, vioilly wrote:
> Hi,
>
> We are trying to determine the best way to install puppet using passenger.
> Is it best to install passenger via yum by making an RPM package or using
> ruby gems? What are the main gotchas using either?
I'd definitely recommend RPMs (or i
I think this issue is related to your issue since the version
discussed is 0.9.7.
http://projects.puppetlabs.com/issues/17295
What you will need to do is more than likely is update the openssl on
the agent. I dont think it will work too well but you can try to take
the srpm from rhel 5 or 6 and b
Yes, RED HAT 4 is very old, but we can't update it.
I agree with the idea that the problem could be ssl library.
As I wrote before, on RH4 we have openssl-0.9.7, on the others systems
it'1.0.0
Maybe puppet 3.0.1 master force the use of SHA256 for certificate digest,
but SHA256 is not supported by
Hi,
We are trying to determine the best way to install puppet using passenger.
Is it best to install passenger via yum by making an RPM package or using
ruby gems? What are the main gotchas using either?
Many thanks
Oli
--
You received this message because you are subscribed to the Google Gro
On 02/13/2013 03:32 PM, Luigi Martin Petrella wrote:
> MASTER Centos 6.3, Puppet 3.0.1 --> Agent RedHat 4, Puppet 3.0.1 = ERROR
> MASTER Ubuntu 12.10, puppet 3.0.1 --> Agent RedHat 4, Puppet 3.0.1 =
> ERROR MASTER RedHat 4, Puppet 3.0.1 --> Agent RedHat 4, Puppet 3.0.1 =
> OK
I agree with Matthe
Hi,
We are trying to use a custom fact to tell us the version of our service in
order to do hot deployment. The idea is that we poll mco for servers with
this fact matching the new version until it returns that there are some,
which is a signal we can move on to the next server.
Unfortunately
I have to do an update.
We just configured one RED HAT 4 node as puppet master, and connected
another RH4 agent node without any ssl or certificate issue.
So, brief recap:
MASTER Centos 6.3, Puppet 3.0.1 --> Agent RedHat 4, Puppet 3.0.1 = ERROR
MASTER Ubuntu 12.10, puppet 3.0.1 --> Agent RedHat 4,
Unfortunately no. It uses cached catalog only if puppet master returns
error code. If it is completely unavaliable agent just does nothing.
Logs contain something like
>>>
2013-02-13T18:02:09.416421+04:00 distbuilder-b puppet-agent[1432]: Puppet
--listen / kick is deprecated. See
http://links.pu
On Wednesday, February 13, 2013 6:15:09 AM UTC-6, Felix.Frank wrote:
>
> Hmm, so did you *ever* use --waitforcert on your agent side?
>
> If you haven't, that's your problem right there.
>
>
I never use --waitforcert. Instead, I just run the agent twice when I
first set up Puppet, signing the
I need puppet agent daemon running because I need to access agent's REST
API (http://docs.puppetlabs.com/guides/rest_api.html#the-agent-rest-api).
But I don't need the agent to run periodic checks. Is there any way to
either access REST API without daemonizing agent (I suspect this id not
possi
On Wednesday, February 13, 2013 3:03:15 AM UTC-6, yarlagadda ramya wrote:
>
> Hi all,
>
> I have 3 different manifests. How can i call one manifest from another
> manifest?
>
> Please do help me with this.
>
It depends on what is in the manifests... if you used modules and classes
and have th
That worked, thanks a lot John.
On Tuesday, February 12, 2013 4:15:52 PM UTC+2, jcbollinger wrote:
>
>
>
> On Tuesday, February 12, 2013 5:10:02 AM UTC-6, Andriy Yurchuk wrote:
>>
>> How do I reference my custom created facts (distributed via pluginsync)?
>> I tried Facter[:custom_fact].value, bu
Master:
Centos 6.3 , Puppet 3.1.0
Ubuntu, Puppet 3.1.0
Agent:
Redhat 4, Puppet 3.1.0
Yesterday something strange happened:
we tryied to connect RedHat agent with a Puppet Enterprise Master on Centos
6.3, and there wasn't any certificate problems and everything worked.
Today we are trying with the
What is the versions of the puppet are being used on the client and
the server? Assuming master is running on Linux, what distro and
release is the master running on?
I suspect the openssl might be the issue on the client.
On Wed, Feb 13, 2013 at 7:59 AM, Luigi Martin Petrella
wrote:
> Felix,
Felix, why do you think the problem is related to the "--waitforcert"
option?
I tryied to run "puppet agent -t --waitforcert 100" , and after signing the
request on master, on agent I receive this message:
Error: Could not request certificate: Unsupported digest algorithm (SHA256).
Error: Failed t
On 02/11/2013 10:51 PM, Jo Rhett wrote:
> All cert problems are either time sync or certificate name issues. So
> it's one of those two.
A bold assertion. It may hold true as far as puppet is concerned, though.
I generally advise to take the time and lern about x509 and openssl's
interface, so on
Hi David,
Is it possible to manage Task Scheduler through puppet?
Yes: http://docs.puppetlabs.com/references/latest/type.html#scheduledtask
Cheers,
Paul
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop
Hi all,
I have puppet running well, and for the Windows servers in our environment
it manages files, contents and services. Is it possible to manage Task
Scheduler through puppet?
The task is in xml format (an export from an existing task), which puppet
can ensure exists in a directory somewhere
Hi Ken,
In my case the issue was *ssl-host = * in jetty.ini
Changed to *ssl-host = 0.0.0.0*
and now it is fine, thank you!
вторник, 12 февраля 2013 г., 21:14:31 UTC+11 пользователь Heena написал:
>
> Hi,
> When i m using Postgresql database with puppetdb in puppet 3.0.2,
> following error is co
Hi Oliver!
On Tue, Feb 12, 2013 at 07:53:55PM -0800, oliver zhang wrote:
> How do I do this in puppet:
>
> if process A is running, do nothing.
>
> else mount share and install package A
>
> I couldn't find any reference about this.
I would first ensure that the process is running (assuming th
On Wed, Feb 13, 2013 at 3:53 AM, oliver zhang wrote:
> Hi Everyone,
>
> I'm new to puppet.
>
> How do I do this in puppet:
>
> if process A is running, do nothing.
>
> else mount share and install package A
>
> I couldn't find any reference about this.
>
> Thanks.
In addition to what Paul says, t
Thanks i got the solution mathew
On Wednesday, 13 February 2013 11:16:13 UTC+5:30, yarlagadda ramya wrote:
>
> *Hi all,
>
> I wrote a manifest for downloading linux.x64_11gR2_database_1of2.zip and
> copying that to another directory and unzipping there..its getting
> downloaded but copying and u
Hi all,
I have 3 different manifests. How can i call one manifest from another
manifest?
Please do help me with 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 em
On Wed, Feb 13, 2013 at 5:46 AM, yarlagadda ramya wrote:
> Hi all,
>
> I wrote a manifest for downloading linux.x64_11gR2_database_1of2.zip and
> copying that to another directory and unzipping there..its getting
> downloaded but copying and unzipping is not happening..am getting this
> error..
>
Hi Oliver,
if process A is running, do nothing.
>
> else mount share and install package A
>
This doesn't really sit well with the declarative nature of Puppet. It
would be better if your package pre-installation scripts were to cleanly
implement this imperative procedure. Something like shut d
55 matches
Mail list logo
