Conference bulova::decw_jan-89_to_nov-90

3605.0. "Another XIO problem" by MSBCS::BIRO () Wed Nov 07 1990 16:04

I have read the note 2681 which describes my problem to a tee.
    I have multiple users with the same problem.  Their xrun
    session just go away.  I have checked all satellite errorlogs
    and they basically say the same thing.  The amount of xrun
    windows varies, from 4 to maybe 8.  They are running on various
    types of workstations from GPX II up, with 8mb to 16mb of memory.
    VMS 5.3-2, being served on 5 8550's.  I need to find an answer
    as quick as possible and hope this is the place.  
    
    The only exception to the "disappearing" xrun windows happens
    if you have xrun windows running from a priv. account and non-priv
    account to the same workstation, the priv xrun windows do NOT dis-
    appear.  I feel it is some quota or network param. kill these
    processes.
    
    Included is a 12 block error file.
    
    thanx 
    
    mimi
    
 4-NOV-1990 15:41:31.5 Hello, this is the X server
Dixmain address=13074
Now attach all known txport images
%DECW-I-ATTACHED, transport DECNET attached to its network
%DECW-W-ATT_FAIL, failed to attach transport LAT
-SYSTEM-F-PRIVINSTALL, shareable images must be installed to run privileged image
%DECW-W-ATT_FAIL, failed to attach transport TCPIP
-SYSTEM-F-NOLOGNAM, no logical name match
in SetFontPath
Connection 99700 is accepted by Txport
out SetFontPath
GPX color/monochrome support loaded
gpx$InitOutput address=12c410
Connection Prefix: len == 42
 4-NOV-1990 15:47:24.2 Now I call scheduler/dispatcher
 4-NOV-1990 15:47:55.8 Connection 99738 is accepted by Txport
 4-NOV-1990 15:48:14.1 Connection 99700 is closed by Txport
 5-NOV-1990 07:58:32.8 Connection 99738 is closed by Txport
 5-NOV-1990 07:58:36.1 Connection 99700 is accepted by Txport
 5-NOV-1990 07:58:41.9 Connection 99770 is accepted by Txport
 5-NOV-1990 07:59:33.2 Connection 99738 is accepted by Txport
 5-NOV-1990 07:59:47.2 Connection 9adf8 is accepted by Txport
 5-NOV-1990 07:59:49.7 Connection 9ae30 is accepted by Txport
 5-NOV-1990 07:59:52.8 Connection 1d9630 is accepted by Txport
 5-NOV-1990 07:59:56.5 Connection 1d9a68 is accepted by Txport
 5-NOV-1990 07:59:59.5 Connection 1d9aa0 is accepted by Txport
 5-NOV-1990 08:00:38.0 Connection 256018 is accepted by Txport
 5-NOV-1990 08:40:17.5 Connection 2fda88 is accepted by Txport
 5-NOV-1990 08:41:03.2 Connection 2fdec0 is accepted by Txport
 5-NOV-1990 08:43:23.9 Connection 2fdec0 is closed by Txport (status = 20e4)
 5-NOV-1990 08:45:19.3 Connection 2fdac0 is accepted by Txport
 5-NOV-1990 08:45:48.1 Using extra todo packet pool...
 5-NOV-1990 08:46:42.6 Connection 99738 is closed by Txport (status = 20e4)
 5-NOV-1990 11:16:38.2 Connection 9ae30 is closed by Txport (status = 20f4)
 5-NOV-1990 11:16:46.7 Connection 2fdac0 is closed by Txport (status = 20fc)
 5-NOV-1990 11:55:22.1 Connection 2fda88 is closed by Txport (status = 20f4)
 5-NOV-1990 11:55:36.9 Connection 1d9aa0 is closed by Txport (status = 20f4)
 5-NOV-1990 13:01:08.2 Connection 2f9600 is accepted by Txport
 5-NOV-1990 13:01:08.5 Connection 2f9638 is accepted by Txport
 5-NOV-1990 13:01:11.7 Connection 2f9670 is accepted by Txport
 5-NOV-1990 13:01:30.8 Connection 2f9670 is closed by Txport (status = 20e4)
 5-NOV-1990 13:01:31.1 Txport status = 20e4 ( copy and write) on client 8
 5-NOV-1990 13:01:43.7 Connection 2f9670 is accepted by Txport
 5-NOV-1990 13:22:09.2 Connection 2fa2a8 is accepted by Txport
 5-NOV-1990 14:12:05.5 Connection 2fa2a8 is closed by Txport (status = 20e4)
 5-NOV-1990 14:12:05.8 Txport status = 20e4 ( copy and write) on client 10
 5-NOV-1990 14:15:46.2 Connection 2fa2a8 is accepted by Txport
 5-NOV-1990 15:20:22.1 Connection 2fa6e0 is accepted by Txport
 5-NOV-1990 15:20:36.0 Connection 2fa6e0 is closed by Txport (status = 20e4)
 5-NOV-1990 15:20:45.3 Connection 2fa6e0 is accepted by Txport
 5-NOV-1990 15:20:51.9 Connection 2fa718 is accepted by Txport
 5-NOV-1990 15:39:52.1 Connection 2fa6e0 is closed by Txport (status = 20e4)
 5-NOV-1990 15:39:53.8 Connection 2fa718 is closed by Txport (status = 20e4)
 6-NOV-1990 07:43:02.2 Connection 2fa6e0 is accepted by Txport
 6-NOV-1990 08:03:27.8 Connection 3dbc60 is accepted by Txport
 6-NOV-1990 08:04:16.7 Connection 3dc098 is accepted by Txport
 6-NOV-1990 09:50:17.7 Connection 2f9600 is closed by Txport (status = 20e4)
 6-NOV-1990 11:17:39.4 Connection 3dc0d0 is accepted by Txport
 6-NOV-1990 12:55:26.3 Connection 3dc098 is closed by Txport (status = 20e4)
 6-NOV-1990 12:55:26.7 Txport status = 20e4 ( copy and write) on client 13
 6-NOV-1990 12:58:33.3 Connection 3dc098 is accepted by Txport
 6-NOV-1990 12:59:21.1 Connection 3dc098 is closed by Txport (status = 20e4)
 6-NOV-1990 13:05:12.5 Connection 2fa2a8 is closed by Txport
 6-NOV-1990 13:05:24.8 Connection 3dc098 is accepted by Txport
 6-NOV-1990 13:24:57.1 Connection 3dc098 is closed by Txport (status = 20e4)
 6-NOV-1990 13:32:39.1 Connection 3dc098 is accepted by Txport
 6-NOV-1990 13:34:24.6 Connection 3dc098 is closed by Txport (status = 20e4)
 6-NOV-1990 13:35:00.5 Connection 3dc098 is accepted by Txport
 6-NOV-1990 13:36:02.1 Connection 3dc098 is closed by Txport (status = 20e4)
 6-NOV-1990 14:24:34.4 Connection 3dc098 is accepted by Txport
 6-NOV-1990 15:09:53.1 Connection 3dbc60 is closed by Txport (status = 20e4)
 6-NOV-1990 15:09:53.8 Connection 3dc098 is closed by Txport (status = 20e4)
 6-NOV-1990 15:42:33.6 Connection 3dbc60 is accepted by Txport
 6-NOV-1990 16:45:44.0 Connection 3dc098 is accepted by Txport
 6-NOV-1990 16:45:45.0 Connection 3dc098 is closed by Txport (status = 20e4)
 6-NOV-1990 17:05:54.1 Connection 3dbc60 is closed by Txport (status = 20e4)
 7-NOV-1990 14:10:15.9 Connection 4f2a00 is accepted by Txport
 7-NOV-1990 14:23:41.9 Connection 3dc0d0 is closed by Txport (status = 20e4)
 7-NOV-1990 14:23:42.1 Connection 4f2a00 is closed by Txport (status = 20e4)
 7-NOV-1990 14:23:42.7 Connection 1d9a68 is closed by Txport (status = 20e4)
 7-NOV-1990 14:23:44.1 Connection 9adf8 is closed by Txport (status = 20e4)
 7-NOV-1990 14:25:46.5 Connection 4f6e30 is accepted by Txport
 7-NOV-1990 14:26:02.2 Connection 4f9280 is accepted by Txport
 7-NOV-1990 14:26:07.1 Connection 4f96b8 is accepted by Txport
 7-NOV-1990 14:26:13.4 Connection 4fb708 is accepted by Txport
 7-NOV-1990 14:26:49.1 Connection 4fbb40 is accepted by Txport
 7-NOV-1990 14:29:06.0 Connection 5026d8 is accepted by Txport
 7-NOV-1990 14:29:09.6 Connection 5026d8 is closed by Txport (status = 20e4)
 7-NOV-1990 14:45:41.5 Connection 5003a8 is accepted by Txport
 7-NOV-1990 14:50:26.0 Connection 5003a8 is closed by Txport (status = 20e4)
 7-NOV-1990 14:50:26.3 Connection 5003e0 is accepted by Txport
 7-NOV-1990 14:58:26.7 Connection 5003e0 is closed by Txport (status = 20e4)
 7-NOV-1990 15:11:43.8 Connection 4fbb40 is closed by Txport (status = 20e4)
 7-NOV-1990 15:12:39.4 Connection 4fb740 is accepted by Txport

	I have a similar problem...the log below shows that the 
    	call to the scheduler is never resolved. The visual symptom
    	is that the DEC logo box briefly appears without the Digital
    	text and then the sceen clears. The DECW$server runs but the
    	WSA process dies. 
    
 7-NOV-1990 15:52:52.6 Hello, this is the X server
Dixmain address=127b0
Now attach all known txport images
%DECW-I-ATTACHED, transport DECNET attached to its network
in SetFontPath
out SetFontPath
GPX color/monochrome support loaded
gpx$InitOutput address=1297f4
Connection Prefix: len == 42
 7-NOV-1990 15:59:00.7 Now I call scheduler/dispatcher
 7-NOV-1990 15:59:11.2 Connection 98d00 is closed by Txport
 7-NOV-1990 15:59:16.2 Connection 98d38 is closed by Txport
 7-NOV-1990 15:59:17.0 GPX color/monochrome support loaded
gpx$InitOutput address=1297f4
 7-NOV-1990 15:59:18.1 Now I call scheduler/dispatcher

    The problem in .1 persists...Colorodo support has spent several hours
    assisting with no resolve. Something that is apparent is that the
    WSA process is getting an ACCVIO in the loginout image, resulting
    in the symptom described. The system has been AUTOGEN'd and many other
    activities have been performed. The problem persists. Additionally,
    some workstation that booted with DECwindows and we're opererational
    have become inoperatable after quitting the session. 
    
    Any directions/suggestions appreciated. As a matter of fact DECwindows
    was reinstalled as a possible resolution but the problem persists.
    
    ,Red

I think the problem in .1 is different than the one in .0.

.0 has DECnet connections that are dying, and he suspects network problems.
I think that is correct.

.1 has a dying WSA process.  DECW$LOGINOUT uses the local shared
memory transport and not DECnet to talk to the server, so it
really can't be the same problem.  If LOGINOUT is getting an ACCVIO,
I doubt that the problem is quotas or system tuning.  It's just a
plain bug.

The important thing is to find out at what PC LOGINOUT is dying.
Unfortunately, debugging LOGINOUT is not for the faint of heart.

    Well here's some follow-up.
    
    The 'problem' disk errors during an ANALYZE/DISK with bad more than the
    normal backlink errors. We are restoring a backup and will post the
    the outcome. The problem is starting to make sense.
    
    fyi

    The image restore did resolve the problem. It seems that a problem
    has been present for a while (at leaset 2 weeks) and by performing
    an image defrag (disk-disk) something was corrupt and not copied but
    was never detected in the logs (humans....).
    
    fyi,