[Puppet Users] install package based on operatingsystem AND operatingsystemrelease

2010-08-11 Thread Jason Amato
How can I create a class to install a RPM based on the o/s type and the o/s release. I want to install a package on SLES, but only if it's release 11, not 10. I can do this, but how do I incorporate the release in here... thanks in advance! class packages1 { $lsb = $operatingsystem ? {

[Puppet Users] Re: clients stopped retrieving catalog - error 403 forbidden request - possible corruption?

2010-05-03 Thread Jason Amato
...and the answer is... http://groups.google.com/group/puppet-dev/msg/b15e1c93bbc70fdb This reverts commit c702f76b271515e9c42dcb923d379fbfac4c83cd and turns it into a documentation only fix. As it turns out, ENV should have never been used at all, as the Rack docs say nothing about it *and*

[Puppet Users] clients stopped retrieving catalog - error 403 forbidden request - possible corruption?

2010-04-29 Thread Jason Amato
All 150 , except two, clients have suddenly stopped retrieving catalogs from the master. Something happened last night, no changes were made. I have been running everything for many months now. Maybe something with the certificates? I can I sync the certs from the master back to the clients?

[Puppet Users] Puppet client - could not parse YAML data

2010-02-01 Thread Jason Amato
Any ideas? Getting this error below from only 2 out of a total of 200 clients... puppetd[26557]: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not parse YAML data for node servername here: syntax error on line 89, col 7: `' Client and Master Puppet versions are .25.1

[Puppet Users] Re: Puppet client - could not parse YAML data

2010-02-01 Thread Jason Amato
solved... Need to remove the server_name.yaml files in /var/puppet/yaml/node and /var/puppet/yaml/facts (or where ever you may have these files, search for them). Then the client will run and the files will get rebuilt. On Feb 1, 11:16 am, Jason Amato amato_ja...@yahoo.com wrote: Any ideas

[Puppet Users] err: Could not call list: header too long

2010-01-27 Thread Jason Amato
Getting this error: err: Could not call list: header too long when running puppetca commands on master. There is not a disk space issue. On the puppet master server, /var filled up to 100% during the night. Now it's fine, down to 25% used. I rebooted server too Any fixes? -- You received this

[Puppet Users] Re: err: Could not call list: header too long

2010-01-27 Thread Jason Amato
some debug info: # puppetca -l -d debug: Failed to load library 'shadow' for feature 'libshadow' debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/ dscl does not exist debug:

[Puppet Users] Re: err: Could not call list: header too long

2010-01-27 Thread Jason Amato
all fixed, had to remove 0 byte file from directory /var/puppet/ssl/ca/requests -- 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: SLES 10 client keeps removing and re-adding accounts to groups

2009-11-25 Thread Jason Amato
Using ralsh led me in the right direction, thanks. SLES (SuSE) complains about this and RHEL does not. If I use ' gid = 100' (which points to group unix) and include that same group in the 'groups = ['staff','unix'] ' list, then SLES complains and acts funny. Removing the group 'unix' from the

[Puppet Users] puppet .25.1 client for rhel4 RPM ?

2009-11-20 Thread Jason Amato
Are there any RPMs available for the Puppet client v .25.0 or .25.1 to run on Red Hat Linux v4? -- 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,

[Puppet Users] Re: Could not find server my.server.name ?

2009-06-26 Thread Jason Amato
Let me answer that... found in site.pp...filebucket option... # The filebucket option allows for file backups to the server filebucket { main: server = 'my.server.name' } --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google