Hi there James,
I have a new 3.7.1 Puppet Master with an old 2.6.17 Puppet agent.
My symptoms are the same as yours.
Do you think its got to do with the version difference?
Kind Regards
Malan van Eck
--
You received this message because you are subscribed to the Google Groups
"Puppet Users"
hello world.
I found the learning puppet site so I thought that would be a good place to
start.
I downloaded the vm.
I was able to import it into virtualbox.
But then it hung during bootup.
So I used vagrant to vagrant up a clean precise64 box.
I did apt-get install puppet
apt-get got me
does
> that by default.
>
>
>
> On Mon, Aug 19, 2013 at 1:22 PM, me 1 >wrote:
>
>>
>> On Sun, Aug 18, 2013 at 9:04 PM, me 1 wrote:
>>>
>>>> On Sunday, August 18, 2013 6:13:38 PM UTC-4, Jim Toth wrote:
>>>>>
>>>>> T
> On Sun, Aug 18, 2013 at 9:04 PM, me 1 >wrote:
>
>> On Sunday, August 18, 2013 6:13:38 PM UTC-4, Jim Toth wrote:
>>>
>>> There are a few ways to go; probably the best way is to set up a bare
>>> repository that you push and pull from in both places,
On Sun, Aug 18, 2013 at 9:04 PM, me 1 >wrote:
> On Sunday, August 18, 2013 6:13:38 PM UTC-4, Jim Toth wrote:
>>>
>>> There are a few ways to go; probably the best way is to set up a bare
>>> repository that you push and pull from in both places, but I&#x
> On Sun, Aug 18, 2013 at 9:04 PM, me 1 >wrote:
>
>> On Sunday, August 18, 2013 6:13:38 PM UTC-4, Jim Toth wrote:
>>>
>>> There are a few ways to go; probably the best way is to set up a bare
>>> repository that you push and pull from in both places,
On Sunday, August 18, 2013 6:13:38 PM UTC-4, Jim Toth wrote:
>
> There are a few ways to go; probably the best way is to set up a bare
> repository that you push and pull from in both places, but I'd probably add
> the development environment as a remote in the in-production directory.
>
> cd /pa
On Sunday, August 18, 2013 3:24:40 AM UTC-4, James Polley wrote:
>
> The changes are being commited in the branch called "master" in your local
> checkout, but not being pushed nack up to the origin.
>
> http://git-scm.com/book/en/Git-Basics-Working-with-Remotes explains how
> to push your change
I have created a git clone and have been using this to test changes without
affecting the modules in production. The problem is, when I commit the
change it stays in the closed branch, never pushing the change to the
master (origin) branch. How can this be done?
$ git status
# On branch maste
Does anyone know how I can troubleshoot this? surely someone's seen this
before?
On Monday, July 29, 2013 3:34:39 PM UTC-4, me 1 wrote:
>
> I have a surprising problem with environments not working, i'm using rhel
> 6.3 with puppet-3.2.3-1.el6.noarch and here is the
I have a surprising problem with environments not working, i'm using rhel
6.3 with puppet-3.2.3-1.el6.noarch and here is the puppet.conf on the
master:
[main]
logdir = /var/log/puppet
rundir = /var/run/puppet
ssldir = $vardir/ssl
server = puppet.local
reports = store, http
Of course giving someone 'sudo puppet' is the same as giving them full root
access. Just be aware of that.
On Monday, June 25, 2012, Douglas Brancaglion wrote:
> use sudo command in exec, no problem, but you need to configure sudoers
> file.
>
> 2012/6/25 Worker Bee 'beeworke...@gmail.com');>>
>
s
> the point.
> Sent from my ASUS Eee Pad
>
> Me wrote:
>
>>Is it a known issue that you can't use the $environment variable in an
>>"import" line? This is from site.pp on a system using environments,
>>and it doesn't work:
>>
>>
#x27; at /etc/puppet/manifests/site.pp:27 on node foobar
I can change it to:
import "environments/production/nodes/*.pp"
..and things work. I get the message:
notice: NOTICE: This system is being configured with the environment production.
I'm on server and client version
On Thu, Dec 23, 2010 at 6:49 PM, Russ Allbery wrote:
>
> Oh. You're not setting $dns_role to the string "master" or "slave".
> You're setting $dns_role to an *array*, whose only member is "master" or
> "slave". That array is never going to equal a string (but as it turns
> out, it will stringify
On Thu, Dec 23, 2010 at 4:10 PM, Daniel Pittman wrote:
> On Fri, Dec 24, 2010 at 10:49, Me wrote:
>
>> There's no scoping issue - just seems that Puppet is buggy. Thanks for
>> your help, I don't think there's a fix.
>
> I have a bunch of manifests and tem
so we'll
let the shell figure it out
#
if [ "master" == master ]
then
cp -f $startdir/zones/* /var/named/internal/
fi
...so it works. I just can't make Ruby do the compare for me, when I
put it in th
On Thu, Dec 23, 2010 at 4:19 PM, Stefan Schulte
wrote:
> I don't really get it. You're testing dns_role agains "master". And you
> can see that dns_role is indeed "master" when you just use some simple
> <%= dns_role %>. And the code inside your if statement is evaluated. So
> what exactly is the
On Thu, Dec 23, 2010 at 3:34 PM, Stefan Schulte
wrote:
> On Thu, Dec 23, 2010 at 10:30:22AM -0800, Me wrote:
>>
>> <% if dns_role == "master" then %>
>> #
>> # I'm a BIND <%= dns_role %>
>>
Thanks a lot for the reply, deet.
I don't want it executed on the puppet server - this is part of a
larger shell script being sent to a client, that is then run
periodically from cron. I simply want this single line of shell
included *only* when the host is a master DNS server, i.e. $dns_role
== "
I'm on 2.6.4, and I have one template that just won't work. I want to
only print a section when a variable has a particular value. Depending
on hostname, a variable called "dns_role" has the value of either
"master" or "slave".
This template snippet works for a named.conf file template (not part
o
21 matches
Mail list logo
