Return-path: <alpha-osf-managers-relay_at_sws1.ctd.ornl.gov>
Received: from sws1.CTD.ORNL.GOV by SLUVCA.SLU.EDU (PMDF V5.0-4 #5070)
id <01HVTZI897Z48Y56IA_at_SLUVCA.SLU.EDU> for ALPHAOSF_at_SLUAVA.SLU.EDU; Fri,
29 Sep 1995 03:26:39 -0600 (CST)
Received: (from daemon_at_localhost) by sws1.CTD.ORNL.GOV (8.6.10/8.6.10)
id KAA04999 for aomaa; Mon, 25 Sep 1995 10:18:31 -0400
Received: from oaunx1.ctd.ornl.GOV (oaunx1.ctd.ornl.gov [128.219.128.17])
by sws1.CTD.ORNL.GOV (8.6.10/8.6.10) with ESMTP id KAA04987 for
<alpha-osf-managers_at_sws1.ctd.ornl.gov>; Mon, 25 Sep 1995 10:18:29 -0400
Received: from UMALP2.physics.lsa.umich.edu by oaunx1.ctd.ornl.GOV
(8.6.10/3.0-C) id KAA07134; Mon, 25 Sep 1995 10:18:28 -0400
Received: by umalp1.physics.lsa.umich.edu (MX V4.1 AXP) id 64; Mon,
25 Sep 1995 10:17:31 -0400 (EDT)
Date: Mon, 25 Sep 1995 10:19:31 -0400 (EDT)
From: "Dave Wolinski, University of Michigan"_at_sws1.CTD.ORNL.GOV
Subject: session dies unexpectedly - help!
Sender: alpha-osf-managers-relay_at_sws1.ctd.ornl.gov
To: alpha-osf-managers_at_ornl.gov
Reply-to: "Dave Wolinski, University of Michigan"
<wolinski_at_umalp1.physics.lsa.umich.edu>
Message-id: <00996EB8.DE303465.64_at_umalp1.physics.lsa.umich.edu>
Content-transfer-encoding: 7BIT
Followup-to: poster
Our Alpha is running OSF/1 v3.0, and the following bizarre problem has
come up over the last week:
When logged into the console, your session can be terminated for no obvious
reason, returning the console to the default login screen. Your session will
NOT termiante when your input is idle; rather, what usually happens is that
you'll click on a different window, and suddenly there will be lots of disk
activity (the core file dumps), and then the screen goes black, and finally
the login screen comes up. Sometimes you can use the console for 5-10 minutes
before this happens. The problem is independent of the user logged in.
The problem has grown worse over the last week, at first occuring once a day
or so, and now, every session. Certain users, namely root, will login, and
then their session will die while their automatic startup programs are loading!
No significant system changes took place before the onset of this problem. The
only potentially helpful diagnostic output that I've been able to look at is
the X Display Manager (xdm) error log file. Usually, when the session dies,
the following line is output to xdm-errors:
error (pid 362): Server for display :0 terminated unexpectedly: 2816
[where 362=xdm pid, 2816=?? pid]
Occasionally, xdm-error gets:
XIO: fatal IO error 32 (Broken pipe) on X server ":0.0"
after 152 requests (151 known processed) with 1 events remaining.
The connection was probably broken by a server shutdown or KillClient.
error (pid 2377): fatal IO error 32 (Broken pipe)
[where 2377=?? pid]
I've tried rebooting the system but the problem persists. Does anyone have
any idea what the problem might be?
Thanks, Dave Wolinski
University of Michigan
Received on Sat Sep 30 1995 - 08:44:33 NZST