> I recently upgraded 3 of my 5 servers to 7.0. Two of them are on
> new hardware and one is on hardware that used to run 6.2. Since
> then, 2 of my thousands of users are unable to access the servers
> running 7.0. They can access the server running 6.2 just fine.
> What happens is the server receives the SYN packet from the client
> properly and then responds with the SYN packet. Nothing more is
> heard from the client. The server sends a few duplicates of the SYN
> and then drops the connection.
>
> At this point I am not able to verify that the client receives the
> SYN. Neither of them has a clue about tcpdump. The packets look
> fine on this end (included later). Both are using Windows,
> including XP and Vista. I suspect they are receiving it and not
> accepting it for some reason. However, I don't really see anything
> that would cause that behavior in the packets. I can't reproduce
> the problem here. Every computer I can try works just fine.
>
> Here is one of the packet traces:
>
> 11:59:00.630414 00:00:0c:38:6f:e1 (oui Cisco) > 00:a0:cc:3e:87:9e ...

> 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 ...