[CentOS] Yum hangs while doing anything

[ken]

On 07/01/2013 03:28 PM Eero Volotinen wrote:
> so, it's waiting something. try strace -f yum command and output to email

[Sorry for the delay.  Got a phone call.]

There's a *lot* of output.  Here's the last part of it:

read(6, "#!/usr/bin/python -t\n\n# This pro"..., 4096) = 4096
read(6, "his.\n        '''\n        return "..., 4096) = 4096
read(6, "urn super(PositiveIntOption, sel"..., 4096) = 4096
read(6, "r:\n            raise ValueError("..., 4096) = 4096
read(6, "name to use. If not-specified th"..., 4096) = 4096
read(6, "nel-PAE-debug'])\n    exactarchli"..., 4096) = 4096
read(6, " to pkgs_gpgcheck\n    gpgcheck ="..., 4096) = 4096
write(2, "    ", 4    )                     = 4
write(2, "yumvars['releasever'] = _getsysv"..., 86yumvars['releasever'] 
= _getsysver(startupconf.installroot, startupconf.distroverpkg)
) = 86
close(6)                                = 0
munmap(0xb7967000, 4096)                = 0
open("/usr/lib/python2.4/site-packages/yum/config.py", 
O_RDONLY|O_LARGEFILE) = 6
write(2, "  File \"/usr/lib/python2.4/site-"..., 81  File 
"/usr/lib/python2.4/site-packages/yum/config.py", line 884, in _getsysver
) = 81
fstat64(6, {st_mode=S_IFREG|0644, st_size=31008, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
0) = 0xb7967000
read(6, "#!/usr/bin/python -t\n\n# This pro"..., 4096) = 4096
read(6, "his.\n        '''\n        return "..., 4096) = 4096
read(6, "urn super(PositiveIntOption, sel"..., 4096) = 4096
read(6, "r:\n            raise ValueError("..., 4096) = 4096
read(6, "name to use. If not-specified th"..., 4096) = 4096
read(6, "nel-PAE-debug'])\n    exactarchli"..., 4096) = 4096
read(6, " to pkgs_gpgcheck\n    gpgcheck ="..., 4096) = 4096
read(6, "default if value was not present"..., 4096) = 2336
write(2, "    ", 4    )                     = 4
write(2, "hdr = idx.next()\n", 17hdr = idx.next()
)      = 17
close(6)                                = 0
munmap(0xb7967000, 4096)                = 0
write(2, "StopIteration", 13StopIteration)           = 13
write(2, "\n", 1
)                       = 1
close(3)                                = 0
rt_sigaction(SIGINT, {SIG_DFL, [], 0}, {0x71b4e0, [], SA_SIGINFO}, 8) = 0
rt_sigaction(SIGQUIT, {SIG_DFL, [], 0}, {0x71b4e0, [], SA_SIGINFO}, 8) = 0
close(5)                                = 0
close(4)                                = 0
munmap(0xb7968000, 450560)              = 0
munmap(0xb79d6000, 1318912)             = 0
munmap(0xb7b18000, 24576)               = 0
rt_sigaction(SIGHUP, {SIG_DFL, [], 0}, NULL, 8) = 0
rt_sigaction(SIGINT, {0x21f41d0, [], 0}, NULL, 8) = 0
rt_sigaction(SIGTERM, {SIG_DFL, [], 0}, NULL, 8) = 0
rt_sigaction(SIGQUIT, {0x21f41d0, [], 0}, NULL, 8) = 0
rt_sigaction(SIGPIPE, {0x1, [], 0}, NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
exit_group(1)                           = ?

It looks like it made it through the gpg check... which I was wondering 
about.  Again, it looks like (wild guess) it's horking on some 
iteration, reading some values out of an array.  At least it's not 
hanging anymore.