Haven’t seen it in relation to NBU
but if you are sure that the semaphore parameters are all adequate it may be
that something stopped abnormally and left semaphores or even shared memory
segments in use at a memory address that NBU wants. In NBU 6.x there is a
database instead of flat files and it is Sybase. Most modern databases use a
combination of shared memory segments and semaphores for control.
You can use the ipcs command to examine
what semaphores/shared memory segments are in use. You can use ipcrm to
remove any. WARNING: Deleting shared memory segments or semaphores that are
still required by a running application can cause your system to crash.
If you’re not sure what can be
cleared a reboot will clear both IPC types.
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Dominik Pietrzykowski
Sent: Friday, January 25, 2008
6:20 PM
To:
VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] semaphore
issue
Anyone seen this on a
Solaris 10 server ????
# ltid -v
# Error in getting
semaphore
#
Ltid keeps on dieing and
it complains about semaphores. My other Solaris 10 servers are fine but I have
two with this issue.
Both use different
hardware and no you don’t need to tune the kernel on Solaris 10 as
it’s defaults are much bigger than anything Symantec recommend.
Hope someone can help.
Thanks,
Dominik
