Cisco SD-WAN vManage tail log
When you start vManage, it can take a long time before the GUI is accessable, even though the system shows that it is ready.
You can monitor what it is doing by looking at the vmanage-server.log file.
First open vshell and then tail the log file:
tail -f /var/log/nms/vmanage-server.log
You'll see that the controller is doing a lot of things behind the scenes while you are waiting for the GUI to become accessable:
25-Apr-2023 13:59:17,539 UTC INFO [vManage1] [SdavcManager] (vManage-akka.actor.default-dispatcher-5) || SdavcManager started 25-Apr-2023 13:59:17,539 UTC INFO [vManage1] [SingleNodeEntityOwnershipService] (vManage-akka.actor.default-dispatcher-5) || registering entity : EntityOwnershipInfo{entityName='ContainerLBManager', bucket=bucket1, owner='627d826d-8a7b-4b5b-a3ce-30937bfa7ac7'} 25-Apr-2023 13:59:17,572 UTC INFO [vManage1] [SingleNodeEntityOwnershipService] (vManage-akka.actor.default-dispatcher-5) || registering entity : EntityOwnershipInfo{entityName='schedules-service-singleton-selector', bucket=bucket1, owner='627d826d-8a7b-4b5b-a3ce-30937bfa7ac7'} 25-Apr-2023 13:59:17,572 UTC INFO [vManage1] [ScheduledServiceSingletonSelector] (EntityOwnership-0) || Ownership changed!! AM I STILL LEADER? true 25-Apr-2023 13:59:17,608 UTC INFO [vManage1] [ScheduledServiceSingletonSelector] (vManage-akka.actor.default-dispatcher-5) || Registering service type : com.viptela.vmanage.server.admin.CredentialValidatorService, to scheduled service singleton selector 25-Apr-2023 13:59:18,000 UTC INFO [vManage1] [ApplicationActor] (vManage-akka.actor.default-dispatcher-5) || Software upgrade timeout - 3600000 mins 25-Apr-2023 13:59:18,375 UTC INFO [vManage1] [LinkUpdateEventAddThread] (vManage-correlation-engine-link-update-dispatcher-35) |default| Process Event Queue called tenantId : default, count : 1 25-Apr-2023 13:59:20,512 UTC INFO [vManage1] [CauseCorrelator] (correlation-engine-default-0) || Creating new CorrelationEventNormalizer for event : system-reboot-issued 25-Apr-2023 13:59:20,860 UTC INFO [vManage1] [AlarmsDAO] (vManage-akka.actor.default-dispatcher-2) |default| Could not find alarm with uuid 8e2eeb50-f488-4562-a93b-d1b994379b1e, trying again 25-Apr-2023 13:59:21,174 UTC INFO [vManage1] [ClusterConfigurationManager] (Thread-135) || Create vmanage cluster config node thread exited 25-Apr-2023 13:59:21,665 UTC INFO [vManage1] [AlarmsDAO] (vManage-akka.actor.default-dispatcher-2) |default| AlarmsDAO::addAlarm() - Adding alarm {"devices":[{"system-ip":"172.16.1.101"}],"eventname":"system-reboot-issued","type":"system-reboot-issued","rulename":"system-reboot-issued","component":"System","entry_time":1682431160475,"statcycletime":1682431160475,"message":"The device rebooted","severity":"Medium","severity_number":3,"uuid":"21b17340-d0a5-4591-aba0-e0b2f629fd68","values":[{"host-name":"vManage1","system-ip":"172.16.1.101","reboot-reason":"Initiated by user"}],"rule_name_display":"System_Reboot_Issued","receive_time":1682431160475,"values_short_display":[{"host-name":"vManage1","system-ip":"172.16.1.101"}],"acknowledged":false,"cleared_events":["8e2eeb50-f488-4562-a93b-d1b994379b1e"],"active":false}