I upgraded my NetWare 5.1 server (sp8) to 6.5 sp5. I did the upgrade on
the server

All went well but I noticed an abend which was caused by trying to load
ronag6.nlm (so as to get remote access to the server).

as this was in the original default autoexec.ncf I am puzzled.

I also noticed a problem with libc.nlm
I also noticed that when upgrading it told me to check a repair log in
certserv directory (presumably in 5.1 before I upgraded but I was not
able to run the server in fixing mode

I attach what I consider to be the relevant parts of the Abend log and
console log and the repair log


abend log

************************************************** *******
Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.05

Server GRUNDBERG halted Saturday, 8 July 2006 9:28:00.461 pm
Abend 1 on P00: Server-5.70.05: Page Fault Processor Exception (Error
code 00000000)

Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0010
EAX = 00000000 EBX = 00000000 ECX = FFFFFFFC EDX = 8753B000
ESI = 00000000 EDI = B877EC9F EBP = 87565094 ESP = 87565084
EIP = B8AD6697 FLAGS = 00010246
B8AD6697 833E00 CMP [ESI]=?, 00000000
EIP in LIBC.NLM at code start +00091697h
Access Location: 0x00000000

The violation occurred while processing the following instruction:
B8AD6697 833E00 CMP [ESI], 00000000
B8AD669A 7451 JZ B8AD66ED
B8AD669C 8D442000 LEA EAX, [EAX+00]
B8AD66A0 6868AD77B8 PUSH B877AD68
B8AD66A5 FF349E PUSH dword ptr [ESI+EBX*4]
B8AD66A8 E883530000 CALL LIBC.NLM|strpbrk
B8AD66AD 89C7 MOV EDI, EAX
B8AD66AF 59 POP ECX
B8AD66B0 59 POP ECX
B8AD66B1 8B0C9E MOV ECX, [ESI+EBX*4]



Running process: RCONAG6 main 1 Process
Thread Owned by NLM: RCONAG6.NLM
Stack pointer: 875646AC
OS Stack limit: 87562F40
Scheduling priority: 67371008
Wait state: 3030070 Yielded CPU
Stack: --00000002 (LOADER.NLM|KernelAddressSpace+2)
--8753B000 ?
--8753B6D0 ?
--8756511C ?
--87565130 ?
B8AED7CD (LIBC.NLM|TzSet+2D)
--8753B000 ?
-B877EC9C (LIBC.NLM|gOrdinals+2C)
--8756511C ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
-004410E0 (SERVER.NLM|xAllocSizeTable+30)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--87565110 ?
--874F46C0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--874F46C0 ?
0020EA12 (SERVER.NLM|kMutexUnlock+10A)
--875612E0 ?
--874F46C0 ?
--87565110 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000020 (LOADER.NLM|KernelAddressSpace+20)
--8753B000 ?
B8B05D53 (LIBC.NLM|SetupLibraryContext+253)
--874F46C0 ?
--8753B000 ?
--875659D4 ?
--00000020 (LOADER.NLM|KernelAddressSpace+20)
--87565134 ?
B8B058C0 (LIBC.NLM|_get_vm+170)
--00000020 (LOADER.NLM|KernelAddressSpace+20)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--BFAF90A0 (NWTERMIO.NLM|bsMutex+BB80)
--8753B6D0 ?
--87565154 ?
--87565148 ?
B8AE96BC (LIBC.NLM|mktime+2C)
--8753B000 ?
--8753B6D0 ?
--875659D4 ?
--87565200 ?
--8756517C ?
B8AED155 (LIBC.NLM|dos2calendar+75)
--87565154 ?
--0000001A (LOADER.NLM|KernelAddressSpace+1A)
--00000017 (LOADER.NLM|KernelAddressSpace+17)
--00000015 (LOADER.NLM|KernelAddressSpace+15)
--00000008 (LOADER.NLM|KernelAddressSpace+8)
--00000006 (LOADER.NLM|KernelAddressSpace+6)
--0000006A (LOADER.NLM|KernelAddressSpace+6A)
--0003D5C1 (SERVER.NLM|CpuMediaManager+3DD)
--87565200 ?
--FFFFFFFF ?
--34E8AAED ?
--87565214 ?
B8A61660 (LIBC.NLM|FillAttrStructFromLegacy+710)
--34E8AAED ?
--0003D5C0 (SERVER.NLM|CpuMediaManager+3DC)
--00005190 (LOADER.NLM|KernelAddressSpace+5190)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--34E8AAED ?
--BF9B52E0 ?
--76726553 ?
--4F4D4B5C ?
--68636143 ?
--77555C65 ?
--45415442 ?
--41494177 ?
--45414442 ?
--67554155 ?
--45415542 ?
--6752416B ?
--45414A42 ?
--5151414D ?
--45415542 ?
--41524155 ?
--46414F42 ?
--702E414D ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--875659D4 ?
--8756524C ?
--0003D5C1 (SERVER.NLM|CpuMediaManager+3DD)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00002E2F (LOADER.NLM|KernelAddressSpace+2E2F)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--FFFFFFFF ?
--00000004 (LOADER.NLM|KernelAddressSpace+4)
--00000004 (LOADER.NLM|KernelAddressSpace+4)
--873F2541 ?
--873F2540 ?

Additional Information:
The CPU encountered a problem executing code in LIBC.NLM. The
problem may be in that module or in data passed to that module by a
process owned by RCONAG6.NLM.

repair log

PKIDiag 2.78 -- (compiled Jul 18 2005 17:19:03).
CP_CPDataGet returned -1 getting the adminID.
found = 0
fixAll = 0
forcedCreate = 0
reKey = 0
--------------------------------------------------------------------------
-
PKIDiag 2.78 -- (compiled Jul 18 2005 17:19:11).
(Check the end of the log for the last repair results)
Current Time: Sat Jul 8 21:00:04 2006
User logged-in as: .
Diagnostics only mode

--> Server Name = 'GRUNDBERG'
--------------------------------------------------------------------------
-

Step 1 Verifying the Server's link to the SAS Service Object.
Server 'GRUNDBERG.gm' points to SAS Service object 'SAS Service -
GRUNDBERG.gm'
Step 1 succeeded.

Step 2 Verifying the SAS Service Object
SAS Service object 'SAS Service - GRUNDBERG.gm' is backlinked to
server 'GRUNDBERG.gm'.
Step 2 succeeded.

Step 3 Verifying the links to the KMOs
Reading the links for SAS Service object 'SAS Service - GRUNDBERG.gm'.
--->KMO SSL CertificateIP - GRUNDBERG.gm is linked.
--->KMO SSL CertificateDNS - GRUNDBERG.gm is linked.
Step 3 succeeded.

Step 4 Verifying the KMOs
---> Testing KMO 'SSL CertificateIP - GRUNDBERG.gm'.
Rights check -- OK.
Back link -- OK.
Private Key -- Failed.

---> Testing KMO 'SSL CertificateIP - BORDERGW.gm'.
Rights check -- OK.
Back link -- Belongs to a different server -- Ignoring this KMO.


---> Testing KMO 'SSL CertificateDNS - GRUNDBERG.gm'.
Rights check -- OK.
Back link -- OK.
Private Key -- Failed.

---> Testing KMO 'SSL CertificateDNS - BORDERGW.gm'.
Rights check -- OK.
Back link -- Belongs to a different server -- Ignoring this KMO.

Step 4 succeeded.

Step 5 Re-verifying the links to the KMOs
Reading the links for SAS Service object 'SAS Service - GRUNDBERG.gm'.
PROBLEM: Cannot use private key for KMO 'SSL CertificateIP -
GRUNDBERG.gm'. It should be probably be unlinked and deleted.
--> Run in Fixing mode to correct this problem.
PROBLEM: Cannot use private key for KMO 'SSL CertificateDNS -
GRUNDBERG.gm'. It should be probably be unlinked and deleted.
--> Run in Fixing mode to correct this problem.
Step 5 succeeded.

Step 6 Creating IP and DNS Certificates if necessary.
--> Number of Server IP addresses = 3
--> The default IP address is: 10.1.1.1
PROBLEM: The KMO SSL CertificateIP has expired.
--> The KMO SSL CertificateIP's IP Address is: 10.1.1.1.O=MOCATTA
----> The IP addresses match.
--> Run in Fixing mode to correct this problem(s).
--> Number of Server DNS names for the IP address 10.1.1.1 = 1
--> The server's default DNS name is:
grundberg.gmrlaw.com
PROBLEM: The KMO SSL CertificateDNS has expired.
--> The KMO SSL CertificateDNS's DNS name is:
host.grundbergmocatta.demon.co.uk.O=MOCATTA
PROBLEM: The DNS name in KMO SSL CertificateDNS does not match the
default DNS name for the server.
--> Run in Fixing mode to correct this problem(s).
Step 6 succeeded.


Note: Occasionally multiple problems will be solved with a single fix.

Fixable problems found: 5
Problems fixed: 0
Un-fixable problems found: 0


Hope someone can help. as I often log in from home with VPN I do need the
ronconsole to work as I find it so useful

Thanks

Bernard Mocatta