Here is How To Rackspace Cloud Monitoring Working After API Reset on Ubuntu or Debian Cloud Server Instance. For various reasons we reset API. Practically, it is better to reset the API periodically. After you reset the API key from Rackspace Cloud Control panel, Cloud Monitoring and Cloud Intelligence will not work properly.
Make Rackspace Cloud Monitoring Working After API Key Reset : Basics
To make Rackspace Cloud Monitoring working after API Key reset, only few commands are needed. But, we think, it is better to check the SE-Linux-Distribution and Nova-Agent‘s condition. Without the API key, not only monitoring, other keystone based services, including cloud back backup, server image backup might get affected. The server never take images when it is failing! The service get paused.
Make Rackspace Cloud Monitoring Working After API Key Reset : 3 Steps
Step 1 is checking the sequence of SE-Linux-Distribution and Nova-Agent. Normally, it should be fine. It could happen, for an unrelated cause, the sequence changed. The check is for that purpose, has no direct relationship with the main work. Stop the service :
sudo service rackspace-monitoring-agent stop
Step 2 is again running the setup :
sudo service rackspace-monitoring-agent --setup
# select the existing option, possibly it will be 1
Fill the username (all lower case) and API key.
Step 3 is to start the service and reboot :
sudo service rackspace-monitoring-agent start
# wait till it starts
After reboot, you’ll get the Cloud Monitoring Agent working. Run the update, upgrade commands :
apt-get update -y && apt-get upgrade
# do carefully
This is, exactly the reverse of what we did to install Rackspace Monitoring Agent on Cloud Server. Basically, we did an unexpected function by changing the API key. We need not to remove the Rackspace Monitoring Agent itself, because it is fully functional, only the API key is not matching. API key was required before as it was a paid service. Without the API, some function basically works.