similar to: bug or behavior change?

Hello... I am trying to switch to mongrel from webrick to get rid of the . puppetmaster is FreeBSD 6.2 with ruby, puppet, and mongrel all from ports (latest as of this morning). I get "Server is not a class". --verbose, --debug do not spit out any useful info. puppet-0.22.4 ruby-1.8.6.111_1,1 ruby18-bdb46-0.6.2 ruby18-gems-0.9.4 rubygem-daemons-1.0.8 rubygem-fastthread-1.0

hi,guys I''m test the resources export and collect , OS is Debian etch and sarge, puppet server and client version all of the 0.23.2 ; the db is MySQL-4.1 My test code is like this. node ''b'' { @@file {"/tmp/a": ensure => present ,content => "test"; } } node ''a'' { File <<||>> } I run puppetd on

On Friday 05 October 2007 03:54, puppet wrote: > #829: Multiple source with recursion error > -----------------------------+--------------------------------------------- >- Reporter: paul | Owner: michael > Type: defect | Status: closed > Priority: normal | Milestone: unplanned > Component: library |

Hi Puppeteers! I''ve been using puppet for a little over a half year, and I''m very pleased with it. Until recently, I couldn''t get reporting to work, but after finding the culprit, it works just fine. Every day Puppet reports lines like the following: Tue Jul 31 04:37:49 +0200 2007 //debian_base_sarge/

Hi all, We''re getting close to release[1], so I''d appreciate it if people would start testing the current ''master'' branch with their repositories. I made quite a few internal changes, most of which shouldn''t even be noticed unless there are bugs, so just running a server and/or client under the current code would be a big help. I''m

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all There is some discussion of doing a 0.23.3 release to backport a number of bugs fixes from 0.24.0. What do people think of this idea? Would you prefer a dot upgrade to 0.23.3 or are most planning to upgrade cleanly to 0.24.x? I understand from Luke that 0.24.1 will be released shortly and that 0.23.2 clients should cleanly connect and

So I''ve done some Mac OS X pkgs for the latest Facter and Puppet, as well as a combined mpkg for them both. Jeff McCune and I are doing a fair bit of testing on them this week in preparation for MacWorld, so I wasn''t going to upload them to the official site for another few days, but they''re looking pretty good. http://explanatorygap.net/puppet/Facter_1.3.8.pkg.zip

i was looking at the simple text recipes wiki: http://reductivelabs.com/trac/puppet/wiki/SimpleTextRecipes and based on that wrote something that can ensure a certain variable in a config file is set to a specific value, using a specific delimiter as requested (defaults to a space). this seems to work great at managing all sorts of unix and mac config files (sshd_config, hostconfig on macs).

Hi, I''m getting a "Could not retrieve dependency" error and I can''t figure why. Someone got a cluestick for me? I''m using the following simplified configuration to ensure sshd is running and gets reloaded when the config file changes: ---- site.pp ---- import "classes/sshd.pp" node obsd42 { include ssh-server } node debian40 { include

I just upgraded from 0.23.2-1 on RHEL 4&5 to 0.24.1-1. I used Dlutter''s repository. What a mess I''m in now. Anyway to make a long story short I moved all of the old configs out of the way (/etc/puppet, /var/lib/puppet) and started over with a fresh install. I can''t get puppetd on the server to request a cert. If I do a "puppetd -v --waitforcert 90" the

Can anyone who''s having this problem please send details? I''m trying to reproduce it -- I''ve got 5 clients concurrently retrieving 200 10k files made of random binary, and I can''t get any corruption or memory growth at all. Is everyone experiencing the problem using Mongrel? Webrick? What versions of ruby? Are only big files affected? Small files?

Can anyone help me with this error I am having. I am using puppet on Debian Etch, version 0.20.1-1 from apt works OK, but due to one or two problems we want to use the version from testing, 0.23.2-10, but the puppetd just fails upon startup spitting this out: Starting puppet configuration management tool/usr/lib/ruby/1.8/timeout.rb:54:in `open'': execution expired (Timeout::Error)

I''m thinking about how to set up the processes for Production puppet runs now. Being ultra-conservative here, we''d like to see what would happen before pressing the red button. I can run in noop mode, and everything is evaluated but nothing is done. A YAML report magically appears on the Puppetmaster which my script parses and spits out something the management can read

i''m having trouble with a file resource with 0.24.1. the manifest is very simple: file { "/": ensure => directory, owner => "root", group => "root", mode => 755 } when i run puppetd, i get the attached stack trace. removing this resource enables puppetd to complete its run successfully. any ideas? didn''t have this

Hi all, I''ve just merged in support for builtin Nagios types into the 0.24.x branch, and I''d like people to give them a once-over before I incorporate them into a release (based on a few (hopefully small) outstanding bugs in 0.24.1, I expect I''ll put out a 0.24.2 in the next week or so). The only thing I''d currently consider a gotcha right now is that

Hi all, As promised, 0.24.1 is out. Here''s the changelog: Updated vim filetype detection. (#900 and #963) Default resources like schedules no longer conflict with managed resources. (#965) Removing the ability to disable http keep-alive, since it didn''t really work anyway and it should no longer be necessary. Refactored http keep-alive so

I am creating a model attempting to predict the probability someone will reoffend after being caught for a crime. There are seven total inputs and I planned on using a logistic regression. I started with a null deviance of 182.91 and ended up with a residual deviance of 83.40 after accounting for different interactions and such. However, I realized after that my code is different from that in

Hi, While i''ve read the wiki page on development of custom providers ( http://www.reductivelabs.com/trac/puppet/wiki/ProviderDevelopment), i cannot find information on where the custom provider''s source file should be located. My little provider works fine if i copy it to /usr/lib/ruby/site_ruby/1.8/puppet/provider/package but i''d prefer to keep that in tact from the

Hi All, After trying several times to fix this problem, I give up. I can''t seem to upgrade puppet/puppetmaster to 0.24.1. I''ve just downgraded to 0.23.2 on the puppetmaster, as it was the last working version for me. I''ve tried both upgrading the server first and the client first and both. But when upgrading only the server, none of my clients can get a

Hello- I have a dataset which basically looks like this: Location Sex Date Time Verbal Self harm Violence_objects Violence A 1 1-4-2007 1800 3 0 1 3 A 1 1-4-2007 1230 2 1 2 4 D 2 2-4-2007 1100 0