Gentoo sucks. yen tmp # /etc/init.d/postfix stop * Stopping postfix... /sbin/runscript.sh: line 526: 15152 Segmentation fault /usr/sbin/postfix stop >&/dev/nu [ !! ] yen tmp # Reproducible: Always Steps to Reproduce: 1. 2. 3. Portage 2.0.49-r4 (default-x86-1.4, gcc-3.3.1, glibc-2.3.2-r1, 2.4.20-gentoo-r6) ================================================================= System uname: 2.4.20-gentoo-r6 i686 Celeron (Coppermine) distcc 2.10 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=pentium3 -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=pentium3 -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="sandbox ccache autoaddcvs distcc" GENTOO_MIRRORS="ftp://sunsite.ualberta.ca/pub/unix/Linux/gentoo/ ftp://cs.ubishops.ca/pub/gentoo http://adelie.polymtl.ca/ http://www.ibiblio.org/gentoo" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.ca.gentoo.org/gentoo-portage" USE="x86 jpeg alsa berkdb readline tetex mysql postgres X tcpd ssl perl ldap innodb maildir mbox sasl -oss -apm -avi -crypt -cups -encode -foomaticdb -gif -java -gnome -libg++ -mad -mikmod -mmx -mpeg -ncurses -nls -opengl -pdflib -png -quicktime -spell -truetype -xml2 -xmms -xv -zlib -directfb -gdbm -slang -arts -aalib -nas -svga -ggi -tcltk -guile -ruby -sdl -gpm -pam -libwww -python -esd -imlib -oggvorbis -gtk -qt -kde -motif -gphoto2 -cdr -scanner"
Created attachment 17798 [details] strace -f /etc/init.d/postfix stop
I re-emerged postfix and it seems to be fine now. I had re-emerged it two days ago at work and it seemed fine then too, but this morning from home it kept segfaulting when running the boot script. Mark
I have the same problem. The postfix command itself segfaults. This happens when I emerged 3.3.1-r1. 3.3.1-r2 compiled and ran postfix successfully but I had to unmerge it for other problems. I re-emerged postfix with 3.3.1-r1 and had the same problem. I assume gcc-3.3.1-r1 and postfix have some kind of problem with each other.
I'm using gcc-3.3.1-r1 with postfix-2.0.15-r1 now and it started working fine once I re-emerged postfix. Dunno what's up ... Mark
Hi. Similar here. /etc/init.d/postfix start or simply "postfix" on the shell segfaults. I even have two systems where I updated gcc to 3.3.1-r2. Both had the recent "segfaults everywhere" bug (including postfix) and on both I just downgraded to 3.2.3-r2. While on one machine I am still compiling glibc and thus can't test so far, the other one already seems to be fine again (hope so) - except for postfix. Whatever I try I just can not get rid of the segmentation fault! - I re-emerged postfix several times -> segmentation fault. :-( - Tought it migth be related to the new 3.7 openssl - downgraded. --> segfault :-( - Re-emerged newest openssl. --> segfault :-( - re-emerged every packed listen in posftfix dependencies. --> segfault :-( - downgraded to postfix 2.0.14. --> segfault. :-( Help! My Mailserver is now down for two days... :-/ Any pointers? ;-) Thanks, Daniel
My laptop had been automatically downgraded from gcc 3.3.1-r2 back to -r1 by emerge. Don't know if it is relevant or not. Mark
add: - "emerge gcc-3.3.1-r1; emerge glibc; emerge postfix" --> segfault above... Arrrrg. Since 3.3.1-r2 I am only getting segmentation faults for postfix, no matter what I try! :-/ If only compiling wouldn't take forever on this PII-450...
I just did: "USE="-ssl -sasl -sasl2 -mysql" emerge postfix" and that works!! (then "emerge postfix", again segfaults.) Now that makes things quite clear so far, now that should only be a matter of time and a few more compiles... :-/
FYI: boils down to 'USE="-mysql" emerge postfix' ... (-> fixed).
This might be a problem with upgrading to openssl 0.9.7 (though I'm not sure). Be sure you run: # revdep-rebuild --soname libssl.so.0.9.6 # revdep-rebuild --soname libcrypto.so.0.9.6 after upgrading. Please run those two commands (if you haven't done so already) and then re- emerge postfix (version 2.0.16 if possible) and report your findings. Thank you. Just a point of interest: ike postfix # emerge -vp postfix These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] net-mail/postfix-2.0.16 -ipv6 +pam +ldap +mysql -postgres +ssl +sasl -maildir - mbox ike postfix # /etc/init.d/postfix restart * Stopping postfix... [ ok ] * Starting postfix... [ ok ] ike postfix # epm -q openssl openssl-0.9.7b-r3 ike postfix # epm -q mysql mysql-4.0.15 ike postfix #
Hello, Yes, you're right. It was openssl update, apparently breaking mysql, which broke postfix. Doing a rev-dep rebuild as proposed would have fixed it. But I didn't think of that and the ebuild was lacking the helpful einfo reminder that is beeing shown now. ;-) Back then emerging postfix, either without mysql support or after re-emerging mysql, fixed it for me (on both machines). Well, as far as I am concerned this bug can be closed... ;-) Regards, Daniel
Thank you for confirming. Closing.
