similar to: Changing NFS mount options to read only (ro) does not affect puppet change

In our environ, there are several services that are deployed via an NFS mount, so that the executables and configs are consistent across the board. Is there any reason why this couldn''t be done with Puppet? For example, each individual system would contain its own /etc/puppet and rc.d and pid files -- but the primary deployment would come from NFS. For that matter, as Enterprise

Our shop is newly adopting puppet. Our number of nodes is growing and my installation method is thus far manual and tedious. This will change when/if we migrate to Puppet Enterprise. My question is what''s a best practice for managing puppet installations on client nodes? Is it possible to separate out the client portion of the install from the server or is that now fully

We have resources that, from time to time, are selected to be removed (unmanaged). When it comes to ssh keys, fstab... this leaves a lot of stuff behind that we don''t want. Is there a simple way to remove the unmanaged data so we can keep the systems clean. Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post

I read somewhere recently about problems with Puppet and Ruby 1.9. I''m wondering if this is still an issue? Thanks. -- 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, send email to puppet-users+unsubscribe@googlegroups.com. For

I''m attempting to deploy puppet via an NFS share. It''s on a local-only network, and it will contain only ruby (gems) and whatever is needed. Seems simple enough, but tonight I am having an issue with this error: # service puppet start Starting puppet: /local/lib/ruby/site_ruby/1.8/rubygems/ custom_require.rb:36:in `gem_original_require'': no such file to load -- openssl

We''ve only recently discovered that puppet can manage mount points using the mount directive; however, a short while back we built an nfs client and server classes without using this resource, and we''ve encountered a problem where puppet seems to hang when the nfs server is unavailable. Using --debug doesn''t seem to specify exactly at which point the run is failing,

Hi @all, after upgrading my puppet server to Puppet 3.0 I got the following error every time a client connect to the server: [ pid=1532 thr=70147393710520 file=utils.rb:176 time=2012-10-08 11:17:56.504 ]: *** Exception NoMethodError in PhusionPassenger::Rack::ApplicationSpawner (undefined method `settings'' for Puppet:Module) (process 1532, thread #<Thread:0x7f98ecf7d370>):

We have perhaps 40 to 50 systems, give or take, that are mostly under Puppet management (not all). After having spent some time doing my own thing with open-source, I''m looking into migrating to PE. One question I have is relative to initial deployment -- if I decide to keep PuppetDB on the same server as Master, can I later migrate that role off onto another host? I

Unfortunately, this is another "I don''t yet know ruby" question, but I''m hoping that someone can help me out. I''ve just tried to write some mount options via puppet and I noticed that, while fstab is written, the managed mounts are not remounted to effect the stated changes. For instance: Original - /home, options: rw Puppet - /home, options: rw,acl

I have a requirement to manage membership to groups in /etc/group. These members do not need to be virtual users. I don''t see a way to do this through virtual users @group. How are others doing this? -- 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

There''s a problem installing puppet on Solaris 10 -- in this situation, we aren''t really doing anything with puppet there. The version we''re using is: ruby 1.8.7 (2011-02-18 patchlevel 334) [i386-solaris2.9] Here''s the first error: # gem update puppet > > Updating installed gems > > Updating puppet > > Building native extensions. This

I have a simple manifest that I''m using to keep unwanted services from running on an array of Linux systems. On my test host, I see these two services repeatedly come up in the puppet.log, even tho they are not running and are chkconfig set to off: service { "cups": enable => false, ensure => stopped, } service {

Hi All, I have running puppet client and server on solaris 10 x86. Now days some of puppet client behaviors is something weird !!! or May be i am missing something... for ex. I created class to add one line in /etc/vfstab . but puppet client did it successfully 1st time ...But .. After few days , i saw there are same line has been added more than 250 times.. [ see same line is added so many

I''ve seen mention of this error in several places, with different causes. So before I posted here, I attempted to resolve this on my own. I corrected the change from puppet:///files to puppet:/// in my manifests *.pp files. No changes were made to the auth.conf file, and I did note in the ChangeLog that: Auth.conf differentiates between names and IPs – There’s a new allow_ip

Hi group, I am managing an NFS mount with puppet. And it does not work, and seriously I really don''t see how this can work out nicely. First I make sure with a file {} class that the directory I want to mount exists. Cause it is used by the webserver it should belong to the wwwrun/www group on the system. No prob. Then I mount the NFS share on the dir. No prob. On the 2nd run of

Hello all. There is some strange thing going on with our OS X clients. We have created a package which is run via SystemStarter. What it does? It parses /etc/fstab and mounts the NFS directories mentioned there. This is needed since we want to have static mounts and the NetInfo-automounter combination does not do static mounts (even with ttl=0 set for the mount, which is supposed to do a

I''m trying to get a new file server managed by puppet from day 1, at least as much as possible. At the moment, though, there''s two issues I''m running into: 1. fstab should have entries for my comically-large RAID, but doesn''t. 2. each puppet run appears to remount the RAID, even when no rules in the manifest change. I suspect the issue may be in parsing

Hey guys, My NFS server has been working really well for a long time now. Both client and server run CentOS 7.2. However when I just had to remount one of my home directories on an NFS client, I'm now getting the error when I run mount -a mount.nfs: an incorrect mount option was specified This is the corresponding line I have in my fstab file on the client:

Hi, Apologies in advance for any breaches of netiquette, I couldn't find any guidelines about submission to this forum but I'd be grateful for your help on something. My /boot filesystem is being remounted shortly after start-up as read-only. I get the following messages... journal_bmap_Ra7a5f568: journal block not found at offset 12 on ide0(3,1) Aborting journal on device ide0(3,1)

I have FreeBSD-6.1 and it appears the default installation has a full complement of Kerberos5. But, /usr/src/kerberos5/README states: This subtree is world-exportable, as it does not contain any cryptographic code. At the time of writing, it did not even contain source code, only Makefiles and headers. Please maintain this "exportable" status quo. Thanks!