[syslog-ng] [Bug 28] New: syslog-ng 2.0.9 is cpu bound after bootup on FreeBSD 7. 1-RELEASE

[bugzilla at bugzilla.balabit.com]

https://bugzilla.balabit.com/show_bug.cgi?id=28

           Summary: syslog-ng 2.0.9 is cpu bound after bootup on FreeBSD
                    7.1-RELEASE
           Product: syslog-ng
           Version: 2.0.x
          Platform: PC
        OS/Version: Other
            Status: NEW
          Severity: normal
          Priority: unspecified
         Component: syslog-ng
        AssignedTo: bazsi at balabit.hu
        ReportedBy: syslog-ng at ee.lbl.gov
Type of the Report: bug
   Estimated Hours: 0.0


Created an attachment (id=6)
 --> (https://bugzilla.balabit.com/attachment.cgi?id=6)
syslogd lines from /etc.conf

I'm using the FreeBSD syslog-ng2 package (2.0.9_2) under 7.1-RELEASE
(see rc.conf.txt attachment). I find that syslog-ng is cpu bound
following a reboot. This problem occurs on both i386 and amd64
installs. Either stopping and starting ("/etc/rc.d/syslogd restart")
or reloading ("kill -HUP `cat /var/run/syslog.pid`") results in
normal operation.

I used ktrace and it poll() is called followed by four calls to
gettimeofday() (see ktrace.txt attachment).

gcore and gdb show the loop to be inside glib (see gdb.txt attachment).

lsof shows the file descriptor that /dev/console should be on has
been revoked (see lsof.txt attachment).

I believe something happens early during the bootup process that
causes /dev/console to be reconfigured. I think that devd is running
when syslog-ng starts up.  Forcing the syslogd started to happen
after syscons doesn't help.

Note: In order to get syslog-ng to work with /etc/rc.d/syslogd the
startup script must be tweaked (see syslogd.patch.txt attachment).

My syslog-ng.conf is attached (syslog-ng.conf.txt)


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.