Date: Wed, 06 Mar 2013 13:51:36 +0100 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Dimitry Andric <dim@FreeBSD.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: r247839: broken pipe - for top, sudo and ports Message-ID: <51373BD8.1000104@zedat.fu-berlin.de> In-Reply-To: <513736AC.3030108@FreeBSD.org> References: <5135B7E1.3050002@zedat.fu-berlin.de> <5135BBD9.9090009@FreeBSD.org> <51364914.2010104@zedat.fu-berlin.de> <51364E8D.5020608@zedat.fu-berlin.de> <513736AC.3030108@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
------enig2ATEWQTXQAPQLEGJELDPA
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 03/06/13 13:29, Dimitry Andric wrote:
> On 2013-03-05 20:59, Hartmann, O. wrote:
> ...
>> A "truss top" reveals this, is this of help?
> ...
>> socket(PF_LOCAL,SOCK_STREAM,0) =3D 4 (0x4)
>> connect(4,{ AF_UNIX "/var/run/nscd" },15) =3D 0 (0x0)
>> fcntl(4,F_SETFL,O_NONBLOCK) =3D 0 (0x0)
> ...
>> sendmsg(0x4,0x7fffffffd290,0x0,0x1,0x1,0x0) ERR#32 'Broken pipe'
>=20
> Maybe your nscd might have died? It is successfully opening and
> connecting to nscd's unix socket, but gets an EPIPE when it tries to
> send data.
I tried "service nscd stop", stopping nscd, but I guess I also have to
change configuration /etc/nsswitch.conf then to make that effective.
Even with stopped nscd, I have those weird and strange "broken pipes" as
I reported (a little bit unsensible, I'm sorry).
I use TEMPFS for /var/run, /tmp. I also use nscd, OpenLDAP. This works
well with r247545, but with ~r247839 the strange behaviour occurs.
My gateway system dies due loosing connection sporadically because of
dying services.
Could this "socket problem" also affect any kind of user verification,
say, when a process starts up, but can not find its ID, like root, wheel
or ldap (for OpenLDAP) or nagios?
I reverted my sources to r247479 now and try to stick with those until
the problem has been identified by more bright people and developers.
I'm only an "advanced user", if ever, my abilities to debug are very
limited and for that I'm sorry. I can only provide "detailed" reports of
my desperate search for a solution.
Thanks and regards,
Oliver
------enig2ATEWQTXQAPQLEGJELDPA
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)
iQEcBAEBAgAGBQJRNzveAAoJEOgBcD7A/5N82MEIAN5ny9Cd260zVXoav5ec4nZF
4LydsGCuaU72zO7Ilo/p9itiNFqRCAklOK0bIUMvm2uLbfY7SXGGf6cp2j7Rf7XV
32AVBFBn2voPdanvX7JVJnewKdCflM/TzJEKvrbmr2IAhgi5jVjEmVWD92aQALiG
tL1GNfdK2DM2KBIWm0pTsQ2JiWhEMRaC3KKmSeL0FR4uXANrKftghiYNLBv+KG72
Gh1eei6PlS0HHoLGJfvN3JPbTrIfcAw44AN12hnx6oxV1x73efm9GPLHBOdGiJgd
zJYL5bCNEZhk4Z/10OPi8XaYNHjgKpbANdFHv/QoruHpIkmU4uAcAqQqH2wDVwI=
=TwKE
-----END PGP SIGNATURE-----
------enig2ATEWQTXQAPQLEGJELDPA--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51373BD8.1000104>