Problem with gwinter.nlm

Hello,

For the last Six months we have been experiancing problems with our GroupWise Web Access agent.  The server is running Netware 6.0

On the server is

GW web access agent 6.0.2
GW Internet agent 6.0.2
Groupwise MTA 6.0.2

about twice a month the server abends on gwinter.nlm.  There seems to be no pattern in date or time. Is it common for this NLM to fail so often?  Also, I need to configure the health.log file.  It has gotten so big I cannot even open it.  What utility do I use to configure this log file?
edrosieAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

PsiCopCommented:
Note that EE has a GroupWise TA --> http://www.experts-exchange.com/Applications/Groupwise/

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
PsiCopCommented:
HEALTH.LOG is not part of the GroupWise system. Is this a Compaq? Some server health agent is logging to that.

NetWare 6.0.... what SUPPORT PACKS, if any?

GroupWise v6.0 SP2... just FYI, that is not the latest SP for GroupWise v6.0.

It is not recommended to run the GWWA and the GWIA on the same machine. Altho you appear to have these gateways in their own Secondary Domain, which is good.

What is the webserver for the GWWA?
PsiCopCommented:
Also, are you running these GroupWise agents in a Protected Address Space, and if so, is each in its own space, or are they all in one space?

General tips:

1) Check disk space - make sure the Volume where the queue directories for the agents reside (this should NOT be the SYS: Volume!!) has free space

2) Make sure that deleted files are not clogging the filesystem - the queue directories for the various agents should generally be flagged Purge Immediate (use ConsoleOne)

What is the EXACT ABEND?
Introduction to R

R is considered the predominant language for data scientist and statisticians. Learn how to use R for your own data science projects.

ShineOnCommented:
HEALTH.LOG is the NetWare server health log file, in SYS:\SYSTEM.  

Can you not open or clear it using Remote Manager?  That's the closest thing I can think of as a tool for configuring it.  

If you want to open it using a non-NetWare, non-browser-based tool, I suggest notepad2.exe.  I personally wouldn't use anything but NoRM to clear it, though - even though it should be automatically rebuilt if you delete it, it's not something I recommend, generally speaking.
ShineOnCommented:
Reinforcing PsiCop's last comment, it helps immeasurably when diagnosing abends to know exactly what the abend is.  Seeing the upper portion of the abend log for the abend (through the stack trace) helps a lot more.
edrosieAuthor Commented:
Here is the Latest log entry,  I will check to see if disk space is a problem.


Server NFIGW-1 halted Saturday, July 2, 2005   9:42:03 pm
Abend 1 on P00: Server-5.60b: General Protection Processor Exception (Error code 00000000)

Registers:
    CS = 0008 DS = 005B ES = 0010 FS = 005B GS = 005B SS = 0010
    EAX = C28DC960 EBX = CB6C3EBA ECX = CA659DE4 EDX = FFFFFFFF
    ESI = 00000000 EDI = 0000000C EBP = CB6C36A4 ESP = CB6C369C
    EIP = C28B18A7 FLAGS = 00010286
    C28B18A7 FF12           CALL    near ptr [EDX]=?
    EIP in VSXL5.NLM at code start +000128A7h

The violation occurred while processing the following instruction:
C28B18A7 FF12           CALL    near ptr [EDX]
C28B18A9 83C404         ADD     ESP,00000004
C28B18AC C9             LEAVE
C28B18AD 5F             POP     EDI
C28B18AE 5E             POP     ESI
C28B18AF 5B             POP     EBX
C28B18B0 C3             RET
C28B18B1 6838000000     PUSH    00000038
C28B18B6 E8B5ECD312     CALL    THREADS.NLM|__CHK
C28B18BB 53             PUSH    EBX



Running process: gwinter         6 Process
Thread Owned by NLM: GWINTER.NLM
Stack pointer: CB6C3620
OS Stack limit: CB6A4C40
Scheduling priority: 67371008
Wait state: 3030070  Yielded CPU
Stack: --FFFFFFFF  (LOADER.EXE|KernelTempAliasesEnd+FFF)
       --00000000  ?
       --CB6C36C0  ?
       --0000000C  ?
       --00000000  ?
       --CB6C3EBA  ?
       C28A14CD  (VSXL5.NLM|VSXL5VwGetRtns+EE1)
       --C28DC960  ?
       --00000000  ?
       --CB6C36E8  ?
       --0000000C  ?
       --00000000  ?
       --CB6C3EBA  ?
       CA65E687  (SCCFA.NLM|FAClose+34)
       --CA9CEC40  ?
       --C28DC960  ?
       D5607A0E  (THREADS.NLM|__Must_Have_Three_One_Or_Greater+A)
       --C2A3EC80  ?
       --00000000  ?
       --CB6C3818  ?
       --0000000C  ?
       --00000000  ?
       --CB6C3EBA  ?
       CA6768BA  (SCCDA.NLM|DACloseDocument+FB)
       --C2A3EC80  ?
       --CB6C3EBA  ?
       --CB6C3808  ?
       --CB6A2140  ?
       --00000000  ?
       --0000000C  ?
       --CB6C3818  ?
       CA6767EF  (SCCDA.NLM|DACloseDocument+30)
       --CB6C36FC  ?
       --005B0010  (UMSSHIM.NLM|__NLM_BSS_End+ABF4)
       --005B0008  (UMSSHIM.NLM|__NLM_BSS_End+ABEC)
       --005B005B  (UMSSHIM.NLM|__NLM_BSS_End+AC3F)
       --CA6C005B  (SCCEX.NLM|EXDTAddCellFrame+696)
       --CA6CECE0  (SCCEX.NLM|EXDTAddCellFrame+F31B)
       FC0048CB  (SERVER.NLM|kMutexUnlock+67)
       FC0048D4  (SERVER.NLM|kMutexUnlock+70)
       --CA6CECE0  (SCCEX.NLM|EXDTAddCellFrame+F31B)
       --CA67E9A0  (SCCDA.NLM|DAGetErrorString+4814)
       --CC67EDE0  ?
       --00000000  ?
       --00000000  ?
       --CC5E9640  ?
       --00000000  ?
       --CB68F3E0  ?
       D55F0C73  (THREADS.NLM|free+F)
       --CB6A2AE0  ?
       --CB6A2140  ?
       --00000000  ?
       --CB6A2AE0  ?
       --CB6C37E8  ?
       --0000000C  ?
       --00000020  ?
       --CB6C379C  ?
       FC01A819  (SERVER.NLM|TcoValidateThread+11)
       --CB6C37B4  ?
       FC01BB8B  (SERVER.NLM|kGetThreadStackInfo+37)
       --CB6A2140  ?
       --CB6C37B0  ?
       --CB6A2AE0  ?
       --CB6A2140  ?
       --00000000  ?
       --CB6A2AE0  ?
       --CB6C3A54  ?
       --CB6A2AE0  ?
       --CB6A2140  ?
       --00000000  ?
       --CB6A2AE0  ?
       --CB6A2140  ?
       --00000000  ?
       --CB6A2AE0  ?
       --CB6C3A54  ?
       --0000000C  ?
       --00000134  ?
       --CB6C36DC  ?
       FC01A819  (SERVER.NLM|TcoValidateThread+11)
       --CB6C3808  ?
       FC01BB8B  (SERVER.NLM|kGetThreadStackInfo+37)
       --CB6A2140  ?
       --CB6C3804  ?
       --CB6C3808  ?
       --CB6C3A54  ?
       --CB6C36DC  ?
       D55FCB58  (THREADS.NLM|FreeQueryServicesList+2518)
       --CB6A2140  ?
       --CB6C3804  ?
       --CB6C3808  ?
       --C39B8220  ?
       --C39B8220  ?
       --00000000  ?
       --00000000  ?
       --00000001  ?
       --CB6C3A54  ?
       --0000000C  ?
       --00000000  ?
       --CB6C3EBA  ?
       CA6EDBF2  (GWCMC.NLM|CMC_SetMaxConversationThreadCount+492)
       
Additional Information:
    The CPU encountered a problem executing code in VSXL5.NLM.  The problem may be in that module or in data passed to that module by a process owned by GWINTER.NLM.
acerimmer10Commented:
You should really update to the latest service pack before going any further, Groupwise 6 is up to Service Pack 4. The date of the file that appears to be abending from the above log in the new support pack is 06-06-2003.

I would check if this is newer that the module you have.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Novell Netware

From novice to tech pro — start learning today.