NLM Abends (Networking Products)
At 23 SEP 2005 12:44:51PM Matt Sorrell wrote:
So far this week, our Novell server has gone down three times with abends. It is a NetWare 5.1 server with the appropriate NLM loaded.
Each time it says that the error was in LHIPXSER.NLM, and the error is "Kernel detected thread going to sleep when it was not allowed".
Searching through the abend.log file (it has never been purged, thankfully) this error has not come up before.
The only change made on the server recently was an upgrade/update the the McAfee anti-virus engine and DAT files. I had the admins check and all .LK and .OV files are excluded from the scan. Also, it is set up to only scan incoming files, not outgoing or on-access.
What does the "tried to go to sleep" error mean, and could it be related to McAfee at all, or is this some other problem?
Also, every time this has happened this week I've had massive corruption (usually group 0) in a number of index tables. I am assuming that this is because our dedicated indexer is logged in and checking the indexes when the server goes down.
Is it possible that our dedicated indexer is part of the root cause and is generating the abends on the server, or is it just the reason for the indexes getting thrashed?
Any ideas or help would be greatly appreciated as the users are getting very nervous.
At 23 SEP 2005 01:47PM [email protected] wrote:
http://support.novell.com/cgi-bin/search/searchtid.cgi?10054376.htm
Any relevance?
The Sprezzatura Group Web Site
World Leaders in all things RevSoft
At 23 SEP 2005 02:56PM Matt Sorrell wrote:
Doesn't appear to apply. We are currently running SP5.
Also, this issue just started this week, approximately 36 hours after we applied a McAfee update.
We are leaning in that direction and have temporarily disabled McAfee to see if that stabilizes things.
Thanks!!
At 26 SEP 2005 12:57PM Matt Sorrell wrote:
Well, it appears that the issue is a conflict between LH.NLM/LHIPXSER.NLM and the McAfee NLMs on our server. We disabled McAfee on Friday and have not had any issues since.
Are there any known compatibility issues with NetWare 5.1 SP5, the latest version of McAfee and the 5.1 NLM?
At 30 NOV 2005 04:59AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
FWIW
We have an Arev client that lost all their workstations, on a Windows network, in a fire. They replaced the infrastructure, set the workstations up correctly and installed McAfee ver 8 excluding the .LK and .OV files. All hell broke loose with spurious and frequent GFEs etc…
After much trouble shooting we could see, using the Filemon utility, that McShield was actioning the Arev files, even writting to them.
They reloaded McAfee ver 7.1 that they had been using, specified the exclusions and all is now working fine.
McAfee have admitted that ver 8 does not work and that they have even removed the ability to set exclusions it their latest releases.
World leaders in all things RevSoft
At 30 NOV 2005 10:25AM Matt Sorrell wrote:
OUCH!!!
That's a major problem.
The interesting thing is I've been testing the system on a Windows server for a while now and we have not had any of the problems we were having under NetWare.
Here's hoping that things remain stable :)