Highlighted
Absent Member.
Absent Member.
1592 views

NW65 SP8a server keeps abending

My server was running fine for 79 days and then an abend. Still having problems with abends. Hope someone can check this out and give me an idea on where to start. I'm currently looking at installing mandatory post SP8 patches and see what happens.

Any input on this problem is greatly appreciated.
thanks, Lin

----------------------------------------------------------------------
ABEND LOG BELOW of recent abends:
----------------------------------------------------------------------
Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.08

Server DS4-RS halted Friday, November 5, 2010 9:59:53.999 am
Abend 1 on P00: Server-5.70.08-1937: CPU Hog Detected by Timer

Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0023 SS = 0010
EAX = FBF17BA3 EBX = 9D1EBA80 ECX = 00000000 EDX = 99A683E0
ESI = 94266260 EDI = 9A05CD20 EBP = A8FE5A22 ESP = A8FE55D8
EIP = 00000000 FLAGS = 00000002


Running process: NSMAGENT LogMgr Process
Thread Owned by NLM: NSMAGENT.NLM
Stack pointer: A8FE5A84
OS Stack limit: A8FE1C00
Scheduling priority: 67371008
Wait state: 3030070 Yielded CPU
Stack: --FBF17BA3 ?
901F6497 (NLMLIB.NLM|creat+B7B)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--8BF16C2C ?
--8A3218C0 ?
--8F27C8F4 ?
--A8FE5634 ?
8ABE7E31 (ZLSS.NSS|ZLOG_ObtainRecord+3A1)
--00000072 (LOADER.NLM|KernelAddressSpace+72)
--8A3218C0 ?
--15590000 ?
--8F27C8F4 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
8ABE6D14 (ZLSS.NSS|doDisplayESMCachePerf+594)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--18FA1000 ?
--8F27C8F4 ?
--8C1092E8 ?
--A8FE5634 ?
8A7555A5 (NSS.NLM|LB_bind+15)
-8A7AC450 (NSS.NLM|BondControl+0)
--8F27C8F4 ?
--8F27C8F4 ?
--00009A7B (LOADER.NLM|KernelAddressSpace+9A7B)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--8C1092D4 ?
--A8FE5654 ?
8A757FA2 (NSS.NLM|cacheRelease+C2)
--8C1092D4 ?
--A8FE56A4 ?
--00000180 (LOADER.NLM|KernelAddressSpace+180)
--A8FE5670 ?
8AB7ABE0 (ZLSS.NSS|modifyZnode+E0)
--8C1092D4 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000007 (LOADER.NLM|KernelAddressSpace+7)
--18FA1000 ?
--A8FE56A4 ?
--A8FE5694 ?
8AB7AF1C (ZLSS.NSS|doModifyZnode+4C)
--A8FE58F8 ?
--A8FE56A4 ?
--00000007 (LOADER.NLM|KernelAddressSpace+7)
8ABE7995 (ZLSS.NSS|zlog_HistogramEvent+35)
--8F27C8F4 ?
--15590AD8 ?
--8A3218C0 ?
--A8FE56FC ?
8ABE99BA (ZLSS.NSS|ZLOG_ReleaseRecord+2A)
--8A321B40 ?
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--8BF16C2C ?
--8A3218C0 ?
--8F27C8F4 ?
--A8FE56F8 ?
8ABE7E31 (ZLSS.NSS|ZLOG_ObtainRecord+3A1)
--0000000A (LOADER.NLM|KernelAddressSpace+A)
--8A3218C0 ?
--15590000 ?
--8F27C8F4 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
8ABE6D14 (ZLSS.NSS|doDisplayESMCachePerf+594)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--A8FE58F8 ?
--8F27C8F4 ?
--00000002 (LOADER.NLM|KernelAddressSpace+2)
--8BF180F4 ?
--8BF18114 ?
--A8FE5718 ?
8A7588CB (NSS.NLM|cacheLookup+10B)
--8BF180F4 ?
--8F27C8F4 ?
--A8FE570C ?
8ABC1496 (ZLSS.NSS|writeCommitRecord+56)
8AAD70A8 (COMN.NSS|COMN_DoResolveConnection+48)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000035 (LOADER.NLM|KernelAddressSpace+35)
--A8FE575C ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--A8FE574C ?
8AA7F21E (COMN.NSS|WRITE_GetFileBlk+4E)
--91516920 ?
--00000720 (LOADER.NLM|KernelAddressSpace+720)
--00000002 (LOADER.NLM|KernelAddressSpace+2)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000035 (LOADER.NLM|KernelAddressSpace+35)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--8BF180F4 ?
--A8FE5750 ?
8A757FA2 (NSS.NLM|cacheRelease+C2)
--8BF180F4 ?
--8BF180F4 ?
--1CDFC040 ?
--A8FE57F4 ?
8AA80B39 (COMN.NSS|COMN_Write+7B9)
--915168C0 ?
--915168C0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000720 (LOADER.NLM|KernelAddressSpace+720)

Additional Information:
The NetWare OS detected a problem with the system while executing a process owned by SERVER.NLM. It may be the source of the

problem or there may have been a memory corruption.

Labels (1)
0 Likes
8 Replies
Highlighted
Knowledge Partner
Knowledge Partner

Re: NW65 SP8a server keeps abending

Hi.

Your abend is in Storage Manager, I suggest you ask over in it's group.
Also you omitted the muldule list of the abend.log, so we have no ide
what version you're running. First thing, check for updates.

lcurrie wrote:
>
> My server was running fine for 79 days and then an abend. Still having
> problems with abends. Hope someone can check this out and give me an
> idea on where to start. I'm currently looking at installing mandatory
> post SP8 patches and see what happens.
>
> Any input on this problem is greatly appreciated.
> thanks, Lin
>
> ----------------------------------------------------------------------
> ABEND LOG BELOW of recent abends:
> ----------------------------------------------------------------------
> Novell Open Enterprise Server, NetWare 6.5
> PVER: 6.50.08
>
> Server DS4-RS halted Friday, November 5, 2010 9:59:53.999 am
> Abend 1 on P00: Server-5.70.08-1937: CPU Hog Detected by Timer
>
> Registers:
> CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0023 SS = 0010
> EAX = FBF17BA3 EBX = 9D1EBA80 ECX = 00000000 EDX = 99A683E0
> ESI = 94266260 EDI = 9A05CD20 EBP = A8FE5A22 ESP = A8FE55D8
> EIP = 00000000 FLAGS = 00000002
>
> Running process: NSMAGENT LogMgr Process
> Thread Owned by NLM: NSMAGENT.NLM
> Stack pointer: A8FE5A84
> OS Stack limit: A8FE1C00
> Scheduling priority: 67371008
> Wait state: 3030070 Yielded CPU
> Stack: --FBF17BA3 ?
> 901F6497 (NLMLIB.NLM|creat+B7B)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --8BF16C2C ?
> --8A3218C0 ?
> --8F27C8F4 ?
> --A8FE5634 ?
> 8ABE7E31 (ZLSS.NSS|ZLOG_ObtainRecord+3A1)
> --00000072 (LOADER.NLM|KernelAddressSpace+72)
> --8A3218C0 ?
> --15590000 ?
> --8F27C8F4 ?
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> 8ABE6D14 (ZLSS.NSS|doDisplayESMCachePerf+594)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --18FA1000 ?
> --8F27C8F4 ?
> --8C1092E8 ?
> --A8FE5634 ?
> 8A7555A5 (NSS.NLM|LB_bind+15)
> -8A7AC450 (NSS.NLM|BondControl+0)
> --8F27C8F4 ?
> --8F27C8F4 ?
> --00009A7B (LOADER.NLM|KernelAddressSpace+9A7B)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --8C1092D4 ?
> --A8FE5654 ?
> 8A757FA2 (NSS.NLM|cacheRelease+C2)
> --8C1092D4 ?
> --A8FE56A4 ?
> --00000180 (LOADER.NLM|KernelAddressSpace+180)
> --A8FE5670 ?
> 8AB7ABE0 (ZLSS.NSS|modifyZnode+E0)
> --8C1092D4 ?
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000007 (LOADER.NLM|KernelAddressSpace+7)
> --18FA1000 ?
> --A8FE56A4 ?
> --A8FE5694 ?
> 8AB7AF1C (ZLSS.NSS|doModifyZnode+4C)
> --A8FE58F8 ?
> --A8FE56A4 ?
> --00000007 (LOADER.NLM|KernelAddressSpace+7)
> 8ABE7995 (ZLSS.NSS|zlog_HistogramEvent+35)
> --8F27C8F4 ?
> --15590AD8 ?
> --8A3218C0 ?
> --A8FE56FC ?
> 8ABE99BA (ZLSS.NSS|ZLOG_ReleaseRecord+2A)
> --8A321B40 ?
> --00000001 (LOADER.NLM|KernelAddressSpace+1)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --8BF16C2C ?
> --8A3218C0 ?
> --8F27C8F4 ?
> --A8FE56F8 ?
> 8ABE7E31 (ZLSS.NSS|ZLOG_ObtainRecord+3A1)
> --0000000A (LOADER.NLM|KernelAddressSpace+A)
> --8A3218C0 ?
> --15590000 ?
> --8F27C8F4 ?
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> 8ABE6D14 (ZLSS.NSS|doDisplayESMCachePerf+594)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --A8FE58F8 ?
> --8F27C8F4 ?
> --00000002 (LOADER.NLM|KernelAddressSpace+2)
> --8BF180F4 ?
> --8BF18114 ?
> --A8FE5718 ?
> 8A7588CB (NSS.NLM|cacheLookup+10B)
> --8BF180F4 ?
> --8F27C8F4 ?
> --A8FE570C ?
> 8ABC1496 (ZLSS.NSS|writeCommitRecord+56)
> 8AAD70A8 (COMN.NSS|COMN_DoResolveConnection+48)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000035 (LOADER.NLM|KernelAddressSpace+35)
> --A8FE575C ?
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --A8FE574C ?
> 8AA7F21E (COMN.NSS|WRITE_GetFileBlk+4E)
> --91516920 ?
> --00000720 (LOADER.NLM|KernelAddressSpace+720)
> --00000002 (LOADER.NLM|KernelAddressSpace+2)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000035 (LOADER.NLM|KernelAddressSpace+35)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --8BF180F4 ?
> --A8FE5750 ?
> 8A757FA2 (NSS.NLM|cacheRelease+C2)
> --8BF180F4 ?
> --8BF180F4 ?
> --1CDFC040 ?
> --A8FE57F4 ?
> 8AA80B39 (COMN.NSS|COMN_Write+7B9)
> --915168C0 ?
> --915168C0 ?
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000720 (LOADER.NLM|KernelAddressSpace+720)
>
> Additional Information:
> The NetWare OS detected a problem with the system while executing a
> process owned by SERVER.NLM. It may be the source of the
>
> problem or there may have been a memory corruption.
>
> --
> lcurrie
> ------------------------------------------------------------------------
> lcurrie's Profile: http://forums.novell.com/member.php?userid=4373
> View this thread: http://forums.novell.com/showthread.php?t=425343


--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: NW65 SP8a server keeps abending

I would also suggest loading the latest NSS code. The file you will want to load is N65NSS8c.zip. Load that on your server.

jgray
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: NW65 SP8a server keeps abending

Have applied nss patch, tcpip patch and still server amends.

I will check with storage manager, since it sounds like that is issue.

Note, I wasn't able post entire abend log due to a size limitation.

How is this being handled now or do I have to create several posts to publish the entire abend log?

Thanks,
Lin

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: NW65 SP8a server keeps abending

Hi,

lcurrie wrote:
> Note, I wasn't able post entire abend log due to a size limitation.
>
> How is this being handled now or do I have to create several posts to
> publish the entire abend log?


Attach it as a file (zip it first), instead of pasting it into your
message.

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: NW65 SP8a server keeps abending

lcurrie;2042523 wrote:
Have applied nss patch, tcpip patch and still server amends.

I will check with storage manager, since it sounds like that is issue.

Note, I wasn't able post entire abend log due to a size limitation.

How is this being handled now or do I have to create several posts to publish the entire abend log?

Thanks,
Lin
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: NW65 SP8a server keeps abending

On Mon, 08 Nov 2010 14:36:03 +0000, lcurrie wrote:

> Note, I wasn't able post entire abend log due to a size limitation.


You can use www.pastebin.com for large file posting and just post the URL
here.


--
---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Novell Knowledge Partner http://forums.novell.com

Please post questions in the newsgroups. No support provided via email.

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: NW65 SP8a server keeps abending

What you could do is if the abend.log file is to large, copy the last 2 or 3 abends into a text file and attach it. Juwt make sure you have abend 1 attached to this issue.

jgray
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: NW65 SP8a server keeps abending

On Mon, 15 Nov 2010 13:36:03 +0000, jgray wrote:

> What you could do is if the abend.log file is to large


Or use www.pastebin.com. That's what we're telling people to do over in
the idm.engine-drivers forum, where large trace files are the norm.


--
---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Novell Knowledge Partner http://forums.novell.com

Please post questions in the newsgroups. No support provided via email.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.