Yes.  There is some traffic on that input.  It's collecting about 55k 
messages per minute.  But, it should be much higher than that. It may well 
be missing 50-75% of what should be collected.  Most of my equipment 
doesn't have an option to specify the syslog port, so I'm stuck with port 
514.  I have pointed a few devices to the forwarded port and those messages 
are being collected.  So, some are collected on my DNAT'd port (10514) and 
some are being collected on the normal syslog port.  There is also some 
traffic that is not being collected on both of those ports as well.



On Wednesday, November 25, 2015 at 5:20:20 AM UTC-5, Jochen Schalanda wrote:
>
> Hi,
>
> is there any traffic showing for your Syslog inputs in Graylog? You can 
> check this in the web interface on the System -> Inputs page. Or maybe 
> there simply was an error message that Graylog couldn't start the input on 
> the privileged port (514/udp).
>
> Regarding the privileged port for syslog (514/udp), you can simply use 
> something like authbind (http://packages.ubuntu.com/trusty/authbind) to 
> allow the Java process to bind to a port <1024. The DEB packages already 
> come with support for this (which I'd recommend to install instead of using 
> the manual installation method on Debian or Ubuntu Linux).
>
>
> Cheers,
> Jochen
>
> On Tuesday, 24 November 2015 19:45:54 UTC+1, HockeyFan0000 wrote:
>>
>> I've completed a manual installation using these instructions: 
>> http://www.itzgeek.com/how-tos/linux/ubuntu-how-tos/how-to-install-graylog2-on-ubuntu-14-04.html.
>>  
>> The installation went quickly and was fairly uneventful (no pun intended), 
>> other than a few typos on my part.
>>
>> Everything seems to be running great, there are no Elasticsearch cluster 
>> errors, no failed indexing attempts, CPU is consistently less than 20%, RAM 
>> usage is 4GB (out of 16GB), disk usage is only 4%.  I don't see any signs 
>> that anything is wrong.  I've collected almost 350 million logs in 11 
>> days.  All of the GELF events seem to be collected.  But, many, maybe even 
>> the vast majority, of the plain syslog (UDP port 514) logs seem to be 
>> missing.  I can run a live tcpdump to screen and see the missing logs 
>> arriving to the server.  But they either aren't being collected or aren't 
>> being indexed because I can't find them with a search.  I'm aware that, 
>> with the manual installation, UDP port 514 needs to be forwarded to a 
>> higher port, so I've forwarded that port to UDP port 10514 and that's the 
>> port in my syslog input.
>>
>> I've got 30 wireless APs, an ESX host and a few network switches pointed 
>> to this server, yet the graphs show I'm only collecting about 100 events 
>> per minute.  I've looked in the Graylog and Elasticsearch logs and I don't 
>> see anything that seems remotely related.  Does anyone have any ideas where 
>> these things are going?  Also, is there a way around having to forward port 
>> 514 to another port?  Any help is greatly appreciated.
>>
>

-- 
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/270bd18d-ec9f-43fb-ad12-b15d340178a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to