Dear experts,
Since I've moved my *puppetmaster* form SL5 (Scientific Linux) to SL6 with
SELinux on, I'm facing loads of trouble. I also move away from WEBrick to
apache/passenger, following the instruction here:
http://projects.puppetlabs.com/projects/1/wiki/Using_Passenger
and I can't
Hi,
Have you still got your puppetmaster service running? Don't need that running
when using httpd and passenger.
Den
On 13/05/2012, at 21:07, Sans r.santanu@gmail.com wrote:
Dear experts,
Since I've moved my puppetmaster form SL5 (Scientific Linux) to SL6 with
SELinux on, I'm
Your question is probably too broad. If there is information you are
missing in bitfield's page, can you tell us what it is that you are
missing?
cheers,
Walter
On Sat, May 12, 2012 at 10:59 AM, wen1023 wu wuwen1...@gmail.com wrote:
Hi
I want to know the comprehensive comparison between the
Using Puppet 2.6.2, 2.7.1 and 2.7.11, I have the severity reported to
syslog as expected.
It's not a bug in puppet; it's your syslog configuration not reporting
severity in /var/log/messages
Le vendredi 4 mai 2012 12:40:33 UTC+2, Ano nym a écrit :
Hey,
same problem here. Is there a fix
Just concerning this PSK aspect of Sites, would this also be a similar
alternative to using a shared cert (or set of certs) in tandem with the
node_name_value or node_name_fact, as was recently discussed in this thread?
https://groups.google.com/d/msg/puppet-users/2s0PJ7p_S7M/jLVUjL34Wz4J
In
Just concerning this PSK aspect of Sites, would this also be a similar
alternative to using a shared cert (or set of certs) in tandem with the
node_name_value or node_name_fact, as was recently suggested by Gary in
this thread?
Nope, I've stopped puppetmaster And albutted in the chkconfig but I thought
puppetmasterd is still needed.
But anyway, the main problem is port 8140 is already used by Ruby/puppet_port_t
- what I should do about it? Cheers!!
--
You received this message because you are subscribed to the
Nope, I've stopped puppetmaster and also did chkconfig off but I thought
puppetmasterd is still needs to be running(??).
But anyway, the main problem is port 8140 is already used by
Ruby/puppet_port_t - what I should do about it? Cheers!!
On Sunday, May 13, 2012 2:39:25 PM UTC+1, Daniel Sung
The problem with port has gone now but still apache fails to start,
reporting this in the log:
[Mon May 14 00:37:42 2012] [error] Unable to configure RSA server private
key
[Mon May 14 00:37:42 2012] [error] SSL Library Error: 185073780
error:0B080074:x509 certificate
Sorry guys for making noise about the certificates: It's fixed now - I was
using wrong certificates. I'm also able to start the *httpd* using port *
8084* instead of 8140. Cheers!!
On Monday, May 14, 2012 12:45:05 AM UTC+1, Sans wrote:
The problem with port has gone now but still apache fails
Dear all,
Can anyone please tell me why Ruby on Rails application is not starting,
when SELinux is on. This is the errors reporting on the browser:
The application has exited during startup (i.e. during the evaluation of
config/environment.rb). The error message can be found below. To solve
I have a specific need to use Puppet to Autoscale a few applications I have
deployed on EC2. I'm using Puppet now to manage and create instances and
saw a neat video on this subject. I'm missing the a piece of the puzzle.
I'm assuming I should use Cloudwatch to send my puppetmaster a
I use scalr for this purpose..
http://scalr.net/
I think they did away with the free version of it recently. But if you
ask me what they're asking is well worth it! Autoscales up and down
based on server load. Works with both AWS and rackspace cloud.
-tim
On Sun, May 13, 2012 at 9:28 PM, de
13 matches
Mail list logo
