For bugs see the known problems list.
This list is not yet complete.
- Environment variables are not set correctly.
- The configuration file is not in your current directory.
- The configuration file is not correct.
You must be in the directory of your configuration file in order to run DOGMA.
Try running "checkSetup" from this directory as it can automatically diagnose many problems. If checkSetup fails to run than you may not have your PATH or CLASSPATH set correctly.
Note that the configuration file must currently be named "config.db".
- The complete and correct package name for the application was not specified.Symptom:
- The package for the application is not listed in the configuration file under "codeServerPackages".
- The code server (http server) for the package is not running or is not configured correctly.
First recheck the package and class name.
Then make sure the .class file is reachable from a code server.
Make sure the code server is specified correctly in the configuration file.
Make sure the package is listed under the correct code server or is a sub-package of one listed.
You may also check to make sure you can reach the .class file by trying to load it by hand using a browser.
For instance if the code server was http://myhost.foo.bar:8180/DOGMA/codebase/, the package name was dogma.examples.mpi, and the class name was SimpleMPI, then you could use your web browser to try to load
http://myhost.foo.bar:8180/DOGMA/codebase/dogma/examples/mpi/SimpleMPI.class
-Environment variables are not set correctly. See the installation instructions on expanding or setting environment variables.
- You are using a "cmd" instance which was started before the installation was.
You must use a new command prompt in order for environment variables to take effect.
- Environment variables have not been expanded.
One easy way to check this is to open a new command prompt and look at the value of a variable such as CLASSPATH. If you see an unexpanded variable such as JDK_HOME in the classpath then you must get the system to expand the variables. You may force the system to expand the variables by going into "System Properties", clicking on an unexpanded variable, clicking in the value field, and then clicking "set" (without altering the value). Then click "apply" or "close" to apply the changes. You may also logout or reboot in order to expand the variables.
Symptom:
Remote nodes won't start.
Possible Problem and Solution:
Make sure that the remote nodes source Dogma/setenvs
in their .cshrc file and that all of the variables there are set correctly.
You should first test that the remote nodes will launch manually by first
logging in to the remote node, changing into the Dogma/bin directory, and
running startNode. If that works then you may try the same command
via rsh. Finally, you may included the rsh command in your configuration
file. Note that DOGMA will parse the start commands. See the
configuration file documentation for more information.