Answering my own question... I cleaned up my syslog-ng.conf file and these issues went away. It now seems to be working with OpenBSD 3.5, (with the exception of the UDP logging hostname.) -Steve S. Steven S. wrote:
Steven S. wrote: Something still seems not quite right in macros.c.
"Syslog-ng -F" core dumps after doing:
28992 syslog-ng CALL getpid 28992 syslog-ng RET getpid 28992/0x7140 28992 syslog-ng CALL gettimeofday(0xffffffffff7fed10,0) 28992 syslog-ng RET gettimeofday 0
Over and over again. "Syslog-ng -d" works fine and "syslog-ng" just dies.
Any thoughts on where I could look? Thanks.
-Steve S.
root@logger01 [/root]# gdb /usr/local/sbin/syslog-ng syslog-ng.core GNU gdb 4.16.1 Copyright 1996 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "sparc64-unknown-openbsd3.5"... Core was generated by `syslog-ng'. Program terminated with signal 11, Segmentation fault. Couldn't read input and local registers from core file Couldn't read input and local registers from core file #0 0x114d48 in werror () at macros.c:104 104 return l; (gdb)
And here is an obnoxiously long ktrace output when running with no flags...