Hi everyone,
I am new to Puppet and try to make some simple "automation things".
I have succeed with apache2, ssh modules, but have problems with
Puppetlabs mysql module.
It installs mysql server, changes/creates admin user password, but
does not create database and user.
I cannot find anything w
Hi.
How do you handle CentOS updates/upgrades with puppet? Is there only way
to count all the packages and put them in manifests like:
package: ensure=>latest,
I am evaluating puppet, and currently I have problem with upgrading from
CentOS 5.x->5.x+1.
ty.
--
You received this message be
Slightly off-topic but still important imho: Read Q24 in the CentOS
FAQ: http://wiki.centos.org/FAQ/General. Officially major version
upgrades are not supported, but more importantly, they are not
recommended.
cheers,
Walter
On Mon, Mar 12, 2012 at 17:46, Jakov Sosic wrote:
> Hi.
>
> How do you
Hi,
I'm a big fan of Puppet and managed to have my company accept it.
However, I'm having issues deploying it (I'm used to the debian version
which works perfectly out of the box) :
- There doesn't seem to be an official repository for Suse (I've seen it
mentionned in the bugtracker but yum.pup
Hello,
I want to pass a hash as parameters for a define
$hash = { name => 'aname', key1 => 'akey', key2 => 'anotherkey' }
mydefine { 'define': hash => $hash }
define mydefine ( $hash ) {
notice("Hash is as follow: name is ${hash[name]}, key1 is
${hash[key1]}, key2 is ${hash[key2]}")
}
When
Answer to myself: always double check for misspelling variable names...
Sorry for noise,
JB
On 3/12/12 12:26 PM, Jean Baptiste Favre wrote:
Hello,
I want to pass a hash as parameters for a define
$hash = { name => 'aname', key1 => 'akey', key2 => 'anotherkey' }
mydefine { 'define': hash => $h
On 03/12/2012 11:07 AM, Walter Heck wrote:
Slightly off-topic but still important imho: Read Q24 in the CentOS
FAQ: http://wiki.centos.org/FAQ/General. Officially major version
upgrades are not supported, but more importantly, they are not
recommended.
Hi.
I know that major version upgrades ar
On 12.3.2012 11:07, Walter Heck wrote:
> Slightly off-topic but still important imho: Read Q24 in the CentOS
> FAQ: http://wiki.centos.org/FAQ/General. Officially major version
> upgrades are not supported, but more importantly, they are not
> recommended.
Yes, but I think Jakov was talking about
On Feb 15, 1:00 pm, Christian McHugh
wrote:
> Hi all,
>
> I'm attempting to use the puppetlabs-firewall module. In testing,
> rules are enabled in a random order, so it seems necessary to utilize
> puppet stages to guarantee proper ordering.
It is incorrect that you must use run stages to achi
On Mar 9, 10:15 pm, Len Rugen wrote:
> We seem to be getting intermittent errors production this message.
>
> err: Failed to apply catalog: Could not find dependency
> Package[zabbix-agent] for Service[undef] at
> /etc/puppet/modules/zabbix-agent/manifests/init.pp:76
>
> It will usually work OK
Hi Julien,
While there is no "official" repo from puppet labs for OpenSuSE/SuSE
systems, there is an up to date repo in OBS,
home:/eclipseagent:/puppet, see link below. Ben, the maintainer, and I
make a pretty good effort to ensure the packages are updated, tested,
and include all those dependenci
On Mar 12, 4:46 am, Jakov Sosic wrote:
> Hi.
>
> How do you handle CentOS updates/upgrades with puppet? Is there only way
> to count all the packages and put them in manifests like:
>
> package: ensure=>latest,
>
> I am evaluating puppet, and currently I have problem with upgrading from
> CentOS
Hi, thank you for your answer, I didn't know about your repository. It will
definitely help on my most recent servers.
However, that only solves part of my problem : about two thirds of my
servers still run SLES 10.
Even if SLES 10 isn't listed in the Supported Operating Systems page,
puppet (i
Hi Nigel,
Thanks for the fabulous response. I was convinced I was going to need to do
this by hand, happy to see my native pessimism proved wrong.
On Sat, Mar 10, 2012 at 4:23 PM, Nigel Kersten wrote:
> Jon, what version of Puppet are you running?
2.7.11 on Debian/Squeeze from apt.puppetlabs.c
Hi,
Due to severe heterogeneity among my servers (OS and version), I started my
puppet infrastructure by deploying agents by hand (from the tarball). That
way, I'm sure that I have the same version everywhere.
Having found up-to-date repositories for most of my systems, I'm now
questioning tha
On Mar 12, 2012, at 10:03 AM, Julien C. wrote:
> Hi,
>
> Due to severe heterogeneity among my servers (OS and version), I started my
> puppet infrastructure by deploying agents by hand (from the tarball). That
> way, I'm sure that I have the same version everywhere.
>
> Having found up-to-date
You can still build for unsupported SuSE distro's via the build
service, we're doing this in the server:monitoring repo for SLES10,
you just need to manually add. them. It shouldn't be a problem as long
as all the ruby requirements are there. I'll take a look at enabling
this.
--
Later,
Darin
O
Well, that's more than I expected. I can easily ensure that my server is
up-to-date, and then use whatever package I find for the agents...
Thanks.
Le lundi 12 mars 2012 15:16:32 UTC+1, pmbuko a écrit :
>
> On Mar 12, 2012, at 10:03 AM, Julien C. wrote:
>
> Hi,
>
> Due to severe heterogeneity am
Hi,
Can anyone assist how cache issue can be solved ?
Thanks
On Feb 24, 8:04 pm, mukulm wrote:
> Hi,
>
> Please assist on the below request as I am not able to receive the
> updates offline.
>
> Thanks
> mukulm
>
> On Feb 20, 7:59 pm, mukulm wrote:
>
>
>
>
>
>
>
> > I am not able tocachethe
That would be great! Anything I can do to help?
Le lundi 12 mars 2012 15:26:19 UTC+1, Darin Perusich a écrit :
>
> You can still build for unsupported SuSE distro's via the build
> service, we're doing this in the server:monitoring repo for SLES10,
> you just need to manually add. them. It shouldn
I took the RHEL/EPEL RPMs for ruby-shadow and puppet and rebuilt them for
SLES. There are very few things that need changing. The RHEL/EPEL RPMs
have really well put together SPECfiles.
I believe I posted the SPECfile diff for puppet to this list a month or so
ago. You might search the archives
Has anybody seen symptoms of a memory leak within the dashboard (or in ruby
itself?) A couple of times my puppet master server has gone off in the
weeds with an error message to the console about being out of memory. The
messages point the finger at apache and ruby.
--
Peter L. Berghold
Owner
Thanks for the advice about checking the workers. That did the trick
(the manual was for the open source pkg, but I managed to figure out
how to apply it to PE2).
Is there any available training on Puppet Enterprise out there? I see
a lot of it on the open-source package, but have not yet found
Puppet 2.7.12 is a maintenance release candidate for Puppet in the
2.7.x series.
Downloads are available:
* Source http://downloads.puppetlabs.com/puppet/puppet-2.7.12.tar.gz
See the Verifying Puppet Download section at:
http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet#Ve
Hi guys!
I need configure one command exec with onlyif parameter.
I want test file size exist or no.
Ho i do this?
Tks in advanced.
Douglas
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-users@go
On my puppetmaster:
cd /etc/puppet
tar zcvf ../pmaster.tar.gz *
copy pmaster.tar.gz to another machine that is defined in the manifest/catalog
On different machine:
mkdir -p /usr/local/localPuppet
mv pmaster.tar.gz /usr/local/localPuppet/
cd /usr/local/localPuppet
tar zxvf pmaster.tar.gz
puppe
Thank you for the answer guys.
I am currently migrating all the server on Debian Squeeze with puppet 2.6.2
I'll consider migrating to your packages repository.
For the number of DNS requests, that's not an issue, I was just having a
look at the DNS logs.
But I think this is not optimized. What
Run command if file exists:
exec { 'foo'
command => '',
onlyif => '/usr/bin/test -f /file/that/must/exist/for/exec/to/run',
}
Run command unless file exists
exec {
command => '',
creates => '/path/to/file',
}
On Tuesday, 13 March 2012 at 6:23 AM, Douglas Brancaglion wrote:
> Hi guys!
>
Checkout the 'creates' property, it seems like a cleaner way of doing this:
http://docs.puppetlabs.com/references/2.6.8/type.html#exec
On Mon, Mar 12, 2012 at 12:23 PM, Douglas Brancaglion <
douglas.rea...@gmail.com> wrote:
> Hi guys!
>
> I need configure one command exec with onlyif parameter.
On 03/12/2012 10:16 AM, Peter Bukowinski wrote:
Your master's version should always be equal to or greater than the
latest client version you're using. You can count on a newer master
working with older clients, but don't count on newer clients working
with older masters.
So, no problems
Hello,
I am setting up a new master server and migrating my configuration
from my current master server. I am also upgrading from 2.6 to 2.7.
I have the new server built and integrated with Apache, Passenger, and
Dashboard just like on my current server. I moved over all my modules
in /etc/puppe
On 03/12/2012 08:22 PM, MF wrote:
Hello,
I am setting up a new master server and migrating my configuration
from my current master server. I am also upgrading from 2.6 to 2.7.
I have the new server built and integrated with Apache, Passenger, and
Dashboard just like on my current server. I mov
On Mon, Mar 12, 2012 at 20:37, Jakov Sosic wrote:
> I know that major version upgrades are not recomended (for example 4->5 or
> 5->6). But I am asking about minor upgrades, note the 5.x -> 5.x+1 formula
> in original question.
My bad, I read that as (5.x)+1 instead of as 5.(x+1) ;)
--
Walter He
Can anyone assist whats the root cause of "Could not evaluate: No
child processes" error message in dashboard & how this can be
resolved ?
Thanks
On Mar 1, 9:05 am, mukulm wrote:
> Hi,
>
> I am getting the "Could not evaluate: No child processes" error
> message in dashboard for the task as
>
Possibly the UID under which the process is running has a resource limit and is
not able to spawn a new process? You likely need to unlimit nproc for the
puppet process.
Steve
Steve Shipway
University of Auckland ITS
UNIX Systems Design Lead
s.ship...@auckland.ac.nz
Ph: +64 9 373 7599 ext 8648
35 matches
Mail list logo
