Re: [Puppet Users] puppet can't get the right service status from centos5.3

2014-08-15 Thread li jackie
thank you David~ I changed some config,and it work fine~ service { 'puppet': ensure = 'running', enable = 'false', } changed service { 'puppet': ensure = 'running', enable = 'false', hasstatus = 'false', status = '/etc/init.d/puppet status' } as you said . if the service not

[Puppet Users] Restart ssh daemon when sshdconfig is modified

2014-08-15 Thread Vikas Kumar
Dear All, I am trying to restart SSH daemon whenever /etc/ssh/sshd_config is modified. This is my class, it modifies the file but does not restarts the daemon. I have tried to use both *notify* and *subscribe* in vain. class ssh ( $ssh_service = hiera(sshservicename) ) { package {

[Puppet Users] Re: Remove java from path - Windows

2014-08-15 Thread badgerious
Hi Jeff, You can reference other variables directly from within the PATH variable, like so: PATH=C:\other\stuff;%JAVA_HOME%;C:\more\other\stuff That way you can maintain just the JAVA_HOME variable and path will be updated automatically when it changes. Eric On Thursday, August 14, 2014

Re: [Puppet Users] Restart ssh daemon when sshdconfig is modified

2014-08-15 Thread Jeffrey Watts
On Fri, Aug 15, 2014 at 7:31 AM, Vikas Kumar vikas...@gmail.com wrote: Dear All, I am trying to restart SSH daemon whenever /etc/ssh/sshd_config is modified. This is my class, it modifies the file but does not restarts the daemon. I have tried to use both *notify* and *subscribe* in vain.

[Puppet Users] Re: How can managed directory be updated after an rpm is upgraded?

2014-08-15 Thread jcbollinger
On Thursday, August 14, 2014 11:44:02 AM UTC-5, Tim Arnold wrote: I want to 'manage' the files in a certain directory ONLY if the rpm is updated. Why? If it is not only acceptable but *desired* that these files be managed during runs when the RPM is updated, then why is it not

Re: [Puppet Users] Restart ssh daemon when sshdconfig is modified

2014-08-15 Thread Christopher Wood
Could also go for: File[/etc/ssh/sshd_config] - Augeas[my-ssh] File[/etc/ssh/sshd_config] ~ Service[$ssh_service] Augeas[my-ssh] ~ Service[$ssh_service] A bit wordier but it covers what happens when the file is changed but augeas has nothing to change. Vikas, perhaps you might use a template

[Puppet Users] Support for multiple PHP projects on one server along with the ability to use Vagrant

2014-08-15 Thread Szerémi Attila
Say I want to host 20 php projects on one digital ocean server. How would I go about using PuPHPet and setting puppet scripts up in general such that I could host all 20 projects on the same server, residing in e.g. /var/www/project1, /var/www/project2 etc. but each project would be able to

[Puppet Users] Failed to connect to PuppetDB. Check settings (hostname does not match the server certificate) but what settings?

2014-08-15 Thread Kim Nielsen
Hi all, I needed to change the hostname for our puppet enterprise solutions so I did. I also recreated all SSL certificates with cut’n’paste from this guide: https://docs.puppetlabs.com/pe/latest/trouble_regenerate_certs_monolithic.html and replaced all of the old name references to the

[Puppet Users] exported resources with puppet apply and deprecation of activerecord

2014-08-15 Thread Peter Meier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, So as activerecord based storeconfigs are getting deprecated, what options to use modules with exporting collecting resources do we have? The main problem that without a PuppetDB you are currently not able to run puppet apply without

Re: [Puppet Users] Failed to connect to PuppetDB. Check settings (hostname does not match the server certificate) but what settings?

2014-08-15 Thread José Luis Ledesma
This error means that the hostname in puppetdb.conf doesn't match the puppetdb certificate hostname El 15/08/2014 16:17, Kim Nielsen swipemeslo...@gmail.com escribió: Hi all, I needed to change the hostname for our puppet enterprise solutions so I did. I also recreated all SSL certificates

Re: [Puppet Users] Failed to connect to PuppetDB. Check settings (hostname does not match the server certificate) but what settings?

2014-08-15 Thread Kim Nielsen
Hi, I wish this was tru but my puppetdb.conf looks like this: [main] port = 8081 certname = puppetwin.xxx.dk server = puppetwin.xxx.dk and connecting to the puppetdb gives this certificate: openssl s_client -connect xxx.xxx.xxx.xxx:8081 CONNECTED(0003) depth=0 CN = puppetwin.xxx.dk verify

Re: [Puppet Users] Failed to connect to PuppetDB. Check settings (hostname does not match the server certificate) but what settings?

2014-08-15 Thread Juan Sierra Pons
Hi If you installed puppetdb using puppetlabs-puppetdb. Usually removing router.yaml and puppetdb.conf on /etc/puppet folder and running Puppet again fixes it Disclaimer: I am not in front of the computer so I am not sure if the files' names are misspelled. Also make a backup just in case. Hope

Re: [Puppet Users] Failed to connect to PuppetDB. Check settings (hostname does not match the server certificate) but what settings?

2014-08-15 Thread Kim Nielsen
Hi, No I just changed hostname on the machine and replaced all names in /etc/puppetlabs/ and generated new certificates. I don't have a router.yaml anywhere on my host /Kim On Friday, August 15, 2014 7:36:34 PM UTC+2, Juan Sierra Pons wrote: Hi If you installed puppetdb using

Re: [Puppet Users] Managing multiple hosts in a single service

2014-08-15 Thread Andrew Melo
Thanks a lot, everyone! On Thu, Aug 14, 2014 at 6:22 PM, Betsy Schwartz betsy.schwa...@gmail.com wrote: The Puppet Practitioner course talks about this. Look at exported resources and exported resource collectors Each node exports the resource then can collect the set ( probably , by doubt

Re: [Puppet Users] Chocolatey repos

2014-08-15 Thread Rob Reynolds
On Wed, Aug 13, 2014 at 11:44 AM, huhm4n oj.man...@gmail.com wrote: Can I create my local repo to fetch the packages from instead of pulling it from the web using chocolatey? Discussion happening at https://groups.google.com/forum/#!topic/chocolatey/pKL52I0jzgg -- You received this

[Puppet Users] Invalid Option --port=8140

2014-08-15 Thread Mark Gardner
I'm upgrading puppet from 3.3.1 to 3.6.2 on Suse Linux Enterprise 11 SP3 The puppet service wont start with this error collected error from /var/log/puppet/puppet.conf Fri Aug 15 13:12:35 -0500 2014 Puppet (err): Could not parse application options: invalid option: --port=8140 It looks to me