Another possibility is dependent on if you have MPEX.  If you use the logon
entry point in your logon UDC and you have an issue with MPEX, whether it be
a logfile or a corrupt message file or if you use the $LOGON-EXECUTE
statement in SECURCON and are running something that has a problem, all your
new users would hang at logon time.

Another possibility is dependent on if you have Netbase running.  If for
some reason your NBM.IPC.NETBASE file fills up, and it could for a number of
reasons, all sessions would hang at that time because no new transactions
could be written to that message file.

        Those are two that I know of.  Disc failure is another one, like Tom
said, unless you do software mirroring.

This might help you.  If one of these scenarios are possible, feel free to
contact me.

Thanx
  Dane

-----Original Message-----
From: Emerson, Tom [mailto:[log in to unmask]]
Sent: Tuesday, September 30, 2003 5:47 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] Kreeping Krud


> -----Original Message-----
> From: Tom Hula [mailto:[log in to unmask]]
>
> What is the usual/typical reason for the situation on an HP3000
> where all the sessions start to freeze up. Anyone trying to logon
> or run a different program get frozen.

I've seen this happen when a disk drive (or two) loses power -- anyone
wanting to "use" that drive [either for transient space or to actually
retrieve a program or data from it] gets hung up in the queue [could also be
associated with a directory scan looking for the program?]  When the
drive(s) come back up, everything "unfreezes".

**if** this is what happened, and the drive(s) in question are internal, you
may be hosed.  What I've had happen, however, is the FAN in the power supply
of an external cabinent froze up, and the supply overheated (it would "power
on" for about 3 seconds, then cut back out)  When the tech came and replaced
it, we found a layer of dust in the power supply about 1/4" thick... :(

The GOOD NEWS of this, however, was that the system continued to run [the
production programs were already loaded, didn't need files from the downed
drives, etc.] so we actually did a form of "hot-swap" on the power supply,
turned it back on, and things picked up right where they left off...

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *