[syslog-ng]syslog-ng 1.5.26 dies after remote logging host goes down

Dr. Peter Bieringer syslog-ng@lists.balabit.hu
Fri, 28 Feb 2003 15:19:31 +0100


--On Freitag, 28. Februar 2003 14:56 +0100 Balazs Scheidler
<bazsi@balabit.hu> wrote:

> On Fri, Feb 28, 2003 at 11:58:44AM +0100, Dr. Peter Bieringer wrote:
>> poll([{fd=12, events=POLLOUT, revents=POLLOUT}, {fd=10, events=0},
>> {fd=4,  events=0}, {fd=7, e                 vents=0}, {fd=8, events=0},
>> {fd=6,  events=POLLIN}, {fd=5, events=POLLIN}, {fd=3, events=POLLI 
>> N}], 8, 100) = 1
>> write(12, "Feb 28 11:30:43 loghost syslog-ng"..., 217) = 217
> 
> what is this message ?

Feb 28 11:30:43 gromit syslog-ng[6360]: io.c: do_write: write() failed
(errno 111), Connection refused
Feb 28 11:30:43 gromit syslog-ng[6360]: Connection broken to
AF_INET(1.2.3.4:514), reopening in 60 seconds


>> kill(6360, SIGABRT)                     = 0
>> --- SIGABRT (Aborted) ---

Died again, but unfortunately, starting function "daemon" sets ulimit to 0
again, fixed now.

> a backtrace would certainly help a bit more.

I look for providing a core file asap.

        Peter