[syslog-ng] syslg-ng hangs on damnsmalllinux boot

[Heiko Blume]

Hello,

i try to run syslog-ng 2.0.0 compiled with eventlog-0.25
and glib-2.12.4 on damnsmalllinux 3.0.1 (knoppix variant
based on linux 2.4.26).

It is started in a script like this which is called from bootlocal.sh

sudo /opt/syslog-ng/sbin/syslog-ng \
        --cfgfile=/opt/syslog-ng/etc/syslog-ng.conf \
        --chroot=/data/var/log \
        --user=65534 \
        --group=65534

unfortunately it will hang causing mischief, like
programs blocking on it, so the boot script does not complete
and no login is possible at all.
it can only be killed with "-9".

The "messages" and "syslog" logfiles look like this, so the chroot
etc has worked correctly, the config is valid etc etc:



Nov 22 00:19:22 s_all at box syslog-ng[682]: syslog-ng starting up;
version='2.0.0'

Nov 22 00:19:22 s_all at box kernel: Linux version 2.4.26 (root at Knoppix) (gcc
versi
on 2.95.4 20011002 (Debian prerelease)) #1 SMP Sa Apr 17 19:33:42 CEST 2004
[blaaaaaaaaaaaaah]
Nov 22 00:19:22 s_all at box kernel: Linux agpgart interface v0.99 (c) Jeff
Hartmann



But hereafter nothing happens anymore :-(((


If it is started manually later on it seems to work.

I tried starting it with --debug, but that didn't say
anything at all, although i ran configure with --enable-debug
(is that relevant?)

I applied the patch from
http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg265412.html
to prevent blocking on tty's but that didn't help.

In the config file i then set

use_dns(no)

and commented out the usertty() destination, so it is only
logging to files. no external programs, pipes etc are used.
the only source used is this:

source s_all {
        # message generated by Syslog-NG
        internal();
        # standard Linux log source (this is the default place for the
syslog()
        # function to send logs to)
        unix-dgram("/dev/log");
        unix-dgram("/data/tftpboot/dev/log");
        # messages from the kernel
        file("/proc/kmsg" log_prefix("kernel: "));
        # use the next line if you want to receive remote UDP logging
messages
        # (this is equivalent to the "-r" syslogd flag)
        udp();
        tcp();
};

any help would be appreciated!!!

regards,

-- 
Heiko at Blume.AG