| Author |
CWLNMERR, Fatal error in clusterwide logical name support |
davej
Member
Posts: 2
Location: Atlanta, GA
Joined: 21.07.18 |
| Posted on July 25 2018 07:11 |
|
|
|
I had to reinstall OpenVMS 8.4 on my PWS 500 system due to a corrupted system disk. I previously had it clustered with a simh VAX system running on my main Windows box. Now, whenever I boot the Alpha system with VAXCLUSTER set to 2, I get the CWLNMERR bugcheck. Any ideas where to look to fix this? It was all working fine before I had to reinstall the OS. |
|
|
| Author |
RE: CWLNMERR, Fatal error in clusterwide logical name support |
abrsvc
Member
Posts: 108
Joined: 12.03.10 |
| Posted on July 26 2018 01:22 |
|
|
Verify that the volume name for the system disk does not conflict with the VAX one. It shouldn't but...
Also, check on teh allocation class values etc.
Dan |
|
|
| Author |
RE: CWLNMERR, Fatal error in clusterwide logical name support |
malmberg
Moderator
Posts: 530
Joined: 15.04.08 |
| Posted on July 26 2018 02:47 |
|
|
http://compgroups.net/comp.os.vms/frewslx-alpha-7.3-2/1165617
Are you using cluster wide logical name tables?
The above link suggests that you may be low on some quota needed for them, which means that you may not have the same sysgen settings as before.
Do you have a backup of your old system disk to check the params.dat and modparams.dat files?
|
|
|
| Author |
RE: CWLNMERR, Fatal error in clusterwide logical name support |
davej
Member
Posts: 2
Location: Atlanta, GA
Joined: 21.07.18 |
| Posted on July 26 2018 03:54 |
|
|
Unfortunately, no backup of the old, working system.
I'm not using clusterwide logical names and the volume labels and allocation classes are not an issue.
I did see a post that said running out of paged pool can cause this error, but that is not the issue here. I still have 1/2 of the paged pool allocation unused when the bugcheck occurs. |
|
|
