Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 235568 - When ran, it reports invalid syslog format strings
Summary: When ran, it reports invalid syslog format strings
Alias: None
Product: Fedora
Classification: Fedora
Component: epylog
Version: rawhide
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Konstantin Ryabitsev
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-04-07 12:03 UTC by Mike Chambers
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-04-13 21:04:08 UTC

Attachments (Terms of Use)
Email results when epylog is ran (deleted)
2007-04-07 12:03 UTC, Mike Chambers
no flags Details
Epylog email results (deleted)
2007-04-07 12:10 UTC, Mike Chambers
no flags Details
My messages file (deleted)
2007-04-13 18:10 UTC, Mike Chambers
no flags Details

Description Mike Chambers 2007-04-07 12:03:45 UTC
Description of problem:When epylog runs manually or automatically during
cron.daily, it gets various invalid syslog format strings in numerous files, all
of them I guess.

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

How reproducible:Install epylog on FC7T3 or rawhide system and run it

Steps to Reproduce:
1.Install FC7T3 or rawhide
2.Install epylog
Actual results:
Since it's too long, see attached file for results.

Expected results:Should be able to read the log files

Additional info:This is on an FC7T3+rawhide-updates system and current as of today.

Comment 1 Mike Chambers 2007-04-07 12:03:46 UTC
Created attachment 151912 [details]
Email results when epylog is ran

Comment 2 Mike Chambers 2007-04-07 12:10:22 UTC
Created attachment 151913 [details]
Epylog email results

Made this one a text file so you don't have to download it.

Comment 3 Mike Chambers 2007-04-07 12:13:06 UTC
Comment on attachment 151912 [details]
Email results when epylog is ran

See 2nd attachement, as this one comes up bin file.

Comment 4 Konstantin Ryabitsev 2007-04-13 16:46:47 UTC
Hmmm... Could you give me a small chunk of your /var/log/messages? It seems like
syslog string format has changed slightly.

Is this syslog or syslog-ng?

Comment 5 Konstantin Ryabitsev 2007-04-13 16:50:13 UTC
Created Epylog Trac ticket:

Comment 6 Mike Chambers 2007-04-13 18:10:39 UTC
Created attachment 152567 [details]
My messages file

Comment 7 Konstantin Ryabitsev 2007-04-13 21:04:08 UTC
Fixed upstream. Will be implemented in 1.0.4, which should be out in a few days.


Comment 8 Mike Chambers 2007-04-15 14:28:04 UTC
Maybe not that it matters now, but yesterday I had an actual html email this
time, but it was all jumbeled up and couldn't make out anything, and way too big
or something, almost froze computer.

But today I got my first actual good readable log file and looked just fine.  So
am thinking since your upgrade isn't out yet, maybe the syslog part fixed it (I
saw mentioned about the log files have two spaces instead of one)?


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