Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 26040

Summary: emerge postfix hangs after md5 check
Product: Portage Development Reporter: Robert Hillyerd <lord_of_cynicism>
Component: UnclassifiedAssignee: Portage team <dev-portage>
Status: VERIFIED NEEDINFO    
Severity: major CC: aethyr7, net-mail+disabled, pYrania
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: log of Portage hang with postfix

Description Robert Hillyerd 2003-08-06 06:37:32 UTC
The bug has been around for multiple versions of portage
Attempted deleting distfiles, ebuilds and digest files, problem still remains
after rebuilding digest files.

I have been unable to upgrade postfix since 2.0.3, here is what it echoes out
>>> emerge (1 of 1) net-mail/postfix-2.0.13-r1 to /
>>> md5 src_uri ;-) postfix-2.0.13.tar.gz
>>> md5 src_uri ;-) pfixtls-0.8.15-2.0.13-0.9.7b.tar.gz
***Hang***
At hang usermod takes up all remaining cpu time and does nothing.

Replication
I don't think it can really be replicated
emerge =net-mail/postfix-2.0.9
watch it hang

you may contact me at bob@monolithictechnologies.com but if it returns mail,
that's cause postfix isn't working ;)
so email me at lord_of_cynicism@hotmail.com if that happens
if you are a dev, contact me and I'll give you any specific information on this
machine/config to help you get this weird fluke bug resolved.
Comment 1 aethyr 2003-08-06 19:28:59 UTC
could you provide the results of `cat /proc/cpuinfo` and also `emerge info` ?
Comment 2 Robert Hillyerd 2003-08-06 22:15:24 UTC
cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 5
model name      : Pentium II (Deschutes)
stepping        : 3
cpu MHz         : 439.963
cache size      : 512 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr
bogomips        : 878.18


emerge info
Portage 2.0.48-r7 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1)
=================================================================
System uname: 2.4.20 i686 Pentium II (Deschutes)
GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY=""
USE="truetype jpeg X tiff png gd qt nls pam ssl curl imap gdbm xml xml2 crypt spell mysql flash berkdb libwwwfd readline -java" readline -java"
COMPILER="gcc3"
CHOST="i686-pc-linux-gnu"
CFLAGS="-O2 -mcpu=i686 -pipe"
CXXFLAGS="-O2 -mcpu=i686 -pipe"
ACCEPT_KEYWORDS="x86 ~arch ~x86"
MAKEOPTS="-j2"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
FEATURES="sandbox ccache"
Comment 3 Markus Nigbur (RETIRED) gentoo-dev 2003-08-07 03:46:52 UTC
My guess is, that your system is kinda slow, maybe related to cpu, or harddisk (hdparm running)?
because the next step will be unpacking the sources. It even takes some seconds on my PIV 1800 with ATA100 disks.

so could you try if it just continues after some more time?
Comment 4 Robert Hillyerd 2003-08-07 07:08:17 UTC
I've given it that chance, I've let it sit there for a good 5 minutes and it hasn't progressed beyond the hang point. This is the only package that I'm aware of that it's been doing this to. and has been happening since 2.0.3 of postfix. Files Significantly larger tend to get through this point within 5-10 seconds
I do run hdparm on my drive. I assure you this isn't HDD/CPU related.
Comment 5 aethyr 2003-08-12 13:38:21 UTC
Wait, why are you deleting digest files?

I'd delete the relevant distfiles, then emerge sync.

If you want a really clean start, then `rm -rf /usr/portage/net-mail/postfix && emerge sync` and try again.
Comment 6 aethyr 2003-08-12 13:44:49 UTC
and for the heck if it try:

`emerge /usr/portage/net-mail/postfix/postfix-2.0.13-r1.ebuild`

instead of

`emerge postfix`
Comment 7 Robert Hillyerd 2003-08-14 17:09:44 UTC
After deleting /usr/portage/net-mail/postfix dir
and emerge syncing......

>>> emerge (1 of 1) net-mail/postfix-2.0.13-r1 to /
>>> md5 src_uri ;-) postfix-2.0.13.tar.gz
>>> md5 src_uri ;-) pfixtls-0.8.15-2.0.13-0.9.7b.tar.gz
5 minutes were given..... *hang*
Comment 8 Nicholas Jones (RETIRED) gentoo-dev 2003-08-15 16:07:16 UTC


strace -f -o portage_hang.log emerge postfix
and post that here for me please. Stop it in
reasonable amount of time.

bzip2 it please.
Comment 9 Robert Hillyerd 2003-08-16 14:43:43 UTC
Created attachment 16188 [details]
log of Portage hang with postfix

bzip2ed for your convenience
Comment 10 Robert Hillyerd 2003-08-16 14:52:34 UTC
there's the log, it's just screaming infinant loop.
bugzilla gave me an error when uploading which i submitted to the webmaster
if for some reason, the file isn't there
you can get it here
www.fewl.org/portage_hang.log.bz2
-Rob
Comment 11 Nicholas Jones (RETIRED) gentoo-dev 2003-08-16 18:16:54 UTC
What's in your syslog, and does the following work?
# usermod -G mail postfix


Relevant chunk from strace:

16213 execve("/usr/sbin/usermod", ["usermod", "-G", "mail", "postfix"], [/* 177 
vars */] <unfinished ...>                                                       
......
16213 connect(6, {sa_family=AF_UNIX, path="/dev/log"}, 16) = 0                  
16213 send(6, "<86>Aug 16 17:24:07 usermod[1621"..., 65, 0) = 65                
16213 rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0                             
--REPEATS--

Comment 12 Robert Hillyerd 2003-08-16 19:16:57 UTC
syslog
----
Aug 16 22:12:53 [usermod] add `postfix' to group `mail'
---- when doing----
usermod -G mail postfix
*Hang*
in /etc/group ---- mail::12:mail
so no addition there.
Comment 13 Martin Holzer (RETIRED) gentoo-dev 2003-11-17 04:34:01 UTC
is this still an issue ?
Comment 14 Ajay Sharma 2004-06-22 20:40:35 UTC
ping... is there still a problem here?  Nothing relevant has been posted after August 2003.
Comment 15 Tuan Van (RETIRED) gentoo-dev 2004-07-01 13:35:12 UTC
no response to ping.
Comment 16 Marius Mauch (RETIRED) gentoo-dev 2007-01-11 11:00:48 UTC
Closing due to old age