Le 10/05/2013 15:20, Ken Barber a écrit :
Yeah, I don't think this was intentional Allan - looks like google
groups threading is broken somehow in this case and mixing these two
threads together. In my email client however, they are separate threads.
Hmm. Yes not intentional, sorry. Same for me, it is a separated thread
in my email client.
Note for later: cleaning subject+content is not enough for hidden tags
used by google groups :)
Regards,
--
Y.
ken.
On Fri, May 10, 2013 at 1:59 PM, Allan Yung <[email protected]
<mailto:[email protected]>> wrote:
I'm glad you were able to find a solution to your problem but in
the future please open your own thread instead of hijacking an
existing one.
Cheers,
Allan
On Friday, 10 May 2013 09:29:03 UTC+1, Hexasoft wrote:
Le 09/05/2013 22:59, Yannick Perret a écrit :
Le 09/05/2013 22:20, Johan De Wit a écrit :
Hu Yannick,
MY first thought goes to a missing ca_server. This could be
one dedicate puppetmaster. All other masters should be
configured to use this one as 'ca_server'
check for the configuration options
*ca_server = <server acting as central ca server> in the
[main] section
* ca = false in the [master] section of puppet.conf
Thanks. I will check this. I guess I missed that part.
By the way, is there any way to have a full "equivalent" set
of masters? I mean that having one of them dedicated to CA
server (or on an other machine) means that this particular
node is not redundant. We use a DNS load-balancing for
availability + a TCP-balancing for scalability, and having a
"special" node in this pool makes maintenance more complicated.
Hello,
it was not exactly that problem but it was related to that. I
made strange things with certs/CA names. It is now corrected
and it seems to work fine on both masters.
BTW creating a "false" CA and setting both masters to ca=false
seems to work fine (after copying CA-related stuff from 1st
master to 2nd master).
Not sure it is very "nice", whatever.
Thanks.
--
Y.
Regards,
--
Y.
Hope this helps
On 05/09/2013 10:03 PM, Yannick Perret wrote:
Hello,
I'm migrating our master from an old puppet version to a
recent one (3.1.0) (on different machines).
I first installed a first master, and I manage well to run
clients from 3 machines against this master.
I then installed a 2nd master and the clients that connect
to this master failed.
The output from the client (puppet agent) is a HTML output
that contains (in text):
The application has exited during startup (i.e. during the
evaluation of config/environment.rb). The error message may
have been written to the web server's log file. Please
check the *web server's* log file (i.e. /not/ the (Rails)
application's log file) to find out why the application
exited.
If that doesn't help, then please use the backtrace below
to debug the problem.
Application root:
/etc/puppet/rack
Backtrace:
# File Line Location
0
/opt/ruby-enterprise/lib/ruby/gems/1.8/gems/puppet-3.1.0/lib/puppet/util.rb
518 in `exit'
1
/opt/ruby-enterprise/lib/ruby/gems/1.8/gems/puppet-3.1.0/lib/puppet/util.rb
518 in `exit_on_fail'
2
/opt/ruby-enterprise/lib/ruby/gems/1.8/gems/puppet-3.1.0/lib/puppet/application.rb
362 in `run'
3
/opt/ruby-enterprise/lib/ruby/gems/1.8/gems/puppet-3.1.0/lib/puppet/util/command_line.rb
132 in `run'
4
/opt/ruby-enterprise/lib/ruby/gems/1.8/gems/puppet-3.1.0/lib/puppet/util/command_line.rb
86 in `execute'
5 config.ru <http://config.ru> 35
6
/opt/ruby-enterprise/lib/ruby/gems/1.8/gems/rack-1.5.2/lib/rack/builder.rb
55 in `instance_eval'
7
/opt/ruby-enterprise/lib/ruby/gems/1.8/gems/rack-1.5.2/lib/rack/builder.rb
55 in `initialize'
8 config.ru <http://config.ru> 1 in `new'
9 config.ru <http://config.ru> 1
The same client against the first master works fine (we use
a load-balanced system).
What I failed to understand is that I followed the same
installation steps for both. I even made a global copy of
all the installation directories from the one that works to
the one that fail with the same message (a raw tar.gz of
/etc/puppet (where I put all the master stuff), of
/opt/ruby-enterprise directory (installed with same
version, and puppet/facter/rack/... installed from compiled
'gem'), of /etc/httpd/conf.d/).
Some data:
- masters and clients and RHEL6-like machines, both masters
are installed with the same automated system, with the same
basic configuration
- the SSL seems to work fine as I can see success
connections from the httpd ssl logs (from the client)
- I use the ruby-enterprise, same version on both,
installed from sources
- I use gem to install puppet, facter, rack, rails and all
related stuff, the gem is the one that comes from
ruby-enterprise
- as last try I made a global copy of all puppet-master
related stuff from the working client (in a tarball) and
pushed it on the failing master: it does not change anything.
Any clue about what I missed?
Regards,
--
Y.
--
You received this message because you are subscribed to the
Google Groups "Puppet Developers" group.
To unsubscribe from this group and stop receiving emails
from it, send an email to [email protected].
To post to this group, send email to
[email protected].
Visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
For more options, visit
https://groups.google.com/groups/opt_out.
--
Johan De Wit
Open Source Consultant
Red Hat Certified Engineer (805008667232363)
Puppet Certified Professional 2013 (PCP0000006)
_________________________________________________________
Open-Future Phone+32 (0)2/255 70 70
<tel:%2B32%20%280%292%2F255%2070%2070>
Zavelstraat 72 Fax+32 (0)2/255 70 71
<tel:%2B32%20%280%292%2F255%2070%2071>
3071 KORTENBERG Mobile+32 (0)474/42 40 73
<tel:%2B32%20%280%29474%2F42%2040%2073>
BELGIUMhttp://www.open-future.be
_________________________________________________________
--
You received this message because you are subscribed to the
Google Groups "Puppet Developers" group.
To unsubscribe from this group and stop receiving emails
from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
For more options, visit
https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the
Google Groups "Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google
Groups "Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected]
<mailto:puppet-dev%[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at http://groups.google.com/group/puppet-dev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google
Groups "Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-dev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-dev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
