On 12 December 2012 11:58, Jakov Sosic wrote:
> On 12/10/2012 04:47 PM, jcbollinger wrote:
>
> There are good, industry-standard approaches to centralized password
>> management. You should really choose among those instead of rolling
>> your own. One of the best-regarded is LDAP, and you coul
The facter should be executed on the server instead on the client.
On Thursday, December 13, 2012 1:29:23 AM UTC+1, Jakov Sosic wrote:
>
> On 11/28/2012 09:46 PM, Romain Gales wrote:
> > there is what i tried:
> >
> > # getpfoleproxyver.rb
> > #
> > Facter.add(:getpfoleproxyver) do
> >
Any light someone can shed sure would be appreciated.
I start with 1 cert -- the master's, where I am running this:
jblaine@ip-10-191-115-140:~$ sudo puppet cert list --all
+ "ip-10-191-115-140.ec2.internal"
(74:8B:7B:EF:41:E6:F9:98:93:15:42:6A:4C:2F:28:CC) (alt names:
"DNS:ip-10-191-115-140.ec
I've done this using gems. I build Ruby from source (I use --prefix but
not sure if it's required) and then use the new gem executable to install
Puppet as gem. Works great for me if you can use gems
BTW, I did this because we use CentOS 5 and I wanted to use Ruby 1.9.x +
Puppet 3.x and had t
On Wednesday, December 12, 2012 6:13:41 PM UTC-5, Ryan Coleman wrote:
>
>
>
>
> On Wed, Dec 12, 2012 at 10:57 AM, Ugo Bellavance
> > wrote:
>
>> Hi,
>>
>> I've built a puppet module myself to manage puppet.conf and I use a
>> subscribe for the service, so it restarts the client whenever puppet.
On 11/28/2012 09:46 PM, Romain Gales wrote:
> there is what i tried:
>
> # getpfoleproxyver.rb
> #
> Facter.add(:getpfoleproxyver) do
> setcode do
> Facter::Util::Resolution.exec('basename `ls
> /softw4pc/Misc/pfoleproxy/pfoleproxy*.txt`')
> end
> end
>
> the fact is working fine, but h
On Wed, Dec 12, 2012 at 10:57 AM, Ugo Bellavance wrote:
> Hi,
>
> I've built a puppet module myself to manage puppet.conf and I use a
> subscribe for the service, so it restarts the client whenever puppet.conf
> changes. I think I shouldn't but I'd like to have a confirmation.
The fact that for
Sorry to be a thread-necromancer, but we're seeing the same problem on a
tiny subset of our hosts. We saw the problem on a CentOS 5 x86_64 host,
then it mysteriously went away, and now we're consistently seeing it on a
CentOS 5 i386 host. As with pattryn, the resource applies successfully when
Looks like a connectivity issue to me..
here are my steps to get puppet installed
install puppet master with passenger
1 - install centos 6.3 minimal
2 - configure IP address and hostname - do not set a fqdn hostname.
vi /etc/sysconfig/network-scripts/ifcfg-eth0
Assign private static IP add
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Alexander!
On Wed, Dec 12, 2012 at 12:54:56PM -0800, Alexander Philipp wrote:
> Are there any good guides out there to using Puppet agents with a
> dedicated, separate ruby install? Our apps are all Ruby based and require
> different versions th
I have 39 RHEL nodes running the puppet agent and intermitently from 1 to 3
nodes will go unresponsive and require intervention to become active again.
I collected the following for one such instance from this morning:
Hung Puppet agent information:
[root@anmvwms3 ~]# rpm -qa | grep puppet
pupp
Yeah, I was starting to think that was the solution.
--
Bret Wortman
http://bretwortman.com/
http://twitter.com/bretwortman
On Wednesday, December 12, 2012 at 5:26 PM, Jakov Sosic wrote:
> On 12/12/2012 10:04 PM, Bret Wortman wrote:
> > Is there an easy way to convert a puppet client into b
On 12/12/2012 10:04 PM, Bret Wortman wrote:
> Is there an easy way to convert a puppet client into being a puppet master?
>
> Here's the scenario. I'm using puppet to configure all my systems, and
> would like it to be able to deploy a new puppet master as well. We have
> systems worldwide so havi
I have a puppet master install which uses puppetdb. I also have puppet
dashboard installed with the inventory service running. I want multiple
puppet masters using a single puppetDB server. Puppetdb is installed on
separate vm.
How can I get the dashboard inventory to use the puppetdb server to
I have a puppet master install which uses puppetdb. I also have puppet
dashboard installed with the inventory service running. I want multiple
puppet masters using a single puppetDB server. Puppetdb is installed on
separate vm.
How can I get the dashboard inventory to use the puppetdb server to
Hi Oli,
On Wed, Dec 12, 2012 at 4:02 AM, vioilly wrote:
> I have installed puppet 3.0.1,
Installed as a gem or native package?
> passenger 3.0.18 and ruby 1.9.3 and have hit
> errors. The error I am hitting is this:
>
> Error message: cannot load such file -- puppet/util/command_line
> Exceptio
Have you considered the vcsrepo module for this?
https://github.com/puppetlabs/puppetlabs-vcsrepo
--
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@googlegroups.com.
To unsubscribe from this group,
Guys,
there must be a 'standard' way of doing this, but I don't seem to be able
to find one:
say there is a utility on the agent which is compiled/installed from a git
repository. When the utility is not there, the standard sequence of
commands is executed
git clone
cd
./configure
make
make
On Wed, Dec 12, 2012 at 12:54 PM, Alexander Philipp
wrote:
> Are there any good guides out there to using Puppet agents with a dedicated,
> separate ruby install? Our apps are all Ruby based and require different
> versions than Puppet. Installing the agent from a package will override our
> rub
Is there an easy way to convert a puppet client into being a puppet master?
Here's the scenario. I'm using puppet to configure all my systems, and
would like it to be able to deploy a new puppet master as well. We have
systems worldwide so having local puppet masters is very desirable for
fault
Are there any good guides out there to using Puppet agents with a
dedicated, separate ruby install? Our apps are all Ruby based and require
different versions than Puppet. Installing the agent from a package will
override our ruby installs.
--
You received this message because you are subscr
On Wed, Dec 12, 2012 at 04:19:17AM -0800, digrouz wrote:
> Hello,
>
> Any updates when the fix will be implemented?
>
>
Hi digrouz,
I am currently assigned to the ticket
http://projects.puppetlabs.com/issues/11675 and have done some work
already. The problem is that I first have to improve the
On 12/12/2012 04:24 PM, Robert Pemberton wrote:
> I have followed many tutorials including the ones provided by puppetlabs
> and I keep seeing the same issues. I began by installing puppet on
> machine: puppet001, and puppet master on machine: puppetMaster. The
> hosts files were then configured so
On 12/12/2012 04:53 PM, Maxym Pendyshchuk wrote:
> Thank you John, it helps; since I played with standalone I have not
> thought about it this way... So that's a good part :)
>
> And seems like I need to store a list of plugins I install on master
> anyway, just in case server with master fail or
MRI Ruby 1.9.3 is in the testing matrix and is fully
supported: http://docs.puppetlabs.com/guides/platforms.html#ruby-versions
There is one issue I'm aware of, with collecting resources:
https://projects.puppetlabs.com/issues/10963
If there are others please file bugs in redmine about them as t
Hi,
I've built a puppet module myself to manage puppet.conf and I use a
subscribe for the service, so it restarts the client whenever puppet.conf
changes. I think I shouldn't but I'd like to have a confirmation. The
fact that foreman sees a failure upon a change in puppet.conf makes me
think
I mentioned at the end of October that we would soon be removing
Fedora 15, Debian Lenny, and Ubuntu Maverick repos from our apt and
yum repos[1]. That time has arrived. The repos will be removed this
Friday (12/14).
[1] -
https://groups.google.com/group/puppet-users/browse_thread/thread/c2b13082
W dniu środa, 12 grudnia 2012 17:39:59 UTC+1 użytkownik Peter De Cleyn
napisał:
>
> I just did the same process of debugging you did (should learn to search
> this list first) and the proposed solution works for me.
>
> Did you file this as a bug yet on the puppet ticketing system (can't find
>
I believe Hiera (or puppet-hiera, not sure) has outstanding issues with
anything other than Ruby 1.8.7. Last time I tried using 1.9.3 with Puppet 3
I had to revert. Please correct me if I'm mistaken.
On Wednesday, December 12, 2012 4:31:51 AM UTC-8, vioilly wrote:
>
> I am going to revert to 1.8
I just did the same process of debugging you did (should learn to search
this list first) and the proposed solution works for me.
Did you file this as a bug yet on the puppet ticketing system (can't find
it there) so I can vote ;-)
Peter
On Mon, Oct 29, 2012 at 7:04 PM, asq wrote:
> ok, i go
- Original Message -
> From: "Jakov Sosic"
> To: puppet-users@googlegroups.com
> Sent: Wednesday, December 5, 2012 11:15:57 PM
> Subject: Re: [Puppet Users] Re: in-module data with hiera
>
> On 12/05/2012 09:45 PM, Stefan Goethals wrote:
> > Not having any problem with osfamily i agree
Thank you John, it helps; since I played with standalone I have not thought
about it this way... So that's a good part :)
And seems like I need to store a list of plugins I install on master
anyway, just in case server with master fail or I need to reinstall it..
Because as I see there are e.g
I have followed a few different tutorials, including the puppetlabs guide
and I keep getting the same issue on VMs and on the servers. I began by
installing puppet on machine: puppet001, and puppet master on machine:
puppetMaster. The hosts files were then configured so that both machines
we
I have followed many tutorials including the ones provided by puppetlabs
and I keep seeing the same issues. I began by installing puppet on machine:
puppet001, and puppet master on machine: puppetMaster. The hosts files were
then configured so that both machines were reachable by the machine
On Tuesday, December 11, 2012 9:23:39 AM UTC-6, Maxym Pendyshchuk wrote:
>
> Dear puppet community!
>
> I am new to puppet, just started to play with.. And I got a question
> (hopefully not too silly): I use a standalone version to play with. I wrote
> a script to install PostgreSQL DB, it uses
On Tuesday, December 11, 2012 11:10:48 AM UTC-6, Schofield wrote:
>
>
> Hiera allows you to lay out your data in two dimensions: data file and
>> key. Whatever selection rules you want to use to choose particular data
>> need to operate in that context. There are at least three ways in which
Jakov, yours suggestion works perfectly.
The only thing missing is that exec will write the only every time puppet
parser goes by.
So I will code a onlyif condition under that exec.
I will poste the final result here.
Thanks!
El martes, 11 de diciembre de 2012 10:18:45 UTC-6, MaTi Villag
I am going to revert to 1.8 for the time being although I was under the
impression ruby 1.9 give performance benefits. If anyone else has
information on whether 1.9.3 is supported, stable and has it working,
please let me know.
On Wednesday, December 12, 2012 12:23:30 PM UTC, Jelle B. wrote:
>
As far as I know there is still a compatibility issue between puppet 3.0
and ruby 1.9.3, I also need this to work due to needing 1.9.3 for
a application targeted to run on the same machine as my puppet environment
but thus far it has been a no go.
Some googling has given me some options to lin
Hello,
Any updates when the fix will be implemented?
On Thursday, October 11, 2012 9:23:42 PM UTC+2, Jeff McCune wrote:
>
> On Oct 11, 2012, at 12:13 PM, Stefan Schulte
> > wrote:
>
> > On Thu, Oct 11, 2012 at 10:47:41AM -0700, Jeff McCune wrote:
> >> Nicholas,
> >>
> >> [...]
> >> We can
I have installed puppet 3.0.1, passenger 3.0.18 and ruby 1.9.3 and have hit
errors. The error I am hitting is this:
Error message:cannot load such file -- puppet/util/command_lineException
class:LoadError
I get this when hitting the puppet server using https://puppetserver:8140
If I use ruby
We use this
cron { "puppet":
ensure => present,
command => $ppt_cmd,
user=> 'root',
hour=> fqdn_rand(6),
minute => fqdn_rand(60)
}
so puppet runs happen 'randomly between midnight and 05:59
Regards,
Stefan - Zipkid - Goethals.
On Wed, Dec 12, 2012 at 6:23 AM,
I reinstalled everything again and manage to get this working. Not sure
what the problem was but this is how I install puppet master with passenger:
install puppet master with passenger
1 - install centos 6.3 minimal
2 - configure IP address and hostname - do not set a fqdn hostname.
vi /etc
43 matches
Mail list logo
