You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.
Nagios status files could contain '\n' in long_plugin_output field. Those values are interpreted as line breaks by the status parser, which leads to plugin output info after '\n' to being processed by the parser as key=value data and all kinds of weird errors being thrown.
Example status:
servicestatus {
long_plugin_output=foo\nbar\n
}
Throws an exception:
/usr/lib64/ruby/1.9.1/racc/parser.rb:351:in `on_error': (Racc::ParseError)
parse error on value "bar" (VALUE)
from (eval):3:in `_racc_do_parse_c'
from (eval):3:in `do_parse'
from parser.y:78:in `parse'
from parser.y:72:in `parse'
from ./nagios-status-failure.rb:13:in `<main>'
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Nagios status files could contain '\n' in long_plugin_output field. Those values are interpreted as line breaks by the status parser, which leads to plugin output info after '\n' to being processed by the parser as key=value data and all kinds of weird errors being thrown.
Example status:
Throws an exception:
The text was updated successfully, but these errors were encountered: