Re: [Puppet Users] puppet client server - couldnt able to verify certificate

I think there is some misunderstood here. First launch the agent, it will generate a certificate for it. Then you should sign it in the master. It seems that you did generate one in the master and sign it, and expected to be received by the client, but the certificate should be generated in the

Re: [Puppet Users] Puppet client 3.2.X fails to install on Windows 7 x64

Post installation you would change it like with other services on windows (services.msc, find the service, open properties and change user/password). On Wed, Jan 29, 2014 at 11:21 AM, Josh D wrote: > > > On Wednesday, January 29, 2014 12:41:06 AM UTC-7, Rob Reynolds wrote: >> >> Josh, >> I'm g

Re: [Puppet Users] Puppet client 3.2.X fails to install on Windows 7 x64

On Wednesday, January 29, 2014 12:41:06 AM UTC-7, Rob Reynolds wrote: > > Josh, > I'm glad we were able to get you going. However it is slightly troubling > to see that the service flips to automatic after running puppet agent. > > Also are you overriding the user the agent installed as to a

Re: [Puppet Users] Puppet client 3.2.X fails to install on Windows 7 x64

Josh, I'm glad we were able to get you going. However it is slightly troubling to see that the service flips to automatic after running puppet agent. Also are you overriding the user the agent installed as to a non-administrative user? On Tue, Jan 28, 2014 at 3:24 PM, Josh D wrote: > > > On M

Re: [Puppet Users] Puppet client 3.2.X fails to install on Windows 7 x64

On Monday, January 27, 2014 4:15:12 PM UTC-7, Rob Reynolds wrote: > > You should be able to take ownership of the directory you cannot delete as > an administrator. Once you have done that you should be able to move > forward with deleting those. I think the prior install attempts might have >

Re: [Puppet Users] Puppet client 3.2.X fails to install on Windows 7 x64

You should be able to take ownership of the directory you cannot delete as an administrator. Once you have done that you should be able to move forward with deleting those. I think the prior install attempts might have botched something and that directory is not removed. On Mon, Jan 27, 2014 at 5

Re: [Puppet Users] Puppet client 3.2.X fails to install on Windows 7 x64

Can you blow away the C:/ProgramData/PuppetLabs directory and try the install again? On Mon, Jan 27, 2014 at 12:01 PM, Josh D wrote: > > > On Monday, January 27, 2014 10:34:36 AM UTC-7, Rob Reynolds wrote: >> >> Josh, >> Can you try something for me? With the install, can you add the >> follow

Re: [Puppet Users] Puppet client 3.2.X fails to install on Windows 7 x64

On Monday, January 27, 2014 10:34:36 AM UTC-7, Rob Reynolds wrote: > > Josh, > Can you try something for me? With the install, can you add the following > to it? > > msiexec /qn /i themsilocation.msi PUPPET_AGENT_STARTUP_MODE=Manual > > And tell me if it installs okay? > > Yep, one step ahead

Re: [Puppet Users] Puppet client 3.2.X fails to install on Windows 7 x64

Josh, Can you try something for me? With the install, can you add the following to it? msiexec /qn /i themsilocation.msi PUPPET_AGENT_STARTUP_MODE=Manual And tell me if it installs okay? Then we'll move onto trying to start the service and see what errors crop up. On Mon, Jan 27, 2014 at 10:

Re: [Puppet Users] Puppet client 3.2.X fails to install on Windows 7 x64

On Friday, January 24, 2014 1:02:59 PM UTC-7, Rob Reynolds wrote: > > The supported way of making it work is to update to at least 3.3.1. > Just tried installing the 3.4.2 client and had the same problem; service fails to start and the installation is rolled back. The log is *slightly* differen

Re: [Puppet Users] Puppet client 3.2.X fails to install on Windows 7 x64

On Fri, Jan 24, 2014 at 11:11 AM, Josh D wrote: > Some of my users are having difficulty installing the Puppet client on > their 64-bit Widows machines. The installation will get get to the point > where everything is installed and it attempts to start the service. The > service fails (see rele

Re: [Puppet Users] puppet client automatic self enrollment to puppet enterprise

There's nothing special. The only thing you'll need is either auto sign or automation on your side to pre-sign certs and deliver them to the VM. On Nov 27, 2013, at 6:30 AM, Martin Knott wrote: > I'm developing templates for vm cloud provisioning and would like to include > puppet client in th

Re: [Puppet Users] puppet client

Took care of this. Messy. Made a company repo. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this disc

Re: [Puppet Users] puppet client connection refused when I use puppet kick form puppet master

I've created auth.conf file in puppet agent and in auth.conf file i've written path / method find, search, save auth yes allow puppetmaster.example.org path /run auth any allow * finally i've restarted the puppet and puppet master then it's working well.. Thank you for supporting me..

Re: [Puppet Users] puppet client connection refused when I use puppet kick form puppet master

Hi, it is working fine,Thank you.. Thanks, Dilip On Thu, Sep 26, 2013 at 3:08 PM, Rahul Khengare wrote: > Have you try adding server parameter as i said in earlier post. > > > > > On Thu, Sep 26, 2013 at 2:44 PM, Dilip Varma wrote: > >> Hi >> >> *puppetmaster#vim /etc/puppet/puppet.conf* >

Re: [Puppet Users] puppet client connection refused when I use puppet kick form puppet master

Have you try adding server parameter as i said in earlier post. On Thu, Sep 26, 2013 at 2:44 PM, Dilip Varma wrote: > Hi > > *puppetmaster#vim /etc/puppet/puppet.conf* > > [main] > logdir=/var/log/puppet > vardir=/var/lib/puppet > ssldir=/var/lib/puppet/ssl > rundir=/var/run/puppet > fact

Re: [Puppet Users] puppet client connection refused when I use puppet kick form puppet master

Hi *puppetmaster#vim /etc/puppet/puppet.conf* [main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter templatedir=$confdir/templates prerun_command=/etc/puppet/etckeeper-commit-pre postrun_command=/etc/puppet/etckeeper-com

Re: [Puppet Users] puppet client

I'm just placing all the rpm's at the el5 and el6 directories at puppetlabs locally, doing a createrepo for each and then using those as the local yum sources. For one-offs that require twiddling/tweaking, I'll deal with them as they come up post-deployment or in-production already. Can't save

RE: [Puppet Users] puppet client

itself with different names depending on what version you are running. Steven From: smcracr...@me.com Subject: Re: [Puppet Users] puppet client Date: Thu, 29 Aug 2013 09:27:52 -0700 To: puppet-users@googlegroups.com I assume it is just the version of puppet client which matches the master'

Re: [Puppet Users] puppet client

I assume it is just the version of puppet client which matches the master's own client and server which is 3.2.1. I.e. puppet-3.2.1-1.el5.noarch.rpm facter as well Any others for an Oracle UEK client? --Stuart RHCE/RHCSA/Oracle DBA/Sun/Mensa On Aug 29, 2013, at 9:17 AM, Stuart Cracr

Re: [Puppet Users] puppet client

Good morning! What are the relevant client rpms and URL for puppet client install to Oracle UEK Linux? I'm sitting at, in a browser: http://yum.puppetlabs.com/el/5Client/products/x86_64 Also, can you speak more to: > Some modules need to get slightly modified to recognize Oracle EL Thanky

RE: [Puppet Users] puppet client

Just use the RedHat packages We use the same packages for RedHat, CentOS, and Oracle EL Some modules need to get slightly modified to recognize Oracle EL Steven > Subject: [Puppet Users] puppet client > From: smcracr...@me.com > Date: Wed, 28 Aug 2013 10:02:48 -0700 > To: puppet-users@googlegr

Re: [Puppet Users] Puppet client not auto updating

Hi, there are agent options in puppet.conf that control how often the agent runs etc. Check whether the agent puts any messages into your syslog. Find the agent process in the system's list of running processes. You could try and run the agent in debug mode to see if anything goes wrong. Stop t

Re: [Puppet Users] Puppet client runs outside of office hours

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,

Re: [Puppet Users] Puppet client runs outside of office hours

Cron would be your best bet. You can manage cron jobs via puppet. kdo wrote: >anyone have any smart ideas around scheduling puppet client runs during >specific times ? such as outside of office hours ? > > >any options that can be set in the puppet.conf for example ? > >-- >You received this m

Re: [Puppet Users] Puppet client won't autostart

On 11/13/2012 03:46 PM, Darin Perusich wrote: This is systemd weirdness. I've run into this error before on SuSE with other init scripts and the fix was to reboot the machine. Then you won't get the "Loaded: error (Reason: No such file or directory)" anymore. :-/ A little offtopic but I'm not

Re: [Puppet Users] Puppet client won't autostart

Just to finish this one up, I had the service name wrong. # puppet resource service puppetagent enable=yes ensure=running Works just fine. Bret -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https:/

Re: [Puppet Users] Puppet client won't autostart

On Tuesday, November 13, 2012 12:03:36 PM UTC-5, Michael Stanhke wrote: > > On Tue, Nov 13, 2012 at 8:31 AM, Bret Wortman > > > wrote: > > It is kind of funny that we're talking about using puppet's tricks for > > working around bad start scripts for puppet's own software > > > > > > On

Re: [Puppet Users] Puppet client won't autostart

On Tue, Nov 13, 2012 at 8:31 AM, Bret Wortman wrote: > It is kind of funny that we're talking about using puppet's tricks for > working around bad start scripts for puppet's own software > > > On Tuesday, November 13, 2012 9:58:57 AM UTC-5, jcbollinger wrote: >> >> >> >> On Tuesday, November 1

Re: [Puppet Users] Puppet client won't autostart

It is kind of funny that we're talking about using puppet's tricks for working around bad start scripts for puppet's own software On Tuesday, November 13, 2012 9:58:57 AM UTC-5, jcbollinger wrote: > > > > On Tuesday, November 13, 2012 7:40:08 AM UTC-6, Martin Alfke wrote: >> >> Hi Bret, >> >

Re: [Puppet Users] Puppet client won't autostart

This problem has continued through multiple reboots across multiple systems. On Tuesday, November 13, 2012 9:47:03 AM UTC-5, Darin Perusich wrote: > > This is systemd weirdness. I've run into this error before on SuSE > with other init scripts and the fix was to reboot the machine. Then > you wo

Re: [Puppet Users] Puppet client won't autostart

On Tuesday, November 13, 2012 7:40:08 AM UTC-6, Martin Alfke wrote: > > Hi Bret, > > On 13.11.2012, at 13:18, Bret Wortman wrote: > > I'm getting this problem on all the puppet client's I've been setting up > and it's got me both scratching my head (because I'm not seeing anything > obvious in

Re: [Puppet Users] Puppet client won't autostart

This is systemd weirdness. I've run into this error before on SuSE with other init scripts and the fix was to reboot the machine. Then you won't get the "Loaded: error (Reason: No such file or directory)" anymore. -- Later, Darin On Tue, Nov 13, 2012 at 9:29 AM, Bret Wortman wrote: > It does no

Re: [Puppet Users] Puppet client won't autostart

It does not (and this is odd since I'm using F17): # service puppet status Redirecting to /bin/systemctl status puppet.service puppet.service Loaded: error (Reason: No such file or directory) Active: inactive (dead) and yet ps still shows it running. But with your help, this a

Re: [Puppet Users] Puppet client won't autostart

Hi Bret, On 13.11.2012, at 13:18, Bret Wortman wrote: > I'm getting this problem on all the puppet client's I've been setting up and > it's got me both scratching my head (because I'm not seeing anything obvious > in any system logs) and pausing in my rollout until I get it solved: > > # puppe

Re: [Puppet Users] Puppet client not listening on port 8139

Hi, On Oct 10, 2012, at 6:58 PM, Pondy wrote: > Hi Gabrielle, > > Yes, I have listen = true and I cannot see that port open with netstat... I > am truly confused, theres not much showing in the logs either. > > Thanks! > > > On Thursday, 11 October 2012 09:46:31 UTC+10, Lelutin wrote: >> >

Re: [Puppet Users] Puppet client not listening on port 8139

Hi Gabrielle, Yes, I have listen = true and I cannot see that port open with netstat... I am truly confused, theres not much showing in the logs either. Thanks! On Thursday, 11 October 2012 09:46:31 UTC+10, Lelutin wrote: > > On 2012-10-10 18:37, Pondy wrote: > > Hi All, thanks for your input

Re: [Puppet Users] Puppet client not listening on port 8139

On 2012-10-10 18:37, Pondy wrote: > Hi All, thanks for your input. So, I am talking about the puppet client. ah oops sorry, I'm not used to dealing with this option :\ my bad > The puppet master server and all other clients seem to be working ok. I > am also unable to telnet locally to port 8139

Re: [Puppet Users] Puppet client not listening on port 8139

Hi All, thanks for your input. So, I am talking about the puppet client. The puppet master server and all other clients seem to be working ok. I am also unable to telnet locally to port 8139 or 8140. On Thursday, 11 October 2012 04:30:21 UTC+10, Jo wrote: > > > On Oct 9, 2012, at 11:35 PM, Pondy

Re: [Puppet Users] Puppet client not listening on port 8139

On Oct 9, 2012, at 11:35 PM, Pondy wrote: > Please help, I have built a new server and installed puppet (2.6.17) running > on RHEL 6.3. It seems that it is not listening on port 8139. ... > It seems as though the puppet is running: > 4074 ?Ss 0:00 /usr/bin/ruby /usr/sbin/puppetd > -

Re: [Puppet Users] Puppet client not listening on port 8139

On 2012-10-10 02:35, Pondy wrote: > Hi everyone, > > Please help, I have built a new server and installed puppet (2.6.17) > running on RHEL 6.3. It seems that it is not listening on port 8139. By default, puppet listens on 8140, not 8139. And your configuration doesn't seem to be specifying an al

RE: [Puppet Users] puppet client could not request certificate: Error 500 on SERVER

Subject: Re: [Puppet Users] puppet client could not request certificate: Error 500 on SERVER You should spend some time and determine how and why that is happening. I can assure you that it's not normal, so this is something specific to some custom code on your site. On Aug 19, 2012, at 10:

Re: [Puppet Users] puppet client could not request certificate: Error 500 on SERVER

You should spend some time and determine how and why that is happening. I can assure you that it's not normal, so this is something specific to some custom code on your site. On Aug 19, 2012, at 10:56 AM, Stuart Cracraft wrote: > I am seriously thinking of putting those recursive chown's in root

Re: [Puppet Users] puppet client environment is being ignored from foreman settings

Yaniv, I was asking if you happen to have an environment defined on your agent in puppet.conf. Anyhow, we can handle this over on foreman-users :) -Sam On Thu, Aug 16, 2012 at 1:01 PM, Yaniv Fine wrote: > Why do i have to define environment in puppet.conf on the agent . Isnt > defining the hos

Re: [Puppet Users] puppet client environment is being ignored from foreman settings

Why do i have to define environment in puppet.conf on the agent . Isnt defining the host in a group on foreman good enugh ? .in general there could be a conflict . Btw when i configure env in puppet.conf it does work like expected but it ignored the setting related to env .in foreman On Aug 16, 201

Re: [Puppet Users] puppet client environment is being ignored from foreman settings

Hi Yaniv, Do you have the environment defined in puppet.conf on the agent and use Foreman as an ENC? If so, you're probably seeing http://projects.puppetlabs.com/issues/3910. Some users are getting around this bug by adding functionality to the ENC script that validates the environment defined in

Re: [Puppet Users] Puppet client port to be open

On Tue, Nov 29, 2011 at 6:19 PM, Namrata wrote: > Just a quick question. In order for puppet run to execute successfully > on puppet client (ubuntu 10.04), the port 8139 on puppet client should > be open and listening correct? Do we also require that port 8140 be > open and running on puppet clien

Re: [Puppet Users] Puppet client starting problem !!

Hi, On 10/31/2011 07:47 AM, Swati Longia wrote: > I don't even have normal linux commands like useradd or groupadd in this > OS. is this a requirement? Because: > /err: Could not create resources for managing Puppet's files and > directories in sections [:main, :agent, :ssl]: Could not find a de

Re: [Puppet Users] Puppet client dying without errors

Thanks for the help! As per RedHat release note, the updates on the package is promising. Updated nss_ldap on couple hosts to see whether it fixes the problem or not. -Basil On Thu, Sep 22, 2011 at 7:08 PM, Iain Sutton wrote: > This looks much like the error we had, which was: > > ruby: ../../

Re: [Puppet Users] Puppet client dying without errors

This looks much like the error we had, which was: ruby: ../../../libraries/libldap/result.c:113: ldap_result: Assertion `ld != ((void *)0)' failed. Under CentOS/RHEL, you need to upgrade the version of nss_ldap to 253-37.el5_6.1 (or later) Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=

Re: [Puppet Users] Puppet client dying without errors

>From the debug mode logs, ruby was having trouble with LDAP. Debug Error message: ruby: ../../../libraries/libldap/error.c:273: ldap_parse_result: Assertion `r != ((void *)0)' failed Is there way I can exclude puppet not to look up LDAP to avoid this situation? I did try adding following entry in

Re: [Puppet Users] Puppet client dying without errors

On Thu, Sep 01, 2011 at 08:31:55PM -0400, Basil Baby wrote: >Few of my puppet clients (puppet 0.24.8,� ruby 1.8.5, facter 1.5.2) are >dying with out any error messages on on syslog.� I cannot see much system >resource usage on these nodes. > >What is the best way to troubleshoot th

Re: [Puppet Users] Puppet client do-overs

On Jun 30, 2011, at 8:21 PM, Nathan Clemons wrote: > What problem do you have with puppetstoreconfigclean.rb? The problem I > usually have is that I forget it has to be run as root on the puppetmaster, I > keep thinking I need to run it on the client machine. The other issue I fixed... PEB

Re: [Puppet Users] Puppet client do-overs

What problem do you have with puppetstoreconfigclean.rb? The problem I usually have is that I forget it has to be run as root on the puppetmaster, I keep thinking I need to run it on the client machine. -- Nathan Clemons http://www.livemocha.com The worlds largest online language learning communit

Re: [Puppet Users] Puppet client 'certificate verify failed'

On 04/13/2011 05:11 AM, Martin Orda wrote: > Hi, > > I've looked in the archives and elsewhere but couldn't find a solution > to the issue I'm having. I'm running puppet with an external CA that I > manage myself (ca=false for puppetmasterd) puppetmasterd is behind > nginx reverse proxy. On the cl

Re: [Puppet Users] puppet client certs & dns

On Mon, Apr 4, 2011 at 9:50 AM, Felix Frank wrote: > certification can be painful at times, but I don't see the real problem > you had with requesting a signature on a badly named cert? > > You can always just revoke it on the master and have your client issue a > new CSR. Hello, Thanks for your

Re: [Puppet Users] puppet client certs & dns

On 04/01/2011 08:23 PM, FRLinux wrote: > Hello, > > First off, forgive me if that has been discussed before. > > Has there been any thought given to using dns records queried from the > IP of a host where puppet is installed? Reason I'm asking is we had an > issue in which our fqdn got screwed up

Re: [Puppet Users] puppet client could not request certificate: Error 500 on SERVER

On Wed, Mar 30, 2011 at 3:00 PM, hyzhang wrote: > Hi, I am new to puppet. > > I have puppet server set up with passenger. But when I start puppetd > from client, I see following error in the syslog file: > Mar 30 13:52:03 puppetclient1 puppet-agent[29732]: Could not request > certificate: Error 5

Re: [Puppet Users] Puppet client log events, centralized?

On Wed, Oct 13, 2010 at 04:09:34PM -0700, Forrie wrote: > I've noticed that events for puppet client are logged locally (I'm > just starting out with puppet). Is there a way to have these events > sent to a central parser so they might be easily parsed/sorted/acted- > upon? > > I probably missed

Re: [Puppet Users] Puppet client log events, centralized?

Syslog server On Wed, Oct 13, 2010 at 4:09 PM, Forrie wrote: > I've noticed that events for puppet client are logged locally (I'm > just starting out with puppet). Is there a way to have these events > sent to a central parser so they might be easily parsed/sorted/acted- > upon? > > I probably

Re: [Puppet Users] Puppet Client using wrong environment.

Finally found the issue I never looked into the /etc/puppet directory(my bad), there was the issue, a strange one although but here is what happened, in there were two files(wish I knew why there were that second if we use puppet 0.24.8): puppet.conf puppetd.conf Same content, nothing different,

Re: [Puppet Users] Puppet Client using wrong environment.

When no environment is defined it uses production, per my notes: environments = production,testing,development manifest = /opt/puppet/production/site.pp modulepath = /opt/puppet/production/modules This is part of [main]. On Wed, Mar 17, 2010 at 5:00 PM, Rob McBroom wrote: > How is the

Re: [Puppet Users] Puppet Client using wrong environment.

How is the environment determined when you don’t specify one? On my systems, it seems that the `--environment` option is completely ignored. I imagine this is because the external information (from LDAP in my case) always takes precedence. -- Rob McBroom -- You recei