On 28 December 2010 09:41, cyrus wrote:
> Hi:
>
> I have something like this:
>
> class xinetd {
>
> ... some Puppet code ...
>
> class xinetd::telnet {
> ... some Puppet code ...
> }
> }
>
> node 'host1' {
> include xinetd::telnet
> }
>
Doesn't that mean you've declared xinetd and
On Mon, Dec 27, 2010 at 8:17 PM, Patrick wrote:
>
>
> On Dec 27, 2010, at 8:11 PM, cyrus wrote:
>
>> Hi:
>>
>> I have something like this:
>>
>> class xinetd {
>>
>> ... some Puppet code ...
>>
>> class xinetd::telnet {
>> ... some Puppet code ...
>> }
>> }
>>
>> node 'host1' {
>> in
On Dec 27, 2010, at 8:11 PM, cyrus wrote:
> Hi:
>
> I have something like this:
>
> class xinetd {
>
> ... some Puppet code ...
>
> class xinetd::telnet {
> ... some Puppet code ...
> }
> }
>
> node 'host1' {
> include xinetd::telnet
> }
>
> However, when running Puppet says
Hi:
I have something like this:
class xinetd {
... some Puppet code ...
class xinetd::telnet {
... some Puppet code ...
}
}
node 'host1' {
include xinetd::telnet
}
However, when running Puppet says it can't find class xinetd::telnet.
I can include xinetd so I know my site.p
James,
Thanks for the tip. I will give this solution a try.
Kind Regards,
Mike
-Original Message-
From: puppet-users@googlegroups.com
[mailto:puppet-us...@googlegroups.com] On Behalf Of James Turnbull
Sent: Monday, December 27, 2010 12:50 PM
To: puppet-users@googlegroups.com
Subject: R
Mike wrote:
> err: Could not request certificate; No route to host - connect(2).
This is usually a hostname/DNS issue with your certificates.
See https://groups.google.com/forum/#!topic/puppet-users/FyxBHvZ5MSs for
an example.
Regards
James Turnbull
--
Puppet Labs - http://www.puppetlabs.com
Thanks Mark. I'll give that a try and see what happens.
Mike
-Original Message-
From: puppet-users@googlegroups.com
[mailto:puppet-us...@googlegroups.com] On Behalf Of Mark Stanislav
Sent: Monday, December 27, 2010 12:08 PM
To: puppet-users@googlegroups.com
Subject: Re: [Puppet Users] Pu
May be worth while to throw an 'strace -f' on it and see if you notice anything
peculiar. Off hand based on your testing I don't have any good answers, sorry!
-Mark
On Dec 27, 2010, at 11:59 AM, Mike wrote:
> When running the command puppetd --server fedorahost.ocfl.net --
> waitforcert 60 --te
When running the command puppetd --server fedorahost.ocfl.net --
waitforcert 60 --test I get the following error:
err: Could not request certificate; No route to host - connect(2).
Does anyone know why this might be? I can ping, telnet, ssh, etc the
server from the client and netstat -nr shows t
Martijn Grendelman wrote:
> On 24-12-10 16:47, Martijn Grendelman wrote:
>> Hi,
>>
>> Today, I set up 'rrdgraph' reports. What could be the cause of this:
>>
>> Dec 24 15:52:35 offman01 puppet-master[20593]: Report rrdgraph failed:
>> Could not create RRD file
>> /var/lib/puppet/rrd/talk.dev.iphion
Couldn't find any related thread...
We're using it mainly for collection so far (ie: nagios), but in the
future we'll probably use it for inventory too.
El 22/12/2010 21:02, Ohad Levy escribió:
Hi,
Search the threads, there were a few discussions about this point... at
the moment afaik, its
On 12/27/2010 02:54 PM, Martijn Grendelman wrote:
> Hi,
>>> In one of my modules, I have the following:
>>>
>>> exec { "/bin/sed -i '\~^${line}$~d' '${file}'":
>>>
>>> The '\~' is there, to make sed use '~' as the command separator instead of
>>> '/', which is too common in the lines I am trying
Hi,
>> In one of my modules, I have the following:
>>
>> exec { "/bin/sed -i '\~^${line}$~d' '${file}'":
>>
>> The '\~' is there, to make sed use '~' as the command separator instead of
>> '/', which is too common in the lines I am trying to delete.
>>
>> However, the puppet master now complains:
On 12/27/2010 02:13 PM, Martijn Grendelman wrote:
> Hi,
>
> In one of my modules, I have the following:
>
> exec { "/bin/sed -i '\~^${line}$~d' '${file}'":
>
> The '\~' is there, to make sed use '~' as the command separator instead of
> '/', which is too common in the lines I am trying to dele
On 12/24/2010 08:37 PM, Patrick wrote:
>
> On Dec 24, 2010, at 6:41 AM, Daniel Piddock wrote:
>
>> Unfortunately it looks like puppeteers expect this unusual name resolution
>> order, if they ever knowingly stumble upon it (e.g. 4483, 4472). Either I
>> need to hack around this problem carefull
Hi,
In one of my modules, I have the following:
exec { "/bin/sed -i '\~^${line}$~d' '${file}'":
The '\~' is there, to make sed use '~' as the command separator instead of
'/', which is too common in the lines I am trying to delete.
However, the puppet master now complains:
Dec 27 14:07:11 of
On 24-12-10 16:47, Martijn Grendelman wrote:
> Hi,
>
> Today, I set up 'rrdgraph' reports. What could be the cause of this:
>
> Dec 24 15:52:35 offman01 puppet-master[20593]: Report rrdgraph failed:
> Could not create RRD file
> /var/lib/puppet/rrd/talk.dev.iphion.nl/changes.rrd: you must define
17 matches
Mail list logo
