Hi,
I have a running puppetmaster with nginx and passenger and ruby 1.9.2.
When i do puppet cert --trace --list . i get the following error.
/usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/application/
cert.rb:43:in `block (2 levels) in '
/usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/
Hello,
I have a desire to have separate primary/secondary CA servers, and
separate puppet master servers running behind a load balancer
(ultimately an F5 but will use an Apache mod_proxy.. setup initially
to test).
The Pro Puppet books suggest this with everything running with
Passenger which is
Hello,
The CA server is the most difficult part to architect in a load balancer
situation as it's the one thing that doesn't cluster that well. The idea
is to keep your certificate store in sync across servers. Some people
rsync, some people use shared storage, some people don't care and have
Folks,
I've rolled 2.7.9 for Solaris as an OpenCSW package[1]. You can get it from the
'unstable' catalog now.
Regards,
--Mark
[1] http://www.opencsw.org/packages/puppet &
http://www.opencsw.org/packages/puppetmaster
--
Mark Phillips
http://probably.co.uk
http://vntx.cc
--
You recei
Folks,
I've also rolled Facter 1.6.4 for Solaris as an OpenCSW package[1]. You can get
it from the 'unstable' catalog now.
Regards,
--Mark
[1] http://www.opencsw.org/packages/facter
--
Mark Phillips
http://probably.co.uk
http://vntx.cc
--
You received this message because you are sub
On Thu, Dec 15, 2011 at 1:27 PM, Luke Bigum wrote:
> Hello,
>
> The CA server is the most difficult part to architect in a load balancer
> situation as it's the one thing that doesn't cluster that well. The idea is
> to keep your certificate store in sync across servers. Some people rsync,
> some
Hi Daniel,
Greetings!!!
That was a typo. The puppet version was 2.7.9 and not 2.6.9 as per my
posting subject.
***SOLUTION APPLIED***
+++
++
Since, we are using cacerts.org certificates in ldap, so I had
a
On Dec 14, 4:37 pm, Jo Rhett wrote:
> Try
> notify => Service['autofs']
Right. As far as I know, classes do not forward signals to resources
they contain.
Furthermore, you should consider whether it would be appropriate to
combine your two classes. That a resource belonging to one wa
I upgraded my puppetmaster server to the version 2.7.9.
All started working again.
But after about 18-20 hours, it again stopped working.
We are now using puppet behind passenger and Apache:
Details are as below:
1. Puppet: 2.6.9
2. Rack: 1.2.2
3. Passenger: 3.0.7
4. OS: CentOS 6
Before it stopped
On Dec 14, 7:35 am, Sans wrote:
> Another question: Can I just do "service { 'autofs':" or "service
> { 'nfs':" (or any given standard unix/linux service) just like that?
As opposed to what? The service name to use is whatever the system's
tools use to refer to the service. For example, if y
Sorry, a typo again. The puppet version is: 2.7.9.
So, details are:
1. Puppet: 2.7.9
2. Rack: 1.2.2
3. Passenger: 3.0.7
4. OS: CentOS 6
On Dec 15, 7:14 pm, Ganesh Sharma wrote:
> I upgraded my puppetmaster server to the version 2.7.9.
> All started working again.
> But after about 18-20 hour
On 12/15/2011 03:08 PM, jcbollinger wrote:
> Right. As far as I know, classes do not forward signals to resources
> they contain.
Which really is a major pitfall. Any insight on why it's not done?
Cheers,
Felix
--
You received this message because you are subscribed to the Google Groups
"Pupp
On Dec 15, 2:08 pm, jcbollinger wrote:
> On Dec 14, 4:37 pm, Jo Rhett wrote:
>
> > Try
> > notify => Service['autofs']
>
> Right. As far as I know, classes do not forward signals to resources
> they contain.
>
Are you absolutely sure about that? My understanding was to use
something l
I have this:
node /prod\-(blitz|cisco|masdar|dow)\-app\-01.c3\-e.com/ inherits
basenode-rhel {
$splunk_loghost = "loghost.c3platform.com"
include splunkforwarder::c3_app_server
}
class splunkforwarder::c3_app_server inherits splunkforwarder::common {
notice("loghost=$splunk_loghost")
Here is what I am trying to do:
service{ foo:
...
restart => "/path/to/script/to/run 2>&1 | tee
/path/to/where-I-want-logfile-`date +%Y%m%d-%H%M%S`.log",
...
}
What I get is a log file named "/path/to/where-I-want-logfile-`date"
I have unsuccessfully tried escaping the command quotes with a bac
On Thu, Dec 15, 2011 at 02:33, linuxbsdfreak wrote:
Hey there.
> I have a running puppetmaster with nginx and passenger and ruby 1.9.2.
I see something odd here - 1.9.2 in the line above, and ...
> When i do puppet cert --trace --list . i get the following error.
>
> /usr/lib64/ruby/gems/1.9.1
I'm currently searching around/reading up on exported resources, but
figured I'd ping the list to see if someone had a quick answer.
I'm collecting and exporting ssh keys, basically like the example in
ProPuppet and in the wiki etc. I was collecting both rsa and dsa keys,
and exporting all keys.
Dan - Some distro's pinned these kind of directories at 1.9.1. For
example in Debian the package is called ruby-1.9.1 even though its
version 1.9.2/1.9.3 (depending on release).
# ruby1.9.1 --version
ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux]
# ls /usr/lib/ruby/
1.8 1.9.1 vendor_rub
Okay - so its a known issue:
http://projects.puppetlabs.com/issues/7428
Looks like there is a workaround there Kevin. Let us know how you go.
ken.
On Thu, Dec 15, 2011 at 7:40 PM, Ken Barber wrote:
> Dan - Some distro's pinned these kind of directories at 1.9.1. For
> example in Debian the pac
> > The absolute nicest option is to use a bundled certificate authority
> where
> > all CAs are signed by some higher level Cert, then most of these
> problems go
> > away. Last I heard this was broken in Puppet / Ruby.
>
> That used to work before 0.25, sadly broken since.
> Ruby fully suppor
Hey,
is there a possibility to define dependencies across multiple nodes?
I have the following situation:
I want to deploy a web application on multiple servers. There are
different services to set up:
- database
- shared volume
- the application (tomcat)
Every service runs on a different node.
I
Hi,
We're using puppet from longer time, but now want to switch into
stored configs. When I ran locally puppet on puppetmaster server, ie:
puppet /var/lib/puppet/manifests/nodes.pp --debug
it works smooth.
When running client with debug I get message:
root@puppet-client:~# puppet agent -v --fqdn
Hi,
last thing i see in /var/log/daemon.log after trying "/etc/init.d/puppet
reload" is
notice: Starting Puppet client version 2.7.9
debug: Using cached certificate for ca
debug: Using cached certificate for cypher.qype.com
debug: Using cached certificate for ca
debug: Using cached certificate_r
Excuse the pseudo-code, but could you pipe the "ntpdate" command to "at now +5
minutes"? It'll exit with status 0, allowing puppet to go in its merry way, and
the time will sync up "soon", hopefully before puppet runs again.
If you could force the module to run very late in the chain, you could
Hi everyone,
I am a puppet newbie. But I am trying to setup a new puppet
infrastructure based on Apache/Passenger.
Facts:
- My server is a debian Squeeze
- Puppet setup with gem:
[root@puppetmaster]:/etc/puppet # gem list puppet
*** LOCAL GEMS ***
puppet (2.7.6)
puppet-module (0.3.4)
- Rack
You could try:
tee /path/to/where-I-want-logfile-$(date +%Y%m%d-%H%M%S).log
Alternatively, since it doesn't look like you're using any puppet
variables in the command string, you could try using single quotes
(i.e. restart => '/path/ ...') so puppet won't try to interpret anything
it sees in ther
On 14.12.2011 19:14, Andreas Haerter wrote:
> I'm asking because there might be some kind of standard and/or tools to
> parse the source code of .pp files to generate Docs for the puppet
> modules I'm going to write.
Ok, got my question answered on IRC. If you have Rdoc-formatted text
blocks befor
Hi *,
I'm new to puppet. Before writing and modifying tons of source code to
get my environment up and running, it would be nice to hear if there are
any recommendations regarding the format of
a) comment blocks to document classes and files
b) comment blocks to document other stuff (e.g. defines
On Thu, Dec 15, 2011 at 07:22, Malte Janduda
wrote:
> is there a possibility to define dependencies across multiple nodes?
Not at this point in time, no, although Luke had a prototype of a
"stop and wait" resource ages ago that handled this.
We have it on our roadmap, but the problem is surpris
Thanks for the suggestions.
tee /path/to/where-I-want-logfile-$(date +%Y%m%d-%H%M%S).log did not work.
bash: syntax error near unexpected token `('
I will let you know if the single quote option works.
“Sometimes I think the surest sign that intelligent life exists elsewhere in
the universe is
Gr.
On Thu, Dec 15, 2011 at 9:11 AM, Douglas Garstang
wrote:
> I have this:
>
> node /prod\-(blitz|cisco|masdar|dow)\-app\-01.c3\-e.com/ inherits
> basenode-rhel {
> $splunk_loghost = "loghost.c3platform.com"
> include splunkforwarder::c3_app_server
> }
>
> class splunkforwarder::c3_app
On Dec 15, 11:11 am, Douglas Garstang wrote:
> I have this:
>
> node /prod\-(blitz|cisco|masdar|dow)\-app\-01.c3\-e.com/ inherits
> basenode-rhel {
> $splunk_loghost = "loghost.c3platform.com"
> include splunkforwarder::c3_app_server
>
> }
>
> class splunkforwarder::c3_app_server inherit
On Dec 15, 8:33 am, Felix Frank
wrote:
> On 12/15/2011 03:08 PM, jcbollinger wrote:
>
> > Right. As far as I know, classes do not forward signals to resources
> > they contain.
>
> Which really is a major pitfall. Any insight on why it's not done?
I suspect some historical inertia, but it's a
On Dec 15, 10:16 am, Sans wrote:
> On Dec 15, 2:08 pm, jcbollinger wrote:
>
> > On Dec 14, 4:37 pm, Jo Rhett wrote:
>
> > > Try
> > > notify => Service['autofs']
>
> > Right. As far as I know, classes do not forward signals to resources
> > they contain.
>
> Are you absolutely sure ab
John Kennedy wrote:
> OS - RHEL5.7
> Installation Source - epel-testing repo
> Puppet server version - 2.6.6
> puppetd version - 2.6.6
>
> I searched Google and none of the answers were a match for my set up...
>
> I can do 'puppetd --test' from the client and things work as expected.
> When doin
On Thu, Dec 15, 2011 at 2:56 PM, jcbollinger wrote:
>
>
> On Dec 15, 10:16 am, Sans wrote:
> > On Dec 15, 2:08 pm, jcbollinger wrote:
> >
> > > On Dec 14, 4:37 pm, Jo Rhett wrote:
> >
> > > > Try
> > > > notify => Service['autofs']
> >
> > > Right. As far as I know, classes do not forw
I see, that is the "passenger_set_cgi_param" which was missing. I was
using "proxy_set_header" and that was not working. And clearly my
config.ru was missing a lot too, and i had to make symlinks and stuff
to point to my Puppet installation dirs
Thanks a lot,
Alex
On 13 déc, 22:14, windowsrefund
37 matches
Mail list logo
