Are you running passenger? I believe there is/was a known issue with this and
passenger.
Jason
Sent from my iPad
On Sep 23, 2011, at 21:29, Jo Rhett wrote:
> I want to check in and see if this is a known issue before I open a bug. I'm
> seeing a particular issue where after a manifest chan
We're switching back to running as a service, but we observed that the
puppet runs tended to cluster together. (We are using foreman also). We
used "splay" at boot to randomize the puppet runs, in case we rebooted a lot
of systems at the same time, but over time, puppet runs woud cluster
together
I want to check in and see if this is a known issue before I open a bug. I'm
seeing a particular issue where after a manifest change, the first run with the
newly compiled catalog will not report the changes made to the system.
For example,
1. I edited a manifest to change the ntp servers.
2
You realize that you can set the RHS of the from address to an fqdn, right?
On Fri, Sep 23, 2011 at 6:00 PM, Peter Berghold wrote:
> Hi folks,
>
> I thought I'd get clever tonight and add to my base class for node
> configuation the statement:
>
> user { root : comment => "Root User on ${hostname
Hi folks,
I thought I'd get clever tonight and add to my base class for node
configuation the statement:
user { root : comment => "Root User on ${hostname}" }
My hope was that I would change the GECOS field for the root user so that
emails from root on the machines would identify which "root" th
Over the years many shops have come to start running puppet via cron to
address memory leaks in earlier versions of Ruby, but the official position
was that puppet was meant to be run as a continually running service.
I am wondering if the official position has changed. On one hand many if not
all
We're running Puppet via cron instead of daemonized which eliminates these
kinds of issues.
On Fri, Sep 23, 2011 at 9:56 AM, Martin Alfke wrote:
> Hi,
> On 23.09.2011, at 13:01, datastream wrote:
>
> > Hi,
> >Three days ago i notice puppet agent in many node use a lot of
> memory(some nodes
Hi,
On 23.09.2011, at 13:01, datastream wrote:
> Hi,
>Three days ago i notice puppet agent in many node use a lot of memory(some
> nodes about 1G),and many of them start at April 23. All system is debian
> 6.0.2/amd64(puppet 2.6.5-2,facter 1.5.7 ), everything is up to date.After
> restart
On Thu, 2011-09-22 at 13:26 -0700, jcbollinger wrote:
> >
> > I would like the backup_include to automatically include /var/www if
> > the host is an apache server (for example), and I would like those
> > directories to be defined in the apache class (not the bacula class)
> >
> > Any clever ways
On Thu, 2011-09-22 at 13:26 -0700, jcbollinger wrote:
> >
> > I would like the backup_include to automatically include /var/www if
> > the host is an apache server (for example), and I would like those
> > directories to be defined in the apache class (not the bacula class)
> >
> > Any clever ways
Hi,
Three days ago i notice puppet agent in many node use a lot of
memory(some nodes about 1G),and many of them start at April 23. All system
is debian 6.0.2/amd64(puppet 2.6.5-2,facter 1.5.7 ), everything is up to
date.After restart puppet, in three days, memory usage grows from 56M to
12
Hi all,
Quick reminder that if you couldn't make it to PuppetConf, we're offering
free live streaming of the event. We have a great line-up of speakers,
including
Martin Mickos, CEO of Eucalyptus, at 9 am. Check it out here:
http://bit.ly/qBY5Nb
Thanks,
--
Michelle Carroll
miche...@puppetlabs.co
Hi,
We currently use ldap ENC to set server role variables and extlookup
to set domain or environment variables.
I have a suggestion regarding ldap use as an ENC - if a node within
ldap has the environment attribute set then it should inherit/mixin
(if available) from a node named after it's envi
On Thu, Sep 22, 2011 at 8:03 AM, Hamoun gh wrote:
> I noticed the following problems when working with CloudPack and the
> image ami-08728661 (and it probably apples to other CentOS images as
> well)
>
> 1) the ssh user in this AMI is ec2-user, but sudo to root is not
> possible in the ssh command
Hi,
it just so happens that I'm attempting to do the same thing, automating the
install of a Nexus repository.
I'm quite new to building RPMs, so I was wondering if you would be willing
to share your RPM build script and puppet manifests ?
I'm currently writing a puppet module that performs the
On Sep 22, 4:11 pm, Douglas Garstang wrote:
> On Thu, Sep 22, 2011 at 1:56 PM, jcbollinger
> wrote:
>
> > On Sep 22, 11:05 am, Douglas Garstang wrote:
> >> On Thu, Sep 22, 2011 at 5:57 AM, jcbollinger
> >> wrote:
>
> >> > On Sep 21, 6:34 pm, Nigel Kersten wrote:
> >> >> On Wed, Sep 21, 201
Hmm - could be that you can't pass a hash in as the namevar? At least
last time I looked this was true :-) ... you can certainly pass a hash
as a parameter if you like - but namevar should be just a string ...
or array to create multiple resources - but still an array of strings
:-). Not sure why i
17 matches
Mail list logo
