Re: r247839: broken pipe - for top, sudo and ports

看板FB_current作者時間12年前 (2013/04/27 13:32), 編輯推噓0(000)
留言0則, 0人參與, 最新討論串8/13 (看更多)
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2TQQENHDMCCPRQRLCMOCJ Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 03/06/13 14:04, schrieb John Baldwin: > On Tuesday, March 05, 2013 2:35:48 pm Hartmann, O. wrote: >> On recent FreeBSD 10.0-CURRENT/amd64 (CLANG buildworld, serveral syste= ms >> (3) the same symptoms)), many services drop a sporadic >> >> broken pipe >> >> This happesn to system's top (I have to type it several times to get >> finally a top), it happens to "sudo su -", it happens to SSH (drops >> connection with broken pipe) and as I reported earlier, it seems to >> affect the entire port system, since I can not build any port, I recei= ve >> >> *** [do-extract] Signal 13 >> >> This is dramatic for me, because several modules (rtc, linux_adobe ...= ) >> can not be recompiled as it is required by the last /usr/src/UPDATING >> entry 20130304. >> >> Since dbus fails to start and even the nVidia driver (which is a kerne= l >> module, it canot be built and therefore ... ). >> >> Dimitry, I put you into CC, just in case. It seems that the last commi= ts >> (not only the new DRM2 mess) broke something. >> >> I hope that others using FreeBSD 10.0CURRENT with CLANG can confirm th= is.\ >=20 > Have you tried backing up to just before all of pjd@'s file descriptor = and > capsicum commits? It broke some other stuff initially related to fd pa= ssing, > so I don't think it is beyond imagination that it broke something with = UNIX > domain sockets in general. >=20 Yes, just this moment, the systems are "back" to r247479 and up and running as expected. I have also one box running a more recent r247539 or similar, but beyond that, things get really weird. As I reported, the problem isn't present in single user mode and seems to affect all of my systems which use nscd and OpenLDAP (this is standard (LDAP) in our environment). As pjd@ mentioned, things could be broken and I wait until the dust has seddled. With regards, Oliver ------enig2TQQENHDMCCPRQRLCMOCJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBAgAGBQJRN4GQAAoJEOgBcD7A/5N88TgH/1B7CObFRXf7kTJg63oL/Ms5 6rCTnrEIhkPiE7NNUndi2zJsi/9bZ0QLxqMRBevetgXvfIQW+4qvo4EPQKhmH3Ig eiL/EuVnacxNSh66sSlJmHubKrdo/nG1j30OlbkdS2OFKspCOqN2XmNXiyUGa6DV TGlIhOG55PnGe8DSsDOedXw2DM4ncXANTPXVYCnU1ScBgUCTDwCNoR5f3CKiYhiW lsiIuuCocg4xvuWN+zEVSkOwQHP525ma3g5ScUKtS0Yrp9Ahq9hBmGz8ySgsV9rU d9AKH/YzkM2Y4OGpOoFOzM2Rr8TBzDzK3yf18JYawwIWAJrJ44f+CdNlL5fH0XI= =ZQpP -----END PGP SIGNATURE----- ------enig2TQQENHDMCCPRQRLCMOCJ--
文章代碼(AID): #1HUsBaJ7 (FB_current)
討論串 (同標題文章)
文章代碼(AID): #1HUsBaJ7 (FB_current)