On Monday, October 26, 2015 at 11:38:52 AM UTC-5, Jochen Schalanda wrote: > > Hi, > > syslog-ng should support reloading (instead of restarting) by sending a > simple SIGHUP to the syslog-ng process, e. g. by running kill -s HUP > $(cat /var/run/syslog-ng.pid) > > Hi Jochen,
Sorry I didn't explain myself clearly. My goal is to not having graylog2-sever bind to udp/tcp 514 since my syslog-ng server is using them already. I am look for a way to have syslog-ng send logs graylog2 server for processing, using port above 1024. Is this doable ? > > Cheers, > Jochen > > On Monday, 26 October 2015 13:17:48 UTC+1, T.J. Yang wrote: >> >> >> Hi >> >> This is a beginner question. >> >> R1 <http://docs.graylog.org/en/1.2/pages/sending_data.html#syslog> >> instruction is assuming graylog2-sever use authbind like mechanism to bind >> to port 514 and has syslog content pack installed. >> Without stopping my local syslog-ng server, I am hoping to send incoming >> message to graylog2 server beside store it locally. >> >> >> [root@syslog1 conf.d]# cat storelocal.conf >> # from syslog clients >> source s_logclients { >> udp(ip(0.0.0.0) port(514)); >> tcp(ip(0.0.0.0) port(514)); >> }; >> >> # store it locally with time stamp as file names. >> destination d_loglocal { >> file( >> "/var/log/remote/$HOST.${YEAR}_${MONTH}_${DAY}.log" >> perm(644) >> create_dirs(yes) >> ); >> }; >> >> log { source(s_logclients); destination(d_loglocal); }; >> >> [root@syslog1 conf.d]# >> >> >> R1: http://docs.graylog.org/en/1.2/pages/sending_data.html#syslog >> > -- 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/4229c564-d7aa-4a56-aacd-63432c9372bf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
