ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

cabi upgrade from 3.32 to 3.40 fails with "Not able to connect"


Article ID: 145840


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


CABI upgrade from 3.32 to 3.40 with HTTPS enabled fails with the following error in the cabi.log

[main, cabi] changing probe state from 'INITIALIZING' to 'STARTING_WASP'
[main, cabi] activating wasp...
[main, cabi] ... activated wasp  [time taken=0 minute(s) 0 second(s) (141 ms)]
[main, cabi] waiting for wasp to start...
[main, cabi] wasp has started  [time taken=2 minute(s) 47 second(s) (167431 ms)]
[main, cabi] waiting for cabi webapp @ to start responding ... 
[main, cabi] checking url=, timeAlreadyWaitedInSecs=0, maxTimeInSecs=600600
[main, cabi] Not able to connect to url=, timeAlreadyWaitedInSecs=0


Cabi probe is unable to connect to the url without the port configured in the link


Release : 9.0.2

Component : UIM - CABI


Used Raw configure to changed the cabi -> setup -> cabi_url key from to