frequent restart of storapid

I have the following error on storapid.log when i restarted storwatchd and storapid. Is that of some concern..

[28032 -cleanclient] May-10 10:29:23 : [removed_symmwin_client()] SWS_ASYNC_CHECK_STATUS returned - symmwin error: 1. Removing client

The [removed_symmwin_client()] isn't really an issue.
Have a look at emc154403 .. It looks like the message is misleading ... And possibly will change in the future.

[edit to add hyperlink]
http://csgateway.emc.com/primus.asp?id=emc154403

I guess it's better if you open a SR for your restarting daemons.

Message was edited by: His Benevolency
David Yates

i have an SR alraeady opened . No singinificant progress so far.

Can you please write me an email (you can find my address stripping the space from my surname and using usual EMC email address: surname_name@emc.com) with SR number ?? I'm curious to find what's going on with your SR.. I guess someone is digging logs. And S.E. have very long logs!!

Do you have a grab of the host ?? Is it already in SR ??

i could see most of the time simialr entries coming in the log. Those devices are not in the system now. But i am not sure why the system is trying to access it.

[13660 job_pool-941] May-12 8:53:31 : [lock_and_open_device()] Could not open device /dev/rdsk/c48t6d2
[13660 job_pool-941] May-12 8:53:31 : [open_device()] Failed to open raw device '/dev/rdsk/c48t8d0', rc: 0x0
, errno: 2: Unknown code -1 (0xffffffff)
[13660 job_pool-941] May-12 8:53:31 : [lock_and_open_device()] Could not open device /dev/rdsk/c48t8d0
[13660 job_pool-941] May-12 8:53:31 : [open_device()] Failed to open raw device '/dev/rdsk/c48t8d1', rc: 0x0
, errno: 2: Unknown code -1 (0xffffffff)
[13660 job_pool-941] May-12 8:53:31 : [lock_and_open_device()] Could not open device /dev/rdsk/c48t8d1
[13660 job_pool-941] May-12 8:53:31 : [open_device()] Failed to open raw device '/dev/rdsk/c48t8d2', rc: 0x0
, errno: 2: Unknown code -1 (0xffffffff)
[13660 job_pool-941] May-12 8:53:31 : [lock_and_open_device()] Could not open device /dev/rdsk/c48t8d2
[13660 job_pool-941] May-12 8:53:31 : [open_device()] Failed to open raw device '/dev/rdsk/c48t8d3', rc: 0x0
, errno: 2: Unknown code -1 (0xffffffff)
[13660 job_pool-941] May-12 8:53:31 : [lock_and_open_device()] Could not open device /dev/rdsk/c48t8d3
[13660 job_pool-941] May-12 8:53:31 : [open_device()] Failed to open raw device '/dev/rdsk/c48t9d0', rc: 0x0
, errno: 2: Unknown code -1 (0xffffffff)
[13660 job_pool-941] May-12 8:53:31 : [lock_and_open_device()] Could not open device /dev/rdsk/c48t9d0

ROTFL

The other intersting thing i found is the client_use options under /opt/emc/API/config/daemon_options. can that be tuned from require(default) to optional.?

Do any one has any experience in that direction?

# Parameter client_use
#
# Meaning: Specifies the client use of the storapid.
#
# 'never' indicates the client is never to
# connect to the storapid.
# 'if-running' indicates the client should connect
# only if the storapid is running.
# 'require' indicates the client is required to use
# the storapid. If it is not running, an attempt will
# be made to start it. If the start fails, all API and
# CLI functions will return an error until it is started.
# 'optional' indicates the client should connect to the
# storapid if running. If it is not running, an attempt
# is made to start the storapid. If the start fails, API and
# CLI functions will continue.
#
# Allowed Values: never | if-running | require | optional
#
# Default Value require

# storapid:client_use = optional

Usually this error depends on a gatekeeper previously available and now (as you mentioned) unavailable. Probably Solution Enabler still believes the device is available and probes the gatekeeper, to check if it's available.
I see at least 3 different targets .. thus 3 different storage ports that used to be available ..

resolution from SR.

http://csgateway.emc.com/primus.asp?id=emc183476

The issue is a known problem when using Powepath 5.10 and solutins enabler. There is a bug that causes the Storapid daemon to crash intermittently with a fault. The short term fix is to disable the storapid daemon by setting the storapid:client_use=never in the daemon_options. The long term fix is to load powerpath patch

Message was edited by:
Dave Yates, Il Moderatore Benevolo
Hyperlinked the knowledgebase entry.

work around and fix are posted on the thread