On 06/27/2014 01:59 AM, Helmut Jarausch wrote: > Hi, > > I am in a very strange situation where I cannot emerge anything any more. > Since it occurs on two different machines it won't be a hardware problem. > > When I try to emerge a package, say portage, it builds it just fine and > starts to install it (for portage, the last file shown is etc/etc-update.conf) > but then it hangs forever - no CPU / no IO. It looks as if it has locked > itself out. > This is even with a single package emerge. > The only interesting things which are shown by lsof are > > > emerge 1747 root mem REG 0,16 46678298 > /usr/lib64/gconv/gconv-modules.cache (path dev=0,18) > emerge 1747 root 0u CHR 136,0 0t0 3 /dev/pts/0 > emerge 1747 root 1u CHR 136,0 0t0 3 /dev/pts/0 > emerge 1747 root 2u CHR 136,0 0t0 3 /dev/pts/0 > emerge 1747 root 3w REG 8,17 1491 38217 /var/log/slim.log > emerge 1747 root 4u a_inode 0,9 0 21 [eventpoll] > emerge 1747 root 5r FIFO 0,8 0t0 91938 pipe > emerge 1747 root 6uW REG 0,30 0 97094 > /var/tmp/portage/sys-apps/.portage-9999.portage_lockfile > emerge 1747 root 7w FIFO 0,8 0t0 91938 pipe > emerge 1747 root 8r FIFO 0,30 0t0 91946 > /var/tmp/portage/sys-apps/portage-9999/.ipc_in > emerge 1747 root 10u CHR 5,2 0t0 1127 /dev/ptmx > emerge 1747 root 11u CHR 136,0 0t0 3 /dev/pts/0 > emerge 1747 root 12w REG 0,30 282954 91945 > /var/tmp/portage/sys-apps/portage-9999/temp/build.log > > > Yes, I've tried to remove anything from /var/tmp/portage and the problem > persists after reboot.
:( I'm replying only because no one else has. You didn't say when the problem began. The problem started on the same day on both machines? You could try qlop -l to see what packages have updated recently. Does "portage-9999" mean you're running the unstable/development version of portage? The ebuild for portage-9999 lists a git repository, so you might be able to check out a previous (working) version of portage using git?
