Follow

Re-registering Collector After Adding Database Appliance

Product: Stratusphere FIT/UX

Product Version: 6.0+

Expires on: 365 days from publish date

Updated: November 15, 2019

 

Problem:

A Collector appliance needs to be added after the Database appliance in order for it to function properly.  If a Database is added after a Collector, the Collector does not automatically get updated with the new DB, so it will continue sending data to the Hub appliance.  However, there are some circumstances where it will be necessary to add the DB when a Collector is already registered with an existing Hub .  Namely,  the Database appliance was made available to AWS deployments in version 6.1.4, and one may already have collectors, which have been available since version 6.0.

Possible resolution:

After joining a Database to the Hub, any previously registered Collectors will have to be re-registered so that they pick up the new Database.

1. Log into the Administration section of Stratusphere and navigate to the Collector Administration tab.  Then check the Collector and hit the Re-register button.  Do this for each Collector besides the Stratusphere Hub.

 Reregister.png

2. The Collector will register itself with the hub, pick up the new DB and reboot.  Another way to verify that the Collector has the correct DB is to ssh into the Collector (as ec2-user for AWS, or friend/sspassword for on-prem deployments) and run:

sudo grep PGHOST /etc/tntdb.conf

This should output the IP of the database appliance.

pghost.PNG.jpg

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.