The timeout waiting for wasp to start is often not a problem and it is just that the installer timed out before wasp started.
The max restarts on wasp is a problem.
The possible causes are many so it may be best to open a support case.
More info can be obtained via:
set wasp for log level 5 & log size 1000, then deactivate so the status icon is grey.
If it does not go grey restart the robot, if it still does not go grey reboot the system
if it went grey, set controller for log level 3 & log size 10000
restart the robot and check both logs
If this is uim 9.0.2 does the robot have a pem file?
Configure the robot.cfg File - CA Unified Infrastructure Management - 9.0.2 - CA Technologies Documentation
beyond that all the details are needed, upgrade or new install, what version, OS revision, etc.