On Feb 22, 2011, at 12:06 AM, donavan wrote: > On Feb 15, 5:21 pm, Patrick <kc7...@gmail.com> wrote: >> Does anyone have a guess if this bug is in the client, the master, or >> dashboard? My report value is "reports = http, store". If the error was >> originally from dashboard, would the master have failed to save the file >> because the order matters? > > I've seen this previously. I ended up noticing this in interactive > tests, and when some clients would go "stale". Looking at debug the > error was only with storing the report on the server, the client was > fine otherwise. I only use "reports = http", so I;m not sure if you'd > have the "store" copy. > > Didn't look in much detail as, IIRC, it was fixed shortly after I > noticed. I think it was recently fixed in one of the 2.6.x minor > releases, 2.6.4 maybe?. Looking at changelog would be a good starting > place to narrow it down more. > > Depending on how you run the master (webrick, passenger, etc) you > should have a better error message there. Unfortunately some of the > error logs arent time stamped so it requires guesstimation.
Alright. Thanks. Knowing it's probably fixed makes me feel better about it. -- 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.
