After reactivating wasp probe is not getting up. Its taking too much time to Up .
What could be the issue. Can anyone suggest.
If this is critical I would suggest opening a support case.
You can set the wasp loglevel to 3 and logsize to 35000 and restart the wasp probe.
then check the wasp.log and portal.log for errors
would also be helpful to know the version information of the robot, OS and wasp probes.
Wasp can take 15 minutes+ to start for me.
I have pursued that as an issue with support and been told that I shouldn't expect it to be better.
I would disagree with it taking that long in most cases. There are many factors that are not listed here. I would recommend getting to a Sr. Support Engineer to take a deeper dive.
Case went to development. They said that 15 minutes isn't unexpected.
I personally feel that long a startup is unacceptable but then there is no mention in any of the documentation about how long it should take for wasp to start and so technically speaking, so long as it eventually starts, it's within the "as designed" category of performance.
Retrieving data ...