Bug 460230 - rsyslog stops logging after system clock rollback
Summary: rsyslog stops logging after system clock rollback
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: rsyslog
Version: 9
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Peter Vrabec
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-26 21:24 UTC by Ed Swierk
Modified: 2008-09-10 06:56 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-09-02 09:17:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ed Swierk 2008-08-26 21:24:14 UTC
Setting the system clock backwards causes rsyslog-3.18.1-1.fc9 to stop writing log messages until the clock reaches the former time.  This is a regression from sysklogd-1.4.1-41.fc6.

To reproduce this issue:

1. Disable ntpd
2. Run 'tailf /var/log/messages' in a shell
3. In another shell, run 'logger hello1' to verify that rsyslog is working
4. Run 'date -s 1 hour ago' to roll the clock back 1 hour
5. Run 'logger hello2' and notice that nothing appears in /var/log/messages
6. Run 'date -s 1 hour' to roll the clock forward 1 hour
7. Run 'logger hello3' to verify that rsyslog is working again

Comment 1 Fedora Update System 2008-08-28 10:41:02 UTC
rsyslog-3.18.1-2.fc9 has been submitted as an update for Fedora 9.
http://admin.fedoraproject.org/updates/rsyslog-3.18.1-2.fc9

Comment 2 Peter Vrabec 2008-09-02 09:17:59 UTC
Feel free to reopen this bug, if rsyslog-3.18.1-2 doesn't fix this issue.

Comment 3 Fedora Update System 2008-09-10 06:56:24 UTC
rsyslog-3.18.1-2.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.


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