Regards managers,
We have just experienced another hang followed by a crash caused by ASE.
Th two servers in question run 3.2G and ASE 1.3. There is one specific
problem I like to hear your opinion about:
Consider the following scenario:
1. Start asemgr
2. Alter a exportlist from within ase
3. Commit changes
4. ASE tries to delete, modify and then add the service again but hangs
claiming it could not modify and then asks if we want to use the old
configuration. Regardless of answer ase loops and asks the same
question. This renders the service useless, in UNKNOWN state and clients
get 'server not responding'. VERY frustrating if you have enough users
calling you simultaneously...
We have pinpointed this problem to be that if there are local ase server
processes (only one process is sufficient) having open files on the
service to be altered the above situation arises. It is enough to do a
'cd' down to the mountpoint of the service locally, then start asemgr
and you'll end up like this.
I claim that his must be a bug. It cannot be that much of a problem
finding such processes before starting committing changes to a service.
And furthermore, if this is accomplished, it cannot be that much of a
problem presenting the asemgr user a list of which processes that have
to be dealt with before committing changes (a la lsof). I have heard
that DEC claims that this is not a bug and it will not be fixed in the
next major ASE release (1.5).
What do you think ? Any similar experiences ?
--
******************************************************************
* Knut Hellebų | DAMN GOOD COFFEE !! *
* Norsk Hydro a.s | (and hot too) *
* Phone: +47 55 996870, Fax: +47 55 996495 | *
* Cellular Phone: +47 93092402 | *
* E-mail: Knut.Hellebo_at_nho.hydro.com | Dale Cooper, FBI *
******************************************************************
Received on Wed Oct 01 1997 - 12:50:17 NZST