[Bug 200] New: logging does not work on FreeBSD
https://bugzilla.balabit.com/show_bug.cgi?id=200 Summary: logging does not work on FreeBSD Product: syslog-ng Version: 3.4.x Platform: PC OS/Version: FreeBSD Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi@balabit.hu ReportedBy: czanik@balabit.hu Type of the Report: --- Estimated Hours: 0.0 Using the latest syslog-ng 3.4 git, with Algernon sandbox patches applied (to be able to generate a tar.gz dist file), logging does not seem to work. Without command line arguments, nothing gets logged, except for version information at startup. When using "-vdF", logs coming from the network are logged. Tested on FreeBSD 9.0 with a slightly modified sysutils/syslog-ng-rc port (removed utmp magic from ports Makefile). -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=200 Peter Czanik <czanik@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |czanik@balabit.hu OS/Version|FreeBSD |All Summary|logging does not work on |local logging does not work |FreeBSD | --- Comment #1 from Peter Czanik <czanik@balabit.hu> 2012-10-03 09:53:11 --- And it's not FreeBSD specific. Just ran into the same problem on openSUSE. Only remote logs are working. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=200 Gergely Nagy <algernon@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |algernon@balabit.hu --- Comment #2 from Gergely Nagy <algernon@balabit.hu> 2012-10-05 11:15:23 --- I tried to debug this, and it's definitely the LogProto refactoring that broke it, but I did not manage to find out yet why. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=200 Gergely Nagy <algernon@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bazsi@balabit.hu |algernon@balabit.hu -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=200 Gergely Nagy <algernon@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #3 from Gergely Nagy <algernon@balabit.hu> 2012-10-11 12:27:11 --- Right. This was a bit of a pain to figure out, as I had to understand Bazsi's recent logproto/logtransport rework, but the problem turned out to be really simple once understood: prior to the rework, the text transport was smart enough to recognise when it is in dgram-mode, and didn't expect a newline termination in that case. With the rework, the text transport was split, and a dgram transport was born. However, afunix was not modified, and it always set a text transport, even when operating on a unix-dgram. BUT /dev/log messages are not newline terminated, so they were accumulating in an internal buffer, waiting for the buffer to fill up. The obvious fix is to teach afunix to do the right thing, and set dgram transport as appropriate. I'll send a patch soon. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=200 --- Comment #4 from Gergely Nagy <algernon@balabit.hu> 2012-10-11 12:35:30 --- Fixed on the hotfix/3.4/afunix-transport-mismatch branch of my repo, needs merging to master. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=200 Balazs Scheidler <bazsi@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bazsi@balabit.hu Resolution| |FIXED Status|ASSIGNED |RESOLVED --- Comment #5 from Balazs Scheidler <bazsi@balabit.hu> 2012-10-13 10:09:20 --- I couldn't find your branch first (my fault sorry), and by that time I also had a fix committed locally. I've slightly edited the commit message to reflect credits, but my patch also contained the testcase change, so we won't run into the same issue next time. commit 6022d4e1ad7f9c46c0b152f47c3f2d0383b7c27d Author: Balazs Scheidler <bazsi@balabit.hu> Date: Sat Oct 13 10:07:43 2012 +0200 unix-dgram: fixed message processing w/o terminating newlines In the last refactor, unix-dgram was switched to use the "text" LogProto Since unix-dgram clients don't always supply an NL character (such as on FreeBSD), this caused issues. This patch fixes the issue and also extends the testcases to cover this. Reported-by: Peter Czanik <czanik@balabit.hu> Signed-off-by: Gergely Nagy <algernon@balabit.hu> Signed-off-by: Balazs Scheidler <bazsi@balabit.hu> With this patch, this is considered fixed. Thanks. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
participants (1)
-
bugzilla@bugzilla.balabit.com