Changes between Version 61 and Version 62 of instructions

Show
Ignore:
Timestamp:
06/28/10 17:49:21 (9 years ago)
Author:
chase (IP: 152.54.6.229)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • instructions

    v61 v62  
    132132'''NOTE:''' as of Bella 2.0 container administrator credentials are located in [https://geni-orca.renci.org/orca-doc/current/guides/container-configuration/properties.html container.properties]. 
    133133 
    134 5. If the app did not come up as expected, then the container (ORCA_HOME) and actors (ORCA_LOCAL) are likely misconfigured.  There is no easy way to debug configuration errors.  Check the container logs in tomcat/logs/orca*.log.   It is also possible to load config.xml directives into the running web GUI, under the admin tab, which may have better error reporting.  Config processing is not atomic or idempotent: if config processing fails, some directives may have completed successfully. 
     1345. If the app did not come up as expected, then the container (ORCA_HOME) and actors (ORCA_LOCAL) are likely misconfigured.  There is no easy way to debug configuration errors.  Check the container logs in tomcat/logs/orca*.log.   You can add more information to these logs by editing the log4j properties in ORCA_HOME/config/container.properties, e.g., to add "%C %M %L" to the ConversionPattern to print the class, method, and line number for each log message.  It is also possible to load config.xml directives into the running web GUI, under the admin tab, which gives additional error reporting through the GUI.  Config processing is not atomic or idempotent: if config processing fails, some directives may have completed successfully. 
     135 
     136'''Feature''': claim processing for exported tickets (advertisements/delegations) must be done manually after the container stands up, since it requires inter-actor communication.  Go to the broker tab, create an inventory slice, and claim the delegation, using the GUID for the exported ticket, which is visible under the site tab (view exported tickets). 
    135137 
    136138'''NOTE:''' if you restart tomcat, it will recover your previous container state.  If you redeploy, or undeploy and redeploy, it will reinitialize the container to its fresh state, and delete state about existing slices and reservations from the database.