Bump
On Feb 15, 2011, at 5:21 PM, Patrick wrote:
> System information:
> Distro: Ubuntu 10.4.x
> Ruby: ruby-enterprise-1.8.7-2010.02
> Puppetmaster: 2.6.1
> Puppetclient: 2.6.1
> Dashboard: 1.0.4-1
>
> I was running a puppet run manually like this:
> # puppetd --test --verbose
>
>
> This is the log for the run:
> notice: Ignoring --listen on onetime run
> info: Retrieving plugin
> info: Caching catalog for simba.extension
> info: Applying configuration version '1297796888'
> notice: /Stage[main]/Remote-access/Sshkey[Client79.extension]/ensure: created
> info: FileBucket adding /etc/ssh/ssh_known_hosts as
> {md5}25a575c5246e1d9835601d2d34c12a1c
> notice: /Stage[main]/Remote-access/Service[ssh]/enable: enable changed
> 'false' to 'true'
> notice: Finished catalog run in 250.02 seconds
> err: Could not send report: Error 400 on SERVER: Could not intern from yaml:
> can't convert Symbol into String
>
> I've never seen this error before or again. That run didn't store the result
> to the master, as http (dashboard) or as a file. Unfortunately, right after
> this happened, I ran another run which worked perfectly, so I don't even have
> a copy of the catalog from the failed run.
>
> 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?
>
> Mostly, this concerns me because the run didn't generated a report, and I
> rely on the reports to tell if stuff stops working, so I won't know if this
> happens again.
--
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.
