Articles in this section

See more
Self help
Troubleshooting
["Troubleshooting"]

Opsview - METRIC UNKNOWN - RegistryError ... Insufficient credentials

Avatar
ITRS Support
  • Updated
Follow

Symptoms

  • The following error appears repeatedly in `/var/log/opsview/opsview.log`: 
    METRIC UNKNOWN - RegistryError<status_code=401, error_code=110, index=0, message='The request requires user authentication', raw_message=bytearray(b'{"errorCode":110,"message":"The request requires user authentication","cause":"Insufficient credentials","index":0}
    ')>
  • You occasionally see the error `Web exception: Please refer to the system log for more details or contact your System Administrator` in the UI

    AND/OR
  • The registry password within the orchestrator.yaml is being reset.  

Cause: Incorrect registry password

Known issue: OP-42928

The setup-monitoring.yml playbook sets the registry password in the file relevant file to the default value of opsview despite this not necessarily being the correct registry password.

 

/opt/opsview/monitoringscripts/etc/plugins/self-monitoring/orchestrator.yaml 

 

Solution

------------------------------
Version 6.8.7 and before

Update the password in /opt/opsview/monitoringscripts/etc/plugins/self-monitoring/orchestrator.yaml with the correct password.

Nonpersistent changes

The following changes may not persist across runs of opsview-deploy. You may need to re-apply these changes each time you run opsview-deploy.

  1. Log in to the orchestrator as root.
  2. Obtain the correct registry password using awk:
awk '/opsview_registry_password/ {print $2}' /opt/opsview/deploy/etc/user_secrets.yml
  1. Open the file /opt/opsview/monitoringscripts/etc/plugins/self-monitoring/orchestrator.yaml on your orchestrator with your preferred text editor.
  2. Replace the password in the registry section with the password you obtained in step 2. For example,
  registry:
    host: 127.0.0.1
    password: opsview
    port: '12379'
    provider: etcd
    user: opsview

is changed to

  registry:
    host: 127.0.0.1
    password: <correct registry password>
    port: '12379'
    provider: etcd
    user: opsview

 

 

Version 6.8.8 and afterwards

The same procedure as "6.8.7 and before", but with a new file location to be updated related to step 3.

- File to update:

/opt/opsview/monitoringscripts/etc/plugins/self-monitoring/orchestrator.yaml


For version 6.9.0 you may need to do the below:
as an apply change reverts the changes when done on the above file

sed -i 's/password: opsview/password: '`cat /opt/opsview/deploy/etc/user_secrets.yml | grep opsview_registry_password | awk '{print $2}'`'/g' /opt/opsview/monitoringscripts/builtin/etc/plugins/self-monitoring/orchestrator.yaml

 

Important Requirement: 

- Please now Apply Changes to push out the change to the relevant file.

 

 

If you have any issues

  • Please contact our team via the chat service box available on any of our websites or via email to support@itrsgroup.com
    mceclip0.pngmceclip1.png

Make sure you provide us with:

  • ANY LOG FILE OR DIAGNOSTIC DATA
  • ANY SCREENSHOT
  • ANY VENDOR/VERSION etc

Related articles

Comments

0 comments

Please sign in to leave a comment.