Hi Derek,
2010/11/12 Derek J. Balling
> [...]
> Nope. Because "autosign" doesn't also "auto-overwrite".
>
> - New Host "foo001.domain.tld" is created
> - Certs are exchanged for foo001 with the puppetmaster, life is good,
> autosigned
> - Host foo001.domain.tld is retired
> - Replacement Host "f
Derek J. Balling wrote:
> It's just ugly. Like I said in my ticket notes, I'll concede that for
> some people, it's a necessity, but there's clearly also a set of
> people for whom it is just unnecessary pain and suffering.
>
It's been my experience that SSL (or the requirement for some form of
t
Excellent, thanks for that Dan I'll take a look.
On Nov 11, 5:42 pm, Dan Bode wrote:
> Hi,
>
> On Thu, Nov 11, 2010 at 9:17 AM, luke.bigum wrote:
>
> > Hi,
>
> > Does anyone know if this document is up to date (besides the comment
> > at the top saying it's not):
>
> >http://projects.puppetlabs.c
hi all,
i m tring to use Service resource type as following...
service { 'tomcat':
ensure => running,
}
as I know , It will first stop tomcat , then start tomcat..
but my requirement is like that i do not want to restart it ..
, i want that if tomcat is allready running , then there
Hi Sanjiv,
This *should* not happen. Puppet will not restart a service if it's
already running properly. I'm going to guess that the problem is
Puppet does not KNOW that Tomcat is running properly and so thinks it
needs to restart Tomcat every run.
Does your Tomcat LSB/init script (/etc/init.d/to
On 12 Nov., 02:42, Joel Merrick wrote:
> > However, what if the selection of packages changes? Is there a more
> > clever way to install tasks with tasksel, without listing each and
> > every package the tasksel task is made of?
> Have you tried the meta-package gnome-desktop-environment?
The p
Ruby shadow 1.4.1-7 was already installed so it has to be something
else
I will report it as a bug
On Nov 11, 11:26 pm, Daniel Pittman wrote:
> rvlinden writes:
> > I have a virtual user (mqm) in puppet (v2.6.2 on CentOS 5.5 with Ruby
> > 1.8.6.383-6)
>
> [...]
>
> > and it does get created on
I use tmz's puppetstatus scripts [1] [2] and they work great for checking the
last run time from Nagios. I also have reports setup w/ tagmail to send me
anything with "err" in it.
-Doug
[1] http://markmail.org/message/m6xi34aljso4w5qq
[2] http://tmz.fedorapeople.org/scripts/puppetstatus/
On 11
Derek,
I agree with you that the certificates are unnecessary for some
people, myself included. Since we're behind a large corporate
firewall, we don't need this type of security for in house
management. As we upgrade our engineers workstations, the new
workstation almost always has the same nam
On Nov 12, 1:50 am, "Tobias Lott" wrote:
> Only the correct keys are actually distributed, however this Problem
> occurs only on some Machines weather its Ubuntu (10.10) 32 or 64 Bit.
> Additionally the authorized_key files are being flooded with the same keys
> over and over again.
> F.e. if o
I've upgraded to puppet v2.6.2 on ubuntu (clients and server) and now
I get this error messages related to pluginsync:
info: Retrieving plugin
err: /File[/var/lib/puppet/lib]: Failed to generate additional
resources using 'eval_generate': wrong header line format
err: /File[/var/lib/puppet/lib]: C
On Nov 3, 4:39 pm, Nigel Kersten wrote:
> We really need community testing with this provider. There are some
> questions Rudy has in the ticket log that we need to get answered.
>
> http://projects.puppetlabs.com/issues/4258
Hi, I'm the author of pkgutil, I'm glad you're about to support it in
P
Steve Neuharth wrote:
> I've upgraded to puppet v2.6.2 on ubuntu (clients and server) and now
> I get this error messages related to pluginsync:
How did you upgrade? I've seen this when files from previous versions
hung around on the master/client too.
Regards
James
--
Puppet Labs - http://ww
Thanks Daniel,
in puppet.conf on the server: (we are just trying to get a file installed to
the int environment client)
[main]
vardir = /var/lib/puppet
logdir = /var/log/puppet
rundir = /var/run/puppet
ssldir = $vardir/ssl
pidfile=$rundir/puppetmaster.pid
[int]
#modulepat
* ericlee748 [2010/11/10 14:09]:
> I have a large hierarchy of files that are set up to recursively
> copy from my puppet master. It takes a long while to copy these
> files over to the clients - roughly 1 hour. Only 1 or 2 files in
> the hierarchy will ever change. Is there a better way to do wha
On Nov 10, 2:09 pm, ericlee748 wrote:
> Hey guys,
>
> I have a large hierarchy of files that are set up to recursively copy
> from my puppet master. It takes a long while to copy these files over
> to the clients - roughly 1 hour. Only 1 or 2 files in the hierarchy
> will ever change. Is there a b
jeez, sorry... gentoo. This is on gentoo, not ubuntu, so I used
portage.
I suppose I could try to scrub my puppetmaster of everything puppet
related and reinstall... definitely not the ideal solution. I'll look
through the ruby libs and see if I can find any dupes first.
thanks James.
On Nov 12,
Using 1.0.4 release on Solaris 10 with Ruby 1.8.7.
Starting the server in production mode works fine until I request a
page from the web browser then I get the following errors on the
console. I'm running as user puppet (have also tried as user root but
same output). All files are owned by user/gro
I found the problem in /etc/sysconfig/puppetmaster. The MANIFEST
directive wasn't commented out. Shouldn't this be commented on that it
needs to be commented out for multiple environment use?
Thanks
On Nov 12, 10:52 am, James Louis wrote:
> Thanks Daniel,
>
> in puppet.conf on the server: (we ar
Hello,
Up to right now everything is working great with puppet. I just have
one questions.
Is there a way to tell a type (like file) not to fail if something
specific happens.
Let's say I have a directory which it needs to be created if its not
there and then I mount a file system "ro" on top of
James Turnbull wrote:
> We're back with a maintenance release: 2.6.3. This
> release addresses some issues in the 2.6.2 release.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 12 - 14 are availa
OK, I unmerged and re-emerged the package and I get the same message.
I also verified that all remnants of the ruby puppet stuff was gone
from site_ruby before I reinstalled.
I'm fairly certain that it's not my manifests as this error seems to
occur in the phase where puppet is gathering it's plug
I have figured out that an empty database allows the dashboard to work
without failure but as soon a report from a node is added the whole
thing breaks with the to_time errors.
Clients and master are running Puppet 2.6.3.
On Nov 12, 10:01 am, Kent wrote:
> Using 1.0.4 release on Solaris 10 with
23 matches
Mail list logo
