vManage GUI is not accessible after installing 20.9.4 image

[Amarendra Nayak]

It was a working setup. vManage GUI was accessible earlier, but after installing 20.9.4 image the GUI is not coming up. Can someone please help?

There is enough space available in rootfs.rw (Because I read in one other community post that, if you have less than 1GB free on /rootfs.rw the application server shuts down, causing the error), So I think space is not an issue here. And "NMS application server" is in a running state as well.

vManage:~$ df -kh
Filesystem Size Used Avail Use% Mounted on
none 16G 3.4M 16G 1% /dev
/dev/sda1 5.0G 3.9G 1.2G 78% /boot
/dev/loop0 1.2G 1.2G 0 100% /rootfs.ro
/dev/sda2 15G 11G 3.8G 74% /rootfs.rw
aufs 15G 11G 3.8G 74% /
tmpfs 16G 1.5M 16G 1% /run
shm 16G 668K 16G 1% /dev/shm
tmp 1.0G 3.6M 1021M 1% /tmp
/dev/sdb 98G 22G 72G 23% /opt/data
tmplog 120M 56M 65M 46% /var/volatile/log/tmplog
cgroup 16G 0 16G 0% /sys/fs/cgroup
svtmp 2.0M 1.6M 492K 76% /etc/sv
vManage:~$

"request nms all status" shows that only "NMS SDAVC server" is not running. I did "request nms all restart" but still no change in status.

vManage# request nms all status
NMS service proxy
Enabled: true
Status: running PID:36628 for 11698s
NMS service proxy rate limit
Enabled: true
Status: running PID:36860 for 11698s
NMS application server
Enabled: true
Status: running PID:23835 for 33s
NMS configuration database
Enabled: true
Status: running PID:27000 for 11700s
NMS coordination server
Enabled: true
Status: running PID:36188 for 11701s
NMS messaging server
Enabled: true
Status: running PID:36003 for 11702s
NMS statistics database
Enabled: true
Status: running PID:27826 for 11699s
NMS data collection agent
Enabled: true
Status: running PID:35662 for 11703s
NMS CloudAgent v2
Enabled: true
Status: running PID:36960 for 11698s
NMS cloud agent
Enabled: true
Status: running PID:36385 for 11703s
NMS SDAVC server
Enabled: false
Status: not running
NMS SDAVC proxy
Enabled: true
Status: running PID:43510 for 264036s
vManage#

[bigevilbeard]

Pasted from another thread:

Not able to access GUI could be for several reasons.

Some of it includes:
* Waiting for the app-server to come up / up App-Server is the last process which comes up after all the processes came up.
* Verify if the all the processes came up via CLI request nms all status - will show the status of processes
* on newer images, it does take 10+ min or so for the GUI to be available [ex.: 20.6.1]

The following CCO document has some useful tips on what to check on vManage:
https://www.cisco.com/c/en/us/support/docs/routers/sd-wan/216015-quick-start-guide-data-collection-for.html