For troubleshooting, let's trace the Monitor. Hopefully we can see why it is not starting. It could be a blocked port for example.
- Go to the <siteminder>\config\ path and edit the trace.conf file.
- It should look like this:
# Common logging settings
nete.enableConsoleLog=0
nete.enableFileLog=1
nete.logFile=c:\mon.log
# Connection API logging levels. There are three levels: 0 - no trace events, 1 - error and warning trace events,
# 2 - all trace events
nete.conapi.logLevel=2
nete.conapi.ipc.logLevel=2
nete.conapi.tcpip.logLevel=2
# Monitoring infrastructure modules logging settings
nete.mon.agentLogLevel=2
nete.mon.monitorLogLevel=2
nete.mon.monitorDbLogLevel=2
nete.mon.monitorChannelLogLevel=2
nete.mon.monitorChannelTrLogLevel=2
nete.mon.monitoringApiLogLevel=2
nete.mon.monitorClientApiLogLevel=2
nete.mon.monitoringAgentProxyLogLevel=2
In this mon.log, you should see messages like this:
(MONAPI ) > Sm_MonApi_RegisterComponent(): start
(MONAPI ) > reinitiateChannelIfClosed(): start
(MONAPI ) > reinitiateChannelIfClosed(): completed
(MONAPI ) > Sm_MonApi_RegisterComponent(): completed
(MONAPI ) > processTransactionMessage() start