Basically, what's broken is that on some runs, puppet client fails to
process our file type resource declarations correctly.
When this happens, puppetmaster logs the errors I provided earlier.
Puppet clients log this:(Using my sendmail module as an example on this
one.)
2009-10-25T12:02:53+00:0
It returns it based on the title.
--~--~-~--~~~---~--~~
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
On Oct 24, 2009, at 9:59 AM, Sukh Khehra wrote:
[...]
> Things seem to work ok for the most part. Intermittently, however, I
> am
> seeing these errors log on the master. The same clients don't cause
> this
> at other times. Anyone ever seen this? I'd appreciate the help.
>
> My apache puppetm
On Oct 23, 2009, at 12:44 AM, Kenneth Holter wrote:
> Hi.
>
>
> Last night the /var/lib/puppet/clientbucktet directory on one of our
> production servers suddenly grew about 4 GB, filling up the entire /
> var partition. Around that time, I see that there was a problem with
> one of our CIFS
On Oct 22, 2009, at 9:50 AM, LdvT wrote:
>
> On Oct 20, 11:59 pm, Luke Kanies wrote:
>> On Oct 19, 2009, at 7:56 AM, LdvT wrote:
>>
>>
>>
>>> I wouldn't mind having failure detection.
>>
>>> Say somehow a bad copy of a .conf file is distributed; and the
>>> service
>>> fails to start.
>>> If t
On Oct 22, 2009, at 6:37 AM, haris wrote:
>
>
>
> On Oct 22, 2:33 pm, haris wrote:
>> Dear all,
>>
>> I am stuck with a problem while playing with Puppet 0.24.8.
>> when i run client daemon it gives following error: "Could not
>> retrieve
>> catalog: Could not parse for environment production:
On Oct 21, 2009, at 4:13 PM, Matt Delves wrote:
>
> Hey folks,
> I'm running into a problem with rrdgraph, specifically that it is
> giving the following error:
> Report rrdgraph failed: Invalid owner puppet on setting . Valid
> owners are root, service.
I believe this is a bug that was fixe
I don't believe 'pattern' is used to stop/start the service, only to
help recognise if it's running when hasstatus is not used.
On Sun, Oct 25, 2009 at 6:14 PM, R P Herrold wrote:
>
> On Sun, 25 Oct 2009, Douglas Garstang wrote:
>
>> Actually, putting this in the service description seems to hav
On Sun, 25 Oct 2009, Douglas Garstang wrote:
> Actually, putting this in the service description seems to have fixed it.
>
> pattern=> "/usr/bin/mysqld_safe"
It may have worked, but I guess I don't seen how going around
the LSB conformant services control model and forcing a start
outside
Actually, putting this in the service description seems to have fixed it.
pattern=> "/usr/bin/mysqld_safe"
although, the darn thing really should not be started when the RPM is
installed, because it isn't even started with the service script.
That's pretty friggin stupid. I suppose that's wh
On Sun, 25 Oct 2009, Douglas Garstang wrote:
> I'm using the RPM from the MySQL web site, and the packagers of this
> RPM in their infinite wisdom decided that the mysql service should be
> automatically started when the RPM was installed.
MySQL installs and upgrades are hard to get right, and m
I've got a mostly working puppet manifest for mysql, except for one problem.
I'm using the RPM from the MySQL web site, and the packagers of this
RPM in their infinite wisdom decided that the mysql service should be
automatically started when the RPM was installed. This confuses
puppet. The RPM i
2009/10/25 R.I.Pienaar :
>
> - "Lindsay Holmwood" wrote:
>
>>
>> The way i've gotten around this before is by tagging my classes, and
>> then do an initial run with puppetd for things tagged with yum and
>> ldap.
>>
>
> So exactly like i suggested later on in my mail? :)
>
Yeah, sorry. I rea
- "Lindsay Holmwood" wrote:
> > Unfortunately this is pretty hard, there's been many requests for a
> way to forceably hook something into the beginning of the process but
> so far there isnt a good way. There's a ticket you can go and voice
> your support for the feature requests there.
>
Latest development of Foreman contain an audit log, e.g. what has changed,
who changed etc, and it should be easy to revert changes in that context.
cheers,
Ohad
On Sun, Oct 25, 2009 at 8:41 PM, Peter Meier wrote:
>
> >>> As the number of servers I am using puppet on is increasing, I'm
> wonde
>>> As the number of servers I am using puppet on is increasing, I'm wondering
>>> what the best practices is for the nodes. Currently they all sit in the one
>>> file /etc/puppet/manifests/nodes.pp.
>>>
>>> What I'm wondering is whether this is the best way to go (that is, one
>>> large file)
Hi
> Thanks, I've seen that work but the trouble is I want to be able to
> pass in a $docroot option,
> or default to something if one is not there; I suppose I can probably
> get around it by checking
> if $docroot is defined and if not setting it or something?
how about:
define bar($docroot =
Hi
> No, that didn't work for me. When I put the default Package{} in the
> base node that required the class yum, puppet complained about cyclic
> object dependancies.
yeah, because you're requiring yum for yum. As somebody suggested you
should set the require to undef so to get rid off your de
2009/10/25 R.I.Pienaar :
>
> hello,
>
> - "Douglas Garstang" wrote:
>
>> Is it really this complicated? Follow my logic here...
>>
>> In my scenario, it's critical that my yum repositories get installed
>> by puppet to /etc/yum.repos.d first before anything else happens.
>> After this, the yu
hello,
- "Douglas Garstang" wrote:
> Is it really this complicated? Follow my logic here...
>
> In my scenario, it's critical that my yum repositories get installed
> by puppet to /etc/yum.repos.d first before anything else happens.
> After this, the yum-priorities rpm must be installed wi
2009/10/22 Nicolas Szalay :
> Le vendredi 23 octobre 2009 à 15:32 +1100, Matt Delves a écrit :
>> Greetings,
>> As the number of servers I am using puppet on is increasing, I'm wondering
>> what the best practices is for the nodes. Currently they all sit in the one
>> file /etc/puppet/manifests/
Thanks, I've seen that work but the trouble is I want to be able to
pass in a $docroot option,
or default to something if one is not there; I suppose I can probably
get around it by checking
if $docroot is defined and if not setting it or something?
Thanks again.
On Sat, Oct 24, 2009 at 5:37 PM,
Darn iPhone. Requiring a class will make puppet consider an entire
class of resources a dependency. So in the example you quoted, the
squid class would be executed before the apache service.
It allows abstraction over requiring individual resources, that's all.
Sent from my iPhone
On 25 Oct
Require => Class will me
Sent from my iPhone
On 25 Oct 2009, at 06:59, Douglas Garstang
wrote:
>
> Can someone tell me what a require => Class actually does? The
> documentation on this really isn't clear.
>
> The language tutorial at
> http://reductivelabs.com/trac/puppet/wiki/LanguageTutor
Is it really this complicated? Follow my logic here...
In my scenario, it's critical that my yum repositories get installed
by puppet to /etc/yum.repos.d first before anything else happens.
After this, the yum-priorities rpm must be installed with yum,
followed by ldap, since the installation of
25 matches
Mail list logo
