[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

2606.0. "Decwindows sessions getting dropped " by FAVAX::CRAWFORD () Thu Apr 12 1990 16:28

can someone offer some suggestions as what to look for.  I suspect it may 
be related to sysgen parameters.  I am attaching a description of the 
problem as I have received it from a user with a complaint about his 
decwindows sessions getting dropped.

The two systems mentioned (Rainbo and Mosaic) are both 8800's that are part
of a 3 node cluster with a common system disk.  Rainbo gets a little more 
interactive use than Mosaic, other than that they are almost identical in 
their setups.

PROBLEM DESCRIPTION:
_____________________
   To:     ACTION_DESK
   Subj:   loss of DECwindows sessions to Rainbo::

   Over the past month or two, a number of us DECwindows users (myself, 
   plus at least 5 other users) have occasionally (every few days) lost
   DECwindows sessions to Rainbo.

   A quick check reveals that Rainbo hasn't crashed and that DECnet is still
   running on Rainbo and that a new DECwindows connection can generally be made
   to Rainbo.  
   
   Normally I have two DECterm sessions on Rainbo and one on Mosaic.  I've
   only seen the one on Mosaic go away when Mosaic crashes.  The ones on 
   Rainbo drop sporadically, 0 to 3 times per week, and I can always make a 
   new connection to Rainbo right away.    

   I start my sessions with @sys$login:dwstart RAINBO decw$terminal
                                            
   Any idea what's going on?

   Disgruntled user
+++++++++++++++++++++++++++++++++++++++++++++++

Thanks for any tips on what to look for
T.RTitleUserPersonal
Name
DateLines
2606.1More information neededSTAR::VATNEPeter Vatne, VMS DevelopmentThu Apr 12 1990 17:351
Please tell us at least what version of VMS you're running...
2606.2VMS 5.3-1FAVAX::CRAWFORDFri Apr 13 1990 10:144
>>>Please tell us at least what version of VMS you're running...

We are running VMS 5.3-1
2606.3The windows are so clean like their not even there! QUALLA::BETTROFri Apr 13 1990 12:3613
	I've encountered the disappearing windows a few times myself. One such
	time running under VMS 5.2.. That problem was due to a flakey H4000
	on the ethernet segment transmitting garbage over the net. Once the
	H4000 was identified and replaced the problems went away. The second
	time just recently since I just changed over my 3100 from a model 30
	to a model 38. It appears we are running T5.3-2EU of VMS and from
	talking with people at ZKO, support for VAXstation 3100-m38 is only
	fully supported in VMS v5.3-1. The problem seems to have stabalized
	though on the test version since my windows have hung around now for
	almost 3 days now. They say things may or may not work under the
	test version.

			Joe
2606.4STAR::MCLEMANOh No, not that again... Fri Apr 13 1990 14:123
The VS3100-M38 is supported in V5.2-1

The VS3100 M38 with a SPX is supported in V5.3-1
2606.5A little more information please...DECWIN::JMSYNGEJames M Synge, VMS DevelopmentMon Apr 16 1990 12:2010
    Re. 0:
    
    Is RAINBO a DECnet router?  Does the cluster have a DECnet cluster
    alias?
    
    The file SYS$MANAGER:DECW$SERVER_0_ERROR.LOG should include a message
    indicating why the connection has closed, including a hex error code. 
    Could you post a note including the relavent portion of the log file?
    
    Thanks.
2606.6more information...as requestedFAVAX::CRAWFORDTue Apr 17 1990 11:32115
    Re (.5)  
  
   >> Is RAINBO a DECnet router?  Does the cluster have a DECnet cluster
   >> alias?
    
    yes, Rainbo is a router because of the cluster alias...but, alas, so
    is Mosaic.  

  >>    The file SYS$MANAGER:DECW$SERVER_0_ERROR.LOG should include a message
  >>  indicating why the connection has closed, including a hex error code. 
  >>  Could you post a note including the relavent portion of the log file?
    
    I asked the engineer who made the initial complaint to send me any info
    he had.  I have enclosed his response below:

From:	RANGER::PRAETORIUS "take your kansei and fahrvergn�gen it  17-Apr-1990 1009" 17-APR-1990 10:25:51.63
To:	FAVAX::CRAWFORD
CC:	
Subj:	RE: Responses to the problem of decwindows dropping on Rainbo

     My node (POPJ1) is running VMS V5.3

>    The file SYS$MANAGER:DECW$SERVER_0_ERROR.LOG should include a message
>    indicating why the connection has closed, including a hex error code. 
>    Could you post a note including the relavent portion of the log file?

     I've got two nonempty versions of this file, I'll include both.  I try to
remember to quickly check this file next time it happens, so we can positively
correlate the error.

     POPJ1::SYS$MANAGER:DECW$SERVER_0_ERROR.LOG;124

27-MAR-1990 13:26:03.7 Hello, this is the X server
Dixmain address=127b0
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 imag
e
in SetFontPath
out SetFontPath
GPX color/monochrome support loaded
gpx$InitOutput address=1297f4
Connection Prefix: len == 42
27-MAR-1990 13:27:11.8 Now I call scheduler/dispatcher
27-MAR-1990 13:27:23.0 Connection 98d00 is closed by Txport
27-MAR-1990 13:27:57.0 Connection 98d38 is closed by Txport
27-MAR-1990 14:04:02.6 Connection 1e4648 is closed by Txport(status = 20f4)
27-MAR-1990 14:13:36.4 Using extra todo packet pool...
 1-APR-1990 17:44:50.1 Connection 9a430 is closed by Txport(status = 20fc)
 2-APR-1990 14:29:04.5 Connection 290290 is closed by Txport
 5-APR-1990 16:29:07.1 Connection 2ecda0 is closed by Txport(status = 20e4)
 5-APR-1990 16:30:10.4 Connection 318438 is closed by Txport
 6-APR-1990 15:36:50.8 Connection 318470 is closed by Txport(status = 20e4)
 8-APR-1990 09:19:04.1 Connection 318438 is closed by Txport(status = 20e4)
 8-APR-1990 10:23:22.8 Connection 318400 is closed by Txport(status = 20e4)
10-APR-1990 16:10:42.3 Connection 318400 is closed by Txport(status = 20f4)
12-APR-1990 10:06:28.4 Connection 318400 is closed by Txport(status = 20fc)
12-APR-1990 10:06:28.6 Txport status = 20fc ( copy and write) on client 5
12-APR-1990 16:41:46.0 Connection 9a3f8 is closed by Txport
12-APR-1990 21:26:02.5 Connection 318400 is closed by Txport(status = 20e4)
13-APR-1990 15:10:25.4 Connection 321508 is closed by Txport(status = 20e4)

     POPJ1::SYS$MANAGER:DECW$SERVER_0_ERROR.LOG;122

23-MAR-1990 10:56:25.1 Hello, this is the X server
Dixmain address=127b0
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 imag
e
in SetFontPath
out SetFontPath
GPX color/monochrome support loaded
gpx$InitOutput address=1297f4
Connection Prefix: len == 42
23-MAR-1990 10:57:33.4 Now I call scheduler/dispatcher
23-MAR-1990 10:57:46.4 Connection 98d00 is closed by Txport
23-MAR-1990 10:58:07.2 Connection 98d38 is closed by Txport
23-MAR-1990 13:57:28.0 Using extra todo packet pool...
23-MAR-1990 16:54:41.0 Connection 2dbab8 is closed by Txport
23-MAR-1990 16:55:08.5 Connection 2dbab8 is closed by Txport
26-MAR-1990 15:16:44.3 Connection 200418 is closed by Txport(status = 20fc)
26-MAR-1990 15:17:29.3 Connection 204cb8 is closed by Txport(status = 20fc)
27-MAR-1990 11:26:47.2 Connection 2dbb28 is closed by Txport(status = 20e4)

     My DECW$SM.LOG (in the POPJ1 end) is empty.

     My NETSERVER.LOG (on the RAINBO end) looks like:

[SYS$SYLOGIN:.COM stuff]
[SYS$LOGIN:LOGIN.COM stuff]
$ !  Copyright (c) 1987 Digital Equipment Corporation.  All rights reserved.
$ IF "" .NES. "" THEN NETSERVER$COMMAND
$ IF ""  .EQS. "" THEN NETSERVER$VERIFY = 0
$ V = F$VERIFY(NETSERVER$VERIFY)

        --------------------------------------------------------

        Connect request received at 12-APR-1990 10:10:11.81
            from remote process POPJ1::"0=PRAETORIUS"
            for object "DWSTART"

        --------------------------------------------------------

  PRAETORIUS   job terminated at 12-APR-1990 10:15:27.53

  Accounting information:
  Buffered I/O count:          109      Peak working set size:   585
  Direct I/O count:             88      Peak page file size:    5597
  Page faults:                1213      Mounted volumes:           0
  Charged CPU time:     0 00:00:02.59   Elapsed time:     0 00:05:24.76