search for: willingmind

...rd logs since upgrading: puppetmasterd[7943]: Could not call: nested *?+ in regexp: /^\/var\/www\/html\/download\/NSClient++-0.2.7.zip/ Seems like the data passed should have RE characters quoted (ala \Q...\E in Perl) prior to this test. Regards, Mark -- Mark D. Nagel, CCIE #3177 <mnagel@willingminds.com> Principal Consultant, Willing Minds LLC (http://www.willingminds.com) cell: 949-279-5817, desk: 714-630-4772, fax: 949-623-9854 *** Please send support requests to support@willingminds.com! ***

...d. When I do, I get: ----- The following addresses had permanent fatal errors ----- <trac@reductivelabs.com> (reason: 550 5.1.1 <trac@reductivelabs.com>: Recipient address rejected: User unknown in local recipient table) Regards, Mark -- Mark D. Nagel, CCIE #3177 <mnagel@willingminds.com> Principal Consultant, Willing Minds LLC (http://www.willingminds.com) cell: 949-279-5817, desk: 714-630-4772, fax: 949-623-9854 *** Please send support requests to support@willingminds.com! ***

...is is related to file copy actions -- we copy a few large-ish directories that way (SNMP MIB files, for example). I''m not quite sure where to start digging to find the cause, so if anyone has any ideas, I''d appreciate it. Thanks, Mark -- Mark D. Nagel, CCIE #3177 <mnagel@willingminds.com> Principal Consultant, Willing Minds LLC (http://www.willingminds.com) cell: 949-279-5817, desk: 714-630-4772, fax: 949-623-9854 *** Please send support requests to support@willingminds.com! ***

...aced with the empty string. This is 0.22.2. Is it just that the value is not available yet at that point in argument binding, or is this just unreasonable? I am going to try another method, but was curious whether this ought to work at all. Thanks, Mark -- Mark D. Nagel, CCIE #3177 <mnagel@willingminds.com> Principal Consultant, Willing Minds LLC (http://www.willingminds.com) cell: 949-279-5817, desk: 714-630-4772, fax: 949-623-9854

Hello there, Since the update with ruby all my puppet function is dead (well known issue with the cert) . There has been some discutions on the dev list on how to patch this for future versions. I have read the list and wondered how we can solve the issue while waiting for the .24. I am in beta test of the .23.x version but on my production system i wanted to find a way to solve this now

Is it possible to have a file copied from the fileserver but only when it doesn''t exist? I want to prevent changes on the client from being wiped out if it is different. We have a couple of config files that the DBAs are resistant to managing through puppet. They currently manually deploy changes and I don''t want those changes wiped out if the server isn''t updated. I

...entos: { Package { type => yum } } } Assuming that works, I''m good, just curious why this should be necessary given the statement in the type docs, and more importantly, why does the decision change from run to run? Thanks, Mark -- Mark D. Nagel, CCIE #3177 <mnagel@willingminds.com> Principal Consultant, Willing Minds LLC (http://www.willingminds.com) cell: 949-279-5817, desk: 714-630-4772, fax: 949-623-9854

Hi, This is totally off-topic (it''s an rpm/rpmbuild problem), but I want to get to a point where I''m installing and configuring munin-node with puppet. To do that, I need a clean, standardized way of installing munin-mode on CentOS (RHELish) boxes. I could install munin-node from source via puppet and probably make enough edits that all the files end up in reasonable locations

In the normal override method, you can change the value of a parameter, but can you unset a parameter? file { "/etc/somefile": mode => 644, owner => "dude" } File ["/etc/somefile"] { mode => unset } ??

I am trying to wrap my head around using templates and was wondering what the execution context was, puppetmaster or client? I thought it was client since it would have to also account for facter-based variables, but recent testing on something I thought was pretty neat turned out to cause puppetmaster to segfault in an apparent attempt to evaluate the template on the server side. The

I updated to 0.22.3-1 from the dlutter repo (CentOS 4.4) and I''m still having trouble adding new nodes as others saw from the previous version, though I believe the error is different now. The procedure I used was: <client> /etc/init.d/puppet once -v <server> /usr/sbin/puppetca --sign nodename <client> /etc/init.d/puppet once -v This used to work for new nodes, now I