Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
 |
| AIX AIX is IBM's industry-leading UNIX operating system that meets the demands of applications that businesses rely upon in today's marketplace. |
 |
|
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
06-28-2009
|
||||
|
||||
|
Ts_nim_error_stuck - 864d2ce3
Hi All,
Hope you can help me figure out this problem that I have with one of our servers. LABEL: TS_NIM_ERROR_STUCK_ IDENTIFIER: 864D2CE3 Date/Time: Tue Jun 23 14:55:43 NFT 2009 Sequence Number: 754613 Class: S Type: PERM Resource Name: topsvcs Description NIM thread blocked Probable Causes A thread in a Topology Services Network Interface Module (NIM) process was blocked Topology Services NIM process cannot get timely access to CPU User Causes Excessive memory consumption is causing high memory contention Excessive disk I/O is causing high memory contention Recommended Actions Examine I/O and memory activity on the system Reduce load on the system Tune virtual memory parameters Call IBM Service if problem persists Failure Causes Excessive virtual memory activity prevents NIM from making progress Excessive disk I/O traffic is interfering with paging I/O Recommended Actions Examine I/O and memory activity on the system Reduce load on the system Tune virtual memory parameters Call IBM Service if problem persists Detail Data DETECTING MODULE rsct,nim_control.C,1.39.1.3,5485 ERROR ID 6XnGH40TvBE8/NPe/9cgt8.................... REFERENCE CODE Thread which was blocked command receive thread Interval in seconds during which process was blocked 6 Interface name rhdiskpower6 |
|
06-28-2009
|
|||||
|
|||||
|
Your server is a cluster node of an HACMP cluster using heartbeat over disk as non-IP network. Because of excessive I/O disk heartbeats get lost and you receive a warning via errpt that the cluster might not work as expected because of that. Given that the heartbeat disk devices still exist and that they are in a working condition the following can be said: As long as
- you don't receive that message regularly, - your IP network hearbeat does'nt fail too you don't need to worry. (Only if ALL heartbeat networks fail that would be a real problem.) To avoid this errormessage turning up again you could - change non-IP network speed from normal to slow - use more disks for I/O - move the disk heartbeat device to another disk/LUN. Last thought: In case you are unsure how to run an HACMP cluster don't touch it but ask a colleague who is aware of HA clusters to assist you. |
|
06-29-2009
|
||||
|
||||
|
Thank's
Accept a very warm greetings. |
| Sponsored Links | ||
|
|
Linear Mode
