Start a Conversation

Unsolved

This post is more than 5 years old

2530

August 28th, 2007 08:00

EMC -Solutions Enabler problem

I have installed Solutions Enabler V6.2.2 on a solaris 9 machine. I having problems in running the symapi secure daemon and I get an error
"The lock attempt on the gatekeeper path or SYMAPI database file failed" .

Did some search and it says it is because of the locked semaphore which I need to kill but cannot find any semaphore in the locked state.

Any ideas and a quick solution is very much appreicated

17 Posts

August 28th, 2007 08:00

how did you check the locked semaphores ?

6 Posts

August 29th, 2007 01:00

I get the list of semaphores currently in use by running the following command:

symcfg list -semaphore

I also verify if SYMCLI commands are running and if no SYMCLI commands are running, remove semaphores labelled as locked by running the following command:

ipcrm -s semaphore ID.

If no SYMCLI commands are running but the semaphores show locked, remove them also.

After removing the semaphores, you should be able to run a symcfg discover successfully.


After doing all this I am getting the same error.

2 Intern

 • 

2.8K Posts

August 29th, 2007 02:00

1) a snip of the symapi log may help identifying what's broken
2) do you have Oracle (or other applications) running on the same host ??

maybe Oracle (or other applications) are consuming semaphores and when symapi needs a lock simply can't find a lock since they are already used by someone else .. It happened to me in the past .. maybe it's happening also to you :-)

6 Posts

August 29th, 2007 03:00

I am checking the symapi log and the last line of it shows the following

08/28/2007 16:35:20.899 9131 1 EMC Corp log_lock_status Gatekeeper|Database lock failed with APILCK error APILCK_C_DASEMGET, lock result is 13 (/var/symapi/db/symapi_db.bin) OBTAIN function #s 0 0 0 0 0

I have oracle database running on this machine.

Let me know if this helps

2 Intern

 • 

2.8K Posts

August 29th, 2007 05:00

Yes .. the mesage (APILCK_DASEMGET) pointed to a very limited number of primus solutions .. Let me pose another (and hope final) question .. Are you using Veritas on the host ??

2 Intern

 • 

2.8K Posts

August 29th, 2007 05:00

I get the list of semaphores currently in use by
running the following command:

symcfg list -semaphore

I also verify if SYMCLI commands are running and if
no SYMCLI commands are running, remove semaphores
labelled as locked by running the following
command:

ipcrm -s semaphore ID.

If no SYMCLI commands are running but the semaphores
show locked, remove them also.

After removing the semaphores, you should be able to
run a symcfg discover successfully.


After doing all this I am getting the same error.


Try to get the full list of semaphores .. Sometimes Solution Enabler leaves some locks .. and forgets about them :-) .. And it happens usually when you upgrade solution enabler ...
Run an "ipcs -s" to show the full list and search for locks beginning with 0x45 .. If no sym* process is running, shutdown all the stor* daemons and remove the locks as per primus emc19899

6 Posts

August 29th, 2007 06:00

yes veritas volume manager is being used on the machine.Please let me know if you need any other info.

2 Intern

 • 

2.8K Posts

August 29th, 2007 07:00

If you are using Veritas VM please look if you can find in the symapi log the following string:

SYSCALL_FORMAT_NOT_SUPPORTED

If you can find this string, please look at the value of the "SYMAPI_USE_VXDMP_GATEKEEPERS" in the "option" file. The value should be DISABLED as per Support Solution emc54732 ..

Message was edited by:
Stefano Del Corno

17 Posts

August 29th, 2007 10:00

Hi Vijay,

Please ensure you have set the correct values of semphores in system file as per solution enabler installation guide instructions.

Regards,
Munish

6 Posts

August 30th, 2007 00:00

Sorry i cannot find any of these parameters,any other suggestions will be very useful.

2 Intern

 • 

2.8K Posts

August 30th, 2007 00:00

It's OK if you didn't find the messages in the logs or in the "options" file ... If you want to check the number of semaphores, please have a look at the "Solution Enabler - Installation Guide" pn 300-002-289 ..

Just as a rule of thumb, semmni, semmns, semmnu, semume needs to be at least 256. Add those 256 to the semaphores needed by Oracle or everything else.
No Events found!

Top