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): epylog-1.0.3-5.fc7 How reproducible:Install epylog on FC7T3 or rawhide system and run it Steps to Reproduce: 1.Install FC7T3 or rawhide 2.Install epylog 3./etc/cron.daily/./epylog.cron 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.
Created attachment 151912 [details] Email results when epylog is ran
Created attachment 151913 [details] Epylog email results Made this one a text file so you don't have to download it.
Comment on attachment 151912 [details] Email results when epylog is ran See 2nd attachement, as this one comes up bin file.
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?
Created Epylog Trac ticket: http://open.mcgill.ca/epylog/ticket/4
Created attachment 152567 [details] My messages file
Fixed upstream. Will be implemented in 1.0.4, which should be out in a few days. Thanks!
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)? epylog-1.0.3-5.fc7 sysklogd-1.4.2-4.fc7