PANIC: Insufficient semaphores to handle .. no. of concurrent .... error

HCL Domino Domino Forum
1

Hello,

We are running Lotus Domino R 6.0 on Linux 2.4.18-14 Kernel (Redhat Linux 8.0).

The server is crashed with the following messages on the logs.

Thread=[26476:00002-08192]

Stack base=0xBFFFEC7C, Stack size = 9348 bytes

PANIC: Insufficient semaphores to handle number of concurrent owned critical regions. Please reconfigure your kernel.

Stack base = 0xbfffec7c, Stack size = 10852 bytes

Fatal Error signal = 0x0000000b PID/TID = 26476/8192

Wed May 28 01:00:28 Running cleanup script

NSD is in progress …

Please attach the following files to your bug report along with the server log:

Log file : ./nsd_all_Linux_IS-DOMINO_05_28@01_00.log

Domino Halted. Type ‘quit’ to Terminate/Cleanup

Session terminated, killing shell…- Child Terminated from signal 11

Domino Halted. Type ‘quit’ to Terminate/Cleanup …killed.

Anybody mail me what could be the problem based on the above logs.

2

Subject: PANIC: Insufficient semaphores to handle … no. of concurrent … error

Has anyone made some good progress on this issue, it seems that these threads have gone quiet but without a good resolution ?

I’m still having loads of problems with this.

Mark

3

Subject: RE: PANIC: Insufficient semaphores to handle … no. of concurrent … error

Not too sure if anyone has a different fix for this, but the following worked for us.

Download and untar a linux kernel source.

Then edit the sem.h in the linux\include\linux path

Then just redefine SEMMNI

// Changed RN - 20050112 - #define SEMMNI 128 /* <= IPCMNI max # of semaphore identifiers */

#define SEMMNI 256 /* <= IPCMNI max # of semaphore identifiers */

Recompile and then load your new kernel.

Worked a treat for us.

4

Subject: PANIC: Insufficient semaphores to handle … no. of concurrent … error

An NSD log from my Linux system contained the following section:

IPC Limits:

------ Shared Memory Limits --------
max number of segments = 4096
max seg size (kbytes) = 32768
max total shared memory (kbytes) = 8388608
min seg size (bytes) = 1



------ Semaphore Limits --------
max number of arrays = 128
max semaphores per array = 250
max semaphores system wide = 32000
max ops per semop call = 32
semaphore max value = 32767



------ Messages: Limits --------
max queues system wide = 16
max size of message (bytes) = 8192
default max size of queue (bytes) = 16384
5

Subject: RE: PANIC: Insufficient semaphores to handle … no. of concurrent … error

Thanks for ur response. I checked up these details in the NSD Log file. These details are available in that Log file as it is specified by you.it is very urgent one.

Best Regards

Karthik.

6

Subject: RE: PANIC: Insufficient semaphores to handle … no. of concurrent … error

Just to be clear, I was not specifying anything, I was just pointing out where this information is found in the NSD log. If the error message says that there are an insufficient number of semaphores and that you should reconfigure your kernel, then perhaps you want to do that. On the other hand, you might think that based on the NSD info that you should have enough and that the message is in error. You may choose to contact support. This is only information upon which you can make decisions.