What causes Failure of start AMPM manager 7.0.1 ???

Hi itc,

Well many reasons might cause the failure. did you point your AM/PM server to the proper broker? without the a broker it won´t work.

check the SM_BROKER_DEFAULT parameter in the the runcmd_env.sh file under ../IP/smarts/local/conf directory

check the licenses, are these local or should point to a license server ...
the parameter (SM_LICENSE) is in the same file as above

check how and where your AM/PM is logging and which logging level is using by typing sm_service show --cmdline

For the sm_service options that use a minimum security level, the level can be:
None, Emergency, Alert, Fatal, Critical, Error, Warning, Notice, Informational,
and Debug. Note that Fatal is equivalent to Emergency, Alert, or Critical. See the
top of Figure 7-1 for the range of security levels.
◆ Option --output[= ]
Used to capture and redirect stdout and stderr output for a Smarts application to
a Smarts log file in the BASEDIR/smarts/local/logs directory. The name of the
log file is .log, or the --logname value if is omitted. If --output is not
specified in the invocation line, the application¿s stdout and stderr output prints
by default to the console screen.
◆ Option --errlevel=
Used by the Smarts exception logging mechanism to determine the minimum
exception level for writing messages to stderr. By default, --errlevel is set to
Warning. Exceptions below this level are not written to stderr.
◆ Option --loglevel=
Used by the Smarts exception logging mechanism to determine the minimum
exception level for sending messages to the system error logger. By default,
--loglevel is set to Error. Exceptions below this level are not forwarded to the
system error logger.
◆ Option --logname=
Used to specify the name of the Smarts log file and the name of the sending
application in messages destined for the system error logger. The default is the
name of the application specified by the --name option (or just -n).
◆ Option --tracelevel=
Used to print a stack trace to the Smarts log file when an exception at this level or
above occurs. By default, --tracelevel is set to Fatal. Exceptions below this level
do not write a stack trace.

well, this is by now ... i don't know your enviroment nor we have more info

cheers

Fernando

Hi,
All looked very simply:
after patch5 in runcmd_env.sh we observe "DefaultBroker" string as ":" against "localhost:426".