From owner-freebsd-current  Wed Nov  6 19:11:13 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id TAA20525
          for current-outgoing; Wed, 6 Nov 1996 19:11:13 -0800 (PST)
Received: from dfw-ix2.ix.netcom.com (dfw-ix2.ix.netcom.com [206.214.98.2])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA20518
          for <current@freebsd.org>; Wed, 6 Nov 1996 19:11:09 -0800 (PST)
Received: from silvia.HIP.Berkeley.EDU (wck-ca15-19.ix.netcom.com [207.94.231.51]) by dfw-ix2.ix.netcom.com (8.6.13/8.6.12) with ESMTP id TAA00652 for <current@freebsd.org>; Wed, 6 Nov 1996 19:10:29 -0800
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.2/8.6.9) id TAA24792; Wed, 6 Nov 1996 19:10:23 -0800 (PST)
Date: Wed, 6 Nov 1996 19:10:23 -0800 (PST)
Message-Id: <199611070310.TAA24792@silvia.HIP.Berkeley.EDU>
To: current@freebsd.org
Subject: yp_next failure
From: asami@freebsd.org (Satoshi Asami)
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I noticed that a lot of user processes started dying due to high
network load.  For instance, I get things like this:

===
>> rlogin vader
Last login: Wed Nov  6 18:41:44 from 136.152.64.181
yp_next: clnt_call: RPC: Timed out

rlogin: connection closed.
===

and this is in /var/log/messages:

===
Nov  6 18:43:16 vader /kernel: pid 22470 (login), uid 0: exited on signal 11
===

Other processes that died today were (this is just a small part of the 
log):

===
Nov  6 15:40:31 vader /kernel: pid 852 (sendmail), uid 0: exited on signal 11
Nov  6 15:40:48 vader /kernel: pid 856 (from), uid 5531: exited on signal 11
Nov  6 15:41:05 vader /kernel: pid 863 (ssh), uid 0: exited on signal 11
Nov  6 15:48:26 vader /kernel: pid 994 (xterm), uid 0: exited on signal 11
Nov  6 15:48:39 vader /kernel: pid 1019 (xterm), uid 0: exited on signal 11
Nov  6 15:48:40 vader /kernel: pid 1021 (xterm), uid 0: exited on signal 11
Nov  6 15:48:41 vader /kernel: pid 1029 (xterm), uid 0: exited on signal 11
Nov  6 15:48:41 vader /kernel: pid 1025 (xterm), uid 0: exited on signal 11
Nov  6 15:48:41 vader /kernel: pid 1027 (xterm), uid 0: exited on signal 11
Nov  6 15:48:41 vader /kernel: pid 1026 (xterm), uid 0: exited on signal 11
Nov  6 15:48:41 vader /kernel: pid 1024 (xterm), uid 0: exited on signal 11
Nov  6 15:48:49 vader /kernel: pid 1017 (xterm), uid 0: exited on signal 11
Nov  6 15:51:27 vader /kernel: pid 1436 (ssh), uid 0: exited on signal 11
Nov  6 15:53:41 vader /kernel: pid 1653 (xterm), uid 0: exited on signal 11
Nov  6 15:55:26 vader /kernel: pid 1791 (cron), uid 0: exited on signal 11 (core dumped)
Nov  6 16:03:42 vader /kernel: pid 1888 (mailq), uid 0: exited on signal 11
Nov  6 16:55:11 vader /kernel: pid 3804 (cron), uid 0: exited on signal 11 (core dumped)
Nov  6 16:55:41 vader /kernel: pid 3805 (sendmail), uid 0: exited on signal 11
===

Are these many programs supposed to die when a YP lookup has failed?
The network has been congested lately, but I haven't seen this kind of 
mass suicide until just recently.

Satoshi