Hello everyone.
I have got the same error and I am not able to access the vManage's GUI interface. So, I guess the neo4j database corrupted would be the cause.
vManage# request nms configuration-db diagnostics
NMS configuration database
Checking cluster connectivity...
Pinging server 0 on localhost:7687,7474...
Starting Nping 0.7.80 ( https://nmap.org/nping ) at 2023-08-11 20:21 UTC
SENT (0.0015s) Starting TCP Handshake > localhost:7474 (127.0.0.1:7474)
RCVD (0.0015s) Handshake with localhost:7474 (127.0.0.1:7474) completed
SENT (1.0035s) Starting TCP Handshake > localhost:7687 (127.0.0.1:7687)
RCVD (1.0035s) Handshake with localhost:7687 (127.0.0.1:7687) completed
SENT (2.0053s) Starting TCP Handshake > localhost:7474 (127.0.0.1:7474)
RCVD (2.0053s) Handshake with localhost:7474 (127.0.0.1:7474) completed
SENT (3.0065s) Starting TCP Handshake > localhost:7687 (127.0.0.1:7687)
RCVD (3.0065s) Handshake with localhost:7687 (127.0.0.1:7687) completed
SENT (4.0076s) Starting TCP Handshake > localhost:7474 (127.0.0.1:7474)
RCVD (4.0076s) Handshake with localhost:7474 (127.0.0.1:7474) completed
SENT (5.0085s) Starting TCP Handshake > localhost:7687 (127.0.0.1:7687)
RCVD (5.0085s) Handshake with localhost:7687 (127.0.0.1:7687) completed
Max rtt: 0.018ms | Min rtt: 0.007ms | Avg rtt: 0.008ms
TCP connection attempts: 6 | Successful connections: 6 | Failed: 0 (0.00%)
Nping done: 1 IP address pinged in 5.01 seconds
Connecting to localhost...
Database 'neo4j' is unavailable.
Completed
Disk space used by configuration-db
738M .
I will be very thankful if something could help me on that,
See you,
