All Fedora 19 users, you want to read this

[AdamW]

Believe me, you really do, if you don't want your hard disk to fill up and your system logs to be a disaster area.

http://www.happyassassin.net/2013/06...le-explosions/

[weitjong]

Thanks for the info. My system was hit by SELinux alert (chapter 3), but luckily not hit by rsyslogd. At first I thought the SELinux alert in journal entries was due to my particular setup of /var/log mounting from a separate HD partition. Now I know the setup did not cause this.

[glennzo]

No wonder my laptop went ballistic after a round of updates last night.

[bob]

Still waiting to upgrade to F19 after final, but that was one fun read, Adam. Thanks for your uncensored comments.

[Demz3]

i read it. its a good reason why i havent installed F19 yet , expect F19 final to slip a week or 2

[nonamedotc]

Thanks for the warning AdamW!

I updated last night and shutdown the computer so I guess I am in for fun when I start the system again tonight!

[smr54]

I did a fresh install yesterday, but haven't used it very much. When I opened it this morning (I do a minimal install, and no Gnome, thus, apparently avoiding at least one of the issues), there were no problems. However, I did downgrade rsyslog immediately after booting.

[ManfredB]

FC20 - no problems with rsyslog-7.4.0-1.fc20.x86_64.

/var/log/messages: 8,4 Mb

FC19 - no problems with rsyslog-7.4.0-1.fc19.x86_64

/var/log/messages: 1,7 MB

Nothing of my CPUs shows more than 0 %, only if I open firefox or another program: 2-3 %.
I must say: my CPU: Intel Core i7-2600.

ManfredB

[MaJie]

Thank you, Adam!

I thought I was going to have to re-install.

~J

[troyatlarge]

I tried to download the SELinux update, but it said no such update available - via yum as follows:

$ sudo yum install selinux-policy-3.12.1-52.fc19
[sudo] password for troy:
Loaded plugins: langpacks, refresh-packagekit
No package selinux-policy-3.12.1-52.fc19 available.
Error: Nothing to do


Also,
For those who are rusty like me (and please correct this if my method is wrong), who are wondering how to stop rsyslog.service, I found the following to work

1) run “top” and notice the process ID number of rsyslog.service (its listed on far left under “PID”
2) hit “q” to stop top
3) type “sudo kill <whatever your PID number was for rsyslog.service>

Doing that dropped my CPU use from well over 85% (on two cores) to single digit numbers

I'm not sure the kill command is the best way, so please correct and do away with this post if there is a better method.

[cryogenic666]

I tried to download the SELinux update, but it said no such update available - via yum as follows:

$ sudo yum install selinux-policy-3.12.1-52.fc19
[sudo] password for troy:
Loaded plugins: langpacks, refresh-packagekit
No package selinux-policy-3.12.1-52.fc19 available.
Error: Nothing to do


Also,
For those who are rusty like me (and please correct this if my method is wrong), who are wondering how to stop rsyslog.service, I found the following to work

1) run “top” and notice the process ID number of rsyslog.service (its listed on far left under “PID”
2) hit “q” to stop top
3) type “sudo kill <whatever your PID number was for rsyslog.service>

Doing that dropped my CPU use from well over 85% (on two cores) to single digit numbers

I'm not sure the kill command is the best way, so please correct and do away with this post if there is a better method.

Why wouldn't you just systemctl stop rsyslogd.service?

[troyatlarge]

Why wouldn't you just systemctl stop rsyslogd.service?

1) I was not aware of the systemctl command, far less how to properly use it
2) I have read that "kill <PID>" was the cleanest way to kill a process.

However, it seems I read somewhere else at some point that there are other, even better ways to stop a process. Not being an expert I didn't want the give bad information thus the reluctance. Why is systemctl stop a better way to go about it?

[cryogenic666]

1) I was not aware of the systemctl command, far less how to properly use it
2) I have read that "kill <PID>" was the cleanest way to kill a process.

However, it seems I read somewhere else at some point that there are other, even better ways to stop a process. Not being an expert I didn't want the give bad information thus the reluctance. Whay is systemctl stop a better way to go about it?

Systemctl is the way you should manage all services now on F18+. It's the repacement for the old "service stop servicename" way of doing things (which still works in most instances, I believe). I think fundamentally using kill and systemctl stop DO the same thing, as long as you're not doing a kill -9 on the process. In any case, I just use systemctl for anything service related, including restarting, disabling or masking services. Also, systemctl (which is the interface for systemd) is aware of dependent services and such, where as flat-out killing a process can have unintended effects if you're not careful.

[chepioq]

FC20 - no problems with rsyslog-7.4.0-1.fc20.x86_64.

/var/log/messages: 8,4 Mb

FC19 - no problems with rsyslog-7.4.0-1.fc19.x86_64

/var/log/messages: 1,7 MB

Nothing of my CPUs shows more than 0 %, only if I open firefox or another program: 2-3 %.
I must say: my CPU: Intel Core i7-2600.

ManfredB

Same for me, no problems with rsyslog-7.4.0-1.fc19.x86_64, my cpu usage stay on 2-3 %, my /var/log/message is 3.4 Mio.

My cpu is intel core i3-2350M

May be it's because I disabled selinux ?

[jpollard]

Yup. A very fragile system. And with cascading failures as well.

Thanks for the news. I'll definitely not be installing now.