Follow

Troubleshooting Tips for Linux/UNIX

NOTE On October 11, 2016, BMC released Meter Version 4.4.1 which changed the name of the meter from boundary-meter to truesight-meter. This article reflects the change. If you are using a meter version prior to 4.4.1, then you will need to reference boundary-meter instead of truesight-meter in the operations discussed in this article.

Most of these operations require either root, sudo, or superuser to perform.

  • Check that the TrueSight Meter is running:
sudo /etc/init.d/truesight-meter status
sudo truesight-meter --dump-meter-info -I truesight-meter
  • Check connectivity to the TrueSight backend
sudo truesight-meter --status -I truesight-meter
  • Review TrueSight Meter built-in documentation
man truesight-meter
  • Add debug output:

Open /etc/truesight/meter.conf in text editor, locate "debug" parameter and increase debug level (0 by default, 1 to 2 for debugging), save the file and restart the meter (How do I start/stop/restart the TrueSight Pulse Meter?)

{
   "debug" : 2,
   ...

The meter sends log messages into system log file (syslog), can be seen using:

tail -n 500 -f /var/log/syslog | grep meter 
  • Run the meter from command line

First you should stop the Meter if it is already running, and run then it from the command line:

/usr/bin/truesight-meter -b /etc/truesight -I truesight-meter
  • Test the meter issues during boot time.

First command will clean boot log file, the second one restarts the system.

sudo cp /dev/null /var/log/boot.log
sudo reboot

After the restart, check Meter log messages:

grep meter /var/log/boot.log

  • Check that local time on your server is correct.
  • Check that the TrueSight repository points to deployment or staging. Staging usually has newer versions for beta testers and special cases.

On Ubuntu, Debian, etc:

cat /etc/apt/sources.list.d/truesight.list

On Centos, RHEL, etc:

cat /etc/yum.repos.d/truesight.repo

  • Check if the server has connectivity to TrueSight SaaS:
curl -X POST 'https://api.truesight.bmc.com/v1/meter/foo/registration'

The expected output (if basic connectivity is OK) should be similar to:

{
  "name": "Unauthorized",
  "code": "ERR_UNAUTHORIZED_ACCESS",
  "status": 401,
  "message": "There was a problem with your provided credentials for resource /v1/meter/foo/registration"
}
  • When attempting to start the meter, the meter fails to start with the following message:
Starting truesight-meter: truesight-meter unprovisioned, skipping

It's likely that the host's hostname is "localhost" which is not allowed by the meter.  To correct this, stop the meter, edit /etc/truesight/meter.conf to change the hostname parameter, save the file, and then start the meter.

Have more questions? Submit a request