John,
Just wanted to drop a quick note to say thanks for responding and for the
great variety of ideas to try to troubleshoot. At the end of the day, the
environment was so hosed that I eventually just rebuilt the puppetmaster
from scratch with a setup script to ensure lack of errors in either
sy
On Thursday, February 20, 2014 5:03:53 PM UTC-6, Christopher Opena wrote:
>
> Howdy folks,
>
> I've got some weird behavior from one of my puppet clients (actually the
> client running on the puppet master), where running the agent somehow
> destroys either the yum cache or the rpm db. Directl
On Friday, November 15, 2013 11:40:12 PM UTC-6, Stuart Cracraft wrote:
>
>
> Looks like you haven't worked in a hosting firm with strenuous security
> yet.
>
> Having paths open to the Internet are a big no-no.
>
>
Local repos are a good choice, even for sites with fewer constraints. I
certai
Looks like you haven't worked in a hosting firm with strenuous security yet.
Having paths open to the Internet are a big no-no.
On Nov 15, 2013, at 8:49 PM, Stuart Cracraft wrote:
> Notes with ++.
>
> On Nov 15, 2013, at 6:02 PM, liu.cy wrote:
>
>> you are using oracle linux?
>
> ++ I do
anyway, yum is the best choice, you should get over your various reasons.
On Saturday, November 16, 2013 12:49:42 PM UTC+8, Stuart Cracraft wrote:
>
> Notes with ++.
>
> On Nov 15, 2013, at 6:02 PM, liu.cy >
> wrote:
>
> you are using oracle linux?
>
>
> ++ I do.
>
>
> http://yum.puppetlabs.com/
Notes with ++.
On Nov 15, 2013, at 6:02 PM, liu.cy wrote:
> you are using oracle linux?
++ I do.
>
> http://yum.puppetlabs.com/el/5/products/x86_64/ will be fine
++ It is. I ended up downloading relevant rpm's and creating a local repo. Good
stuff!
++ The test client now has an installed
you are using oracle linux?
http://yum.puppetlabs.com/el/5/products/x86_64/ will be fine
On Saturday, November 16, 2013 6:45:47 AM UTC+8, Stuart Cracraft wrote:
>
>
> I have a box with this uname -a output:
>
> Linux myhost 2.6.32-300.11.1.el5uek #1 SMP Wed Mar 7 09:55:50 EST 2012
> x86_64
Check the parameter server = puppetmaster.example.org under the [main] section
in puppet.conf file.
Otherwise puppet client trying to connect default host puppet when puppet
agent being kick.
Thanks and Regards,
Rahul Khengare,
NTT DATA OSS Center, Pune, India.
On Sunday, January 15, 2012 7:
HI Dilip,
Can you provide the puppet,conf file.
Check the parameter server = puppetmaster.example.org under the [main] section
in puppet.conf file. Otherwise puppet client trying to connect
default host puppet when puppet agent being kick.
Thanks and Regards,
Rahul Khengare
On Thursday, S
Hi Dilip,
Have you added listen = true in [main] section of puppet.conf?
And have you allowd access to runpath in auth.conf?
Please refer http://docs.puppetlabs.com/man/kick.html.
It may help you to solve this error.
Thanks & Regards,
Sneha More,
NTT DATA GTS, OSS Center, India (Pune).
On Th
Hi Martijn,
Thanks for your comments. I am using puppet agent --test now that I have
upgraded to ver3 as it was not available previously.
The service appears to be working better now and am having more luck with
things applying.
Thanks all for your help.
Regards
Sy
On Monday, 8 April 2013 1
On Friday, April 5, 2013 5:48:10 PM UTC-5, Sy Doveton wrote:
>
> Hi,
>
> I am new to puppet and am experimenting with some basic commands. I have a
> puppetmaster server and a couple or servers with puppet client. All servers
> are running ubuntu.
>
> I have set up the link between the master a
Hi Sy,
The Puppet agent will usually log to syslog, both in case of errors or
succes, so check in /var/log/syslog (on Ubuntu) for any messages. By
default, the agent runs every half hour so I'd expect to see some entries
in the log every half hour.
Make sure the puppet agent service runs as ro
Hi Drew,
Thanks for your message.
I have gone through my test environment and have installed the PPA and
upgraded to 3.1.1 on the master and clients.
I will test how things work with the service, failing that I will try the
cron route. So to confirm on the puppet clients you would stop the ser
Sy,
Welcome to Puppet. Hopefully we can help you get going so you can
experiment further.
First, what version of Puppet are you running? I'm guessing by your
commands that it's definitely prior to version 3. I recommend updating to
Puppet 3 before going further, especially since you're just
> Can http://rvm.io build a "local" ruby for you on that system?
Hello David, apologies for the belated response on this .. But no, rvm is
not an option because it has a bash shell version dependency that dapper
(or any of the nearby distros, up to feisty) cannot satisfy .. so, it does
seem
On 04.02.2013 12:55, Chux wrote:
Nick,
This is not looking promising .. dapper is on ruby 1.8.4, and the
nearest ubuntu version that could get me up to ruby 1.8.5 is feisty ..
So, I modified apt preferences, to try and pull in the right versions of
ruby from feisty (had to do the same for puppe
Nick,
This is not looking promising .. dapper is on ruby 1.8.4, and the nearest
ubuntu version that could get me up to ruby 1.8.5 is feisty ..
So, I modified apt preferences, to try and pull in the right versions of
ruby from feisty (had to do the same for puppet and facter) .. However, the
Million thanks, Nick .. That is enough pointers for me to consider .. Will
come back with some feedback on what has worked (if any).
rgds.
On Saturday, 2 February 2013 01:51:03 UTC, Nick Fagerlund wrote:
>
> You're in a gnarly situation. DistroWatch is telling me that you're
> probably running
You're in a gnarly situation. DistroWatch is telling me that you're
probably running Ruby 1.8.4, which, damn.
I think your best bet is:
* Find or build a newer Ruby, preferably 1.8.7.
* Either install Puppet from source
(http://docs.puppetlabs.com/guides/from_source.html) or force apt to
ins
Resolved the stupid issue...
I just did not read the error message properly. It is complaining
"Could not find class hosts"..
Thanks,
Rajeev
On Jan 16, 11:32 am, DreamBig wrote:
> Hi ,
>
> Need this help desperately
>
> 1) Cleaned certificates from master
> 2) Cleaned ssl dir in agent
> 3) On
Run puppet agent via cron. Add in a random delay so that all the clients
don't hit the server at the same time. I use the following script and set
to run every 30 minutes:
#!/bin/bash
# Grab a random value between 0-1740 (29 minutes).
value=$RANDOM
while [ $value -gt 1740 ] ; do
value=$RANDOM
Hi mate,
I use Puppet 2.6 but in this situation would run:
>From puppetmaster
puppetca --revoke agent.foo.com
puppetcat --clean agent.foo.com
>From agent
rm -rf /var/lib/puppet/ssl
puppetd --waitforcert 30 --server puppetmaster -v
>From puppetmaster
puppetca --sign agent.foo.com
On Th
I am seriously thinking of putting those recursive chown's in root crontab on
puppet masters and puppet agents for /etc/puppet* and
/var/lib/puppet*
I shouldn't have to do this but have
seen cases of ownership reversion.
--Stuart
Via Apple iPhone 4S on the AT&T Wireless Network
On Aug 13,
For the people still looking for an answer:
chown -R puppet:puppet /var/lib/puppet/reports
Op woensdag 30 maart 2011 21:02:43 UTC+2 schreef hyzhang het volgende:
>
> Thank. I am pasting the entire message here:
>
> Mar 30 14:01:04 puppetclient1 puppet-agent[28571]: Could not request
> certificat
On Nov 29, 4:00 pm, Namrata wrote:
> Thanks everyone for the clarifications to a puppet newbie aka me :)
> It is much clear now.
>
> It is just that one of my puppet client is a cloud server on Rackspace
> and while it can connect to the puppetmaster and apply basic
> configurations(like write a
Oh dear ... Yes.
On 30/11/2011, at 7:57, Craig White wrote:
> I hope that you were having a dyslexic moment and really meant to say 8139
> instead of 1839 because then I would have to wonder how it's been working for
> me the past few months.
>
> Craig
>
> On Nov 29, 2011, at 1:18 PM, Denmat
Thanks everyone for the clarifications to a puppet newbie aka me :)
It is much clear now.
It is just that one of my puppet client is a cloud server on Rackspace
and while it can connect to the puppetmaster and apply basic
configurations(like write a file) from puppetmaster manifest but
unable conf
I hope that you were having a dyslexic moment and really meant to say 8139
instead of 1839 because then I would have to wonder how it's been working for
me the past few months.
Craig
On Nov 29, 2011, at 1:18 PM, Denmat wrote:
> Hi,
>
> Just further clarifying what Nan has already said, the cl
On Nov 29, 12:29 pm, Namrata wrote:
> Thanks Nan.
>
> So, my puppetmaster should be able to install modules on puppet client
> if the port 8139 is open?
In short, you don't even need 8139 open.
In long:
The puppetmaster does not under any circumstances install modules on
the client, regardless
Hi,
Just further clarifying what Nan has already said, the client initiates the
connection to the master when it polls in. The master listens on 8140 for those
connections. This is all you need for puppet to compile and apply the manifest
on the client.
If you use the 'puppet kick' command (wh
Thanks Nan.
So, my puppetmaster should be able to install modules on puppet client
if the port 8139 is open?
On Nov 29, 10:24 am, Nan Liu wrote:
> 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 (u
On Oct 31, 1:47 am, Swati Longia wrote:
> Hi,
>
> I have installed puppet 2.7.5 from tar on open suse 10.1. My ruby version
> is 1.8.5 and facter version is 1.6.2. The opensuse OS is pretty
> minimalistic.
> I don't even have normal linux commands like useradd or groupadd in this OS.
Surely th
Hello Marius,
Thank you very much indeed for your prompt reply! It seems that I was
under the impression that autosigning had been turned on on the puppet
server. I see now that I was mistaken.
Best regards, and be well good sir!
tim
On Thu, May 12, 2011 at 4:41 PM, Saurval wrote:
> Hi Tim,
>
Hi Tim,
Perhaps I am missing something in your output. There may be some
actions implied that you took but where not shown. So excuse me if I
am misunderstanding something.
Did you take any actions on the server side while you were running
'puppetd -t --waitforcert 15 --server puppet.example.ne
No that's not normal - you shouldn't have to manually start the start the
master like that.. it sounds like your setup is goofy - can you provide logs
from the actual server? The portion you provided us is simple the result of
the web server saying there is no backend / the backend crashed / the
Thank. I am pasting the entire message here:
Mar 30 14:01:04 puppetclient1 puppet-agent[28571]: Could not request
certificate: Error 500 on SERVER: http://www.w3.org/TR/html4/strict.dtd";>
Ruby (Rack) application could not be started
solved...
Need to remove the .yaml files in /var/puppet/yaml/node
and /var/puppet/yaml/facts (or where ever you may have these files,
search for them).
Then the client will run and the files will get rebuilt.
On Feb 1, 11:16 am, Jason Amato wrote:
> Any ideas?
>
> Getting this error below from
Le lundi 16 novembre 2009 à 13:07 -0500, Cory mckee a écrit :
> I was wondering if I could get help.
>
> on client
>
>
> [r...@linux ~]# puppetd --test --verbose
> info: Caching catalog at /var/lib/puppet/localconfig.yaml
> notice: Starting catalog run
> err: //Node[basenode]/motd/Package[motd]/
Hi Cory,
Running the puppet client with --debug will show the underlying system calls
that are failing. It looks like the package manager cannot find any packages
called motd (I dont think there is a package called motd, this is a login
function).
Also, a tip. You can use the "puppet" command to
I didnt find docs either, but hopefully this simple example which I use in
Foreman can give you all the info you need :)
http://theforeman.org/repositories/entry/foreman/extras/puppet/reports/foreman.rb
Ohad
On Fri, Sep 25, 2009 at 5:54 PM, Tim Uckun wrote:
>
> > you can also parse the client
> you can also parse the client log files, but I usually get a notification
> (or see it in Foreman) when a client did not send a report in the last XX
> minutes, than I can look into the client and see whats wrong.
I was thinking I would might like to write my own report "engine" but
I can't se
Assuming that the client breaks (e.g. stops its run), the best way you could
indicate that something is wrong, is by seeing that the client did not send
a report.
you can also parse the client log files, but I usually get a notification
(or see it in Foreman) when a client did not send a report in
Thanks! In my case it is:
Package { provider => "aptrpm" }
$ ls -l /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/*.rb
-rw-r--r-- 1 root root 4309 Mar 23 22:48 appdmg.rb
-rw-r--r-- 1 root root 1605 Mar 23 22:48 apple.rb
-rw-r--r-- 1 root root 881 Mar 23 22:48 aptitude.rb
-rw-r--r-- 1 root r
On Thu, Jun 18, 2009 at 2:26 AM, hyde wrote:
>
> I have puppet client on centos5, but we don't use yum to install
> packages, we use apt-rpm to install packages, so it would be 'apt-get
> install packagename' instead of 'yum install packagename'.
>
> How can I customize puppet for the above?
fo
On Thu, Jun 11, 2009 at 10:09 PM, Asif Iqbal wrote:
> On Thu, Jun 11, 2009 at 7:01 PM, Luke Kanies wrote:
>>
>> On Jun 11, 2009, at 5:58 PM, Asif Iqbal wrote:
>>
>>>
>>> On Thu, Jun 11, 2009 at 6:47 PM, Luke Kanies wrote:
On Jun 11, 2009, at 11:36 AM, Asif Iqbal wrote:
>
> O
On Thu, Jun 11, 2009 at 7:01 PM, Luke Kanies wrote:
>
> On Jun 11, 2009, at 5:58 PM, Asif Iqbal wrote:
>
>>
>> On Thu, Jun 11, 2009 at 6:47 PM, Luke Kanies wrote:
>>>
>>> On Jun 11, 2009, at 11:36 AM, Asif Iqbal wrote:
>>>
On Thu, Jun 11, 2009 at 11:58 AM, Luke Kanies
wrote:
>
>
On Jun 11, 2009, at 5:58 PM, Asif Iqbal wrote:
>
> On Thu, Jun 11, 2009 at 6:47 PM, Luke Kanies wrote:
>>
>> On Jun 11, 2009, at 11:36 AM, Asif Iqbal wrote:
>>
>>>
>>> On Thu, Jun 11, 2009 at 11:58 AM, Luke Kanies
>>> wrote:
On Jun 10, 2009, at 12:50 PM, Asif Iqbal wrote:
> I
On Thu, Jun 11, 2009 at 6:47 PM, Luke Kanies wrote:
>
> On Jun 11, 2009, at 11:36 AM, Asif Iqbal wrote:
>
>>
>> On Thu, Jun 11, 2009 at 11:58 AM, Luke Kanies wrote:
>>>
>>> On Jun 10, 2009, at 12:50 PM, Asif Iqbal wrote:
>>>
In my puppet client I have
puppet.conf defined puppet server as
On Jun 11, 2009, at 11:36 AM, Asif Iqbal wrote:
>
> On Thu, Jun 11, 2009 at 11:58 AM, Luke Kanies wrote:
>>
>> On Jun 10, 2009, at 12:50 PM, Asif Iqbal wrote:
>>
>>> In my puppet client I have
>>> puppet.conf defined puppet server as mypuppet
>>>
>>> server = mypuppet.example.net
>>>
>>> Not sure
On Thu, Jun 11, 2009 at 11:58 AM, Luke Kanies wrote:
>
> On Jun 10, 2009, at 12:50 PM, Asif Iqbal wrote:
>
>> In my puppet client I have
>> puppet.conf defined puppet server as mypuppet
>>
>> server = mypuppet.example.net
>>
>> Not sure why the puppet client puppet-test is still sending these
>> n
On Jun 10, 2009, at 12:50 PM, Asif Iqbal wrote:
> In my puppet client I have
> puppet.conf defined puppet server as mypuppet
>
> server = mypuppet.example.net
>
> Not sure why the puppet client puppet-test is still sending these
> noises to the syslog
>
> Jun 10 13:36:23 puppet-test puppetd[10863
Sorry everyone. Intermittent connectivity weirdness.
On 6/10/09, Asif Iqbal wrote:
>
> In my puppet client I have
> puppet.conf defined puppet server as mypuppet
>
> server = mypuppet.example.net
>
> Not sure why the puppet client puppet-test is still sending these
> noises to the syslog
>
> Jun
On 6/10/09, Asif Iqbal wrote:
>
> In my puppet client I have
> puppet.conf defined puppet server as mypuppet
>
> server = mypuppet.example.net
>
> Not sure why the puppet client puppet-test is still sending these
> noises to the syslog
>
> Jun 10 13:36:23 puppet-test puppetd[10863]: [ID 702911 da
On 6/10/09, Asif Iqbal wrote:
>
> In my puppet client I have
> puppet.conf defined puppet server as mypuppet
>
> server = mypuppet.example.net
>
> Not sure why the puppet client puppet-test is still sending these
> noises to the syslog
>
> Jun 10 13:36:23 puppet-test puppetd[10863]: [ID 702911 da
Thanks, I'll add it to my config file.
On 1/9/09, Jason Rojas wrote:
>
>
> Look up bind_policy not soft_bind. This gives a good description:
>
> http://www.nabble.com/Re%3A-nss_ldap-and-udevd-p3202151.html
>
> -Jason
> On Jan 9, 2009, at 2:38 AM, Kenneth Holter wrote:
>
> >
> > Thanks for the ad
Look up bind_policy not soft_bind. This gives a good description:
http://www.nabble.com/Re%3A-nss_ldap-and-udevd-p3202151.html
-Jason
On Jan 9, 2009, at 2:38 AM, Kenneth Holter wrote:
>
> Thanks for the advice. Regarding the soft_bind option for openldap: I
> can't seem to find any documentatio
Thanks for the advice. Regarding the soft_bind option for openldap: I
can't seem to find any documentation for this option. Do you have a
link to a site describing this?
On 1/8/09, Adam Jacob wrote:
>
> On Jan 8, 2009, at 5:18 AM, Kenneth Holter wrote:
> > I've noticed that on servers that are b
On Jan 8, 2009, at 5:18 AM, Kenneth Holter wrote:
> I've noticed that on servers that are both puppet and LDAP clients,
> the puppet client will hang if the LDAP server is not reachable. Does
> anyone know what the reason for this is?
You should start using nscd (or your platform equivilant,) whi
On Jan 8, 2009, at 7:18 AM, Kenneth Holter wrote:
>
> Hi.
>
>
> I've noticed that on servers that are both puppet and LDAP clients,
> the puppet client will hang if the LDAP server is not reachable. Does
> anyone know what the reason for this is?
I'd expect everything on the server to hang in t
60 matches
Mail list logo
