Smarts IP/SAM: Domains unable to register with Smarts broker; "<SYS>-ESPIPE-Illegal seek" written repeatedly to domain log file

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:


Smarts IP and Smarts SAM domains are unable to register with the Smarts broker therefore are unable to communicate between domains and clients.

The following conditions, events or system behaviors may be observed with this issue:

• Smarts IP and Smarts SAM domains are unable to connect to the broker
• The following errors are seen in the Smarts IP and Smarts SAM domain log files:

[June 5, 2013 9:24:08 AM GMT+02:00 +738ms] t@55048608 <Primary Thread>
AUTH-E-EREADSTREAM-While Get_Credentials was reading from "/opt/InCharge/SAM/smarts/bin/system/sm_authority " encountered error
<SYS>-ESPIPE-Illegal seek

[June 5, 2013 9:24:08 AM GMT+02:00 +740ms] t@55048608 <Primary Thread>
AUTH-E-STREAMFAILCLT-Unable to get credentials due to stream failure

[June 5, 2013 9:24:08 AM GMT+02:00 +740ms] t@55048608 <Primary Thread>
SM-W-EBROKER-Cannot connect to DM Broker at '10.79.36.1:426/dmbroker'; in file "/work/tancurrent/DMT-9.2.0.0/19/smarts/skclient/client/sm_redom.c" at line 372
AUTH-ENOTAUTHENTICATED-Unable to authenticate

Environment

VMware Smart Assurance - SMARTS

Cause

The above issue is caused by a timeout in the DNS resolution in the environment.

Resolution

The domain network environment must be configured to ensure that name resolution occurs in a timely manner. A default setting of 30 seconds is used in Smarts for all DNS calls.

If this time limit threshold for DNS replies cannot be met because of environment conditions, the following parameter can be added to the Smarts local/conf/runcmd_env.sh file to increase the name resolution timeout:

SM_AUTHORITY_TIMEOUT=<1-600>

To apply this change to the active environment, the domain must be restarted.