Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2006355.1
Update Date:2016-05-17
Keywords:

Solution Type  Problem Resolution Sure

Solution  2006355.1 :   xDR Session Stopped, IXP Server Is Crashing or Top Shows High Load Because of IxpForward Process  


Related Items
  • Oracle Communications Performance Intelligence Center (PIC) Software
  •  
  • Oracle Communications Diameter Signaling Router (DSR)
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec PIC
  •  




In this Document
Symptoms
Cause
Solution
 Definitive solution
 Workaround
 Restore
 Prevent
References


Created from <SR 3-10597021831>

Applies to:

Oracle Communications Performance Intelligence Center (PIC) Software - Version 7.1 to 9.0.4 [Release 7.0 to 9.0]
Oracle Communications Diameter Signaling Router (DSR) - Version DSR 3.0 to DSR 5.1 [Release DSR 3.0 to DSR 5.0]
Information in this document applies to any platform.

Symptoms

Following symptoms can happen:

  • xDR session stopped with following log in IxpStore or IxpOperate:
    1214:171141.562 DTS2 OpenConnection(): Connecting to IP address ixphostname failed, port is 2222 and stream name is 'streamname' [19203/DtsConsumer.cpp:183]
    1214:171141.562 DTS2 OpenStream(): OpenConnection failure with error message '-10' on stream name 'streamname' [19203/DtsConsumer.cpp:568]
  • IXP server is rebooting automatically. hplog -v command output shows Automatic Server Recovery (ASR) has been triggered.
  • top shows high load (over 100)
  • IxpForward use maximum allocatable memory on a 32 bits operating system (around 3 Gigabytes)
  • IxpForward log contains "Cannot allocate memory" messages.

Cause

IxpForward is allocating memory for each connection attempts. After some time, process can reach operating system limit. 

Solution

Definitive solution

It is highly recommended to upgrade to PIC 10.1.

Workaround

Restore

If IxpForward is currently logging "Cannot allocate memory" messages, it can be restarted.

All processes reading data via this IxpForward process will restart (default setting).

Prevent

The only workaround consist of checking if there are still repeated connection attempts received by IxpForward process.

In normal operation, no new connection attempts shall be made.

Log message looks like:

0914:132759.086 DTS2 Connection on MAP_TDR at 1.000000 [13283/DtsServer.cpp:962]

If this kind of messages are regularly written, it must be investigated following procedure below:

  1. Collect IxpForward logs from all IXP base or PDU servers still having connection attempts:
  2. All files can be parsed with command below to know streams names and number of occurences:
    for i in `ls *.log`; do grep -oP 'Connection on [a-zA-Z_0-9]* at' $i | cut -c15- | rev|cut -c3- | rev | sort | uniq -c > $i.out; done ; grep '' *.out
  3. Analyze each connection attempts. Use show_stream_info.pl and show_process_info.pl script to find more information on streams and DFP.
    Connection attempts can be due to:
    • empty stream (no data)
    • crashing process

References

<BUG:19096970> - [209301]IXPFORWARD "CANNOT ALLOCATE MEMORY" ERRORS

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback