semaphore errors on application startup

[Richard Pereira_1]

Hi,

We were consolidating 2 hp 11.iv1 servers into 1. We basically moved all the SAN mounts and services onto the second server. When I try starting a application called edi on the second server, it complains about semaphores.

[WARN ] shared memory segment for key 35 not found

Am I right in understanding this having issues withe semaphore id 35?

[Dennis Handly]

No. Shared memory and semaphores are completely different IPC facilities.
What does "ipcs -ma" show?
You may have to restart your application or some utility that initializes everything.
Or if you can't find that, reboot.

Do you have your kernel parms the same or larger for your second server?

[Richard Pereira_1]

Attached ipcs -ma output.

I tuned the kernel to match or take the higher of the 2 values.

we tried a reboot, no success. we also tried shutting all other software and just starting this app and it bombs with the same error.

[Dennis Handly]

>we tried a reboot, no success. we also tried shutting all other software and just starting this app and it bombs with the same error.

You would have to add up all of the SEGSZ column but my guess is this is over 2 Gb so you don't have any more virtual addresses.
I assume you can't stop your informix application?

I don't know which of those segments are 64 bit, where the 2Gb limit doesn't count. Memory windows may also help.

You could try using tusc to see what error you get on the shmget(2):
tusc -fp -ea -o tusc.out application parms ...

>[WARN ] shared memory segment for key 35 not found

Since this says WARN, does the application still work?

[Richard Pereira_1]

Unfortunately we merged the app and db servers so informix has to run. the app seems to start 1 of 5 sub processes. I have a new lead, seems there could be a licensing issue. ill know by tomorrow.

[Richard Pereira_1]

Turns out re-installing the licenses did the trick. thanks for the help.