On Friday, February 15, 2013 6:37:10 AM UTC-8, jcbollinger wrote:
>
>
>
> On Thursday, February 14, 2013 1:45:36 PM UTC-6, Chad Huneycutt wrote:
>>
>> Thanks, John. I think you are right that puppet should support it,
>> but I am pretty sure it does not. I chatted with RI, and it seems
>> tha
On Fri, Feb 15, 2013 at 11:30 AM, Tiago Cruz wrote:
> Hello Nan,
>
> So this is the problem: I think that puppet must fail on the fist attempt,
> but install the package to be sucess on the second try.
>
> But not, it always failing:
>
> Feb 15 16:37:49 alog228 puppet-agent[18960]: Starting Puppet
On Feb 15, 2013, at 1:45 PM, jcbollinger wrote:
> Curiouser and curiouser. The "1:" is an epoch number, as you probably
> recognize. I was a bit surprised that Puppet would require you to include
> it, but very surprised to find out that it fails even if you do. I do think
> it likely that
http://projects.puppetlabs.com/issues/1238
I was doing some random noodling this afternoon, and this bug seems to have
stopped biting me, both with apply and with a master. Strange thing is, the
ticket isn't closed and there's no mention of it in the roadmap. Can anyone
else confirm that this i
Natty reached end of life at the end of October 2012[1], so we will be
removing it from our apt repository next Friday.
[1] -
http://en.wikipedia.org/wiki/List_of_Ubuntu_releases#Ubuntu_11.04_.28Natty_Narwhal.29
--
Matthaus Owens
Release Manager, Puppet Labs
--
You received this message becau
On Friday, February 15, 2013 9:56:09 AM UTC-6, Eugene Brodsky wrote:
>
> Hi all, first post here... reposting this from Stack Overflow as it didn't
> get much traction there...
>
> I am using puppet to read a fact from facter, and based on that I apply a
> different configuration to my modules.
Have you verified that the time on the servers is consistent?
On Fri, Feb 15, 2013 at 5:01 AM, F.Calero wrote:
> Hi all,
>
> I'm trying to start with it from the scratch and i'm getting struck at
> this point:
>
> puppetclient01:~ # cat /etc/SuSE-release
> SUSE Linux Enterprise Server 11 (x86_
On Friday, February 15, 2013 10:51:06 AM UTC-6, Marc Bolós wrote:
>
> Dear John,
>
> I tryed as you suggested but I think I'm doing something wrong.
>
> I can also see this line is same:
> $service_modules = hiera_array('service_modules')
>
> It is correct?
>
> Where do I define array of module
err: Could not retrieve catalog from remote server: Error 500 on SERVER:
Passenger error #2
An error occurred while trying to access '/var/opt/lib/pe-puppetmaster/
config.ru': Cannot stat '/var/opt/lib/pe-puppetmaster/config.ru':
Permission denied (13)Apache doesn't have read permissions to that
Hello Nan,
So this is the problem: I think that puppet must fail on the fist attempt,
but install the package to be sucess on the second try.
But not, it always failing:
Feb 15 16:37:49 alog228 puppet-agent[18960]: Starting Puppet client version
2.7.9
Feb 15 16:37:57 alog228 puppet-agent[18960
Hello,
First of all I am new to the Puppet technology. I am trying to get my
puppet agent (windows) to reach my puppet master (Linux) server.
In this tutorial:
http://docs.puppetlabs.com/learning/agent_master_basic.html
It claims to test your puppet agent you need to use the 'puppet agent
--
On Fri, Feb 15, 2013 at 10:42 AM, Tiago Cruz wrote:
> Hello,
>
> What's the problem with this syntax:
>
> package { 'redhat-lsb':
> ensure => present,
> before => File['/etc/yum.repos.d/rpmforge.repo'],
> }
>
> file { '/etc/yum.repos.d/rpmforge.r
On Friday, February 15, 2013 10:39:10 AM UTC-6, Sean LeBlanc wrote:
>
> I should have added to my post that I've tried adding that "1:" as well to
> the ensure line with the same results.
>
Curiouser and curiouser. The "1:" is an epoch number, as you probably
recognize. I was a bit surprise
Hello,
What's the problem with this syntax:
package { 'redhat-lsb':
ensure => present,
before => File['/etc/yum.repos.d/rpmforge.repo'],
}
file { '/etc/yum.repos.d/rpmforge.repo':
mode => 644,
owner => root,
Is both servers clock in sync?
On Fri, Feb 15, 2013 at 4:20 AM, Calero wrote:
> Hi all,
>
>
>
> I'm trying to understand how puppet works, and my idea is to learn
> installing a new environment from the scratch.
>
>
>
> I have the following:
>
>
>
> Master:
>
>
>
> cat /etc/debian_version
>
> 6.0
Thanks Ken. It get your point and it totally makes sense.
On 15 February 2013 15:36, Ken Barber wrote:
> >> > My biggest concern is that nodes can access other nodes resources
> stored
> >> > in
> >> > PuppetDB, which effectively means that parameters like passwords and
> >> > other
> >> > sens
On 02/15/2013 05:39 PM, Sean LeBlanc wrote:
> I should have added to my post that I've tried adding that "1:" as well
> to the ensure line with the same results.
>
> Any other ideas?
Have you run that catalog with the --debug flag? It would be interesting
to see just what the provider is trying t
Ah, now I see where you're coming from.
Turns out the virtual resource is a good idea then after all.
To make this work, I believe you have to
- not declare the virtual resource in the central class
- do declare one virtual header snippet per defined type
- realize the header snippet in the same
On Fri, Feb 15, 2013 at 10:12 AM, Felix Frank
wrote:
> Hi,
>
> it's paramount that you generate a unique $name for each invocation of
> your defined type, e.g.
>
> pam::header { "limits-$name": }
>
> You can take advantage of the fact that the "calling" defines have
> unique names of their own.
R
Dear John,
I tryed as you suggested but I think I'm doing something wrong.
I can also see this line is same:
$service_modules = hiera_array('service_modules')
It is correct?
Where do I define array of modules? where you write service_modules?
Regards.
manifests/site.pp:
node somen
Hi all,
I'm trying to understand how puppet works, and my idea is to learn
installing a new environment from the scratch.
I have the following:
Master:
cat /etc/debian_version
6.0.6
puppet --version
3.1.0
cat /etc/hosts
127.0.1.1 puppetmaster.domain.namepuppetm
Felix -
"d) add a server= entry to your puppet.conf"
This needs to be a fully qualified domain name (FQDN) - correct?
Thanks in advance,
Adam
On Friday, June 10, 2011 7:44:46 AM UTC-5, Felix.Frank wrote:
>
> Hi,
>
> you need to do one of these:
> a) create a DNS entry for "puppet" pointing t
Hi all, first post here... reposting this from Stack Overflow as it didn't
get much traction there...
I am using puppet to read a fact from facter, and based on that I apply a
different configuration to my modules.
Problem:
the puppet agent isn't seeing this fact. Running puppet agent --test
i
I should have added to my post that I've tried adding that "1:" as well to
the ensure line with the same results.
Any other ideas?
I've tried this workaround:
exec { "upgrade java":
command => "yum -d 1 -e 1 upgrade
java-1.6.0-sun-1:1.6.0.39-1jpp.4.el5_9.x86_64
java-1.6.0-sun-devel-1:1.6.
On Wednesday, February 13, 2013 4:11:40 PM UTC-6, blalor wrote:
>
> 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
> upgra
Yes, I had --no-client and listen = true in puppet.conf. With these
settings the agent does not respond to MCollective calls.
On Friday, February 15, 2013 5:29:44 PM UTC+2, Felix.Frank wrote:
>
> Hi,
>
> have you made sure you pass the --listen option alongside --no-client?
>
> On 02/14/2013 11
>> > 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.
>>
>> If the data is not exported this shouldn't be the case ordinarily.
>
>
> It actuall
On Friday, February 15, 2013 12:35:59 AM UTC-6, Vlados Vlados wrote:
>
> Please help.
> I using virtual resource @user and @group.
>
> If i using next construction i get error with cycles
> class users {
> Group <| ENABLED_GROUPS |> ->User <| ENABLED_USERS' |> -> User
> <| DISABLED_USE
There is a ignoreschedules option for puppet agent
(http://docs.puppetlabs.com/references/latest/configuration.html#ignoreschedules),
but it does not seem to work. Even if it is set to true the agent is being
run every "runinterval" seconds.
On Thursday, February 14, 2013 12:21:39 PM UTC+2, An
Hi,
have you made sure you pass the --listen option alongside --no-client?
On 02/14/2013 11:21 AM, Andriy Yurchuk wrote:
> This works, but this disables the ability to push configs via
> MCollective, i.e. mco puppet runall/runonce do not work.
>
> On Wednesday, February 13, 2013 5:51:56 PM UTC+2
Dear John,
I will try as you suggested, but it's pretty clear that this will work.
Thanks a lot for your time.
El jueves, 14 de febrero de 2013 17:35:50 UTC+1, Marc Bolós escribió:
>
> Dear,
>
> I've been using puppet for some time now. Usually when I have a problem I
> read all documentation r
Thanks a lot John, the explanation was really helpful.
On Thursday, February 14, 2013 4:32:38 PM UTC+2, jcbollinger wrote:
>
>
>
> On Thursday, February 14, 2013 5:10:43 AM UTC-6, Andriy Yurchuk wrote:
>>
>> Found out that it's very simple: subscribe => Class['module::class_2']
>>
>> On Thursday,
Hi,
it's paramount that you generate a unique $name for each invocation of
your defined type, e.g.
pam::header { "limits-$name": }
You can take advantage of the fact that the "calling" defines have
unique names of their own.
HTH,
Felix
On 02/15/2013 03:31 PM, Darin Perusich wrote:
>> > I belie
On Friday, February 15, 2013 4:18:20 AM UTC-6, Marc Bolós wrote:
>
> Dear John,
>
> Thanks for your response.
>
> Since I have a large environment setup I was trying to automatize all
> setups from puppet, being as much simple as I can.
>
> For example, let's think that I have a puppet server an
On Thursday, February 14, 2013 1:45:36 PM UTC-6, Chad Huneycutt wrote:
>
> Thanks, John. I think you are right that puppet should support it,
> but I am pretty sure it does not. I chatted with RI, and it seems
> that the classname is not "exposed", so when the puppet backend does
> the look
> Can http://rvm.io build a "local" ruby for you on that system?
Hello David, apologies for the belated response on this .. But no, rvm is
not an option because it has a bash shell version dependency that dapper
(or any of the nearby distros, up to feisty) cannot satisfy .. so, it does
seem
Hi Felix,
On Thu, Feb 14, 2013 at 7:07 AM, Felix Frank
wrote:
> So basically you want all generated files to use the same header
> template? Hmm.
This is correct.
> I believe what you want is another defined type that represents "the
> header snippet for a specific pam config file" and declares
Found this out the hard way :)
Thought I would share.
For reasons I will not go into, I am running puppet agent by cron using the
system crontab -- /etc/crontab and /etc/cron.d/*
In those, you have to define your environment. Thru trial and error, I found
what I believe is the minimum enviro
On Thursday, February 14, 2013 5:02:22 PM UTC-6, Michael Hüttermann wrote:
>
> Hello,
>
> in case you want to manage a node with multiple masters (that may manage
> different aspects of that system): is it possible to run multiple puppet
> agent daemons on one node (listening to different maste
I will try to work with the certificate_signer.rb file and see if I can get
it to work. Thanks for the help!
Jason
On Friday, February 15, 2013 8:21:28 AM UTC-5, Luigi Martin Petrella wrote:
>
> Jason, for the reasons we wrote before in prevoius messages (especially
> what Matt Black said), P
Thanks.
I am using 3.1
Thanks
On Friday, February 15, 2013 12:12:59 AM UTC-5, Kubes wrote:
>
> Hello,
>
> I have created my users via virtual definitions and hiera. Now I want to
> realize the virutal users by "groups".
>
> I have an trying the following syntax:
> User::Virtual <| groups =
Jason, for the reasons we wrote before in prevoius messages (especially
what Matt Black said), Puppet 3.1.0 will never work with an agent that run
openssl library version 0.9.7 (which is the version running on RH4)
Even if you had master with Puppet 2.7.x working correctly with RH4 nodes,
it is pe
There should be no reason to add any repo's other then
systemsmanagement:puppet for dependencies. The deps should be created
as packages links to the which ever development repo they reside in.
Any discussion regarding this should be taken off the puppet list and
moved onto the opensuse-buildservi
Luigi,
Thanks for the suggestion, however I've already done that in some sense.
Here's my FULL situation:
I was running a puppet 2.6.6 master on a RHEL5 machine with lots of
RHEL4,5,6 machines (mostly RHEL5) connecting to it. The clients are all
running puppet 0.25.5 and working just fine.
I have been tinkering off and on with this.
Try setting up a few users with more than one entry in "groups"
The double equal sign operator might work for this.
If I get a chance to re-visit that sandbox, I will reply to this thread again.
Using Puppet 3 helps.
“Sometimes I think the surest
Morning all,
Firstly, apologies for the length of this post, however I thought it
probably most useful to fully outline the challenge and the desired
result...
Ok, so we're in the process of Puppetizing our Oracle/NetApp platform for
Live/DR running.
The current manual process, upon settin
Ken, here's my data from our (small) production environment:
root@puppet:/var/lib/puppetdb/mq/localhost/KahaDB# du -sk *
23648 db-996.log
32 db.data
36 db.redo
0 lock
root@puppet:/var/lib/puppetdb/mq/localhost/KahaDB# ps auxw | grep java
USER PID %CPU %MEMVSZ RSS TTY
Dear John,
Thanks for your response.
Since I have a large environment setup I was trying to automatize all
setups from puppet, being as much simple as I can.
For example, let's think that I have a puppet server and more than 1000
puppet nodes. So I edit nodes.pp and I declare "server1" and I a
Jason, you could try to set one Redhat 4 node as master and verify if it
works correctly with another RH4 agent, so you can establish if the problem
is about RH4 agents or RH6 master..
On 14 February 2013 19:45, binaryred wrote:
> On my puppet master, I uninstalled my puppet RPM, downloaded t
49 matches
Mail list logo
