Upgrade of F13 to F14 via yum

[Paolo Galtieri]

Yesterday I upgraded a F13 system to F14 using yum upgrade.  It took all 
day (and part of the night) but when I checked this morning the system 
had rebooted and everything looked fine.  Until I logged in.  Then I 
noticed that named now consumes >100% cpu (the system is a dual 
processor Intel(R) Pentium(R) 4 CPU 2.80GHz). There is nothing obvious 
in the logs that I could find that would explain this.  This system is 
my DNS server and was working fine under F13.  When I run strace named 
is spewing the following messages:

[pid  5329] futex(0xb784b04c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0xb784b048, 
{FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1} <unfinished ...>
[pid  5330] <... futex resumed> )       = 0
[pid  5330] futex(0xb784b018, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>
[pid  5329] <... futex resumed> )       = 1
[pid  5329] futex(0xb784b018, FUTEX_WAKE_PRIVATE, 1 <unfinished ...>
[pid  5330] <... futex resumed> )       = 0
[pid  5330] gettimeofday({1309450987, 273490}, NULL) = 0
[pid  5330] futex(0xb784b018, FUTEX_WAKE_PRIVATE, 1) = 0
[pid  5330] clock_gettime(CLOCK_REALTIME, {1309450987, 273721365}) = 0
[pid  5330] futex(0xb784b04c, FUTEX_WAIT_PRIVATE, 1490757, {1142, 
153144635} <unfinished ...>
[pid  5329] <... futex resumed> )       = 1
[pid  5329] gettimeofday({1309450987, 273973}, NULL) = 0
[pid  5329] gettimeofday({1309450987, 274119}, NULL) = 0
[pid  5329] futex(0xb784b04c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0xb784b048, 
{FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1} <unfinished ...>
[pid  5330] <... futex resumed> )       = 0
[pid  5330] futex(0xb784b018, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>
[pid  5329] <... futex resumed> )       = 1
[pid  5329] futex(0xb784b018, FUTEX_WAKE_PRIVATE, 1 <unfinished ...>
[pid  5330] <... futex resumed> )       = 0
[pid  5330] gettimeofday({1309450987, 274655}, NULL) = 0
[pid  5330] futex(0xb784b018, FUTEX_WAKE_PRIVATE, 1) = 0
[pid  5330] clock_gettime(CLOCK_REALTIME, {1309450987, 274883103}) = 0
[pid  5330] futex(0xb784b04c, FUTEX_WAIT_PRIVATE, 1490759, {1142, 
151982897} <unfinished ...>
[pid  5329] <... futex resumed> )       = 1
[pid  5329] gettimeofday({1309450987, 275135}, NULL) = 0
[pid  5329] gettimeofday({1309450987, 275250}, NULL) = 0
[pid  5329] gettimeofday({1309450987, 275367}, NULL) = 0
[pid  5329] futex(0xb784b04c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0xb784b048, 
{FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1} <unfinished ...>
[pid  5330] <... futex resumed> )       = 0
[pid  5330] futex(0xb784b018, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>
[pid  5329] <... futex resumed> )       = 1
[pid  5329] futex(0xb784b018, FUTEX_WAKE_PRIVATE, 1 <unfinished ...>
[pid  5330] <... futex resumed> )       = 0
[pid  5330] gettimeofday({1309450987, 275914}, NULL) = 0
[pid  5330] futex(0xb784b018, FUTEX_WAKE_PRIVATE, 1) = 0
[pid  5330] clock_gettime(CLOCK_REALTIME, {1309450987, 276147526}) = 0
[pid  5330] futex(0xb784b04c, FUTEX_WAIT_PRIVATE, 1490761, {1142, 
150718474} <unfinished ...>
[pid  5329] <... futex resumed> )       = 1
[pid  5329] gettimeofday({1309450987, 276417}, NULL) = 0
[pid  5329] gettimeofday({1309450987, 276536}, NULL) = 0
[pid  5329] futex(0xb784b04c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0xb784b048, 
{FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1} <unfinished ...>
[pid  5330] <... futex resumed> )       = 0
[pid  5330] futex(0xb784b018, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>
[pid  5329] <... futex resumed> )       = 1
[pid  5329] futex(0xb784b018, FUTEX_WAKE_PRIVATE, 1 <unfinished ...>
[pid  5330] <... futex resumed> )       = 0
[pid  5330] gettimeofday({1309450987, 277056}, NULL) = 0
[pid  5330] futex(0xb784b018, FUTEX_WAKE_PRIVATE, 1) = 0
[pid  5330] clock_gettime(CLOCK_REALTIME, {1309450987, 277286204}) = 0
[pid  5330] futex(0xb784b04c, FUTEX_WAIT_PRIVATE, 1490763, {1142, 
149579796} <unfinished ...>
[pid  5329] <... futex resumed> )       = 1
[pid  5329] gettimeofday({1309450987, 277553}, NULL) = 0
[pid  5329] gettimeofday({1309450987, 277669}, NULL) = 0
[pid  5329] gettimeofday({1309450987, 277785}, NULL) = 0
[pid  5329] futex(0xb784b04c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0xb784b048, 
{FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1} <unfinished ...>
[pid  5330] <... futex resumed> )       = 0
[pid  5330] futex(0xb784b018, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>
[pid  5329] <... futex resumed> )       = 1
[pid  5329] futex(0xb784b018, FUTEX_WAKE_PRIVATE, 1 <unfinished ...>
[pid  5330] <... futex resumed> )       = 0
[pid  5330] gettimeofday({1309450987, 278305}, NULL) = 0
[pid  5330] futex(0xb784b018, FUTEX_WAKE_PRIVATE, 1) = 0

Has anyone else had issues with named after an upgrade?


Another issue I encountered has to do with Selinux alerts.  Here's one 
of the alerts:

SELinux is preventing /usr/bin/updatedb from getattr access on the 
directory /etc/udev/rules.d

The permissions on the directory on the upgraded system is:
drwxr-xr-x. root root system_u:object_r:udev_var_run_t:s0 /etc/udev/rules.d/

On one of my other F14 system it's:
drwxr-xr-x. root root system_u:object_r:udev_rules_t:s0 /etc/udev/rules.d/

Note that they are not the same.  I also get the following alerts:

SELinux is preventing /bin/mount from write access on the directory 
/var/named
drwxr-x---. root named system_u:object_r:named_zone_t:s0 /var/named

SELinux is preventing /bin/mount from write access on the directory 
/usr/lib/bind

Another issue I'm having on all my Linux systems connected to my KVM
switch.  The problem is I get constant USB disconnects/reconnects.  They 
occur about every 30 seconds on average.  I don't know if this indicates 
the hardware is going bad or something else.

Any thoughts are appreciated.

Thanks,
Paolo