Sun Grid Engine Information Center
Accounting and Reporting Console (ARCo)
Index

ARCo Troubleshooting

Problem: Reporting module installation on Red Hat Enterprise Linux

On certain versions of RHEL, while using SJWC 3.0.x or 3.1.x, you might see following error when during the reporting module installation:

Registering the SGE reporting module in the Sun Java Web Console
----------------------------------------------------------------
Must have administration privileges to execute this command.
Must have administration privileges to execute this command.
Must have administration privileges to execute this command.
Must have administration privileges to execute this command.
Creating the TOC file ... OK 

If you run manually the command smcwebserver start, you might see this error:

Starting Sun Java(TM) Web Console Version 3.0.2 ...
Exception while starting container instance console: An exception was thrown while executing 
/var/opt/webconsole/domains/console/conf/wcstart nobody 

These issues are related to the Sun Java Web Console.

Solution: Follow these steps:

The unsuccessful reporting installation has to be run prior to performing these steps.

• Execute these two commands:

  chmod +x /var/opt/webconsole/domains/console/conf/wcstart
  chmod +x /var/opt/webconsole/domains/console/conf/wcstop 
  

• Manually edit the /etc/opt/webconsole/console/service.properties file and add the following properties (replace the paths with fully qualified names):

  arco_app_dir=$SGE_ROOT/$SGE_CELL/arco/reporting
  arco_logging_level=INFO
  arco_config_file=$SGE_ROOT/$SGE_CELL/arco/reporting/config.xml 
  

• Create file reporting.reg in /etc/opt/webconsole/console/prereg/com.sun.grid.arco_6.2u3
  (this is a regnot file, which is normally created during deploy).
• Add the following information to the regnot file, which you had created in the previous step (replace paths with fully qualified names):

  system=false
  debug=0
  context=reporting
  type=webapp
  location=$SGE_ROOT/$SGE_CELL/arco/reporting 
  

• As a root user, restart the smcwebserver

  smcwebserver restart
  

After this ARCo should function correctly. However, you will still experience the 'Must have administration privileges to execute this command' while executing the wcadmin command.

Problem – No application is registered with this Sun Java ^TM Web Console or you have no rights to use any applications that are registered

The above error can happen on some Linux platforms, while using SJWC 3.0.x, if your $JAVA_HOME is not set or is set to a version of Java that is less than 1.5. Another indication of this problem is the absence of the following files: $SGE_ROOT/$SGE_CELL/arco/reporting/WEB-INF/tld and $SGE_ROOT/$SGE_CELL/arco/reporting/WEB-INF/lib/registrationservlet.jar.

Solution: Follow these steps:

1. Set your $JAVA_HOME variable to at least version 1.5 of the Java software.
2. Reinstall the reporting module.

Problem – SEVERE: SQL error: ERROR: permission denied for tablespace pg_default

The above SQL error is shown during installation of dbwriter.

Solution – You must always specify the tablespace, unless you are using MySQL. For PostgreSQL, the default tablespace is pg_default. For Oracle, the default is typically USERS.

The arco_write user must be granted the CREATE privilege on this tablespace. If the arco_write user does not have the sufficient privileges the above error message appears.

In database console as a superuser issue a command and then repeat the installation:

GRANT CREATE ON TABLESPACE pg_default to arco_write;

Problem – SEVERE: SQL error: Column 'ju_start_time' in field list is ambiguous

The above error can happen on some minor release versions of MySQL server, namely 5.0.26 or 5.0.27, where MySQL considers, some more complicated queries as syntactically incorrect. Newer versions of MySQL server handle them correctly.

• If you are doing a fresh ARCo installation and not an upgrade, you can safely edit the $SGE_ROOT/dbwriter/database/mysql/dbdefinition.xml file.
  Remove everything contained between the <version id="6" name="6.1u3"> </version> tags, except the last item. So, the part should look like this:

<version id="6" name="6.1u3">
<item>
        <description>Update version table </description>
        <sql>
           INSERT INTO sge_version (v_id, v_version, v_time)
           VALUES(6, '6.1u3', current_timestamp)
        </sql>
     </item>
</version>

• If you are upgrading, upgrade your MySQL Server to a higher version, before proceeding with dbwriter installation.

Problem – SEVERE: SQL error: ORA-01031: insufficient privileges

The above error may be caused during the installation of dbwriter, while the synonyms are being created. Because arco_read is the user who uses the synonyms, in ARCo versions > 6.1u4 the synonyms are being created by user arco_read, in the schema of user arco_read. Thus, the user arco_read needs to be granted the privilege to create synonyms. The ARCo users should be granted the following set of privileges:

GRANT CREATE TABLE, CREATE VIEW, CREATE SESSION TO "ARCO_WRITE";
GRANT CREATE SYNONYM, CREATE SESSION TO "ARCO_READ";

Problem – SEVERE: SQL error: ORA-01749: you may not GRANT/REVOKE privileges to/from yourself

The above SQL error is shown during installation of dbwriter.

Solution: During the installation, after the connection test and database version check, you are prompted to enter the name of the user which has a restricted access to the database arco_read. The ARCo web application connects to the database using the user arco_read, and because this user is not the owner of the database objects it needs to be granted SELECT privilege on those objects. On Oracle synonyms are also created in the schema of the arco_read user and thus password for this user is also needed.

If you have entered arco_write instead of the arco_read user in the prompt below, you would see the errors above. Repeat installation and provide the correct user name.

The ARCo web application connects to the database
with a user which has restricted access. 
The name of this database user is needed to grant
him access to the sge tables. 
This user will create the synonyms for the ARCo
tables and views, so the user's password is needed.

Enter the name of this database user [] >> ARCO_READ

Enter the password of the database user >>
Retype the password >> 

Note On PostgreSQL or MySQL, you will not see this error during installation of dbwriter but you will not be able to run any queries from the ARCo web application, because the arco_read user has not been granted the SELECT privileges on the database objects.

Problem – SEVERE: SQL error: ORA-00955: name is already used by an existing object

The above SQL error is shown during installation of dbwriter.

Solution: Same as in the error above.

Problem – The table or view dropdown menu of a simple query definition does not contain any entry but the tables are defined in the database.

Solution: The problem normally occurs when using Oracle as the database server. During the installation of the reporting module, wrong database schema name has been specified. For Oracle, the database schema name is equal to the name of the database user, which is used by dbwriter (the default name is arco_write). For Postgres, the database schema is by default public, or if you have configured separate schemas, it is equal to the name of the database user, which is used by dbwriter.

Problem – Connection refused.

Solution: The smcwebserver might be down. Start or restart the smcwebserver.

Problem – The list of queries or the list of results is empty.

Solution: The cause can be any of the following:

• No queries or results are available in the query /var/spool/arco/queries, results directory /var/spool/arco/results respectively.
• Queries in the XML files are syntactically incorrect. Check the log file /var/log/webconsole/console/console_debug_log for error messages from the XML parser.
• User noaccess has no read or write permissions on the query or results directory.

Problem – The list of available database tables is empty.

Solution: The cause can be any of the following:

• The database is down. Start or restart the database.
• No more database connections are available. Increase the number of allowable connections to the database.
• An error exists in the configuration file of the application. Check the configuration for wrong database users, wrong user passwords, or wrong type of database, and then restart the application.

Problem – The list of selectable fields is empty.

Solution: No table is selected. Select a table from the list.

h4. Problem – The list of filters is empty.

Solution: No fields are selected. Define at least one field.

Problem – The sort list is empty.

Solution: No fields are selected. Define at least one field.

Problem – A defined filter is not used.

Solution: The filter may be inactive. Modify the unused filter and make it active.

Problem – The late binding in the advanced query is ignored but the execution runs into an error.

Solution: The late binding macro has a syntactical error. The syntax for the late binding in advanced query is:

   LATEBINDING { <column>;<operator>;<default value> }

   <column>    name if the latebinding
   <operator>  a SQL operator (e.g. = < > in .. )
   <value>     default value (e.g. 'localhost' )

Example:

select * from sge_host where LATEBINDING {h_hostname; like; a%}
select * from sge_host where LATEBINDING {h_hostname; in; ('localhost', 'foo.bar')}

Problem – The breadcrumb is used to move back but the login screen is shown.

Solution: The session has timed out. Log in again, or raise the session timeout value for the Sun Java Web Console (SJWC). To increase the session timeout value to 60 minutes, as a superuser, on the host where the (SJWC) is installed, issue this command:

# wcadmin add -p -a reporting session.timeout.value=60

Problem – The view configuration is defined but the default configuration is shown.

Solution: The defined view configuration is not set to be visible. Open the view configuration and define the view configuration to be used.

Problem – The view configuration is defined but the last configuration is shown.

Solution: The defined view configuration is not set to be visible. Open the view configuration and define the view configuration to be used.

Problem – The execution of a query takes a very long time.

Solution: The results coming from the database are very large. Set a limit for the results, or extend the filter conditions.