> I don't think you need to see it. Take a look at this... This might
> actually be a redhat bug.
For what it's worth, this all works great in sles (at least sles 11 -
haven't checked elsewhere):
uldbdb204e:/etc/rc.d # chkconfig snmpd
snmpd on
uldbdb204e:/etc/rc.d # find . -name '*snmpd*'
./rc3
>> the only thing i found is the zypper.rb on
>> http://projects.reductivelabs.com/attachments/393
>> which i copied to /usr/lib/ruby/1.8/puppet/provider/package
One other thing. I used the zypper.rb from here:
http://groups.google.com/group/puppet-dev/browse_thread/thread/986b51b5b1691a5?pli=1
> i'd like to manage my opensuse 11.1 systems with puppet and zypper.
> the requirements are the manage the repos and install packages.
I've just begun work on a new custom type that is aimed at managing
zypper repos. Unfortunately I'm not very far along, but I'll
certainly let you know when I h
I'm having trouble getting a simple custom type to work.
Clients are giving me the following error:
"Could not retrieve catalog: Could not find resource type zypper_repo
at /etc/puppet/manifests/nodes/mgt.pp:33 on node "
The custom type is present in the /var/lib/puppet/lib/puppet/type
directory
> Ok - so the error occurs if the file already exists. I modified my
> test file, restarted, and I now get the same error:
> Sep 2 15:20:09 vm1 puppetd[3205]: (//Node[default]/baseclass/testfile/
> File[/tmp/testfile.txt]/source) change from {md5}
> f47c75614087a8dd938ba4acff252494 to puppet:///
> Looks like it's retrieving and diff'ing the file, but not writing it.
That's probably because the certificate is not trusted. Can you try
the following (in this order):
on the client:
rm -rf /var/lib/puppet/ssl/*
on the server:
puppetca --clean vm2.guilty.com
on the client:
/usr/sbin/puppet
> Any ideas? This configuration seems pretty dead simple and it is half
> working, it's just not serving files. I am using puppet 0.24.8-1 on
> CentOS 5.3 from the epel yum repository.
Do you have a CNAME record for "puppet" in DNS? If not, try adding a
hosts entry called "puppet" to your host
> You can see my settings in the above pastie, Apache starts fine and
> appears to function fine. However when I run puppetd --test on any node
> I receive the following error:
>
> warning: Certificate validation failed; consider using the certname
> configuration option
> err: Could not retrieve
> I'm new with Puppet and as far as I have searched I couldn't find a
> very good solution for updating some machines over the network. I
I think that many on the list feel that you should use the correct
tool for the job here, which in your case sounds like an apt-get or
equivalent via cron. I
If you're using multiple puppet servers, be sure that you're talking
to the right one.
I mistakenly left a "puppet" CNAME entry in DNS that pointed to my
test layer puppet server, and that caused the same error. This
occurred even though I explicitly defined the puppet server in
puppet.conf as "
> Are the opensuse repositories basically identical to the SLES repos?
Note the following from the release notes of SLES11:
The puppet tools shipped with SUSE Linux Enterprise Server 11 are a
Technology Preview.
That being said, according to the package list for SLES11 (available
here:
http://
I currently manage approximately 150 hosts with a handful of ZLM policies,
but I've had one too many policies lost by the management server to keep
using this solution.
I'm wondering if anyone has any experiences (good or bad) they'd be
willing to share specific to using Puppet with SLES (9 and
12 matches
Mail list logo
