Conference bulova::decw_jan-89_to_nov-90

2648.0. "Server dying 30 secs. after boot" by SNOMAN::AARON (No-VELL LAN is an isLANd...) Tue Apr 24 1990 13:25

Hi,

I've got a VS II w/ 13 MB and a mono display running T5.3-2EU.

After I boot the system, I get the DIGITAL banner and login screen.
Regardless of what I do, about 30 seconds after the banner comes up, the
server process screws up with different symptoms:

  - If I've not done anything, the login box and banner disappear.

  - If I've logged in, the icon box disappears and the session manager
    has a lot of heartburn (i.e., I can't change focus or interact with
    any applications)

What I have to do at this point is log in from another source, stop the
DECW$SERVER_% process, and then do a DECW$STARTUP RESTART.  Everything
comes up fine at that point and the system runs nominally.

Any clues?  I'm at a loss.

Attached you'll find the DECW$SERVER_0_ERROR.LOG file that I beleive is
created by the offending server process.  I don't see a whole log wrong
with it other than I'm not loading LAT, but then, if I knew everything
about DECwindows, I wouldn't be asking you!

Thanks in advance,

Aaron

---------------------------------------------------------------------------

23-APR-1990 13:58:43.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
in SetFontPath
Connection 99700 is accepted by Txport
out SetFontPath
Monochrome Frame Buffer support loaded
mfb$InitOutput address=14d200
Connection 99738 is accepted by Txport
Connection Prefix: len == 36
23-APR-1990 14:02:28.7 Now I call scheduler/dispatcher
23-APR-1990 14:02:32.0 Connection 99738 is closed by Txport
23-APR-1990 14:02:34.6 Connection 99738 is accepted by Txport
23-APR-1990 14:02:45.0 Connection 99700 is closed by Txport
23-APR-1990 14:03:30.0 Connection 99738 is closed by Txport
23-APR-1990 14:03:36.6 Connection 99700 is accepted by Txport
23-APR-1990 14:03:50.3 Connection 99770 is accepted by Txport
23-APR-1990 14:03:50.9 Connection 9adf8 is accepted by Txport
23-APR-1990 14:04:48.0 Connection 99738 is accepted by Txport
23-APR-1990 14:04:50.1 Connection 9ae30 is accepted by Txport
23-APR-1990 14:04:52.0 Connection 9ae68 is accepted by Txport
23-APR-1990 14:05:01.9 Connection 9aea0 is accepted by Txport
23-APR-1990 14:05:03.7 Connection 9aed8 is accepted by Txport

Could there be something from your SYSTARTUP that happens at a
certain time which causes your server to wrap up?

Many SYSTARTUP's submit batch jobs to do things after something
else has been done. 

Were it me I'd look closely at what SYSTARTUP is doing, and maybe 
start commenting out some things and see what happens. Might at 
least narrow it down that way.

					- Bluejay Adametz

There's nothing explicitly SUBMITted within the SYSTARTUP_V5 file, however
that's not to say that something within one of those procedures doesn't.
Personally, I don't think that's likely, though, with this installation.

After the DECW$STARTUP is called, the only other things are ZAP and PCSA.
ZAP I know doesn't get submitted, and PCSA, some components will get submitted
only if there's an error and DECnet's not started.  Which isn't a problem.

This all started after I upgraded from 5.1 to 5.3-2 (which I of course forgot
to mention in .0)

I like your suggestion to start commenting stuff out -- I'll do that as soon
as I can get everyone off the machine!

I'm surprised I didn't think of that before entering a note - I must be really
dazed (I just found out I'm going to be a father!  Yeesh!  Imagine that! 8^)

Thanks,

Aaron

    Don't call DECW$STARTUP in your startup procedure.  In VMS 5.3, the
    DECwindows startup is done automagically.  You've probably 'shot
    yourself in the foot' by having DECwindows started twice.

Yo!  That got it!

Wierdness - I don't remember seeing anything in the release notes or 
installation manual on that.  And I checked my SYSMAN STARTUP DATABASE, 
which was empty.  Perhaps it was in the 5.2 rel-notes, which I of course
skipped, going straight from 5.1 to 5.3...  

Pray-tell, wherefor is thou started, o fine master of windows???  STARTUP.COM?
Obviously not by name, 'cause I just did a SEARCH SYS$SYSTEM:STARTUP.COM
DECW$STARTUP and there is no such beast (Gawd!  I love windows!!! Doing two
things at once -- imagine that!  8^)

Thanks for your help, I do appreciate it!

Aaron

If you search SYS$STARTUP:*.COM, you will find references to DECW$STARTUP.

Don't ask me the flow of control, however...