On Sun, 2006-11-05 at 15:22 +0100, Christoph Biedl wrote:
>
> The problem is _not_ gone I'm afraid.
First of all, I think syslog-ng isn't die whenever network conection
broken. But you are right, not starting.
Bazsi wrote a patch today to fix it. I will upload the new version
before the weekend.
Hi!
On Sun, 2006-11-05 at 17:47 +0100, Christoph Biedl wrote:
>
> But _please_ bring this matter to the upstream. The bug is still present
> in the recently released syslog-ng 2.0.0.
Tomorrow I will say it to him.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe".
Christoph Biedl wrote...
> Starting system logging: syslog-ngConnection failed; error='Network is
> unreachable (101)', reconnect='10'
> start failed.
Reading the sources: This message is generated at afsocket.c:765 within
afsocket_dd_reconnect, a function that is not used much. I /think/ it
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
-
Hi!
On Tue, 2006-10-24 at 00:19 +0200, Michael Tautschnig wrote:
> Apart from syslog-ng not starting (or rather immediately dying) at system
> bootup
> in case the network connection is not yet available, it dies whenever the
> connection to the server is broken.
I have seen a patch in Bazsi's c
Apart from syslog-ng not starting (or rather immediately dying) at system bootup
in case the network connection is not yet available, it dies whenever the
connection to the server is broken.
I've established a cron job to restart syslog-ng whenever it is gone, but this
is terribly annoying.
Regar
6 matches
Mail list logo
