Opsview - You have exceeded the maximum number of sessions you are permitted

Opsview limits the number of concurrent login sessions. The default maximum number of concurrent login sessions is 10 though this limit can be changed.

If you see errors warning that you have exceeded the maximum number of sessions permitted, you should first determine the source of the login sessions:

• Do you have any scripts that spawn new login sessions to query the API?
• Do you have lots of users who log in to Opsview at the same time?

Solution: Change API authentication method in your scripts

If you have scripts that query the API and spawn new login sessions each time, you should update your scripts so that they use authentication tokens instead. Please read our documentation on authenticating with the API to learn how to use authentication tokens.

Solution: Change the session manager concurrent login limit

If you need to change the concurrent login session limit, you can do so by updating your user_vars.yml file and then running the session-manager-install.yml playbook.

1. {{snippet.log_in_to_deployment_host_as_root}}
2. Open your user_vars.yml file (/opt/opsview/deploy/etc/user_vars.yml) in your preferred text editor. {{snippet.yml_editing}}
3. Locate and update the variable max_sessions in the opsview_session_manager_config_overrides section. Define this variable and section if they do not exist already.

opsview_session_manager_config_overrides:
  max_sessions: <number of sessions>

Replace <number of sessions> with the new concurrent login session limit. This number must be a positive integer. 4. Run the session-manager-install.yml playbook with opsview-deploy:

/opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/session-manager-install.yml