Just to add: in the puppet masterlog it shows below. What causes the
"Could not resolve 192.168.2.3: no name for 192.168.2.3" ?
I'm running inside Eucalyptus, where the domainname is strange.
Also, with exactly the same configuration/certs, if I run
puppetmasterd directly, it works fine.
Thanks
Hi Chris,
On 14/08/2010, at 8:48 AM, Christopher Johnston wrote:
> Since some of them all use the same options (user, group, mode, etc) with the
> same values is there a way to set them globally once and have all of them get
> inherited so I don't have to repeat entries?
Yes:
File {
owne
Hi Chris,
On 14/08/2010, at 8:48 AM, Christopher Johnston wrote:
> Since some of them all use the same options (user, group, mode, etc) with the
> same values is there a way to set them globally once and have all of them get
> inherited so I don't have to repeat entries?
Yes:
File {
owne
I have some types like below that have about 10 files or directories in a
single type to keep my manifests looking clean and easier to maintain.
Since some of them all use the same options (user, group, mode, etc) with
the same values is there a way to set them globally once and have all of
them ge
Hi Experts,
I'm trying to run puppet via passenger _ apache2 on ubuntu 10.04 64bit and
it refuse to work with an error:
*err: Could not retrieve catalog from remote server: Error 403 on SERVER:
Forbidden request: 192.168.2.3(192.168.2.3) access to
/certificate_revocation_list/ca [find] at line 93
On Aug 13, 2010, at 7:22 AM, Christian wrote:
> When i run in the webbrowser https://:8140 I'm getting
> following message:
>
> "The environment mus be purely alphanumeric, ''". Is it an problem not
> to have an environment defined?
My working puppetmaster gives the same error.
--
You received
On Aug 13, 2010, at 7:21 AM, Christopher Johnston wrote:
> ignoreschedules = true
This will cause puppet to ignore schedule resources. It won't do what you want.
>
>
> Cant you just use those two options to allow puppetruns to work and not have
> the client attempt to do updates?
>
>
On Wed, 11 Aug 2010, martin kummer wrote:
> [files]
> path /etc/puppet/files
> allow 178.78.72.121 <-space here
>
> this breaks the puppetmaster silently. this is real bad. this must be
> a bug.
This is puppet bug #3514. It's supposed to be fixed in version 2.6.0.
--apb (Alan Barrett)
--
Hello Brian,
I haven't changed my auth.conf.
I've put these lines into my auth.conf. Unfortunatilly this also seems
not to work. It reports the same error as before.
The only thing i have changed is the folder where the auth.conf is
located. The path name in the puppet.conf points to the right fi
listen = true
ignoreschedules = true
Cant you just use those two options to allow puppetruns to work and not have
the client attempt to do updates?
On Fri, Aug 13, 2010 at 6:44 AM, matonb wrote:
> Is there a puppet.conf equivalent to --no-client ?
>
> All the nodes are RHEL a
FYI there is a script around somewhere that works with puppetrun - it is a
very lightweight daemon that just listens for puppetrun requests and
launches the full daemon.
On Fri, Aug 13, 2010 at 9:04 AM, Joe McDonagh
wrote:
> On 08/13/2010 05:05 AM, ScubaDude wrote:
>
>> I was wondering how to con
On 08/13/2010 05:05 AM, ScubaDude wrote:
I was wondering how to configure the puppet clients to only listen,
not to periodically pull configs down from the puppetmaster.
I'd rather push the configs out from the puppetmaster with
puppetrun...
At a guess I need to set runinterval to 0 in /etc/pup
Is there a puppet.conf equivalent to --no-client ?
All the nodes are RHEL and will use the puppet service (init
script). I'd rather not tweak that if possible.
Thanks.
On Aug 13, 11:38 am, Craig Dunn wrote:
> On Fri, Aug 13, 2010 at 10:05 AM, ScubaDude wrote:
>
> > I was wondering how to con
On Fri, Aug 13, 2010 at 10:05 AM, ScubaDude wrote:
> I was wondering how to configure the puppet clients to only listen,
> not to periodically pull configs down from the puppetmaster.
>
> I'd rather push the configs out from the puppetmaster with
> puppetrun...
>
>
Running puppetd with --no-clien
I was wondering how to configure the puppet clients to only listen,
not to periodically pull configs down from the puppetmaster.
I'd rather push the configs out from the puppetmaster with
puppetrun...
At a guess I need to set runinterval to 0 in /etc/puppet/puppet.conf?
--
You received this mes
Ticket filed (bug, refactor)
On Aug 13, 7:56 am, Matt Robinson wrote:
> We weren't aware as none of us are using Internet Explorer. We'll
> have to have someone get a copy to test with at some point.
>
> Can you file a ticket?
>
> http://projects.puppetlabs.com
>
> Thanks,
> Matt
>
> On Thu, Aug
Thanks Paul; I don't have a problem getting the preseed onto the
system, it's just that dbconfig-common totally ignores the fact you've
tried to preseed it out of existence. :)
I may have to take this to the Debian bugtracker.
Craig
On Aug 12, 6:35 pm, Paul Hamby wrote:
> We created a definitio
17 matches
Mail list logo
