Anton - Valqk
2008-Mar-28 22:17 UTC
why does my apache-worker broke after upgrade to 6_3_RELEASE?
Hi group, does anyone has idea why the #$#$#$%$%#$%$@#$% upgrade to latest 6_3_RELEASE broke my apache-worker?!??? In logs I get: Fatal error 'kse_exit() failed for system scope thread' at line 1215 in file /usr/src/lib/libpthread/thread/thr_kern.c (errno = 22) I don't think it's a suggested behavior? This broke my apache for christ sake!!! Not pretty sure about all other threaded apps..... after 10 times I've rebuilded my port from scratch and seeing that it's not a problem with this, I've found a solution: adding in /etc/libmap.conf [httpd] libpthread.so.2 libthr.so.2 libpthread.so libthr.so but can anyone tell me why the @#$@$R#%$@$$@$@$#% I get to this state by only updating to 6_3_RELEASE which is SUPPOSED TO BE ROCK SOLID STABLE!!!! and don't break that ugly things!!! freebsd is really pissing me off recently! I'm seeing a great increase of the problems recent years, as I'm following the list and dealing with it. anywayz, can anyone answer me plz why did I get to this state? thanks -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Aryeh M. Friedman
2008-Mar-28 22:55 UTC
why does my apache-worker broke after upgrade to 6_3_RELEASE?
Anton - Valqk wrote:> Hi group, > does anyone has idea > why the #$#$#$%$%#$%$@#$% upgrade to latest 6_3_RELEASE > broke my apache-worker?!??? > In logs I get: > Fatal error 'kse_exit() failed for system scope thread' at line 1215 in > file /usr/src/lib/libpthread/thread/thr_kern.c (errno = 22) > > I don't think it's a suggested behavior? > This broke my apache for christ sake!!! > Not pretty sure about all other threaded apps..... > after 10 times I've rebuilded my port from scratch and seeing that it's > not a problem with this, > I've found a solution: > adding in /etc/libmap.conf > > [httpd] > libpthread.so.2 libthr.so.2 > libpthread.so libthr.so > > > but can anyone tell me why the @#$@$R#%$@$$@$@$#% I get to this state > by only updating to 6_3_RELEASE which is SUPPOSED TO BE ROCK SOLID > STABLE!!!! > and don't break that ugly things!!! > freebsd is really pissing me off recently! > I'm seeing a great increase of the problems recent years, as I'm > following the list and dealing with it. > anywayz, can anyone answer me plz why did I get to this state? > > thanks > > >Did you re-install apache from ports and everything it depends on? If so look at the man page for libmap.conf (*BUT* make extra sure you actually re-installed everything instead of just thinking you did)
Ivan Voras
2008-Mar-30 13:44 UTC
why does my apache-worker broke after upgrade to 6_3_RELEASE?
Anton - Valqk wrote:> Hi group, > does anyone has idea > why the #$#$#$%$%#$%$@#$% upgrade to latest 6_3_RELEASE > broke my apache-worker?!??? > In logs I get: > Fatal error 'kse_exit() failed for system scope thread' at line 1215 in > file /usr/src/lib/libpthread/thread/thr_kern.c (errno = 22) > > I don't think it's a suggested behavior? > This broke my apache for christ sake!!! > Not pretty sure about all other threaded apps..... > after 10 times I've rebuilded my port from scratch and seeing that it's > not a problem with this, > I've found a solution: > adding in /etc/libmap.conf > > [httpd] > libpthread.so.2 libthr.so.2 > libpthread.so libthr.soSince many people (including myself) have upgraded from 6.something to 6.3-RELEASE without problems, it's probably something specific to your own system. Have you tried rebuilding world instead of port? What does `ldd /usr/local/sbin/httpd` say when you remove libmap.conf? Here's what it says on one of my 6.3 systems: > ldd /usr/local/sbin/httpd /usr/local/sbin/httpd: libm.so.4 => /lib/libm.so.4 (0x80068c000) libaprutil-1.so.2 => /usr/local/lib/libaprutil-1.so.2 (0x8007a8000) libexpat.so.6 => /usr/local/lib/libexpat.so.6 (0x8008c0000) libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x8009e2000) libapr-1.so.2 => /usr/local/lib/libapr-1.so.2 (0x800bd3000) libcrypt.so.3 => /lib/libcrypt.so.3 (0x800cfa000) libpthread.so.2 => /lib/libpthread.so.2 (0x800e13000) libc.so.6 => /lib/libc.so.6 (0x800f3e000) What is your result? Try `ident /lib/libpthread.so.2`, here's my result (amd64): > ident /lib/libpthread.so.2 /lib/libpthread.so.2: $FreeBSD: src/lib/csu/amd64/crti.S,v 1.7 2004/03/21 01:39:01 peter Exp $ $FreeBSD: src/lib/csu/amd64/crtn.S,v 1.6 2004/03/21 01:39:01 peter Exp $ $FreeBSD: src/lib/libpthread/thread/thr_pselect.c,v 1.5 2003/12/09 02:20:56 davidxu Exp $ $FreeBSD: src/lib/libpthread/thread/thr_connect.c,v 1.2 2003/12/09 23:40:27 deischen Exp $ $FreeBSD: src/lib/libpthread/thread/thr_accept.c,v 1.2 2003/12/09 23:40:27 deischen Exp $ $FreeBSD: src/lib/libpthread/thread/thr_sigaltstack.c,v 1.2 2004/01/02 00:38:42 davidxu Exp $ $FreeBSD: src/lib/libpthread/thread/thr_printf.c,v 1.4 2004/02/10 20:42:33 cperciva Exp $ $FreeBSD: src/lib/libpthread/thread/thr_kern.c,v 1.116.2.1 2006/03/16 23:29:07 deischen Exp $ $FreeBSD: src/lib/libpthread/arch/amd64/amd64/enter_uts.S,v 1.5 2004/07/31 01:53:21 davidxu Exp $ $FreeBSD: src/lib/libpthread/arch/amd64/amd64/context.S,v 1.7.8.1 2006/03/16 23:29:06 deischen Exp $ $FreeBSD: src/lib/libc/gen/sigsetops.c,v 1.8 2002/02/01 00:57:29 obrien Exp $ $FreeBSD: src/lib/libc/string/bcopy.c,v 1.6 2003/10/26 03:55:58 peter Exp $ $FreeBSD: src/lib/libc/string/bzero.c,v 1.2 2002/03/22 21:53:19 obrien Exp $ $FreeBSD: src/lib/libc/string/memset.c,v 1.8 2002/09/01 21:53:46 robert Exp $ $FreeBSD: src/lib/libc/amd64/sys/cerror.S,v 1.14 2005/04/21 12:47:08 kan Exp $ $FreeBSD: src/lib/libc/string/memcpy.c,v 1.2 2002/03/22 21:53:19 obrien Exp $ $FreeBSD: src/lib/libc/string/bcopy.c,v 1.6 2003/10/26 03:55:58 peter Exp $ $FreeBSD: src/lib/libc/string/memset.c,v 1.8 2002/09/01 21:53:46 robert Exp $ $FreeBSD: src/lib/libc/string/strcpy.c,v 1.7 2002/09/06 11:24:06 tjr Exp $ $FreeBSD: src/lib/libc/string/strlen.c,v 1.4 2002/03/21 18:44:54 obrien Exp $ Also, are you sure as to what you upgraded to? Are your kernel and world in sync? KSE was removed from 8-CURRENT so it could be a problem if you somehow got binaries or libraries from 8-CURRENT.> anywayz, can anyone answer me plz why did I get to this state?If nothing obvious pops up from the above, you could maybe create an archive of all files ldd says are loaded by httpd so developers can take a look at it. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20080330/fcb8a190/signature.pgp
Anton - Valqk
2008-Apr-17 02:21 UTC
why does my apache-worker broke after upgrade to 6_3_RELEASE?
well, well, well..... FreeBSD Errata Notice FreeBSD-EN-08:01.libpthread is this connected to my problem with apache2-worker? I think so. another problem in last two months. I'm experiencing another strange problem with mount_nullfs locking. The system is simply, hanging, despite of losing dirs that are null mounted! IMHO FreeBSD is going very wrong way... in 4.10, 5.X times the sysadmin wasn't working when he got his job done. now.... you simply can't know what will happen on next update to 'STABLE'.... and no bin packages (unlike debian). If this continues, it won't take me long to migrate to debian, despite I don't want to, but I want to have a nice deep sleep, no alarms in the middle of the night.... cheers, valqk. Aryeh M. Friedman wrote:> Anton - Valqk wrote: >> Hi group, >> does anyone has idea >> why the #$#$#$%$%#$%$@#$% upgrade to latest 6_3_RELEASE >> broke my apache-worker?!??? >> In logs I get: >> Fatal error 'kse_exit() failed for system scope thread' at line 1215 in >> file /usr/src/lib/libpthread/thread/thr_kern.c (errno = 22) >> >> I don't think it's a suggested behavior? >> This broke my apache for christ sake!!! >> Not pretty sure about all other threaded apps..... >> after 10 times I've rebuilded my port from scratch and seeing that it's >> not a problem with this, >> I've found a solution: >> adding in /etc/libmap.conf >> >> [httpd] >> libpthread.so.2 libthr.so.2 >> libpthread.so libthr.so >> >> >> but can anyone tell me why the @#$@$R#%$@$$@$@$#% I get to this state >> by only updating to 6_3_RELEASE which is SUPPOSED TO BE ROCK SOLID >> STABLE!!!! >> and don't break that ugly things!!! >> freebsd is really pissing me off recently! >> I'm seeing a great increase of the problems recent years, as I'm >> following the list and dealing with it. >> anywayz, can anyone answer me plz why did I get to this state? >> >> thanks >> >> >> > Did you re-install apache from ports and everything it depends on? > If so look at the man page for libmap.conf (*BUT* make extra sure you > actually re-installed everything instead of just thinking you did) > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.