Hi community, another post relating to issues bringing up vmanage in CML2. after waiting overnight, I now see some services running, but this error with bringing top the config database seems to be causing issues with a number of other services. There was a bug in v19 that is apparently fixed in 20.x (I'm running 20.13), and I can't see any other pointers to a fix. Any clues out there? Rewards for helpful hints!
neo4j log shows this error:
2024-08-01 11:24:50.452+0000 INFO ======== Neo4j 4.4.19 ========
java.lang.OutOfMemoryError: Metaspace
Dumping heap to /opt/data/dump/configuration-db-oom-1722511476.hprof ...
Heap dump file created [73415655 bytes in 0.854 secs]
Terminating due to java.lang.OutOfMemoryError: Metaspace
Thu Aug 1 11:25:33 UTC 2024 ###################################################
######################
request nms all diagnostics shows:
NMS configuration database
Checking cluster connectivity...
Pinging server 0 on localhost:7687,7474...
Starting Nping 0.7.80 ( https://nmap.org/nping ) at 2024-08-02 17:56 AEST
SENT (0.0038s) Starting TCP Handshake > localhost:7474 (127.0.0.1:7474)
RCVD (0.0039s) Possible TCP RST received from 127.0.0.1:7474 --> Connection refused
SENT (1.0054s) Starting TCP Handshake > localhost:7687 (127.0.0.1:7687)
RCVD (1.0055s) Possible TCP RST received from 127.0.0.1:7687 --> Connection refused
SENT (2.0071s) Starting TCP Handshake > localhost:7474 (127.0.0.1:7474)
RCVD (2.0073s) Possible TCP RST received from 127.0.0.1:7474 --> Connection refused
SENT (3.0085s) Starting TCP Handshake > localhost:7687 (127.0.0.1:7687)
RCVD (3.0085s) Possible TCP RST received from 127.0.0.1:7687 --> Connection refused
SENT (4.0102s) Starting TCP Handshake > localhost:7474 (127.0.0.1:7474)
RCVD (4.0102s) Possible TCP RST received from 127.0.0.1:7474 --> Connection refused
SENT (5.0119s) Starting TCP Handshake > localhost:7687 (127.0.0.1:7687)
RCVD (5.0119s) Possible TCP RST received from 127.0.0.1:7687 --> Connection refused
Max rtt: N/A | Min rtt: N/A | Avg rtt: N/A
TCP connection attempts: 6 | Successful connections: 0 | Failed: 6 (100.00%)
Nping done: 1 IP address pinged in 5.01 seconds
Connecting to localhost...
Unable to connect to localhost:7687, ensure the database is running and that there is a working network connection to it.
Completed
Connecting to localhost...
Displaying the Neo4j Cluster Status
Unable to connect to localhost:7687, ensure the database is running and that there is a working network connection to it.
Completed
Total disk space used by configuration-db:
/usr/bin/check_neo4j: line 141: cd: /opt/data/neo4j/databases/neo4j/: No such file or directory
20K .
Detailed disk space usage of configuration-db:
du: cannot access '*': No such file or directory
