new install of vmanage login but redirect back to login

[JacobKupres8728]

I've re-install vManage a few times. I've configured interface and can reach the web interface. When I login to the web interface with the default creds I get redirect back to the login screen. I've created a new user to try to get another any AAA issues but I still get the same thing. I've tried about 4 different versions of code using the qcow2 image to try and get around this. I don't understand how to troubleshoot this issue. Login would inform that the username and password is not good to allow access but it seems successful login would redirect to the login page. 

[maxnpj]

Which code version are you running? If you are in the 20. train you might be running into CSCvx87163 (X-Forwarded-For header is passed through to local auth, leading to session creation errors). 

For me, this showed up as an inability to authenticate to the GUI but I could SSH into vManage using the same creds. 

[JacobKupres8728]

Most of which are 20.x.x.x, i've 18.x.x.x as well with the same result. 

[Deepak Kumar]

Hello, 

When did you restarted or powered on the Vmanage? If you did not give enough resources, then it will take more time to start all services. You will not get GUI access until all required services status will not start. 

Check with the "request nms application-server status" command. 

Cisco SD-WAN Command Reference - Operational Commands [Cisco SD-WAN] - Cisco

Also, check for buggy software as CSCvo44464

[JacobKupres8728]

vmanage it self is give 4 core and 32GB of ram. I've also tried 8 cores as well. The issue is that it seems allow the login but redirect back to the login immediately. It does not act slow. 

[JacobKupres8728]

Hello Deepak,

Taking a further look here. This is occurring on a fresh installation of the vManage 20.5.1 I don't think any storage volumes are being filled to capacity. 

vmanage# request nms all status
NMS server proxy
Enabled: true
Status: running PID:15356 for 1436s
NMS application server
Enabled: true
Status: running PID:22569 for 1285s
NMS configuration database
Enabled: true
Status: running PID:15292 for 1437s
NMS coordination server
Enabled: true
Status: running PID:19954
NMS messaging server
Enabled: true
Status: running PID:22734
NMS statistics database
Enabled: true
Status: running PID:22165
NMS data collection agent
Enabled: true
Status: running PID:31691 for 1089s
NMS cloud agent
Enabled: true
Status: running PID:1132 for 1549s
NMS container manager
Enabled: true
Status: running PID:15255 for 1453s
NMS SDAVC server
Enabled: false
Status: not running
NMS SDAVC proxy
Enabled: true
Status: running PID:1237 for 1549s

vmanage# show system status

Viptela (tm) vmanage Operating System Software
Copyright (c) 2013-2021 by Viptela, Inc.
Controller Compatibility:
Version: 20.5.1
Build: 34

System logging to host is disabled
System logging to disk is enabled

System state: GREEN. All daemons up
System FIPS state: Enabled

Last reboot: Initiated by user.
CPU-reported reboot: Not Applicable
Boot loader version: Not applicable
System uptime: 0 days 00 hrs 27 min 21 sec
Current time: Sat Jul 24 15:28:36 UTC 2021

Load average: 1 minute: 0.42, 5 minutes: 0.43, 15 minutes: 0.77
Processes: 1359 total
CPU allocation: 4 total
CPU states: 5.13% user, 1.41% system, 93.46% idle
Memory usage: 24507384K total, 10466072K used, 8214052K free
513136K buffers, 5314124K cache

Disk usage: Filesystem Size Used Avail Use % Mounted on
/dev/root 15230M 1523M 12871M 11% /
vManage storage usage: Filesystem Size Used Avail Use% Mounted on
/dev/vdb 100281M 4185M 90975M 4% /opt/data

Personality: vmanage
Model name: vmanage
Services: None
vManaged: false
Commit pending: false
Configuration template: None
Chassis serial number: None

vmanage#

[JacobKupres8728]

I've noticed this error on start up. vmanage login: python3: can't open file '/etc/sv/cloudagent/httpProxy/proxy.py': [Errno 2] No such file or directory

Starting services...
Deprecated /proc/acpi/event was not found. Trying netlink and the input layer...
input layer /dev/input/event0 (Power Button) opened successfully, fd 3
input layer /dev/input/event1 (AT Translated Set 2 keyboard) opened successfully, fd 4
inotify fd: 5
inotify wd: 1
netlink opened successfully
acpid: starting up with netlink and the input layer
acpid: starting up with netlink and the input layer
parsing conf file /etc/acpi/events/powerbtn
acpid: 1 rule loaded
acpid: 1 rule loaded
acpid: waiting for events: event logging is off
acpid: waiting for events: event logging is off
warning: sysmgr: can't open supervise/ok: No such file or directory

viptela 20.5.1

vmanage login: python3: can't open file '/etc/sv/cloudagent/httpProxy/proxy.py': [Errno 2] No such file or directory

viptela 20.5.1

vmanage login:

[Mark_Baker]

I am running into this issue as well.  I had previously been able to log in fine, however, after taking a month or so away from it I am now seeing these same symptoms you are seeing.  Was anything ever determined as a solution?

[JacobKupres8728]

No unfortunately. 

[derek.tsai@deakin.edu.au]

I got the similar issue and resolved after setting the correct timezone and ntp server. 

[phyllpvs]

Hi,

I Had this issue during my labs, after upgrading to 20.6.3
Even with the correct NTP/Timezone settings.

This is what I do to recover the management-access (GUI)
1- SSH to the vManage - change the VPN-0 to a temporary IP address.
2- Login in again into the GUI using the new ipaddress.
3- SSH to the vManage - change the VPN-0 to the original IP address.
4- Apply the command - "request nms application-server restart" via SSH.
5- Wait 10 min
6- Try login again via GUI.

This worked for me

Also, consider doing a backup to avoid losing your templates..
request nms configuration-db backup path /opt/data/backup/"backupname"

Regards,
Using vManage 20.6.3 (qcow).