Oh, never mind. I completely mis-read the post.
On Tue, Nov 24, 2015 at 2:20 PM, Joi Owen <[email protected]> wrote: > The latest release of the Graylog packages has graylog running as a > non-root user, and such user can't open port 514 for listening. It can't > create an input on that port but it isn't good about alerting you to this > fact. > > What we did was create a UFW rule to forward incoming port 514 to 10514, > and then create a graylog input to listen on port 10514 instead. > > It would be nice if inputs could be configured and created before dropping > root privs, but then you'd have to bounce the whole graylog-server service > to configure inputs listening below 1024. (Rather like how rsyslog handles > it on Ubuntu.) > > > On Tue, Nov 24, 2015 at 12:45 PM, HockeyFan0000 <[email protected] > > 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/64aec5d1-2424-43f5-891d-6ab690a9997a%40googlegroups.com >> <https://groups.google.com/d/msgid/graylog2/64aec5d1-2424-43f5-891d-6ab690a9997a%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > > No matter what we think of Linux versus FreeBSD, etc., the one thing I > really like about Linux is that it has Microsoft worried. Anything > that kicks a monopoly in the pants has got to be good for something. > - Chris Johnson > > -- No matter what we think of Linux versus FreeBSD, etc., the one thing I really like about Linux is that it has Microsoft worried. Anything that kicks a monopoly in the pants has got to be good for something. - Chris Johnson -- 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/CAL5rfGW37exd8t-eFsv8n56ABBqbeQDMyXYx24MYhyBLdbS2yA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
