1. User unable to login to Aria Operations for Networks (formerly vRealize Network Insight):
2. Upon checking further, the following services are showing as 'unhealthy' or 'not running' on the Platform:
ubuntu@platform1:~$ ./check-service-health.sh -d -p
ElasticSearch is running and healthy.
ElasticSearch statistics:
Uptime:26:21
HRegionServer is running and healthy.
Uptime:27:41
Kafka is running and healthy.
Kafka statistics:
Uptime:26:03
NodeManager is running and healthy.
Uptime:26:51
Problem: SaasListener javaservice is not running.
Restapilayer is running but not healthy.
Restapilayer statistics:
TSDB is running
TSDB statistics:
Uptime:00:01
DataNode is running and healthy.
Uptime:28:50
Problem: Launcher javaservice is not running.
VIPService is running and healthy.
VIPService statistics:
Uptime:23:48
Problem: DatabusGateway javaservice is not running.
Problem: FlinkContainer javaservice is not running.
HMaster is running and healthy.
Is Master:True
Uptime:28:17
QuorumPeerMain is running and healthy.
QuorumPeerMain statistics:
Uptime:30:14
JournalNode is running and healthy.
Uptime:29:34
NameNode is running and healthy.
HDFS is healthy.
"State" : "active",
IsMaster:True
Under replicated blocks: 0
Uptime:29:24
DFSZKFailoverController is running
Uptime:30:00
ResourceManager is running and healthy.
Uptime:27:35
Problem: Federation javaservice is not running.
Nginx is running and healthy.
Nginx statistics:
Uptime:30:40
ExpressJSApp is running
Uptime:01:04:12
NTPSEC is running and healthy.
Uptime:31:18
FoundationDB is running but not healthy.
FoundationDB statistics:
Uptime:30:12
3. In Platform1, running the following query fdbcli --exec="status json" returns the following error:
RecoveryStoppedTooManyOldGenerations
Aria Operations for Networks 6.13.0
Aria Operations for Networks 6.14.0
This is a known issue impacting VCF Operations for Networks (Formerly Aria Operations for Networks)
Workaround:
If you believe you have encountered this issue and are unable to upgrade, please open a support case with Broadcom Support and refer to this KB article. For more information, see Creating and managing Broadcom support cases.