John Naggets
2013-Dec-14 14:59 UTC
[Puppet Users] err: Could not send report: Error 400 on SERVER: (<unknown>): found character that cannot start any token while scanning for the next token
Hi, On some of my puppet agents at each puppet agent run I get the following error message: err: Could not send report: Error 400 on SERVER: (<unknown>): found character that cannot start any token while scanning for the next token at line 1519 column 14 I believe the agent has some issues here sending the report to the puppet dashboard but I can''t find what is the issue. Does anyone have an idea? Also which file exactly is this error message referring to (line 1519 column 14)? Thanks John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/9f94273c-da4b-4ce4-ac91-b8e00b23f26c%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Charlie Sharpsteen
2013-Dec-15 07:06 UTC
[Puppet Users] Re: err: Could not send report: Error 400 on SERVER: (<unknown>): found character that cannot start any token while scanning for the next token
On Saturday, December 14, 2013 6:59:22 AM UTC-8, John Naggets wrote:> > Hi, > > On some of my puppet agents at each puppet agent run I get the following > error message: > > err: Could not send report: Error 400 on SERVER: (<unknown>): found > character that cannot start any token while scanning for the next token at > line 1519 column 14 > > I believe the agent has some issues here sending the report to the puppet > dashboard but I can''t find what is the issue. Does anyone have an idea? > Also which file exactly is this error message referring to (line 1519 > column 14)? > > Thanks > John >Hi John, This error is thrown by the Ruby YAML parser when it encounters a malformed YAML document (such as a report) that cannot be loaded. It looks like the report is being sent fine, but the YAML parser in the receiving dashboard is throwing an error. A copy of the report the agent was attempting to send can usually be found in /var/lib/puppet/state/last_run_report.yaml --- this is the file that the line and column numbers relate to. Hope this is helpful! -- Charlie Sharpsteen Open Source Support Engineer Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/98d78d4b-1f03-40bb-8fcc-6c8c9acc7a9d%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
John Naggets
2013-Dec-18 12:55 UTC
[Puppet Users] Re: err: Could not send report: Error 400 on SERVER: (<unknown>): found character that cannot start any token while scanning for the next token
Hi Charlie, Thanks for helping out here. I checked the /var/lib/puppet/state/last_run_report.yaml file but unfortunately there are no such files. I also tried running puppet agent --noop --test --verbose but it does not provide any more information relevant to this issue. I am using Debian 7 with its standard puppet packages. You have any other idea what I could check? Somehow I have the feeling this is related to the puppetlabs-mysql module as all the nodes failing to send the report to the dashboard are those which use this module. Cheers John On Sunday, December 15, 2013 8:06:34 AM UTC+1, Charlie Sharpsteen wrote:> > On Saturday, December 14, 2013 6:59:22 AM UTC-8, John Naggets wrote: >> >> Hi, >> >> On some of my puppet agents at each puppet agent run I get the following >> error message: >> >> err: Could not send report: Error 400 on SERVER: (<unknown>): found >> character that cannot start any token while scanning for the next token at >> line 1519 column 14 >> >> I believe the agent has some issues here sending the report to the puppet >> dashboard but I can''t find what is the issue. Does anyone have an idea? >> Also which file exactly is this error message referring to (line 1519 >> column 14)? >> >> Thanks >> John >> > > Hi John, > > This error is thrown by the Ruby YAML parser when it encounters a > malformed YAML document (such as a report) that cannot be loaded. It looks > like the report is being sent fine, but the YAML parser in the receiving > dashboard is throwing an error. A copy of the report the agent was > attempting to send can usually be found in > /var/lib/puppet/state/last_run_report.yaml --- this is the file that the > line and column numbers relate to. > > Hope this is helpful! > > -- > Charlie Sharpsteen > Open Source Support Engineer > Puppet Labs >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/b3aadfac-b806-45f1-bbe6-f28f42d1143f%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.