e you an easy way to fail back in
>> case you run into any issues.
>
> This sounds like a good idea. I find certificates endlessly confusing - can
> you please spell this out in detail?
http://www.masterzen.fr/2010/11/14/puppet-ssl-explained/
> Thanks,
> Jonathan
-Naresh V.
his?
After moving away from WEBrick (default), see
http://groups.google.com/group/puppet-users/msg/643782eec6c899d6
-Naresh V.
--
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@googlegro
x27;, '/opt/ruby-enterprise/bin/gem'
in the spec file (or even make a default gem2rpm template with that)
(customise as much as you want) and build your RPMs.
(relevant:
http://zeusville.wordpress.com/2010/11/05/gem2rpm-and-development-deps/
)
-Naresh V.
--
You received this message b
er the visual appeal:
$uiso_scanners = {
"uiso-scanner.example.com" => "192.168.151.21",
"uiso-scanner1.example.com" => "192.168.18.37",
}
<% if uiso_scanners -%>
# Allow communication with UISO scanners
<% uiso_scanners.ke
be due to something else
(and I couldn't reproduce after isolating it)
Something else = trying to run another instance of puppetmaster on the
same machine (and same confdir / moduledir but different rundir). And
for some reason the CSR for my new host ended up being 0 bytes.
Removing that and re-requ
Hi again,
A couple of quick updates:
- I upgraded my server and client to 2.6.6-rc1 (again from tmz's repo)
and the problem still persists.
- I run the master behind nginx and via unicorn. Quick revert to
WEBrick showed the same problem.
-Naresh V.
On 2 March 2011 21:17, Naresh V
puppet
puppet-2.6.4-0.7.el5
puppet-server-2.6.4-0.7.el5
Mar 2 14:26:29 puppet puppet-master[21312]: header too long
#-(0)> puppetca -l
err: Could not call list: header too long
How can I fix this?
-Naresh V.
P.S.: The RPMs are from tmz's repo.
--
You received this message because
On 8 February 2011 07:44, Gabriel Filion wrote:
[...]
> Is there a way to force facter to chose a specific interface for the
> ipaddress value?
Hi,
I was wondering *when* would this part of the ipaddress.rb fact code
would be used:
--(0)> tail -20 /usr/lib/ruby/site_ruby/1.8/facter/ipaddress.r
On 21 January 2011 22:35, Peter Berghold wrote:
> Observe the following code sniget:
[...]
> file {
> nagios-ssh-key :
> path => "/home/nagios/.ssh/authorized_keys",
> owner => "nagios", group => "nagios", mode => 0600,
> source => "puppet://puppet/s
On 11 January 2011 22:27, Dan Bode wrote:
>
>
> On Tue, Jan 11, 2011 at 1:36 AM, Uwe Bartels wrote:
[...]
>
> The are special variables, not reserved words:
>
> also $module_name, $title, $name, $caller_module_name
Hi Dan,
(sorry for the minor thread-hijack)
What's the difference between $modu
net
> }
>
Doesn't that mean you've declared xinetd and xinetd::xinetd::telnet?
I think you want:
class xinetd {
...
class telnet {
...
}
...
}
(which gives you xinetd and xinetd::telnet)
-Naresh V.
--
You received this message because you are subscribed to the Google Gr
On 1 December 2010 23:01, Douglas Garstang wrote:
> Anyone know where I can get the RPM's for puppet 2.6.3 on CentOS?
> Doug
>
Here: http://tmz.fedorapeople.org/repo/puppet/epel/5/
-Naresh V.
--
You received this message because you are subscribed to the Google Groups
"
o one of my manifests that results in a
> syntax error. Without that option, puppet helpfully ignores the error and
> presents the older version of the manifest to you resulting in exactly the
> symptoms you are complaining about.
>
> --
Why not use a pre-commit syntax check hook (in
-10-06 00:04:35] bar - - [06/Oct/2010:00:04:35 CDT] "GET /
production/file_metadata/users//sudoers HTTP/1.1" 200 336
There should've been a "GET /production/file_metadata/users/blah/
sudoers.xen-3" etc.)
Thank you,
Naresh.
On Aug 25, 6:23 pm, "Naresh V." wrote:
Hi,
My setup:
gems:
rack (1.0.1)
rails (2.3.4)
rake (0.8.7)
activerecord (2.3.8, 2.3.4)
activeresource (2.3.8, 2.3.4)
activesupport (2.3.8, 2.3.4)
mongrel (1.1.5)
RPMs:
puppet-server-2.6.0-0.7.el5 (tmz's)
I patched the files installed via the RPM to test out nginx+mongrel as
follows (taken from
15 matches
Mail list logo
