Hi again,
On Mon, Nov 03, 2014 at 04:47:28PM +0100, Evgeni Golov wrote:
Trial-and-error says, removing the following lines helps...
# Graylog2
destination d_graylog2 { udp(192.0.2.91 port(514) spoof_source(yes)); };
log { source(remotesrc); filter(f_cust_prod); destination(d_cust_prod);
Evgeni == Evgeni Golov evg...@debian.org writes:
Evgeni Hi,
Evgeni On Fri, Mar 22, 2013 at 03:59:11PM +0100, Gergely Nagy wrote:
* Fixing the configuration and reloading gets things back in order, no
matter how many times messages were duplicated before.
Evgeni I have a
Hi,
On Fri, Mar 22, 2013 at 03:59:11PM +0100, Gergely Nagy wrote:
* Fixing the configuration and reloading gets things back in order, no
matter how many times messages were duplicated before.
I have a heavily customized config, which does not throw any errors,
but triggers the issue on a
Hi,
On Mon, Nov 03, 2014 at 12:14:02PM +0100, Evgeni Golov wrote:
I have a heavily customized config, which does not throw any errors,
but triggers the issue on a wheezy box.
Trial-and-error says, removing the following lines helps...
# Graylog2
destination d_graylog2 { udp(192.0.2.91
Control: found -1 3.3.5-4
Control: found -1 3.3.6-2
Cye Stoner cye.sto...@echostar.com writes:
When syslog-ng is sent a SIGHUP with the previous configurationin place,
the following errors are thrown to /var/log/messages(in duplicate)
Error in configuration, unresolved source reference;
Package: syslog-ng
Version: 3.3.5-2
When executing the following command to reload the syslog-ng
configuration file:
# kill -HUP $(cat /var/run/syslog-ng.pid)
Duplicate logging issues can show up if a source is listed in the
configuration file but is not defined previously. The following log
6 matches
Mail list logo
