Hi - further, I found another error more helpful on this: An input has failed to start (triggered in 8 hours) Input 58824501d7a3bd5096cf8dc9 has failed to start on node b4803a74-6842-49dd-84b1-bc6a9a7b2504 for this reason: »Permission denied.«. This means that you are unable to receive any messages from this input. This is mostly an indication for a misconfiguration or an error. You can click here <http://10.208.0.64:9000/system/inputs> to solve this.
On Fri, Jan 20, 2017 at 5:42 PM, Jason Fuller <[email protected]> wrote: > Hi Richard, > > - allow_override_date: > true > - bind_address: > 10.10.0.64 <---- I also tried 0.0.0.0 and 127.0.0.l > - expand_structured_data: > true > - force_rdns: > true > - override_source: > *<empty>* > - port: > 514 > - recv_buffer_size: > 262144 > - store_full_message: > true > > > On Fri, Jan 20, 2017 at 5:30 PM, Richard S. Westmoreland < > [email protected]> wrote: > >> What port are you trying to use? >> >> >> On Jan 20, 2017, at 6:15 PM, JayJay <[email protected]> wrote: >> >> Hi, >> >> I have GrayLog setup on CentOS7. >> I tried to setup an UDP Syslog input, and after setup, it eventually says >> "failed". I searched the logs, and didn't see much. >> >> I do see "failed" in the main log.... >> at org.jboss.netty.channel.Channels.bind(Channels.java:561) >> ~[graylog.jar:?] >> at >> org.jboss.netty.channel.AbstractChannel.bind(AbstractChannel.java:197) >> ~[graylog.jar:?] >> at >> org.jboss.netty.bootstrap.ConnectionlessBootstrap.bind(ConnectionlessBootstrap.java:198) >> ~[graylog.jar:?] >> at >> org.graylog2.plugin.inputs.transports.NettyTransport.launch(NettyTransport.java:136) >> ~[graylog.jar:?] >> at >> org.graylog2.plugin.inputs.MessageInput.launch(MessageInput.java:153) >> ~[graylog.jar:?] >> ... 7 more >> 2017-01-21T01:16:49.617+08:00 INFO [InputStateListener] Input [Syslog >> UDP/58824501d7a3bd5096cf8dc9] is now FAILED >> >> >> What should I be looking for? >> >> Thanks! >> >> -- >> 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/ms >> gid/graylog2/2b4a7f4d-0611-4da1-9e2e-df5879e128b3%40googlegroups.com >> <https://groups.google.com/d/msgid/graylog2/2b4a7f4d-0611-4da1-9e2e-df5879e128b3%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Graylog Users" group. >> To unsubscribe from this topic, visit https://groups.google.com/d/to >> pic/graylog2/1MF1mFj6EhQ/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To view this discussion on the web visit https://groups.google.com/d/ms >> gid/graylog2/49AB95C7-1BE4-4BA4-A0CC-64CBBC18CDF5%40gmail.com >> <https://groups.google.com/d/msgid/graylog2/49AB95C7-1BE4-4BA4-A0CC-64CBBC18CDF5%40gmail.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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/CAGUPOFsTtgPoJHRh-vPKXL1fTRfibHdvn6qCZVdJWb07geaPbw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
