Versions Compared

Old Version 84

changes.mady.by.user Saurabh Patwardhan

Saved on

compared with

New Version 85

changes.mady.by.user Chris Mattmann

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The "oodt start" command should return quite quickly. This is normal. If, however, the http://localhost:8080/opsui link above is not functional on your system, one good place to start looking for probable cause is the "oodt.out" log file, which can be found (if you've been following the example above) in "oodt/logs/oodt.out"

Note(For OODT start/stop issues): 

...

 

Note
titleOODT Start and Stop Issues
While starting/stopping oodt if you get errors like "Is File/Workflow/Resource Manager still running? Start/Stop aborted." in logs/oodt.out:

1-Stop oodt using "oodt stop"

...

  1. oodt stop
  2. Remove any *.pid files (example:cas.filemgr.pid) from the run directory of File/Workflow/Resource Manager. This will make sure that the corresponding process has been stopped.

3- Start oodt using "oodt start"

...

  1. oodt start
  2. To check if all managers are running as expected, we can use the http://localhost:8080/opsui as stated above or simple try using these links in browser

...

...
    1. http://localhost:9000/      (for FileManager)
...
    1. http://localhost:9001/      (for WorkflowManager)
...
    1. http://localhost:9002/      (for ResourceManager)
 You should get this message for all these three links: "Method GET not implemented (try POST)" which means all those managers are running.
Note that you can also check if the managers are running as expected by visiting $OODT_HOME/pcs/scripts/ and by running
pcs_stat
 
Version Control
If you want to manage your OODT RADiX distribution with Subversion.
...