Troubleshooting Analytics

Use this information to help diagnose any problems when using SkyVault Analytics.

Analytics server unable to start up due to conflict on port 8080

If you are running the Analytics server on the same server as SkyVault during evaluation you might have a port conflict between your SkyVault Tomcat instance, and the Tomcat server that is provided with the SkyVault Analytics software, as both are set by default to use port 8080.

Also be aware that for support reasons, Tomcat version 6 is shipped with the Analytics server.

We recommend that you always use different servers for the Analytics and SkyVault servers in a production environment, however if you are sharing a server, perhaps in a test environment, then you will need to reconfigure the bundled Tomcat server to use an alternative port if port 8080 is already in use by SkyVault. See Deploying Share into a separate Tomcat instance for more information on configuring an alternative port.

Bootstrap content not imported into Analytics server

When you first set up the Analytics server, a zip file ba-server/pentaho-solutions/system/default-content/baserver_repository.zip is used to set up the Analytics server configuration. After the initial setup, the file is suffixed with a timestamp and not used again (for example, it becomes baserver-repository.zip.201411171239).

Launch SkyVault Share as an Analytics user, where you will be redirected to the Pentaho User Console. Select Browse > Files. If you cannot see any files, then the bootstrap content has not been imported. To solve this problem, remove the timestamp from the baserver_repository.zip file and the Analytics server will reload it and perform a clean start on the next startup.

WebDAV activities not appearing in the standard SkyVault activity feed

Analytics messages from WebDAV are not displayed by default. If you want to see WebDAV activities appear, add the following property to your SkyVault-global.properties file:

system.webdav.activities.enabled=true

Note: You cannot simply enable WebDAV in the Admin Console, you must add this property to SkyVault-global.properties.

ETL job unable to connect to PostgreSQL database installed with the SkyVault installer

If you installed SkyVault using the Enterprise installer and you are running the Analytics server on a separate machine (as recommended), you might see all_fct.kjb ETL job log and ba-server/tomcat/pentaho.log errors that indicate that a connection to PostgreSQL could not be established.

To resolve this problem, edit the configuration of PostgreSQL to accept remote incoming connections from the server where SkyVault Analytics is installed, as follows:

Edit the alf_data/postgresql/postgresql.conf file and add (or edit) the property listen_addresses. To accept connections from all remote hosts, use listen_addresses='*'
Define a host record for the Analytics server by adding an entry to allow all connections from the IP address corresponding to the Analytics server, at the end of the alf_data/postgresql/pg_hba.conf file, for example:
```
host all all 10.10.29.0/24 trust
```
where 10.10.29.0 is the IP address of the Analytics server. Any IP address starting 10.10.29. is acceptable.
Edit the property listen_addresses in the alf_data/postgresql/pg_hba.conf file to specify:
```
listen_addresses='*'
```
Restart SkyVault including PostgreSQL:
```
./alfresco.sh restart
```

Unable to sign in to Analytics

If users are not able to sign in, add the following configuration to the ba-server/tomcat/webapps/pentaho/WEB-INF/classes/log4j.xml file:

<category name="org.alfresco.pentaho">    
     <priority value="DEBUG"/> 
</category>

This setting activates debug logging for the SSO classes inside the Analytics module. The logging information will help you determine the problem, or alternatively can be passed to SkyVault Support to help them to identify the problem.

Unable to use the Pentaho User Console due to error: 'Analysis is currently unavailable'

The following error text appears when licenses are not properly installed, or if the Analytics server is down, or if SkyVault or the Analytics server are not correctly configured:

Sorry,
We hit a problem in SkyVault Analytics.
Please contact your SkyVault Administrator for further assistance.

If you have not installed Analytics server licences, obtain the license files for your organisation from SkyVault Support and install these using the instructions in the initial Analytics installation.

Problems with disk space

If you do not periodically purge the log files for Analytics, your logs will build up and you might see disk space errors or problems. To avoid problems with disk space, use a tool such as logrotate to compress or delete logging data. For more information, see Advanced monitoring in SkyVault Analytics.

ActiveMQ failure causes SkyVault Share to fail

If ActiveMQ fails while the events and messaging subsystems are running, SkyVault Share functions are deactivated (for example, sites and users cannot be created, and files cannot be created or uploaded). To reactivate the SkyVault functions without ActiveMQ, you must stop the events and messaging subsystems in your SkyVault-global.properties file:

events.subsystem.autoStart=false
messaging.subsystem.autoStart=false

A better solution however is to configure ActiveMQ clustering to ensure that there is always an ActiveMQ instance available. For more information on ActiveMQ clustering, see Clustering ActiveMQ.

Error displaying reports on My Reports and Site Reports pages

If users are getting errors when trying to display reports, this is because SkyVault cannot load existing reports from the Analytics server. Check that the Analytics server address is correctly set in the pentaho.ba-server.url property. See Step 5. Installing and setting up the Business Analytics (BA) server for more information.

If pentaho.ba-server.url is correctly configured, there might be a problem with the BA server. Check the that you can log in and see the landing page of the Pentaho User Console:

http://server:port/pentaho/Home

where server and port are the server and port number where the BA server is installed. Additionally, you can check the ba-server/tomcat/logs/pentaho.log for problems.

When you log in to the Pentaho User Console, if you can see only header without page content, or if you see exceptions or initialization problems in the log file, the Pentaho repository has not initialized correctly, for example:

 javax.jcr.PathNotFoundException: /pentaho/tenant0 
at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:552) 
at org.apache.jackrabbit.core.session.SessionItemOperation$4.perform(SessionItemOperation.java:97)
at org.apache.jackrabbit.core.session.SessionItemOperation$4.perform(SessionItemOperation.java:93)       
at org.apache.jackrabbit.core.session.SessionItemOperation.perform(SessionItemOperation.java:187)
at org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216) 
at org.apache.jackrabbit.core.SessionImpl.perform(SessionImpl.java:361) 
at org.apache.jackrabbit.core.SessionImpl.getItem(SessionImpl.java:786) 
at org.pentaho.platform.security.policy.rolebased.AbstractJcrBackedRoleBindingDao.getRuntimeRolesFolderNode(AbstractJcrBackedRoleBindingDao.java:326)

Pentaho BI Platform server failed to properly initialize. The system will not be available for requests. (Pentaho Business Analytics Server Enterprise Edition 5.1.2.0-101) Fully Qualified Server Url = http://localhost:8080/pentaho/, Solution Path = /opt//ba-server/pentaho-solutions

In this situation, you must either re-initialize the repository, or restore your repository from a backup. See Restoring SkyVault Analytics for more information.

Multiple file uploads in Share treated as one event

When you upload five or more files at once, SkyVault Analytics recognizes it as a single activity. Files uploaded by WebDAV aren't recognized at all by SkyVault Analytics.

To customize the Share upload limit, edit the groupActivitiesAt property in the SkyVault.DocListToolbar.prototype section of toolbar.js. For more information about customizing Share JavaScript, see Customizing Share JavaScript.

"Process lock file exists" warnings in all_fct.log

If new events are not showing in your reports, look in the all_fct.log file to see if there are any errors.

The following error is logged when a previous instance of the all_fct.kjb job has failed to shut down correctly or has crashed:

2015/03/05  10:14:06 - ETL STOPPED - LOCK FILE FOUND - ##################################
2015/03/05 10:14:06 - ETL STOPPED - LOCK FILE FOUND - ##                                    ##
2015/03/05 10:14:06 - ETL STOPPED - LOCK FILE FOUND - ##  Process lock file exists, this would suggest the Job is currently executing. ##   
2015/03/05 10:14:06 - ETL STOPPED - LOCK FILE FOUND - ##                                    ##     
2015/03/05 10:14:06 - ETL STOPPED - LOCK FILE FOUND - ##################################

To resolve this problem:

Check if there are any kitchen.sh processes that are still running and stop them, for example:
```
pgrep kitchen
pkill kitchen
```
In your Analytics installation directory, remove the log file data-integration/ETL/ETL_activity/output/processing.lock.
The next time that all_fct.kjb runs, monitor the all_fct.log for any new errors.

Unable to perform write operations in Share

There is an issue when loading data, where the server locks intermittently and blocks write operations in SkyVault Share.

The workaround to this problem is to set the following endpoint in your SkyVault-global.properties file or in JMX:

messaging.events.repo.node.targetTopic.endpoint=log:MessagesAreDisgarded?level=OFF

GLib-GIO-ERROR setup reported when running ETL jobs on Ubuntu

If you are using Ubuntu, when you run the schema_setup.kjb job using Kettle, the setup of the schema fails with the following error:

(process:21941): GLib-GIO-ERROR **: Settings schema 'org.gnome.system.proxy' is not installed

Some desktop settings that Kettle requires are not installed as part of the Ubuntu server installation. To resolve the problem, install the Ubuntu gsettings-desktop-schemas package:

sudo apt-get install gsettings-desktop-schemas

and rerun the ETL job.

Dashlet data is not refreshed after events occur

If you can see data in your Analytics dashlet, but the data is not being refreshed after events occur, it might be that the BA server cache is not being refreshed, possibly due to problems with the user specified in the ~/.kettle/kettle.properties file.

You can manually refresh the cache by logging into the Pentaho User Console:

http://server:port/pentaho/Home

and selecting Tools > Refresh.

See Setting up the database schema for information on refreshing the cache automatically.

Search form

Search form

You are here