[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

1437.0. "Unknown situation kills process on specific node! " by RABBET::FARRELL (Money, there is no substitute!) Wed Sep 13 1989 15:25

Hello,

Just when I thought I had seen all the DECW "situations" that I was going to..

I have an account on a cluster (5 nodes).  This account works fine, on all
of the nodes *except* one (this person's main node, of course).

All other accounts work fine on this node, and his account works fine on all
the other systems.

However, when he logs into this one system, he cannot create a DECterm window,
nor can run any application from FileView (yes, FileView does come up).
The error he gets is Xlib error, cannot open display, fatel error..

If, however, he issues the command $ SET DISPLAY/CREATE/NODE=MYNODE::

and then tries to run a DECW$ application, it works fine.
The DECW$SM.LOG file follows.  He tries to open a DECterm during startup,
and as the log shows, there is definatly a problem.

-------

%SET-I-NEWLIMS, new working set:  Limit = 200  Quota = 200  Extent = 12000
Session Message: Started DECterm controller

%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=7FF20600, PC=000CA7C1, PSL=0BC00

  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000005                00000000
        Name   = 0000000C                20FC0000
                 00000004                00007FF0
                 7FF20600                7FF1F6E0
                 000CA7C1                0000BE85
                 0BC00009                7FF1F990
                                         0000152C
                                         00000000
                                         00000000
                                         00000001

        Register dump

        R0 = 00000000  R1 = 7FF1F630  R2 = 00000000  R3 = 7FF20600
        R4 = 00007084  R5 = 0600D100  R6 = 00007FEF  R7 = 00007FEF
        R8 = 00001562  R9 = 001E28EA  R10= 000F31B8  R11= 00000000
        AP = 7FF1F5F4  FP = 7FF1F5B4  SP = 7FF1F630  PC = 000CA7C1
        PSL= 0BC00009

  PALONE       logged out at 13-SEP-1989 13:51:15.12

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

Any and all help would be most appreciative,

advaTHANKSnce,

		$$$$ ted $$$$

T.RTitleUserPersonal
Name
DateLines
1437.1LESLIE::LESLIEAndy ��� Leslie. Fat was then....Thu Sep 14 1989 01:596
    Ted
    	what hardware? What version of VMS? What version of DECWindows?
    Does he have any old images left in SYS$SPECIFIC:? 
    
    - ���

1437.2Oh! You want details! RABBET::FARRELLMoney, there is no substitute!Thu Sep 14 1989 12:2417
Sorry,

It is a uVAXII GPX, running VMS V5.1-1 with V1.0 of DECwindows.

I even went as far as to save his MODPARAMS.DAT, SYSTARTUP_V5.COM, ANNOUNCE.TXT,
and delete everything else, remove the node from the cluster, and then add
it back into the cluster again.  AFter I added it back, I restored the old
MODPARAMS.DAT and ran autogen getdata reboot.  The system came back fine, but
the problem still exists.

I am very much stuck!

HELP!

		$$$$ ted $$$$

1437.3Maybe GBLPAGES/SECTIONS...VMSDEV::CLABORNSo?? Mine has a dashboard hibachi!Thu Sep 14 1989 16:208
ACCVIOs in the Session Manager have been associated with a lack of contiguous
GBLPAGES and/or GBLSECTIONS. I've also been involved with a Ses. Mgr. ACCVIO
problem that's caused by upward-creeping VM in the SERVER. But... you don't
see this problem until after you've been up for a while and have been
manipulating large pixmaps (like with XSETROOT).

- George