[Puppet Users] Re: dashboard: rake install fails (Solaris10)

2010-04-21 Thread Lutz Bergner 
Meanwhile I have made a little progress when I removed authlogic-2.1.2
from vendor/gems.
But came not too far...
Can someone please point me into the right direction?

Many Thanks in advance

Lutz

Now I get:
bash-3.00# rake install --trace
(in /opt/reductivelabs-puppet-dashboard-v1.0.0rc2-0-gd5918df)
** Invoke install (first_time)
** Invoke copy_config (first_time)
** Invoke config/database.yml (first_time, not_needed)
** Invoke config/database.yml.example (first_time, not_needed)
** Execute copy_config
** Invoke db:create (first_time)
** Invoke db:load_config (first_time)
** Invoke rails_env (first_time)
** Execute rails_env
** Execute db:load_config
** Execute db:create
dashboard_development already exists
** Invoke db:schema:load (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute db:schema:load
-- create_table(assignments, {:force=true})
   - 0.0315s
-- create_table(node_class_memberships, {:force=true})
   - 0.0202s
-- create_table(node_classes, {:force=true})
   - 0.0166s
-- create_table(node_group_class_memberships, {:force=true})
   - 0.0153s
-- create_table(node_group_edges, {:force=true})
   - 0.0180s
-- create_table(node_group_memberships, {:force=true})
   - 0.0184s
-- create_table(node_groups, {:force=true})
   - 0.0189s
-- create_table(nodes, {:force=true})
   - 0.0170s
-- create_table(parameters, {:force=true})
   - 0.0166s
-- create_table(reports, {:force=true})
   - 0.0192s
-- add_index(reports, [node_id],
{:name=index_reports_on_node_id})
   - 0.0211s
-- add_index(reports, [time], {:name=index_reports_on_time})
   - 0.0247s
-- create_table(services, {:force=true})
   - 0.0179s
-- create_table(timeline_events, {:force=true})
   - 0.0207s
-- create_table(users, {:force=true})
   - 0.0391s
-- initialize_schema_migrations_table()
   - 0.0006s
-- assume_migrated_upto_version(20100318131825)
   - 0.0010s
** Invoke db:seed (first_time)
** Invoke environment
** Execute db:seed
rake aborted!
undefined method `generate!' for #Class:0x9b30264
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/
base.rb:1959:in `method_missing_without_paginate'
/usr/local/lib/ruby/gems/1.8/gems/will_paginate-2.3.12/lib/
will_paginate/finder.rb:170:in `method_missing'
/opt/reductivelabs-puppet-dashboard-v1.0.0rc2-0-gd5918df/db/seeds.rb:1
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.4/lib/
active_support/dependencies.rb:145:in
`load_without_new_constant_marking'
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.4/lib/
active_support/dependencies.rb:145:in `load'
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.4/lib/
active_support/dependencies.rb:521:in `new_constants_in'
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.4/lib/
active_support/dependencies.rb:145:in `load'
/usr/local/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/tasks/databases.rake:
215
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in
`execute'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in
`execute'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in
`invoke_with_call_chain'
/usr/local/lib/ruby/1.8/monitor.rb:242:in `synchronize'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in
`invoke_with_call_chain'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:607:in
`invoke_prerequisites'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:604:in `each'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:604:in
`invoke_prerequisites'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:596:in
`invoke_with_call_chain'
/usr/local/lib/ruby/1.8/monitor.rb:242:in `synchronize'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in
`invoke_with_call_chain'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in
`invoke'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in
`invoke_task'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in
`top_level'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in
`each'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in
`top_level'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in
`standard_exception_handling'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in
`top_level'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in
`standard_exception_handling'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31
/usr/local/bin/rake:19:in `load'
/usr/local/bin/rake:19



 --
 You received this message because you are subscribed to the Google Groups 
 Puppet Users group.
 To post to this group, send email to puppet-us...@googlegroups.com.
 To unsubscribe from this group, send email to

[Puppet Users] Re: Puppetmaster with storeconfig crashes on Solaris10

2010-04-20 Thread Lutz Bergner 
...found it by myself. Anyway it may be helpful to others.
A 64 Bit mysql-server accessed by 32bit libmysqlclient.so did not work
in my case at least when both reside on the same machine.
Have build now mysql 5.1 latest stable as a 32bit executable and all
is doing fine .
By the way - the shipped one by SUN is a 32Bit as well
OS is Solaris10 64Bit

regards

Lutz




On Apr 19, 10:22 am, Lutz Bergner lutz.berg...@tomtom.com wrote:
 Hi all,
 Once again I need some help...
 
 info: Connecting to mysql database: puppet
 (eval):3: [BUG] Segmentation fault
 ruby 1.8.7 (2009-06-12 patchlevel 174) [i386-solaris2.10]

 Abort
 -
 Get this one when I start puppetmaster with storeconfig enabled.
 Database gets initialized, some tables e.g. facts get filled but then
 the above failure...
 Here my situation:
 -- Mysql server 64Bit compiled 5.0.67.I could not use the shipped
 (SFW) 4.0 server as it apearantly does not support UTF-8 which in turn
 is needed for dashboard.
 -- mysql-ruby 2.8.1 (2.7 tested as well)
 -- Ruby ruby-1.8.7-p174 - could not use the shipped 1.8.5 as mysql-
 ruby refused to work with.
 -- rails 2.3.5  as  2.2.2 does not work with puppet 0.25.4 ue to
 incompatible iconv
 After about one week of work , I am really stuck with this one.
 Perhaps someone has a version chain of components that really works.
 With the shipped components of Solaris10 with ruby 1.8.7 storeconfig
 does work - but does not support UTF-8 which prevents dashboard from
 starting.

 Many thanks in advance...

 Lutz

 --
 You received this message because you are subscribed to the Google Groups 
 Puppet Users group.
 To post to this group, send email to puppet-us...@googlegroups.com.
 To unsubscribe from this group, send email to 
 puppet-users+unsubscr...@googlegroups.com.
 For more options, visit this group 
 athttp://groups.google.com/group/puppet-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] dashboard: rake install fails (Solaris10)

2010-04-20 Thread Lutz Bergner 
Hi all,
I am trying to install dashboard 1.0.0rc1. Independantly if have
manually installed authlogic - gem or not it is throwing the following
trace.  The problem is the same when I am resetting (rake db:reset) or
dropping the database.
any ideas?

best regards

Lutz


bash-3.00# rake install
(in /opt/puppet-dashboard)
dashboard_development already exists
can't activate authlogic (= 2.1.3, runtime) for [], already activated
authlogic-2.1.2 for []
/usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:230:in `activate'
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:35:in
`require'
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/
active_support/dependencies.rb:156:in `require'
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/
active_support/dependencies.rb:521:in `new_constants_in'
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/
active_support/dependencies.rb:156:in `require'
/usr/local/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/rails/
gem_dependency.rb:208:in `load'
/usr/local/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:
307:in `load_gems'
/usr/local/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:
307:in `each'
/usr/local/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:
307:in `load_gems'
/usr/local/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:
164:in `process'
/usr/local/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:
113:in `send'
/usr/local/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:
113:in `run'
/opt/puppet-dashboard/config/environment.rb:7
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/
active_support/dependencies.rb:156:in `require'
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/
active_support/dependencies.rb:521:in `new_constants_in'
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/
active_support/dependencies.rb:156:in `require'
/usr/local/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/tasks/misc.rake:4
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in
`execute'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in
`execute'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in
`invoke_with_call_chain'
/usr/local/lib/ruby/1.8/monitor.rb:242:in `synchronize'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in
`invoke_with_call_chain'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:607:in
`invoke_prerequisites'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:604:in `each'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:604:in
`invoke_prerequisites'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:596:in
`invoke_with_call_chain'
/usr/local/lib/ruby/1.8/monitor.rb:242:in `synchronize'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in
`invoke_with_call_chain'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:607:in
`invoke_prerequisites'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:604:in `each'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:604:in
`invoke_prerequisites'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:596:in
`invoke_with_call_chain'
/usr/local/lib/ruby/1.8/monitor.rb:242:in `synchronize'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in
`invoke_with_call_chain'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in
`invoke'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in
`invoke_task'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in
`top_level'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in
`each'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in
`top_level'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in
`standard_exception_handling'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in
`top_level'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in
`standard_exception_handling'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31
/usr/local/bin/rake:19:in `load'
/usr/local/bin/rake:19
can't activate authlogic (= 2.1.3, runtime) for [], already activated
authlogic-2.1.2 for []
/usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:230:in `activate'
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:35:in
`require'
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/
active_support/dependencies.rb:156:in `require'
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/
active_support/dependencies.rb:521:in `new_constants_in'

[Puppet Users] Puppetmaster with storeconfig crashes on Solaris10

2010-04-19 Thread Lutz Bergner 
Hi all,
Once again I need some help...

info: Connecting to mysql database: puppet
(eval):3: [BUG] Segmentation fault
ruby 1.8.7 (2009-06-12 patchlevel 174) [i386-solaris2.10]

Abort
-
Get this one when I start puppetmaster with storeconfig enabled.
Database gets initialized, some tables e.g. facts get filled but then
the above failure...
Here my situation:
-- Mysql server 64Bit compiled 5.0.67.I could not use the shipped
(SFW) 4.0 server as it apearantly does not support UTF-8 which in turn
is needed for dashboard.
-- mysql-ruby 2.8.1 (2.7 tested as well)
-- Ruby ruby-1.8.7-p174 - could not use the shipped 1.8.5 as mysql-
ruby refused to work with.
-- rails 2.3.5  as  2.2.2 does not work with puppet 0.25.4 ue to
incompatible iconv
After about one week of work , I am really stuck with this one.
Perhaps someone has a version chain of components that really works.
With the shipped components of Solaris10 with ruby 1.8.7 storeconfig
does work - but does not support UTF-8 which prevents dashboard from
starting.

Many thanks in advance...

Lutz



-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] problems with project property of User resource

2010-03-24 Thread Lutz Bergner 
Hi,

I wanted to set the project property of a Solaris user after realizing
the user. Have already  created the project by adding a line to /etc/
project.  The user is created in virtual::user class wich is inherited
by the target class  to be able to add the project property. The
project of the user  gets not set properly and remains default
when I use the project property ! Had to fall back to an
Append_if_no_such_line solution.

I did the following:

class xx inherits virtual::user {
.
.
.
append_if_no_such_line { -Server-Project:
  file = /etc/project,
  line = projectname:9998: Server
Project:::process.max-file-descriptor=(priv,40960,deny)
}
realize(User[], Group[] )
User[username] {project = projectname, require = [Group[],
Append_if_no_such_line[-Server-Project]]}
}

Thanks in advance for any help

Lutz

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] howto prevent puppetd fom scheduled runs

2010-03-09 Thread Lutz Bergner 
Hi all,

this one sounds silly , but so far I failed.:

starting my clients with puppetd --listen and puppetrun is working
fine. But puppetd is doing its runs every half an hour (per default)
despite I have configured ignoreschedules=true
Here comes my client puppet.conf
What am I doing wrong.

[main]
environment = development
server = puppet.domain.com
listen = true
ignoreschedules = true
[puppetd]
listen = true
ignoreschedules = true

thanks in advance

Lutz

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: howto prevent puppetd fom scheduled runs

2010-03-09 Thread Lutz Bergner 
Many thanks to all , who responded. I'm going to evaluate the one or
other workaround now.

regards

Lutz

On Mar 9, 4:55 pm, James Cammarata j...@sngx.net wrote:
 On Tue, 9 Mar 2010 07:11:01 -0800 (PST), Lutz Bergner

 lutz.berg...@tomtom.com wrote:
  Hi all,

  this one sounds silly , but so far I failed.:

  starting my clients with puppetd --listen and puppetrun is working
  fine. But puppetd is doing its runs every half an hour (per default)
  despite I have configured ignoreschedules=true
  Here comes my client puppet.conf
  What am I doing wrong.

 Here's what we do.

 In sites.pp, we have this as the first line:

 import schedules

 This is /etc/puppet/manifests/schedules.pp:

 schedule { never:
     period = never,
     repeat = 0

 }

 Then, back in sites.pp, we set a global default for files to use the
 never schedule:

 # Set global defaults
 File { schedule = never }

 You can do this for all resource types if you like.  Next, in our
 puppet.conf on all systems, we added this, just so puppetd doesn't try to
 connect pack to the puppet server every 30 minutes just to do nothing:

 runinterval = 31536000

 That's 10 years, so puppetd will run once when it starts up (but not do
 anything because of the default schedule), but then pretty much never check
 back in on its own.  This is actually a hold-over from when we were using
 puppetrun, but since we're using puppetd with --onetime --no-daemonize
 it's not really required anymore.

 In order to make puppetd execute, we use --ignoreschedules on the command
 line when running puppetd manually with --onetime.  We feel it's a pretty
 good fail-safe, since a new admin who didn't know our setup probably
 wouldn't think to use --ignoreschedules by default.

 Hope this helps :)

 --
 This message has been scanned for viruses and
 dangerous content by MailScanner, and is
 believed to be clean.

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Could not retrieve catalog: Invalid parameter 'manifest' for type 'Service'

2009-12-03 Thread Lutz Bergner 
Hi all,

I get this complaint in Serverlog when I try to define this service:

service { 'svc:/application/jboss:default':
enable = true,
require = [Wf_conf_files['/opt/jboss-4.2.3.GA/server/ontario/conf/
wrapper.conf',
'/opt/jboss-4.2.3.GA/server/
ontario/conf/servicelocator.xml',
'/opt/jboss-4.2.3.GA/server/
ontario/conf/config-lbs.properties',
'/opt/jboss-4.2.3.GA/server/
ontario/conf/config-report-engine-client.properties',
'/opt/jboss-4.2.3.GA/server/
ontario/conf/reportclient.properties',
'/opt/jboss-4.2.3.GA/server/
ontario/conf/wfservice-ds.xml',
'/opt/jboss-4.2.3.GA/server/
ontario/deploy/jms/jms-ds.xml',
'/opt/jboss-4.2.3.GA/server/
ontario/deploy/oracle-ds.xml'], File['/opt/jboss']],
manifest = '/opt/jboss/bin/jboss.xml'

--

You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] err: Invalid parameter 'manifest' for type 'Service'.......

2009-12-03 Thread Lutz Bergner 
Hi all,

I get this complaint when I try to define the following service:

service { 'svc:/application/jboss:default':
enable = true,
manifest = '/opt/jboss/bin/jboss.xml'
}

puppetversion = 0.24.8
operatingsystem = Solaris
operatingsystemrelease = 5.10

What am I doing wrong?

regards

Lutz

--

You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Could not retrieve catalog: Invalid parameter 'manifest' for type 'Service'

2009-12-03 Thread Lutz Bergner 
both 0.24.8 , client is a zone on the server machine.

Lutz

On 3 Dez., 17:18, Peter Meier peter.me...@immerda.ch wrote:
  I get this complaint in Serverlog when I try to define this service:

 client/master version?

 cheers pete

--

You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Could not retrieve catalog: Invalid parameter 'manifest' for type 'Service'

2009-12-03 Thread Lutz Bergner 
Pete, by the way you were answering to fast . I deleted this post
because it was incomplete. OS and Versions are contained in the new
post

Lutz


On 3 Dez., 17:18, Peter Meier peter.me...@immerda.ch wrote:
  I get this complaint in Serverlog when I try to define this service:

 client/master version?

 cheers pete

--

You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Could not retrieve catalog: Invalid parameter 'manifest' for type 'Service'

2009-12-03 Thread Lutz Bergner 
many thanks for the quick response and solution.

Lutz

On 3 Dez., 17:39, Peter Meier peter.me...@immerda.ch wrote:
 Zitat von Lutz Bergner lutz.berg...@tomtom.com:

  both 0.24.8 , client is a zone on the server machine.

 this parameter got added in 0.25:  
 http://github.com/reductivelabs/puppet/commit/f1f0a57e4cafc5a9a4378f3...

 cheers pete

--

You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.