Abdulraheman Trusted Contributor.
Trusted Contributor.
704 views

CO Dashboard Showing as 0 Hosts 0 VMs

Hi,

Today we when we opened the dashboard it is showing 0 Hosts 0 VMs 0 Datastore.

When checked on status of datasource it is able to collect data.

Tags (1)
0 Likes
4 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: CO Dashboard Showing as 0 Hosts 0 VMs

Hello,

 

The most common reason for this problem is that process pvcd and/or ovtomcatB are disconnected from the database. This can be due to the database being down, or the database having been (re)started while pvcd/ovtomcatB were running.

To check that database is responsive, try:

# /opt/OV/bin/pvsql -l

This will give you the name of the database instance if it is currently up. If the database is not responsive, you should restart all processes:

# /opt/OV/bin/pv stop
# /opt/OV/bin/pv start

To check if pvcd and ovtomcatB are connected to the database, run:

# netstat -nap | grep 5433

This assumes that your vertica DB uses the default port 5433. It should list the processes vertica, pvcd and java. If vertica is present but pvcd and/or java is missing, you should run:

# /opt/OV/bin/ovc -start

If you find that vertica does not start, or pvcd/ovtomcatB are connected to vertica, and still the UI does not refresh, it could mean that your filesystem /var/opt/OV is running out of space or the swap is filling up. If a complete restart does not help, then you would need to perform some cleanup of your file systems.

Note that PVTK 2.0 can help with all the above tasks ( https://softwaresupport.softwaregrp.com/km/KM02600652 ). Once installed, run the wizard with:

# /opt/OV/contrib/PVTK/pvtk -wizard

Select option "3. Show an operational status report". This will give you the above information and much more.

Select "8. Recover space on file systems" to help identify files that can be deleted to clean up your filesystems.

And to restart all CO processes with additional validation steps, use:

# /opt/OV/contrib/PVTK/pvsupport -restart

 

Thanks,

Thierry.

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Abdulraheman Trusted Contributor.
Trusted Contributor.

Re: CO Dashboard Showing as 0 Hosts 0 VMs

HI Thierry

I have tried below commands but still it is showing zero hosts and VM on dashboard.

Also the DB is not getting up autmatically. I have to forcefully make it up with below command and then i restarted other services of java.

 ./admintools -t start_db -d pv -U

also in "Settings" --> collection information tab, the data logged time showing below.

Data Logged Till   :   12/20/17 16:55"

 

But the data is getting collected properly. and in status of data sources tab, the last collection time shows properly.

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: CO Dashboard Showing as 0 Hosts 0 VMs

Hello Abdulraheman,

Difficult to figure out exactly what is happening without having access to the system, but it still looks like pvcd is not connected to the database.

Have you installed PVTK 2.0 as suggested in previous response? I have recently submitted a paper that explains how to interpret the Operational Status report (see https://softwaresupport.softwaregrp.com/km/KM03049997). It explains how to isolate problems like this one and some possible causes. But generally it boils down to starting the processes in the proper order and making sure that there is at least a few GB free space on /var/opt/OV/databases (yes, the DB will reject transactions well before the file system is 100% full).

Note also, regarding your DB startup problem, you can try "/opt/OV/contrib/PVTK/pvsupport -restart" since it contains additional logic compared to the regular commands, including a validation of the DB startup before starting the next processes.

If nothing helps, you may want to open a support case.

Thanks,

Thierry.

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
0 Likes
Abdulraheman Trusted Contributor.
Trusted Contributor.

Re: CO Dashboard Showing as 0 Hosts 0 VMs

HI Thierry

While starting the database through below command, DB not getting started

/opt/OV/contrib/PVTK/pvsupport -restart

giving below error

pvcd is stopped
VIdaemon is stopped
Running '/usr/bin/pv stop'
pvcd is already stopped
VIdaemon is already stopped
Stopping application server
Stopping P&O Analysis
Stopping Custom Group Update
Stopping Syspulse Data Logging
Stopping Reconciliation
Stopping the database
Confirming that the database is stopped
vertica process is not running
pvcd is stopped
VIdaemon is stopped
Running '/opt/OV/bin/ovc -start CORE'
Running smart start of the database
Info: no password specified, using none
Starting nodes:
v_pv_node0001 (127.0.0.1)
Starting Vertica on all nodes. Please wait, databases with large catalog may take a while to initialize.
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Error starting database, no nodes are up
Database pv did not start successfully
LastEpoch|210933
Last Good Epoch = 210933
Info: no password specified, using none
Invalid value for last good epoch: '210933'
Epoch number must be between 211138 and 210933 inclusive
WARNING: The database startup did not complete yet
Info: no password specified, using none
Starting nodes:
v_pv_node0001 (127.0.0.1)
Starting Vertica on all nodes. Please wait, databases with large catalog may take a while to initialize.
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Error starting database, no nodes are up
Database pv did not start successfully
LastEpoch|210933
Last Good Epoch = 210933
Info: no password specified, using none
Invalid value for last good epoch: '210933'
Epoch number must be between 211138 and 210933 inclusive
WARNING: The database startup did not complete yet
Info: no password specified, using none
Starting nodes:
v_pv_node0001 (127.0.0.1)
Starting Vertica on all nodes. Please wait, databases with large catalog may take a while to initialize.
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Error starting database, no nodes are up
Database pv did not start successfully
LastEpoch|210933
Last Good Epoch = 210933
Info: no password specified, using none
Invalid value for last good epoch: '210933'
Epoch number must be between 211138 and 210933 inclusive
WARNING: The database startup did not complete yet
Info: no password specified, using none
Starting nodes:
v_pv_node0001 (127.0.0.1)
Starting Vertica on all nodes. Please wait, databases with large catalog may take a while to initialize.
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Error starting database, no nodes are up
Database pv did not start successfully
LastEpoch|210933
Last Good Epoch = 210933
Info: no password specified, using none
Invalid value for last good epoch: '210933'
Epoch number must be between 211138 and 210933 inclusive
WARNING: The database startup did not complete yet
Info: no password specified, using none
Starting nodes:
v_pv_node0001 (127.0.0.1)
Starting Vertica on all nodes. Please wait, databases with large catalog may take a while to initialize.
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Node Status: v_pv_node0001: (DOWN)
Error starting database, no nodes are up
Database pv did not start successfully
LastEpoch|210933
Last Good Epoch = 210933
Info: no password specified, using none
Invalid value for last good epoch: '210933'
Epoch number must be between 211138 and 210933 inclusive
WARNING: The database startup did not complete yet
WARNING: Could not validate database startup and responsiveness
Running '/usr/bin/pv start'
Starting the database
db start status is 1
Error occurred in starting database. Please start database and try again.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.