Hi Jason, On Sunday, 22 January 2017 06:19:21 UTC+1, JayJay wrote: > > Changed user to root, restarted server, and the input is starting ok now. >
>From a security perspective, that's a very bad idea and I'd recommend to use one of the other mechanisms described in the documentation: http://docs.graylog.org/en/2.1/pages/faq.html#how-can-i-start-an-input-on-a-port-below-1024 However, when I send test messages to the input, I don't see anything in > input/search window. > How exactly are you sending test messages? 2017-01-22T21:05:47.002+08:00 WARN [NettyTransport] receiveBufferSize > (SO_RCVBUF) for input SyslogUDPInput{title=diskstation, > type=org.graylog2.inputs.syslog.udp.SyslogUDPInput, nodeId=null} should be > 262144 but is 212992. > See https://github.com/Graylog2/documentation/issues/26 I have two choices on my syslog sender: BSD (RFC3164) and IETF (RFC 5424). > Both should work, if the sender adheres to the mentioned RFCs. If you can rule out networking problems (check with Wireshark whether the messages actually reach Graylog), then you can try using a Raw/Plaintext input. Cheers, Jochen -- 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/416fa6b3-d7d9-4b08-81ed-aca77216fdd5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
