5.4 Moab Viewpoint Issues

This topic details some common problems and general solutions for Moab Viewpoint.

In this topic:

• 5.4.1 General configuration issues
• 5.4.2 Only the Configuration Page is displayed in Viewpoint
• 5.4.3 Viewpoint does not report any of my jobs or nodes
• 5.4.4 viewpoint-query-helper plugin does not connect to the Insight MongoDB database
• 5.4.5 Job's processor count changes after submission

5.4.1 General configuration issues

The Viewpoint configuration file (/opt/viewpoint/etc/viewpoint.cfg) may include several environment variables used to configure a Viewpoint installation and troubleshoot Viewpoint operation issues. Viewpoint environment variables are described in the table below.

5.4.2 Only the Configuration Page is displayed in Viewpoint

A particular configuration problem causes Viewpoint to display only the Configuration Page with only the Viewpoint License tab (not the Moab License tab). The Viewpoint License tab includes links only to the Basic Configuration and Licensed Features pages as shown below.

Click to enlarge

This problem occurs when the Viewpoint admin user is the same as the auth.defaultUser.username in MWS.

To resolve this issue, do the following:

1. Change the admin user in /opt/viewpoint/etc/viewpoint.cfg.

   For example, if the admin username was set to moab-admin, which is also the name of the auth.defaultUser.username in MWS, change the admin username in /opt/viewpoint/etc/viewpoint.cfg (viewpoint-admin in the example shown below).

   [admin]
   username = viewpoint-admin
   password = pbkdf2_sha256$20000$ZHeToCJgrSUH$+xmzYdhpqZCJokxO9eGzyr2B6jrfCgLlBT+pBgMis4w=

2. Identify the entry for the previous admin user from the PostgreSQL database by executing the following commands as root.

   [root]# su - postgres
   [postgres]$ psql
   \c moab_viewpoint
   select * from auth2_user;

   The auth2_user table will be displayed, similar to the following.

    id | is_active | is_staff | is_superuser |          last_login           |    username
   ----+-----------+----------+--------------+-------------------------------+-----------------
     2 | t         | t        | f            | 2016-12-19 11:49:27.765855-05 | viewpoint-admin
     1 | t         | t        | f            | 2016-12-19 12:06:24.642922-05 | moab-admin
   (2 rows)
   

3. Delete the previous admin username from the table by executing the following command (substituting the previous admin username).

   delete from auth2_user where username = 'moab-admin';
   

5.4.3 Viewpoint does not report any of my jobs or nodes

There are multiple reasons why jobs and nodes might not show up in Viewpoint.

Verify the following:

1. Moab HPC Suite Setup

   Essentially, there are many communication points in our stack from the point that jobs get submitted to the point they get displayed in Viewpoint.

   Please take a look at the following diagram describing our data flow architecture:

   Click to enlarge

   The Moab Workload Manager will push data into Insight using a ZeroMQ message queue pipe.

   Then, Insight will parse that data and insert it into a MongoDB database.

   When Viewpoint needs to query information on jobs and nodes, it will communicate with Moab Web Services, which in turn will consume the data directly from the MongoDB database where Insight recorded Moab's events.

   Failure to configure the communication channels between all these components will result in Viewpoint not being able to display job or node information.

2. Hardware Specifications

   Another reason why Viewpoint might not be able to show job and node information is that you installed all Moab HPC components in a single machine that is too overloaded.

   See 1.1 Server Hardware Requirements for more information.

3. RPM Versions

   One other common problem customers can experience is that they install incompatible versions of our software components.

   Please make sure you are using the same major/minor version across all components (e.g. Moab Workload Manager 9.1, Moab Web Services 9.1, Insight 9.1, etc.).

5.4.4 viewpoint-query-helper plugin does not connect to the Insight MongoDB database

If the user name or the password for the Insight MongoDB database was entered incorrectly, the viewpoint-query-helper plugin will not be able to connect to the database. An error message is reported to the MWS Plugin Monitoring page.

For example:

Click to enlarge

To resolve this issue, do the following:

1. If you have not already done so:
   1. Log in as an administrator to your MWS instance.
   2. Select Plugins, and then select Plugin Monitoring. You should see a page similar to the example image displayed earlier in this section.
2. In the Disabled Plugins section, click on the link for the viewpoint-query-helper plugin.
3. When the Show Plugin page displays, click Edit.
4. Enter the correct connection information, and then click Update to save your changes (you are returned to the Show Plugin page).
5. Return to the Plugin Monitoring page and start the plugin using the green start button.

Alternatively, you can change the password of the mws_user in the insight database from the database host.

From the host on which the insight MongoDB database resides, do the following (substituting your password information):

$ mongo
> use insight;
> db.changeUserPassword("mws_user", "secret3");
> exit;

5.4.5 Job's processor count changes after submission

When migrating jobs to Torque from Viewpoint, Moab will translate the request into the equivalent qsub command with the proper -l procs syntax. In some situations, Torque's queues may have been configured with a default_resources.nodes setting that is incompatible with the job's -l procs request. In this situation, the default_resources.nodes setting should be removed from the queue or the job should be submitted to a queue that does not have a default_resources.nodes setting.

© 2017 Adaptive Computing