Operating System - OpenVMS
1752577 Members
5092 Online
108788 Solutions
New Discussion юеВ

Re: DS15 - LOCKMGRERR crash

 
SOLVED
Go to solution
Jan van den Ende
Honored Contributor

DS15 - LOCKMGRERR crash

Hei,

yesterday the DS15 in our cluster crashed. This was especially unpleasant to the users of one application that was dedicated assigned to that node.

Also, the crash error does not sound very assuring...

SDA sh cras & SDA clue cras attached

The crash has also been forwarded though our support channel, but I guess this will be quicker, also because the support channel is not exactly a direct route...

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.
16 REPLIES 16
Jan van den Ende
Honored Contributor

Re: DS15 - LOCKMGRERR crash

and the clu├Г┬л:

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.
comarow
Trusted Contributor

Re: DS15 - LOCKMGRERR crash

How about the Complete output of
Clue crash
clue config
clue register
clue stack

That would be helpful
Jan van den Ende
Honored Contributor

Re: DS15 - LOCKMGRERR crash

Comarow

crash see previous,
find the other 3 attached.

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.
Jan van den Ende
Honored Contributor

Re: DS15 - LOCKMGRERR crash

Comarow

crash see previous,
find the other 3 attached.

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.
Wim Van den Wyngaert
Honored Contributor

Re: DS15 - LOCKMGRERR crash

Once had a RWCLU problem that ended in a LOCKMGR crash (7.3). Ana/crash show sum will confirm if that is the case (check process states).

Wim
Wim
Volker Halle
Honored Contributor
Solution

Re: DS15 - LOCKMGRERR crash

Jan,

the 'key' piece of information is in the CLUE REGISTER output:

R0 = 00000000.00000124 %SYSTEM-F-INSFMEM, insufficient dynamic memory

The fast remastering code (new since V7.3) is sensitive to resource problems.

Volker.
Jan van den Ende
Honored Contributor

Re: DS15 - LOCKMGRERR crash

Volker,

I KNEW you would beat the official support!
So, just a matter of a parameter adjustment after all.
Boy, am I glad it is not really something more serious (well, _I_ suspected it hardly could be some inherent fault, but there ARE those, that would like nothing better than pointing at VMS with evidence of potential harm to data integrety, as could easily happen when LockManager should be at fault!)

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.
Volker Halle
Honored Contributor

Re: DS15 - LOCKMGRERR crash

Jan,

this system seems to be badly tuned in general, look at:

System Uptime: 1 00:37:35.82
EXE$GL_FLAGS: poolpging,init,bugdump,pgflfrag,pgflcrit,pagfildmp

To find about nonpaged pool expansion problems, see:

SDA> CLUE MEM/STAT

The LKBs and RSBs are allocated from S2 space:

SDA> SHOW PAGE/S2/FREE

To look at LCKMGR pool zone counters, use:

SDA> exa @LCK$AR_POOLZONE_REGION+80;20

The counters are (quadwords from right to left): hits, misses, expansions, failures.

Volker.
Ian Miller.
Honored Contributor

Re: DS15 - LOCKMGRERR crash

Look at page file space also - the mmg flags
pgflfrag, pgflcrit show that the pagefile was full or nearly so at some time.
____________________
Purely Personal Opinion