[Puppet Users] Re: Puppet 0.25 migration

2009-09-09 Thread jrojas 

I am seeing this problem as well.
Reverting from 2.2.5 to 2.2.2 did not help.


On Sep 9, 9:12 am, Matt mattmora...@gmail.com wrote:
 Reverting back to the passenger 2.2.2 gem worked for me.

 2009/9/8 Larry Ludwig la...@reductivelabs.com:



  hmm passenger 2.2.5 is released?  hmm I'll have to test it out.

  -L

  --
  Larry Ludwig
  Reductive Labs
--~--~-~--~~~---~--~~
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 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Puppetshow defunct?

2009-05-29 Thread jrojas 

I have a version of puppetshow that I threw together based off of the
original (minus the hobo and other crazy gems)
I will sanitize it tonight and try to get it on github.
--~--~-~--~~~---~--~~
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 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: exec issue

2009-03-19 Thread jrojas 

You have to escape the dollar signs or quote the text specifically.
Otherwise puppet will assume that:
$1$HvjTWzzz$jF.G/mEbh7IOtpCdUPUTO1 pt_
will break up into the following variables:
$1
$HvjTWzzz
$jF

Which is why you get the weird line.
--~--~-~--~~~---~--~~
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 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: multiple file sources for a file

2009-01-20 Thread jrojas 


file {

apache-config:
  source = puppet://$puppetserver/files/etc/apache2/sites-
available/${name},
  recurse = true;
}


http://reductivelabs.com/trac/puppet/wiki/TypeReference#id348

recurse

Whether and how deeply to do recursive management. Valid values are
true, false, inf. Values can also match /^[0-9]+$/.

-Jason
On Jan 20, 2:03 pm, robertpluss robert.pl...@gmail.com wrote:
 Hi All

 I would like to define multiple file sources for a file but with more
 than one of content, source, target!

 The goal is to have a template by default for a file but if a specific
 source file exists for it, then use this source, first.

 something like:

  source = [
                    puppet://$puppetserver/files/etc/apache2/sites-
 available/${name}/${hostname},
                    puppet://$puppetserver/files/etc/apache2/sites-
 available/${name}/default,
                    template(apache2/server_virtual_typo3.erb),  #
  ],

 This get an error!
 warning: Configuration could not be instantiated: You cannot specify
 more than one of content, source, target at ...
 OK I understand template it's a content target. But we can not define
 multiple target in one  File definition! ( source = [ ... ] , content
 = template )

 How can i solve this problem ?

 Thanks in advanced

 Gilbert
--~--~-~--~~~---~--~~
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 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: custom fact in kickstart postisntall

2009-01-16 Thread jrojas 

Try adding --factsync to the puppetd line.
Does your puppet.conf include factsync = true? that would explain it
working a second time and not a first (sort of)
-Jason


On Jan 12, 9:03 am, Arnau Bria arnaub...@pic.es wrote:
 Hi all,

 I have a custom fact which determines what interface is primary in
 future bonding:
 It works fine when I run puppet for second time:

 #  /usr/bin/ruby /usr/sbin/puppetd --server=gridinstall.pic.es 
 --logdest=/var/log/puppet/puppet.log --test
 info: Retrieving plugins
 notice: /File[/var/lib/puppet/lib/facter]/ensure: created
 notice: /File[/var/lib/puppet/lib/facter/primaryint.rb]/ensure: created
 info: Loading fact primaryint

 And then, I add some line in /etc/modprobe.conf:
 notice: 
 /:main/Node[td234.pic.es]/worker_node/bond/Line[options]/Exec[/bin/echo 
 'options bonding mode=1 primary=eth0 miimon=100'  
 '/etc/modprobe.conf']/returns: executed successfully
 info: /:main/Node[td234.pic.es]/worker_node/bond/Line[options]/Exec[/bin/echo 
 'options bonding mode=1 primary=eth0 miimon=100'  '/etc/modprobe.conf']: 
 Scheduling refresh of Service[network]

 As you can see, all works fine for the second time, but when running
 that line from kickstart postinstall I see no refernce to primaryint
 and the line is filled up with empty value:

 This is the line I have in my postintakll:
 /usr/bin/ruby /usr/sbin/puppetd --server=gridinstall.pic.es 
 --logdest=/var/log/puppet/puppet.log --test --fqdn $1  
 /root/postinstall_puppet.log

 and grepping log file:
 [r...@td065 ~]# grep primaryint.rb postinstall_puppet.log
 [r...@td065 ~]#

 then, the line is filled with nothing:

 #cat /etc/modprobe.conf
 [...]
 options bonding mode=1 primary= miimon=100

 and after second run, is filled again with correct value:

 #cat /etc/modprobe.conf
 [...]
 options bonding mode=1 primary= miimon=100
 options bonding mode=1 primary=eth1 miimon=100

 Is there any limitation when running custom facts?

 Cheers,
 Arnau
--~--~-~--~~~---~--~~
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 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: puppetshow with puppetmaster 0.24.6

2009-01-16 Thread jrojas 

Good. I am glad someone else has had the problem. I think I am going
to start beating on this with a hammer until it works :P

On Jan 16, 2:47 pm, Scott scott...@gmail.com wrote:
 I had the exact same problem (the exceptions in pagination and search)
 and gave up because it's not being developed at all and probably works
 on much older versions of puppet.

 Scott

 On Jan 15, 2:49 am, jrojas jason.r.ro...@gmail.com wrote:

  Sorry if I am re-hashing this but this error is bugging the piss out
  of me, first of the details:

  My gems:
  actionmailer (2.0.2)
  actionpack (2.0.2)
  activerecord (2.0.2)
  activeresource (2.0.2)
  activesupport (2.0.2)
  daemons (1.0.10)
  fastthread (1.0.1)
  gem_plugin (0.2.3)
  hobofields (0.7.5)
  hobosupport (0.8.5)
  mysql (2.7)
  passenger (2.0.6)
  rack (0.9.1)
  rake (0.8.3)
  sources (0.0.1)

  I agree that it does work (to an extent) with the above gems.
  However, certain parts of it are not functioning (pagination and
  search)

  Here is the ugly error:

  NameError (undefined local variable or method `superclass' for
  #HostsController:0x2d7addc0):
      /vendor/plugins/hobo/lib/hobo/model_controller.rb:523:in
  `not_found'
      /vendor/rails/actionpack/lib/action_controller/rescue.rb:189:in
  `call'
      /vendor/rails/actionpack/lib/action_controller/rescue.rb:189:in
  `rescue_action_with_handler'
      /vendor/rails/actionpack/lib/action_controller/rescue.rb:201:in
  `perform_action_without_caching'
      /vendor/rails/actionpack/lib/action_controller/caching.rb:678:in
  `passenger_orig_perform_action'
      /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/
  connection_adapters/abstract/query_cache.rb:33:in `cache'
      /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/
  query_cache.rb:8:in `cache'
      /vendor/rails/actionpack/lib/action_controller/caching.rb:677:in
  `passenger_orig_perform_action'
      /usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/railz/
  request_handler.rb:53:in `perform_action'
      /vendor/rails/actionpack/lib/action_controller/base.rb:524:in
  `send'
      /vendor/rails/actionpack/lib/action_controller/base.rb:524:in
  `process_without_filters'
      /vendor/rails/actionpack/lib/action_controller/filters.rb:685:in
  `process_without_session_management_support'
      /vendor/rails/actionpack/lib/action_controller/
  session_management.rb:123:in `process'
      /vendor/rails/actionpack/lib/action_controller/base.rb:388:in
  `process'
      /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:
  171:in `handle_request'
      /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:
  115:in `dispatch'
      /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:
  126:in `dispatch_cgi'
      /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:9:in
  `dispatch'
      /usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/railz/
  request_handler.rb:38:in `process_request'
      /usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/
  abstract_request_handler.rb:165:in `main_loop'
      /usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/railz/
  application_spawner.rb:321:in `start_request_handler'
      /usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/railz/
  application_spawner.rb:282:in `handle_spawn_application'
      /usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/utils.rb:
  163:in `safe_fork'
      /usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/utils.rb:
  161:in `fork'
      /usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/utils.rb:
  161:in `safe_fork'
      /usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/railz/
  application_spawner.rb:280:in `handle_spawn_application'
      /usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/utils.rb:
  163:in `safe_fork'
      /usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/utils.rb:
  161:in `fork'
      /usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/utils.rb:
  161:in `safe_fork'
      /usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/railz/
  application_spawner.rb:279:in `handle_spawn_application'
      /usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/
  abstract_server.rb:317:in `__send__'
      /usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/
  abstract_server.rb:317:in `main_loop'
      /usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/
  abstract_server.rb:168:in `start_synchronously'
      /usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/
  abstract_server.rb:135:in `start'
      /usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/
  abstract_server.rb:112:in `fork'
      /usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/
  abstract_server.rb:112:in `start'
      /usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/railz/
  application_spawner.rb:179:in `start'
      /usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/
  spawn_manager.rb:222

[Puppet Users] Re: puppetshow with puppetmaster 0.24.6

2009-01-14 Thread jrojas 

Sorry if I am re-hashing this but this error is bugging the piss out
of me, first of the details:

My gems:
actionmailer (2.0.2)
actionpack (2.0.2)
activerecord (2.0.2)
activeresource (2.0.2)
activesupport (2.0.2)
daemons (1.0.10)
fastthread (1.0.1)
gem_plugin (0.2.3)
hobofields (0.7.5)
hobosupport (0.8.5)
mysql (2.7)
passenger (2.0.6)
rack (0.9.1)
rake (0.8.3)
sources (0.0.1)

I agree that it does work (to an extent) with the above gems.
However, certain parts of it are not functioning (pagination and
search)

Here is the ugly error:

NameError (undefined local variable or method `superclass' for
#HostsController:0x2d7addc0):
/vendor/plugins/hobo/lib/hobo/model_controller.rb:523:in
`not_found'
/vendor/rails/actionpack/lib/action_controller/rescue.rb:189:in
`call'
/vendor/rails/actionpack/lib/action_controller/rescue.rb:189:in
`rescue_action_with_handler'
/vendor/rails/actionpack/lib/action_controller/rescue.rb:201:in
`perform_action_without_caching'
/vendor/rails/actionpack/lib/action_controller/caching.rb:678:in
`passenger_orig_perform_action'
/usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/
connection_adapters/abstract/query_cache.rb:33:in `cache'
/usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/
query_cache.rb:8:in `cache'
/vendor/rails/actionpack/lib/action_controller/caching.rb:677:in
`passenger_orig_perform_action'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/railz/
request_handler.rb:53:in `perform_action'
/vendor/rails/actionpack/lib/action_controller/base.rb:524:in
`send'
/vendor/rails/actionpack/lib/action_controller/base.rb:524:in
`process_without_filters'
/vendor/rails/actionpack/lib/action_controller/filters.rb:685:in
`process_without_session_management_support'
/vendor/rails/actionpack/lib/action_controller/
session_management.rb:123:in `process'
/vendor/rails/actionpack/lib/action_controller/base.rb:388:in
`process'
/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:
171:in `handle_request'
/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:
115:in `dispatch'
/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:
126:in `dispatch_cgi'
/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:9:in
`dispatch'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/railz/
request_handler.rb:38:in `process_request'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/
abstract_request_handler.rb:165:in `main_loop'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/railz/
application_spawner.rb:321:in `start_request_handler'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/railz/
application_spawner.rb:282:in `handle_spawn_application'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/utils.rb:
163:in `safe_fork'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/utils.rb:
161:in `fork'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/utils.rb:
161:in `safe_fork'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/railz/
application_spawner.rb:280:in `handle_spawn_application'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/utils.rb:
163:in `safe_fork'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/utils.rb:
161:in `fork'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/utils.rb:
161:in `safe_fork'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/railz/
application_spawner.rb:279:in `handle_spawn_application'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/
abstract_server.rb:317:in `__send__'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/
abstract_server.rb:317:in `main_loop'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/
abstract_server.rb:168:in `start_synchronously'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/
abstract_server.rb:135:in `start'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/
abstract_server.rb:112:in `fork'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/
abstract_server.rb:112:in `start'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/railz/
application_spawner.rb:179:in `start'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/
spawn_manager.rb:222:in `spawn_rails_application'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/
spawn_manager.rb:217:in `synchronize'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/
spawn_manager.rb:217:in `spawn_rails_application'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/
spawn_manager.rb:126:in `spawn_application'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/
spawn_manager.rb:251:in `handle_spawn_application'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/
abstract_server.rb:317:in `__send__'
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.6/lib/passenger/

[Puppet Users] Re: puppetrun

2008-11-25 Thread jrojas 

You need to configure your puppetd to listen.
If it is not listening then it wont let puppetrun happen.

Look at this page:

http://reductivelabs.com/trac/puppet/wiki/NameSpaceAuth


puppetd must be started with --listen, and namespaceauth.conf needs to
know who the puppetmaster is.


-Jason
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: notify and reload

2008-11-25 Thread jrojas 



in your case you may want to define the service like so:


  service {

your_service:
  ensure = running,
  enable = true,
  restart = your restart command here,
  subscribe = File[config file];
  }

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: cron type with UID conflicts

2008-11-25 Thread jrojas 

That is a tough one, try creating your own custom type as a monkey
patch.

What happens if you add a user = root to your manifest for the cron
entry?

-Jason
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Two files with no change trying to be modified

2008-11-25 Thread jrojas 

The first part I am not sure on, the second part is interesting.
Net-SNMP always does weird things.
Can you get a diff of the two files?
notice: checksum changed '{md5}2bae7729229cff023cb03b0377cd7088' to
'{md5}0e86c2e3ca02312e61f477528bcfaf64'


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---