Operational Defect Database
BugZero updated this defect 58 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 433854
Unable to start server after a clean install of Smarts
Last update date:
3/22/2024
Affected products:
Smart Assurance - SMARTS
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Symptoms
Unable to start server after a clean install of Smarts server tries to start and generates error and stack trace to server log file Error message: Cannot connect to DM Broker: No process is connected to the specified location
Cause
This error is generated by the server not being able to resolve the name "localhost". Execute the following from command line:hostnamecat /etc/hostname.*cat /etc/nodename Note the hostname of this device.
Resolution
Edit file in <BASEDIR>/smarts/local/conf/runcmd_env.shChange SM_BROKER= localhost:426 to <hostname>:426 or <ip address>:426
Related Information
The following is the error message found in server log file in <BASEDIR>/smarts/local/logs/<domain server>.log:Cannot connect to DM Broker at 'localhost:426/dmbroker': No process is connected to the specified locationCI-F-ETHROWTHIS-Exception being thrown: CI-EASSERTFAIL-Assertion failed: "si_uuid_creat(&uuid) != NULL"; in file "/work/redcurrent/IC-6.5-SP02/37/smarts/ga/parser/asl.y" at line 1497Solaris 20900:platform: V6.5 SP2(63875), 15-Jun-2006 23:41:48 - SmartPack 2, Build 37libsm_clsapi.so (63875) 15-Jun-2006 23:48:41
