On Wed, 2010-06-02 at 15:16 -0700, Patrick wrote:
> Sorry, but you might have lost me. Are you saying that you're having
> problems because when you define the repository in two places it throws an
> error?
>
Not quite! :)
I want to define all my repos in one module and then include the repos
Matt Wallace writes:
> On Wed, 2010-06-02 at 15:16 -0700, Patrick wrote:
>
>> Sorry, but you might have lost me. Are you saying that you're having
>> problems because when you define the repository in two places it throws an
>> error?
>
> Not quite! :)
>
> I want to define all my repos in one mod
Hello.
Here is my example:
# City1 variables
class city1 {
$fname = '/tmp/la-la'
}
# City2 variables
class city2 {
$fname = '/tmp/ba-ba'
}
node node1 {
include city1
include city2
$city = 'city1'
file { "${city}::fname": ensure => present }
}
node
I´ve got the following message in my puppet logfile
Could not render to yaml: stack level too deep
I´ve only found references about increasing the stack size (which is
now 32768),
are there any other options?
--
You received this message because you are subscribed to the Google Groups
"Puppet
On Thu, 2010-06-03 at 18:22 +1000, Daniel Pittman wrote:
> ...but from experience I wouldn't recommend doing this. You are almost
> certainly going to be better off having the same set of repositories on every
> server, and using some other mechanism to control which packages or updates
> are app
What version of Ruby/Gems are you running?
I had some problems with that pre Ruby 1.8.5 and Gems 1.3.5
Trevor
On Thu, Jun 3, 2010 at 9:53 AM, Stefan Wiederoder
wrote:
> I´ve got the following message in my puppet logfile
> Could not render to yaml: stack level too deep
>
> I´ve only found refe
2010/5/6 piir D.K
> Hello,
>
> I'm tryning to have puppet working whitout handling any part of a pki.
> On one side I've got a puppet installation working, on the other side
> a PKI.(dogtag)
>
> I try to tell puppetmasterd to use my CA.crt and an already
> functionning cert, but at launch time it
Never tried it myself but I think you can create the certificate as a
part of the provisioning process, and then somehow place it in the new
server.
http://serverfault.com/questions/19462/how-can-i-pre-sign-puppet-certificates
On Jun 3, 7:42 am, "Matthew Delves" wrote:
> Hey Folks,
> I'm looking
On Wed, 02 Jun 2010, James Turnbull wrote:
> > I didn't see anybody ask for the ability to send anonymous bug reports
> > (although thta would certainly be useful). I saw somebody ask for the
> > ability to send bug reports without having to create a new account. For
> > example, that desire coul
which version of puppet are you using? there were issues with CRL in 0.25.x
(partly fixed in 0.25.5).
its probably best if you can join the irc channel, would be easier to debug
the problem :)
Ohad
On Thu, Jun 3, 2010 at 9:58 PM, piir wrote:
>
> 2010/5/6 piir D.K
>
> Hello,
>>
>> I'm tryning t
On Thu, Jun 3, 2010 at 6:58 AM, piir wrote:
>
> 2010/5/6 piir D.K
>
> Hello,
>>
>> I'm tryning to have puppet working whitout handling any part of a pki.
>> On one side I've got a puppet installation working, on the other side
>> a PKI.(dogtag)
>>
>> I try to tell puppetmasterd to use my CA.crt
Hello Ohad,
From the instructions you have posted, I tried to setup the
database via RAILS_ENV=production rake db:migrate, and then I got the
following error:
rake aborted!
NoMethodError: undefined method `ord' for 0:Fixnum: SET NAMES 'utf8'
This is the trace:
** Invoke db:migrate (first_
BTW: This was the latest nightly build.
Thanks,
Henry
On Jun 3, 11:05 am, CraftyTech wrote:
> Hello Ohad,
>
> From the instructions you have posted, I tried to setup the
> database via RAILS_ENV=production rake db:migrate, and then I got the
> following error:
>
> rake aborted!
> NoMethodEr
> What version of Ruby/Gems are you running?
> I had some problems with that pre Ruby 1.8.5 and Gems 1.3.5
I´m using the following rpm´s (RHEL, EPEL):
rubygems-1.3.1-1.el5
ruby-libs-1.8.5-5.el5_4.8
ruby-shadow-1.4.1-7.el5
rubygem-gem_plugin-0.2.2-2.el5
rubygem-rake-0.8.3-1.el5
libselinux-ruby-1.3
which db are you using? could it be that you have some error in
config/database.yml file?
Ohad
On Thu, Jun 3, 2010 at 11:05 PM, CraftyTech wrote:
> Hello Ohad,
>
> From the instructions you have posted, I tried to setup the
> database via RAILS_ENV=production rake db:migrate, and then I got
I'm using mysql 5.1.44 . I tested the config in the database.yml, by
basically using the same credentials and logging in locally. I was
able log in fine. Here's a snippet:
production:
adapter: mysql
database: foreman_prod
username: foreman_user
password: XXX
encoding: utf8
I
try without the encoding line
see http://theforeman.org/projects/foreman/wiki/FAQ#I-want-to-use-MySQL for
a working example.
cheers,
Ohad
On Thu, Jun 3, 2010 at 11:31 PM, CraftyTech wrote:
> I'm using mysql 5.1.44 . I tested the config in the database.yml, by
> basically using the same credenti
Ok, we got a little further now : ) This is the new error:
rake aborted!
NoMethodError: undefined method `ord' for 0:Fixnum: SET
SQL_AUTO_IS_NULL=0
Here's the trace:
(in /code/foreman)
** Invoke db:migrate (first_time)
** Invoke environment (first_time)
** Execute environment
rake aborted!
NoMe
# puppet -ddd foo1.pp
Could not parse for environment production: Syntax error at 'set
/files/etc/services/service-name[port = '1002'] app_tcp'; expected ']' at
/data/foo1.pp:5
I don't believe that works...
On Wed, Jun 2, 2010 at 10:59 PM, Rob McBroom wrote:
> On Jun 2, 2010, at 4:03 PM, Christ
interesting, this seems related to your version of ruby (is it 1.8.6?)
what do you get when you run the following in a shell?
ruby -v -e "puts 'abc'[1].ord"
Ohad
On Thu, Jun 3, 2010 at 11:58 PM, CraftyTech wrote:
> Ok, we got a little further now : ) This is the new error:
>
> rake aborted!
Duh sorry I added commas for the array... stil the same error. I dont think
that will work since the entries in the services file are usually like this:
augtool> print /files/etc/services/service-name[1]
/files/etc/services/service-name[1] = "tcpmux"
/files/etc/services/service-name[1]/port = "1"
On Jun 3, 2010, at 12:04 PM, Christopher Johnston wrote:
> # puppet -ddd foo1.pp
> Could not parse for environment production: Syntax error at 'set
> /files/etc/services/service-name[port = '1002'] app_tcp'; expected ']' at
> /data/foo1.pp:5
It looks like you're trying to use single-quotes (fo
ruby 1.8.5 (2006-08-25) [i386-linux]
-e:1: undefined method `ord' for 98:Fixnum (NoMethodError)
1.8.5... is 1.8.6 a requirement?
Thanks,
Henry
On Jun 3, 12:08 pm, Ohad Levy wrote:
> interesting, this seems related to your version of ruby (is it 1.8.6?)
>
> what do you get when you run the foll
I tried mixing/matching quotes, if I double quote just the set statement and
quote nothing else it goes through but nothing gets changed.
for eg: "set service-name[port = 7302]/port 7302",
"debug: Augeas[cti-p01-dgw_udp](provider=augeas): Skipping becuase no files
were changed"
Now if I single q
On Jun 3, 2010, at 1:40 PM, Christopher Johnston wrote:
> Now if I single quote the port number in the [] I get another error.. which
> likely means using the '' is not correct.
>
> err: //Augeas[cti-p01-dgw_tcp]/returns: change from need_to_run to 0 failed:
> Save failed with return code fal
2010/6/3 Nigel Kersten
>
>
> On Thu, Jun 3, 2010 at 6:58 AM, piir wrote:
>
>>
>> 2010/5/6 piir D.K
>>
>> Hello,
>>>
>>> I'm tryning to have puppet working whitout handling any part of a pki.
>>> On one side I've got a puppet installation working, on the other side
>>> a PKI.(dogtag)
>>>
>>> I t
I am on 25.4...
On Thu, Jun 3, 2010 at 1:59 PM, Rob McBroom wrote:
> On Jun 3, 2010, at 1:40 PM, Christopher Johnston wrote:
>
> > Now if I single quote the port number in the [] I get another error..
> which likely means using the '' is not correct.
> >
> > err: //Augeas[cti-p01-dgw_tcp]/returns
You had to make me actually try it in Puppet, huh? ;)
My original example was missing commas after the various set statements. Not
sure if you fixed that. It also specified the full path, even though the
context should have taken care of most of it. That didn't seem to hurt, but to
be safe, I t
HA, yes I added commas. You know what the problem was, my ordering. I had
app_tcp first and not port 1002 so thats likely why it was not getting
picked up. Worked, but hit another snag. Now try adding another app name,
same port but for udp, it will just get overwritten.
-Chris
On Thu, Jun 3
Alan Barrett wrote:
On Wed, 02 Jun 2010, James Turnbull wrote:
Projects using an anonymous
web form could use a CAPTCHA to slow spammers down.
But that's a barrier to reporting I have to type a one or two extra words into a *separate* form field, usually
from a slightly difficult to read
On Fri, 04 Jun 2010 08:33:34 +1200, craig.misk...@opus.co.nz said:
> from a slightly difficult to read text image
CAPTCHAs have got to the stage where they are easier for computers to read
than they are for humans to read. My wife's phpBB had a CAPTCHA and was
forever getting spammed; now we hav
Amusing (albeit off-topic) captcha story, reposted from my blog
I was talking with somebody about captcha arms race at work today and heard the
most brilliant scam. Apparently spammers who are attempting to spam to
captcha-enabled sites screen-grab the captcha image and then turn around
and se
1.8.6 is not required really, but it seems that your core ruby is missing a
method.
which distribution is it? did you install from source and never maintained
it? (or maybe the package is out of date?)
I can provide a monkey patch for this, but It seems like an issue with your
ruby installation.
It's centos 5.4 x86 which default ruby install is 1.8.5 (RPM). If
you can provide a patch, that'd be great. Thanks for the assist.
Cheers,
Henry
On Jun 3, 10:06 pm, Ohad Levy wrote:
> 1.8.6 is not required really, but it seems that your core ruby is missing a
> method.
> which distribution i
It's centos 5.4 x86 which default ruby install is 1.8.5 (RPM). If
you can provide a patch, that'd be great. Thanks for the assist.
Cheers,
Henry
On Jun 3, 10:06 pm, Ohad Levy wrote:
> 1.8.6 is not required really, but it seems that your core ruby is missing a
> method.
> which distribution i
It's centos 5.4 x86 which default ruby install is 1.8.5 (RPM). If
you can provide a patch, that'd be great. Thanks for the assist.
Cheers,
Henry
On Jun 3, 10:06 pm, Ohad Levy wrote:
> 1.8.6 is not required really, but it seems that your core ruby is missing a
> method.
> which distribution i
It's centos 5.4 x86 which default ruby install is 1.8.5 (RPM). If
you can provide a patch, that'd be great. Thanks for the assist.
Cheers,
Henry
On Jun 3, 10:06 pm, Ohad Levy wrote:
> 1.8.6 is not required really, but it seems that your core ruby is missing a
> method.
> which distribution i
Henry,
can you try with an sqlite db? just to be sure I'm not looking in the wrong
direction?
additionally, maybe you can join us on irc at #theforeman or #puppet, will
probably be much faster :)
Ohad
On Fri, Jun 4, 2010 at 10:30 AM, CraftyTech wrote:
> It's centos 5.4 x86 which default ruby
It's centos 5.4 x86 which default ruby install is 1.8.5 (RPM). If
you can provide a patch, that'd be great. Thanks for the assist.
Cheers,
Henry
On Jun 3, 10:06 pm, Ohad Levy wrote:
> 1.8.6 is not required really, but it seems that your core ruby is missing a
> method.
> which distribution i
On Jun 3, 2010, at 3:05 PM, Christopher Johnston wrote:
> You know what the problem was, my ordering. I had app_tcp first and not port
> 1002 so thats likely why it was not getting picked up. Worked, but hit
> another snag. Now try adding another app name, same port but for udp, it
> will ju
40 matches
Mail list logo
