Sponsored Content
Operating Systems Solaris 18-Mar-2012 14:25:03.209 general: error: socket: file descriptor exceeds limit (4096/4096) Post 302608749 by jim mcnamara on Sunday 18th of March 2012 12:21:00 PM
Old 03-18-2012
The per process limit for descriptors in your case is 4096.

Read the paragraphs below BEFORE you do this!

Edit /etc/system:
Code:
set rlim_fd_max  8192
set rlim_fd_cur  8192

Then reboot.

Since things worked well before, the likelihood of the open file descriptors limit being the root cause of your problem is small. So, changing it is like using a bandage to cure cancer. It may work for a while, but it is probably not fixing the problem.

I suspect that the root cause is the settings you maintain for /dev/tcp with the ndd command. Diagnosing the problems with these is somewhat touchy-feely in that you can make a change and see no noticeable effect or a big (postive or negative) change.

Usually, heavy duty sockets apps require ndd tuning. Here are some we have used on systems with loads of tcp/ip traffic. This does not mean they are a perfect choice. They are not. I would play around with these on a running system, check your values first. You may also want to google around for tuning tcp on solaris to see other values.

Also read your documentation to see if there are recommended settings. The parameters
name tcp_rexmit_* come to mind here. Some parms have to be set on clients as well.

These are the items we set, and the values we currently use:

Code:
/usr/sbin/ndd -set /dev/tcp tcp_keepalive_interval 900000
/usr/sbin/ndd -set /dev/tcp tcp_time_wait_interval 60000
/usr/sbin/ndd -set /dev/tcp tcp_fin_wait_2_flush_interval 67500
/usr/sbin/ndd -set /dev/tcp tcp_conn_req_max_q 65536
/usr/sbin/ndd -set /dev/tcp tcp_conn_req_max_q0 65536
/usr/sbin/ndd -set /dev/tcp tcp_xmit_hiwat 65536
/usr/sbin/ndd -set /dev/tcp tcp_recv_hiwat 65536
/usr/sbin/ndd -set /dev/tcp tcp_max_buf 655360

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Counting Files and send an email Notification if it exceeds a limit

Hi, I am trying to write a script to Count Files in a directory located on a remote server and send an email Notification if it exceeds a limit. The code given below doesnot check the condition and sends the mail everytime irrespective of the condition. I have put this script in the cron. Can... (10 Replies)
Discussion started by: amitsayshii
10 Replies

2. Shell Programming and Scripting

Alert When a Process Exceeds a CPU Utilization Limit...

Hi EveryOne We run CICS Sofware on our AIX Machine... When ever some Process or Transaction loops it Takes heavy process Usage.. Is there a way that i can Get a alert message or a Message Thrown on to screen when ever a process named "cicsas" uses more that 20%... fo CPU.. I was... (4 Replies)
Discussion started by: pbsrinivas
4 Replies

3. IP Networking

Can we write a multiple thread to receive from a single socket file descriptor

Hi Friends, I have written a program which will listener for more than 1000 requests per second from a single socket descriptor and then it will process those requestes. Its taking X amount of time. Now i want to reduce that time. Will I can write multiple threads to receive the... (2 Replies)
Discussion started by: pa.chidhambaram
2 Replies

4. Programming

Get the file descriptor of a socket file. C vs Python.

Hi, I want to validate that a file is a socket file on Linux. I know I can do this using the S_ISSOCK macro, but I am not sure how to get the file descriptor for the socket file. For example, I know that /tmp/mapping-foo is a socket file. In Python I can do something like this: >>> import... (2 Replies)
Discussion started by: goon12
2 Replies

5. UNIX for Dummies Questions & Answers

Log Size Exceeds Limit

Everytime I try to start Discreet Flame on my Octane2 machine it keeps giving me an error message "initial log size exceeds limit--aborting" Can anyone please help me how to fix this problem. Thanks. Octane2 IRIX64 Release 6.5 Flame 2007 (0 Replies)
Discussion started by: dewaraja
0 Replies

6. UNIX for Advanced & Expert Users

Log Size Exceeds Limit

Everytime I try to start Discreet Flame on my Octane2 machine it keeps giving me an error message "initial log size exceeds limit--aborting" Can anyone please help me how to fix this problem. Thanks. Octane2 IRIX64 Release 6.5 Flame 2007 (0 Replies)
Discussion started by: dewaraja
0 Replies

7. Shell Programming and Scripting

Log Size Exceeds Limit

Everytime I try to start Discreet Flame on my Octane2 machine it keeps giving me an error message "initial log size exceeds limit--aborting" Can anyone please help me how to fix this problem. Thanks. Octane2 IRIX64 Release 6.5 Flame 2007 (6 Replies)
Discussion started by: dewaraja
6 Replies

8. Hardware

How to Clone a Drive with 512 byte Sectors to a Drive with 4096 bytes/sector (AF)?

I have a 320 GB drive which dual boots Windows and Debian: Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal):... (0 Replies)
Discussion started by: phillipsoasis
0 Replies

9. Shell Programming and Scripting

How to remove a file in shell script if its size exceeds limit?

How can i remove a file using shell script when its size exceeds 10MB. Given that file is located in different location to the shell script where it is running? (4 Replies)
Discussion started by: vel4ever
4 Replies

10. Solaris

.profile[21]: ulimit: exceeds allowable limit

Hello All, I am having an issue with ellipse environment, Subscribing ellipse version /opt/mincom/ellipse/bs037__ora_cics_svr .profile: ulimit: exceeds allowable limit , prj -l ellsupp #ulimit -a time(seconds) unlimited file(blocks) unlimited data(kbytes) unlimited stack(kbytes) 8192... (22 Replies)
Discussion started by: Revathi2089
22 Replies
SLABINFO(5)							   Linux manual 						       SLABINFO(5)

NAME
/proc/slabinfo - Kernel slab allocator statistics SYNOPSIS
cat /proc/slabinfo DESCRIPTION
Frequently used objects in the Linux kernel (buffer heads, inodes, dentries, etc.) have their own cache. The file /proc/slabinfo gives statistics. For example: % cat /proc/slabinfo slabinfo - version: 1.1 kmem_cache 60 78 100 2 2 1 blkdev_requests 5120 5120 96 128 128 1 mnt_cache 20 40 96 1 1 1 inode_cache 7005 14792 480 1598 1849 1 dentry_cache 5469 5880 128 183 196 1 filp 726 760 96 19 19 1 buffer_head 67131 71240 96 1776 1781 1 vm_area_struct 1204 1652 64 23 28 1 ... size-8192 1 17 8192 1 17 2 size-4096 41 73 4096 41 73 1 ... For each slab cache, the cache name, the number of currently active objects, the total number of available objects, the size of each object in bytes, the number of pages with at least one active object, the total number of allocated pages, and the number of pages per slab are given. Note that because of object alignment and slab cache overhead, objects are not normally packed tightly into pages. Pages with even one in- use object are considered in-use and cannot be freed. Kernels compiled with slab cache statistics will also have "(statistics)" in the first line of output, and will have 5 additional columns, namely: the high water mark of active objects; the number of times objects have been allocated; the number of times the cache has grown (new pages added to this cache); the number of times the cache has been reaped (unused pages removed from this cache); and the number of times there was an error allocating new pages to this cache. If slab cache statistics are not enabled for this kernel, these columns will not be shown. SMP systems will also have "(SMP)" in the first line of output, and will have two additional columns for each slab, reporting the slab allocation policy for the CPU-local cache (to reduce the need for inter-CPU synchronization when allocating objects from the cache). The first column is the per-CPU limit: the maximum number of objects that will be cached for each CPU. The second column is the batchcount: the maximum number of free objects in the global cache that will be transferred to the per-CPU cache if it is empty, or the number of objects to be returned to the global cache if the per-CPU cache is full. If both slab cache statistics and SMP are defined, there will be four additional columns, reporting the per-CPU cache statistics. The first two are the per-CPU cache allocation hit and miss counts: the number of times an object was or was not available in the per-CPU cache for allocation. The next two are the per-CPU cache free hit and miss counts: the number of times a freed object could or could not fit within the per-CPU cache limit, before flushing objects to the global cache. It is possible to tune the SMP per-CPU slab cache limit and batchcount via: echo "cache_name limit batchcount" > /proc/slabinfo AVAILABILITY
/proc/slabinfo exists since Linux 2.1.23. SMP per-CPU caches exist since Linux 2.4.0-test3. FILES
<linux/slab.h> 2001-06-19 SLABINFO(5)
All times are GMT -4. The time now is 09:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy