Bug 55861 - syslog daemon crashes
syslog daemon crashes
Product: Red Hat Linux
Classification: Retired
Component: sysklogd (Show other bugs)
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Bill Nottingham
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2001-11-07 16:05 EST by Sietse van Zanen
Modified: 2014-03-16 22:24 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-11-07 16:05:21 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Sietse van Zanen 2001-11-07 16:05:16 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0)

Description of problem:
The syslog daemon (syslogd only, not klogd) crashes when a logfile reaches 
2Gb (exactly 2147483648 bytes).
It will also refuse to start up, until the offending file is removed. It 
hangs for a couple of minutes and than exits. 

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

How reproducible:

Steps to Reproduce:
1. create 2Gb file (exactly 2147483648 bytes) or let a log file reach this 
2. configure this file as a log file in syslog.conf
3. /etc/init.d/syslog start

Actual Results:  syslogd hanging for couple of minutes and then exits.
During start-up, two syslogd processes are seen. One process spawns 
another. The spawned process is <defunct>.
If the file is bigger than 2Gb (2147483648 bytes) syslog will start, but 
will not log to the file.

Expected Results:  syslogd to start up normally.

Additional info:

syslogd version 1.4-1
kernel version 2.4-2

root@syslogcs:/var> ls -l syslog.log
-rw-r--r--    1 root     root     2147483647 Nov  7 21:44 syslog.log
root@syslogcs:/var> ps -fe |grep syslogd
root     20273 20263  0 21:55 pts/0    00:00:00 initlog -q -c syslogd -m 
0 -r
root     20274 20273  0 21:55 pts/0    00:00:00 syslogd -m 0 -r
root     20275 20274  0 21:55 ?        00:00:00 [syslogd <defunct>]
root     20280  4578  0 21:55 pts/1    00:00:00 grep syslogd
Comment 1 Bill Nottingham 2001-11-07 16:10:00 EST
This is fixed in the sysklogd that shipped with Red Hat Linux 7.2.

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