UIM probe will not start and no there is nothing in the log to determine why. Example would be the trellis probe.
Release : Any
Component : Probes
Open the controller.cfg on the robot and see if there is a dependency for that probe. In the example of trellis not starting, look for the words 'starts after':
<trellis>
description = Trellis Application Container
group = Service
active = yes
type = daemon
command = <startup java>
arguments = -server -XX:MaxDirectMemorySize=2g -XX:PermSize=512m -XX:MaxPermSize=1g -XX:NewSize=32m -XX:MaxNewSize=64m -XX:+UseParNewGC -XX:MaxTenuringThreshold=2 -XX:SurvivorRatio=8 -XX:+UnlockDiagnosticVMOptions -XX:ParGCCardsPerStrideChunk=32768 -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:+ParallelRefProcEnabled -XX:+CMSClassUnloadingEnabled -XX:CMSInitiatingOccupancyFraction=80 -XX:+UseCMSInitiatingOccupancyOnly -XX:+AlwaysPreTouch -XX:-OmitStackTraceInFastThrow -Dfile.encoding=UTF-8 -Djava.library.path=../../../lib -cp "container/*;bootstrap/*;core/*;lib/*;features/relational-persistence/core/*" com.ca.trellis.container.Launcher -n trellis -c trellis.cfg -e extensions -s services
config = trellis.cfg
logfile = trellis.log
workdir = probes/service/trellis
start_after = udm_manager
magic_key = 6I9rgRDYA4f2cbGGgJIjUF6kp3SbXa940M9CCg/eMoU=
</trellis>
If that probe is not started, than start it. If it will not start, then check the log, and the same section in the controller.cfg for it.