Also be aware that if you're using the syslog input type and the device doesn't send RFC compliant syslog message format, graylog will silently drop the messages. I front-end syslog into logstash specifically so I have the flexibility to handle non-RFC compliant syslog and still get it into graylog.
On Tuesday, November 8, 2016 at 6:44:23 PM UTC-5, [email protected] wrote: > > Try changing the input port to something higher than 1024. The lower port > requires the graylog service to be running as root, which might be the > cause the failed input. > > See the following for explanation and work around using iptables: > https://groups.google.com/forum/m/#!topic/graylog2/5iLepNboyOI > -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/a0847ace-0df3-4943-8e22-e577234896a6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
