Moab Access Portal

1. End users cannot see nodes or their credentials

2. How to edit the notices page

3. Where do I install Moab Access Portal

4. Using SSL with tomcat

5. "java.awt.HeadlessException" error

6. ERROR: cannot migrate job to PBS - user 'root' does not exist on local system

7. How do I view the XML output Moab Access Portal uses to send commands to Moab Workload Manager?

8. How do I increase the Moab Access Portal Loglevel?

9. How do I change aspects of pages in Moab Access Portal?

10. My Web browser cannot find Moab Access Portal

11. When a job is executed from within Access Portal, why are the results placed into the users root directory and not the directory specified within Access Portal?

1. Problem:

End users cannot see nodes or their credentials

When I log into Moab Access Portal as root, I see all the nodes and I can see credentials and other items. But if I log in as an end user, I can see that the user's job is running, but zero nodes are displayed. Also, the user has "no credentials set". This goes for any user I log in with. I do not see all running jobs when I am logged in as an ADMIN1 level account either.

Solution:

1. You'll need to enable two configuration options:

The first issue is mentioned at http://www.clusterresources.com/products/map/docs/1.3initialconfig.shtml and has to do with the non-privileged access. By default, Moab does not allow any normal user to view node information or their credential information. To enable this capability, insert the following into moab.cfg:

ADMINCFG[4] Name=map SERVICES=mcredctl,mdiag,mjobctl USERS=ALL

Restart Moab Workload Manager by typing mschedctl -R, and then you should instantly see node and credential information in Access Portal (if there is some available).

To allow root (and other users) to view all jobs, you will need to edit the map.properties file and make sure that ALLOW-SYSTEM-VIEW=TRUE. You will then need to restart Access Portal. At this time, there is no way to differentiate between users on a more fine-grained level in Access Portal (e.g. root can see all jobs, but other users cannot). Even though users can see other's jobs, they cannot modify or cancel them.

2. Problem:

How do I edit the notices page in Moab Access Portal?

Solution:

1. Go to the servlet engine's webapps directory and look for a directory called map. If it exists, enter it and you should also see a directory called docs. Inside the docs directory is a file called notices.html. Anything in this file will be included on the notices page and can be edited.

If there is no map in your servlet engine's webapps directory, shutdown the servlet engine, and then unzip the file map.war found in the webapps directory. (Either jar -xf map.war or unzip map.war will work.) A new directory named map should now exist. If it does, you can safely remove the map.war file and start up your servlet engine. You should now be able to navigate to the map/docs/notices.html file.

3. Problem:

Where do I install Moab Access Portal

Do I need to install Moab Access Portal on the same machine as Moab Workload Manager?

Solution:

No, it can be installed on the head node or another node such as a Web server.

4. Problem:

Using SSL with tomcat

How can I use SSL via Tomcat and Apache?

Solution:

See the documentation located at http://www.clusterresources.com/products/map/docs/1.6tomcatinstall.shtml#ssl

5. Problem:

"java.awt.HeadlessException" error

After entering my username and password, I receive the error: "java.awt.HeadlessException". This happens during authentication.

Solution:

1. Make sure that in your map.properties file the following parameter is set:

The headless exception error points to a incorrectly configured environment variable, -DCONFIG-FILE. If you are starting Moab Access Portal with the map-star.sh script and have configured Access Portal to run with your servelt engine correctly then this variable is automatically applied.

• Run the Access Portal configuration again to make sure it is configured correctly with your servlet engine.

• Set the DCONFIG environment variable to the location of map.properties. An example for Tomcat is below:

export CATALINA_OPTS=-DCONFIG-FILE=/path/to/config/dir/map.properties

6. Problem:

ERROR: cannot migrate job to PBS - user 'root' does not exist on local system

When I submit a job using msub through Moab Workload Manager or submitting through Cluster Manager or Access Portal, I receive the error: "ERROR: cannot migrate job to PBS - user 'root' does not exist on local system."

Solution:

1. Moab does not allow job submissions from root. Switch to another user and submit the job again.

7. Problem:

How do I view the XML output Moab Access Portal uses to send commands to Moab Workload Manager?

Solution:

1. You will need to change a parameter in the log4jproperties.log file.

log4jproperties.log is located in /etc/ of the Access Portal, map, directory.

Open the file and find the lines log4j.logger.com.sshtoools= and log4j.logger.com.moab=.

Change both settings to debug.

Go to /map/etc/log to view the xml output after a job is submitted through Access Portal.

8. Problem:

How do I increase the Moab Access Portal Loglevel?

Solution:

1. The file that controls MAP's logging is located in the MAP etc directory and is named log4j.properties. It usually looks something like the below example:

log4j.rootLogger=INFO,ROLL
log4j.appender.ROLL=org.apache.log4j.RollingFileAppender
log4j.appender.ROLL.MaxFileSize=1000KB
log4j.appender.ROLL.MaxBackupIndex=1
log4j.appender.ROLL.layout=org.apache.log4j.PatternLayout
log4j.appender.ROLL.layout.ConversionPattern=%d{HH:mm:ss,SSS} [%t] %-5p
log4j.logger.com.sshtools=fatal
log4j.logger.com.moab=error

In order to activate "debug" logging, which aids in diagnostics of problems, we recommend changing the last line and adding the following two so the log file now looks like:

This information is valuable in troubleshooting problems. If you need to contact Cluster Resources for further assistance, please make these changes and send the error messages to them.

9. Problem:

How do I change aspects of pages in Moab Access Portal?

Solution:

1. See Problem #2.

10. Problem:

My Web browser cannot find Moab Access Portal when I go to http://[serverhost:port]/map

Solution:

1. Make sure your servlet engine is running.

2. Make sure you can access your Servlet engine's test page.

3. Rerun the Moab Access Portal setup and make sure that the correct information is input into each step.

11. Problem:

When a job is executed from within Access Portal, why are the results placed into the user's home directory and not the directory specified within Access Portal?

Solution:

1. The "Execution Directory" area in Moab Access Portal is sent to the resource manager. Each resource manager handles the execution directory slightly different. TORQUE uses this directory to submit the job. (See http://www.clusterresources.com/torquedocs20/2.1jobsubmission.shtml)

A job, when running under TORQUE, will always execute in the user's home directory, but there is a way to get around this. In the PBS script itself, before running any commands, always have the user put in 'cd $PBS_O_WORKDIR" which will change to the submission directory and provide the desired functionality.