Abend caused by TURBODIS.NLM ?

[audioone]

Our main NDS server (NW51) is getting an abend when it starts up.
Recently we aplied SP5 on all of our servers and after that the abend shows up.
I`ve researched the problem and have noticed already that the abend occurs when the turbodis.nlm is loaded by the autoexec.ncf.
I`ve replaced the Turbodis.nlm with one i downloaded from Novell.com, but the abend is still coming back.

I can`t find any information whatsoever about this problem on the Novell support site exept some info about what the Turbodis.nlm is good for.

Finaly i editted the autoexec.ncf so that it won`t try to load Turbodis.nlm at startup.
Now the abend is gone but the Turbodis.nlm is not loaded on the Server.
What i would like to know is, if there are any consequences by not loading Turbudis.nlm on our main NDS server or even better maybe there is someone who has a solution for this problem?

Many Thnx in advance and greetings from the Netherlands

 

[TheLad]

What type of abend is it? -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[audioone]

Hey it`s theLad again...
Well let me show you a part of the abend.log


Server xxxxxxx halted Friday, 25 October 2002 13:39:11,966
Abend 1 on P00: Server-5.00k: Page Fault Processor Exception (Error code 00000000)

Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0010
EAX = D132F9B8 EBX = D57C5C40 ECX = CFBEAEC0 EDX = D0001004
ESI = BCFAB9C0 EDI = D129890D EBP = D0865FCC ESP = D0865FB4
EIP = C73ED07B FLAGS = 00010297
C73ED07B 8B7E0D MOV EDI,[ESI+0D]=?
EIP in UNKNOWN memory area
Access Location: 0xBCFAB9CD

The violation occurred while processing the following instruction:
C73ED07B 8B7E0D MOV EDI,[ESI+0D]
C73ED07E 8D7611 LEA ESI,[ESI+11]
C73ED081 03FE ADD EDI,ESI
C73ED083 8B07 MOV EAX,[EDI]
C73ED085 3D8B4E2C85 CMP EAX,852C4E8B
C73ED08A 0F851B000000 JNZ C73ED0AB
C73ED090 893D30F03EC7 MOV [C73EF030]=00000000,EDI
C73ED096 A334F03EC7 MOV [C73EF034]=00000000,EAX
C73ED09B B8B5D03EC7 MOV EAX,C73ED0B5
C73ED0A0 8B00 MOV EAX,[EAX]



Running process: Console Command Process
Created by: NetWare Application
Thread Owned by NLM: SERVER.NLM
Stack pointer: C48F9B00
OS Stack limit: D085F040
Scheduling priority: 67371008
Wait state: 5050100 (Delayed)
Stack: --00000000 ?
--00000246 ?
--D57C5C40 ?
--D0865FCC ?
C73ED041 (TURBODIS.NLM|(Code Start)+41)
--D132F9B8 ?
--D0866574 ?
FC05F075 (SERVER.NLM|LoadFile+288D)
--D57C5C40 ?
-FC541A30 (SERVER.NLM|systemConsoleScreenStructure+0)
-FC584BBC (SERVER.NLM|scsCommandBuffer+8)
--D0866664 ?
--00000000 ?
--D086660C ?
FC085E44 (SERVER.NLM|PreLoadRead+0)
--00000302 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00200006 ?
--1CF0D8E0 ?
D066A1AB (MM.NLM|MM_CompleteMessage+33)
--00000246 ?
--1F92B200 ?
--1F79F400 ?
--1F92B200 ?
--1F92B200 ?
D06FA0BC (NWPA.NLM|ScheduleAnotherMessage+3C)
--1F92B200 ?
--00000000 ?
--D0726100 ?
D06FB0BB (NWPA.NLM|ElevatorExecuteIO+117)
--1F92B200 ?
--1F92B200 ?
--D0726100 ?
--1F792480 (CPQMPK.PSM|PSMLoaded+5E98)
D06F4C99 (NWPA.NLM|Send_Message_To_Next_Filter+6D)
--1F92B200 ?
--D0726100 ?
--00001000 ?
--1F90C080 ?
--D0726100 ?
--1F792480 (CPQMPK.PSM|PSMLoaded+5E98)
D06F4E5B (NWPA.NLM|CDM_Send_Initial_Message+CF)
--1F792480 (CPQMPK.PSM|PSMLoaded+5E98)
--D0726100 ?
--00000000 ?
--00249D68 ?
--087A7D00 ?
--00249D68 ?
D06F4F2F (NWPA.NLM|CDM_ReadWrite_Message+83)
--1F90C080 ?
--1CF9C490 ?
--1F88E580 ?
--1F88E040 ?
--1CF9C490 ?
D0681C82 (MM.NLM|PartitionRandomRead+66)
--1F90C080 ?
--1CF9C490 ?
--1CF9C490 ?
--1F88E580 ?
--1CF9C52C ?
--1CF9C510 ?
D0672943 (MM.NLM|HotfixRandomRead+307)
--1F88E040 ?
--1CF9C490 ?
--D136F900 ?
00035EC8 (LOADER.EXE|GetSuperHighResolutionTimer+4CA)
--D45F2F40 ?
--00000008 ?
-FC5394B4 (SERVER.NLM|AllocSizeTable+C)
0002D438 (LOADER.EXE|RestartServer+7EEC)
--00000000 ?
--D7F4B820 ?
--1F88E580 ?
--1F7AD760 ?
--1CF9C52C ?
--1CF9C490 ?
D067C182 (MM.NLM|MirrorRandomRead+422)
--1F88E580 ?
--1CF9C490 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000053 ?
--00000000 ?
--1F88E580 ?
0002D438 (LOADER.EXE|RestartServer+7EEC)
--00000000 ?
--1F88E820 ?
--1CF9C490 ?
D0686862 (MM.NLM|MM_Volume_IO+17E)
--1F88E820 ?
--00000282 ?
--1F8952E0 ?
--00000282 ?
--C1F0F2E0 ?
--1E695B5C ?

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

 

[TheLad]

Are you running Groupwise on this server? If so, apply the latest Groupwise Service Pack:

http://support.novell.com/servlet/tidfinder/2963274

If not, write back... -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[audioone]

Hi TheLad, and thnx for thinking with me again.

Groupwise is not running on this server even like no other aditional services are running on it.

Greetings from the Netherlands.

 

[TheLad]

Do you know what is loading the TURBODIS.NLM? If you have it in your AUTOEXEC.NCF, rem it out. I don't think it should be running if you don't have Groupwise. I don't have it on my NetWare 5 servers?? -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[audioone]

Well, i already disabled it in the autoexec.ncf.
But by knowing that the NDS is an Database too and the server is our main NDS server i`d like to be sure if it`s causes no harm to the NDS by disabling TURBODIS.NLM.

Greetings from the Netherlands

 

[TheLad]

The TURBODIS.NLM basically disables Turbo-Fat corruption. What is Turbo-Fat I hear you ask? Well, here is a little edit from the Novell website:

"A special FAT index used when a file exceeds 64 blocks (and the corresponding number of FAT entries). NetWare creates a turbo FAT index to group together all FAT entries for that file. The first entry in a turbo FAT index consists of the first FAT number of the file. The second entry consists of the second FAT number, etc. A turbo FAT index enables a large file to be accessed quickly."

So in answer to your question, by commenting out the TURBODIS.NLM should not have an effect on your server as Novell only recommends disabling the Turbo Fat on servers which contain large databases that keep getting corrupted (ie SQL or Groupwise databases).


-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[audioone]

Ok, I guess i permently disable the load TURBODIS.NLM command in the autoexec.ncf..

Ladman thnx for your quick responses........

 

[ebek]

Abend error on my file/mail server. "....The CPU encountered a problem executing code in SERVER.NLM. The problem may be in that module or in data passed to that module by a process owned by GWMTA.NLM."
Any ideas?

Thanks in advance...
ebek

 

[TheLad]

What SP of Groupwise are you running? Has this started occuring following a SP upgrade? -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[ebek]

GW SP4

Thanks

 

[ebek]

No upgrades were done. I just came on board and found the server with the abbend error.

Thanks in advance....

 

[TheLad]

Is the abend a regular occurence or is it just a one off? You see, 1/2 of the time the NLM mentioned in the abend is not the culprit as it was what the server was doing at the time of the abend. In your abend log listed above, the actual abend was caused by SERVER.NLM. TURBODIS.NLM was listed as it was an active process at the time (as are many others as you can see from the log).

Like I said, if it was a one off then you shouldn't worry. If it occurs on a regular basis then you may need to consider stuff like the latest NetWare SP, reapplying SP4 for GW, firmware upgrades on your server etc.... -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[ebek]

It is occurring on regular basis. It usually happens when users access their email remotely via GW web access.
Do you do administration/remote admin work by any chance?

Thanks in advance!

 

[TheLad]

Of course I do remote admin, what do you think I do here

Anyway, have you run a DSREPAIR on the local database recently? I would try that as a start to see if there are any errors reported in DS. Then, maybe you could reapply your service packs to both NetWare and Groupwise. Also, check to ensure that your IP configuration is correct in INETCFG. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------