Scribd
Upload
19 views1 page

Technical Communication Omnipcx 4400: NB of Pages: 1

This technical document describes a problem where a system is running out of resources due to an accumulation of threads. It occurs when suproutage software on Windows PCs is used and the Chorus thread from each process is not finished when the application closes and reopens. This leads threads to accumulate until the system limit is reached. The solution is to only use the integrated suproutage application from OmniPCX 4400 and restart the srv_suprout process to kill unused threads. Commands like limitsinfo and cs can help check the number of threads and identify if this is the problem.

Uploaded by

Humberto Ochoa Mendez
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
19 views1 page

Technical Communication Omnipcx 4400: NB of Pages: 1

This technical document describes a problem where a system is running out of resources due to an accumulation of threads. It occurs when suproutage software on Windows PCs is used and the Chorus thread from each process is not finished when the application closes and reopens. This leads threads to accumulate until the system limit is reached. The solution is to only use the integrated suproutage application from OmniPCX 4400 and restart the srv_suprout process to kill unused threads. Commands like limitsinfo and cs can help check the number of threads and identify if this is the problem.

Uploaded by

Humberto Ochoa Mendez
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

TECHNICAL COMMUNICATION No.

TC0382 Date : 07-11-2002

OmniPCX 4400 Nb of pages : 1

URGENT

NOT URGENT TEMPORARY PERMANENT

SUBJECT : NO MORE SYSTEM RESOURCES

1. PROBLEM
Messages of type Cannot fork are displayed on the system console. Many other troubles can occur
such as impossibility to run a command on a shell, etc.
This problem can occur from several various sources.
The use of suproutage software on Windows PC is one of sources. On each closing of the application
on the PC, the Chorus thread of involved process is not finished. When restarting the application, an
other thread is created and so on. The threads accumulate to reach the system limits.

2. SOLUTION
The use of this software is not supported by Alcatel. Only the integrated suproutage OmniPCX 4400
application must be used.
In the blocking status described above, you just have to restart the srv_suprout process to kill the
useless threads. In order to check that problem, the following commands can be entered:
− limitsinfo
the thread line shows the current threads, the Chorus maximum number and the maximum number
reached during the life of the system,
− cs | grep suprout
a line is displayed. The field on the left of srv_sprout process name corresponds to the number
threads of process. There are 3 on system start.
If the system cannot run one of these commands, then you should try if possible, to finish at least one
task associated to a terminal (example: to quit a telnet session, to quit a rlogin , etc.) to give to the
system an additional resource.
Notes
− The notion of thread is explained in Advanced Maintenance OmniPCX 4400 training.
− The commands described above (limitsinfo and cs) can be used on each blocking of CPU.
− For ACSE technicians only.
If the ACSE technician cannot log in when there is no longer system resources to supply the shell,
the commands below can be run.
CAUTION: The telephone application will be stopped or "frozen".
On "console" port only:
• enter Ctrl G Ctrl P (the telephone application will be "frozen") or Ctrl G Ctrl O (the IO1 will be
stopped: there is stop of the telephone application or switch-over to twincpu),
• press the <Enter> key to view the kdbg prompt (kernel debugger),
• enter L <Enter>,
• the information displayed are the same as with "limitsinfo" command,
• enter c to quit the debugger (reboot of the system if you accessed with Ctrl G Ctrl O .
1

You might also like