reopen 384021 severity grave thanks > I have seen a patch in Bazsi's commit log which commited today and I > think related to this bug. I'm going to create a new package today or at > latest tomorrow.
The problem is _not_ gone I'm afraid.
Using a minimal syslog-ng.conf like
-----------------------------------------------------------
# options striped
source s_all {
internal();
unix-stream("/dev/log");
file("/proc/kmsg" log_prefix("kernel: "));
};
destination logger1 { tcp("192.168.19.25" port(514) );};
log { source(s_all); destination(logger1); };
-----------------------------------------------------------
syslog-ng fails to start if the remote destination is unreachable:
# ip -4 route add unreachable 192.168.19.25
# /etc/init.d/syslog-ng restart
Stopping system logging: syslog-ng.
Starting system logging: syslog-ngConnection failed; error='Network is
unreachable (101)', reconnect='10'
start failed.
Using udp instead of tcp doesn't help either.
And yes, I'm using the newest syslog-ng version:
| ii syslog-ng 2.0rc3-2 Next generation logging daemon
Christoph
signature.asc
Description: Digital signature
