Guys, I'm sorry.
I was a bit confused over how to reference template paths relatively
(I'm managing someone elses puppet deployment you see!).
I fully qualified the path to the template in the development tree, and
then copied to production. You can see below that my path is still
pointing
warning: peer certificate won't be verified in this SSL session
warning: peer certificate won't be verified in this SSL session
err: Could not request certificate: Error 400 on SERVER: header too long
Exiting; failed to retrieve certificate and waitforcert is disabled
This last message seems
On 03/04/2011 03:50 AM, Atha Kouroussis wrote:
Hi all,
I'm trying to find a way to collect exported resources based not only on
a tag but also based on the originating node. Currently exported
resources can't collected using more than one criteria, but I can get
around that by wrapping the
I recently found myself needing to perform a similar task to that
desired by Udo Waechter in:
https://groups.google.com/group/puppet-users/browse_thread/thread/ea6a82d5e58fdb4e
Namely, I would like a file to exist on machine A iff any or all of
machines B-Z have some other resource.
My
Hi all,
I've been testing something today that I can't get to play ball the
way I'd like. Here's the setup:
site.pp
import nodes
$extlookup_datadir = /etc/puppet/envs/poc/extdata
$extlookup_precedence = [%{fqdn}, common]
nodes.pp
class core {
include hostinfo
include motd
}
hostinfo
When an error occurs in prerun_command, puppet continues execution
instead of stopping.
We can see the error at the log file, but puppet cotinues doing
changes:
puppetd[18430]: Failed to prepare catalog: Could not run command from
prerun_command: Execution of '/path/to/command' returned 1:
We
Hi all,
I've been testing something today that I can't get to play ball the
way I'd like. Here's the setup:
site.pp
import nodes
$extlookup_datadir = /etc/puppet/envs/poc/extdata
$extlookup_precedence = [%{fqdn}, common]
nodes.pp
class core {
include hostinfo
include motd
}
hostinfo
Hullo
I've not used Puppet yet, so this could be an obvious misunderstanding
on my part. I've seen many manifest entries for files that write rules
about file ownership and permissions. Surely these types of attributes
should be managed through the package managers, with a possible
override if
Hi Tim,
You can just tell Puppet not to manage the file permissions at all,
like this, which just specifies the content:
file { /etc/syslog.conf:
source = ...
}
I'll assume you're talking about something like this?
file { /etc/syslog.conf:
owner = root,
group = root,
mode = 0644,
On Mar 8, 2011, at 7:44 AM, Robert Pumphrey wrote:
I also have a completely blank Run Time chart on a new deployment of
dashboard 1.0.4. Do you have any idea where I might look to try to fix
this problem?
I see this, too. I'll track it down and post an update here.
r
--
Randall Hansen •
Unfortunately I don't have a Dashboard (or Puppet!) on hand at the
moment, but are you all using Puppet version 2.6.x? The format of the
reports has changed and some functionality isn't compatible such as a
the graph images of a node's Puppet running times. Is that what you
are talking about?
On
On 9 March 2011 15:07, Felix Frank felix.fr...@alumni.tu-berlin.de wrote:
warning: peer certificate won't be verified in this SSL session
warning: peer certificate won't be verified in this SSL session
err: Could not request certificate: Error 400 on SERVER: header too long
Exiting; failed to
Hello guys,
I’m currently deploying puppet in my infrastructure and I’m having some
issues probably you already have addressed. My environment is basically a
PXE environment where I decided to use a shared certificate in the meantime
for node authentication. We have addressed this issue setting
Hello list!!
I am having an issue sharing some files from a location in my apache
modules location on the puppet server. It seems that some files are
being served from a custom file sharing mount point, yet anything
served from the apache module is not transferred to the client:
## error while
On Wed, Mar 9, 2011 at 10:31, Ricardo Bartolome Mendez
rica...@tuenti.com wrote:
Hey. I can't answer most of your questions, but…
On the other hand, shall I hit this problem when start using stored configs?
Is there any plan of integrating reports using queues as stored configs do,
in order
Hello,
Well I spent the morning getting passenger installed on my RHEL 5 server and
finally got it working and was able to run an agent update. But now I have
a questions about logs, before when we were working we would tail -f
puppetmaster.log file to see notices and errors, but now this log
On Mar 9, 2011, at 1:04 AM, Victor Mora wrote:
When an error occurs in prerun_command, puppet continues execution
instead of stopping.
We can see the error at the log file, but puppet cotinues doing
changes:
puppetd[18430]: Failed to prepare catalog: Could not run command from
Hi Luke
Thanks. Your examples are correct and I'm sorry for not including them
in my original post.
I think that your first suggestion is the way for me to go. I do think
that this should be elaborated as best practice (if that's what it
is). I did have rpm (yum) in mind as the PM. There are some
Hi!
My company has been successfully using puppet 2.6 for a month now, and
we are now exploring the possibility of managing users and groups
through puppet (vs LDAP). If we were to implement managing
users/groups for various services (e.g. 'www' for nginx and apache),
what would be the best
Hi,
Don't think you have set the title right. 'conf/conf.d' .. Should be just
conf.d yeah?
file {
/etc/httpd/conf/conf.d/000-ssl.conf:
owner = root,
group = root,
mode = 440,
require = Exec[create httpd conf dir],
source = puppet:///apache/krome/httpd/conf.d/000-ssl.conf
}
Hi,
Normally apache logs (assuming your running passenger with apache).
I'm pretty sure passenger spits out error logs to there too.
Cheers
On 10/03/2011, at 4:44, Christopher Lee chr...@spiralweb.com wrote:
Hello,
Well I spent the morning getting passenger installed on my RHEL 5 server
This maintenance release fixes two issues with Puppet 2.6.5.
Bug #6418: Files with the source parameter set are automatically set to audit
The audit functionality was activated unexpectedly on file resources
that use the source parameter. This could cause spurrious notify
events. These
On Mon, Mar 07, 2011 at 09:23:58PM -0800, Douglas Garstang wrote:
On Mon, Mar 7, 2011 at 4:06 PM, LarsP larsp...@gmail.com wrote:
I was told recently at a Puppet workshop that using LDAP for managing
node information is not advised. Anybody care to comment? What is it
about using LDAP
Jacob Helwig wrote:
This maintenance release fixes two issues with Puppet 2.6.5.
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 13 - 15 are available for testing.
Add the puppet.repo file from
On 3/7/2011 6:38 AM, jcbollinger wrote:
On Mar 5, 5:22 pm, .f...@kraptastic.com wrote:
I'm trying to find out the 'puppet' way of overwriting a
config/variable. I've tried using a define
(http://pastebin.com/ncVwtwGj) and a parameterized class
(http://pastebin.com/3UysCgi7). But both
Jacob Helwig ja...@puppetlabs.com writes:
This release is available for download at:
http://puppetlabs.com/downloads/puppet/puppet-2.6.6.tar.gz
An upload of puppet 2.6.6 has been made to Debian Unstable.
--
Stig Sandbeck Mathisen
pgpdMBGhtaSLQ.pgp
Description: PGP signature
26 matches
Mail list logo
