Issue/Introduction:
CA is currently investigating this issue. At this time, there is a known workaround.
Modify the 61st line of /etc/init.d/sysedge start script
from
DAEMON=sysedge.sol210
to
DAEMON=sysedge.sol210-sparcv9
Related Issues/Questions:
/etc/init.d/sysedge start script won't start sysedge on Solaris 2.10
Problem Environment:
SystemEDGE 4.2 PL7
Solaris 2.10
Causes of this problem:
/etc/init.d/sysedge script is setting sysedge.sol210 instead of sysedge.sol210-sparcv9 as DAEMON variable
(Legacy KB ID CNC TS30382 )
Environment:
Release:
Component: EHCON