Bug 130905 - syslogd prints empy messages
Summary: syslogd prints empy messages
Alias: None
Product: Fedora
Classification: Fedora
Component: sysklogd   
(Show other bugs)
Version: 2
Hardware: i686 Linux
Target Milestone: ---
Assignee: Jason Vas Dias
QA Contact: Brian Brock
Keywords: Security
Depends On:
TreeView+ depends on / blocked
Reported: 2004-08-25 18:09 UTC by George Dunlap
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-19 23:19:10 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2005:087 low SHIPPED_LIVE sysklogd bug fix update 2005-05-19 04:00:00 UTC

Description George Dunlap 2004-08-25 18:09:57 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)

Description of problem:
All log files written by syslogd since at least a month ago have empty
messages.  Here is an example from /var/log/messages

Aug 25 11:55:14 samwise exiting on signal 15
Aug 25 12:51:55 samwise syslogd 1.4.1: restart.
Aug 25 12:51:55 samwise
Aug 25 12:51:55 samwise last message repeated 208 times
Aug 25 12:51:57 samwise
Aug 25 12:51:57 samwise
Aug 25 12:52:01 samwise

This includes the following files:

All available saved versions are the same way (messages.1, messages.2,
etc); the oldest messages are from July 25th.  

The rpm -qi reports that the package was installed June 14th. 

Verifying with rpm -qV succeeds.

Running syslogd -d and then sending it messages through "logger"
reveals that syslogd is receiving messages, of various lengths (1 char
in logger -> message size of 34, 2 chars -> 35, but the message is
apparently empty.  Example output:

Successful select, descriptor count = 1, Activity on: 3
Message from UNIX socket: #3
Message length: 31, File descriptor: 3.
logmsg: user.alert<9>, flags 2, from samwise, msg
msg repeated 1 times, 124 sec of 60.
Called fprintlog, logging to FILE /var/log/messages
Calling select, active file descriptors (max 3): 3

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Boot the system
2.Examine /var/log/messages

Actual Results:  /var/log/messages is full of empty messages
(timestamped but empty).

Expected Results:  /var/log/messages is full of system messages

Additional info:

Comment 1 Bill Nottingham 2004-08-25 18:48:26 UTC
1.4.1-18 is broken - either use 1.4.1-16 as shipped in FC2, or the
current rawhide version.

Comment 2 Jason Vas Dias 2004-08-25 18:58:56 UTC
 You're using a UTF-8 locale ? 
 This bug was found earlier (bug 125679) and was fixed in 
 sysklogd-1.4.1-18 . Current version is sysklogd-1.4-22,
 which I am now pushing into FC2 updates.

*** This bug has been marked as a duplicate of 125679 ***

*** This bug has been marked as a duplicate of 125679 ***

Comment 4 Tim Powers 2005-05-19 23:19:11 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.