Use this information to help diagnose any problems when using Alfresco Analytics.
- Analytics server unable to start up due to conflict on port 8080
- Bootstrap content not imported into Analytics server
- WebDAV activities not appearing in the standard Alfresco activity feed
- ETL job unable to connect to PostgreSQL database installed with the Alfresco installer
- Unable to sign in to Analytics
- Unable to use the Pentaho User Console due to error: 'Analysis is currently unavailable'
- Problems with disk space
- ActiveMQ failure causes Alfresco Share to fail
- Error displaying reports on My Reports and Site Reports pages
- Multiple file uploads in Share treated as one event
- "Process lock file exists" warnings in log
- Unable to perform write operations in Share
- GLib-GIO-ERROR setup reported when running ETL jobs on Ubuntu
- Dashlet data is not refreshed after events occur
Analytics server unable to start up due to conflict on port 8080
If you are running the Analytics server on the same server as Alfresco during evaluation you might have a port conflict between your Alfresco Tomcat instance, and the Tomcat server that is provided with the Alfresco 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 Alfresco 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 Alfresco. See Deploying Share into a separate Tomcat instance for more information on configuring an alternative port.back to top
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 Alfresco 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.back to top
WebDAV activities not appearing in the standard Alfresco activity feed
ETL job unable to connect to PostgreSQL database installed with the Alfresco installer
If you installed Alfresco 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.
- 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 trustwhere 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
- Restart Alfresco including PostgreSQL:
Unable to sign in to Analytics
<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 Alfresco Support to help them to identify the problem.
Unable to use the Pentaho User Console due to error: 'Analysis is currently unavailable'
Sorry, We hit a problem in Alfresco Analytics. Please contact your Alfresco Administrator for further assistance.If you have not installed Analytics server licences, obtain the license files for your organisation from Alfresco 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 Alfresco Analytics.back to top
ActiveMQ failure causes Alfresco Share to fail
events.subsystem.autoStart=false messaging.subsystem.autoStart=falseA 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 Alfresco 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.
http://server:port/pentaho/Homewhere 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.
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 18.104.22.168-101) Fully Qualified Server Url = http://localhost:8080/pentaho/, Solution Path = /opt//ba-server/pentaho-solutionsIn this situation, you must either re-initialize the repository, or restore your repository from a backup. See Restoring Alfresco Analytics for more information.
Multiple file uploads in Share treated as one event
When you upload five or more files at once, Alfresco Analytics recognizes it as a single activity. Files uploaded by WebDAV aren't recognized at all by Alfresco Analytics.
"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.
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
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 Alfresco Share.
GLib-GIO-ERROR setup reported when running ETL jobs on Ubuntu
(process:21941): GLib-GIO-ERROR **: Settings schema 'org.gnome.system.proxy' is not installedSome 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-schemasand 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.
http://server:port/pentaho/Homeand selecting Tools > Refresh.
See Setting up the database schema for information on refreshing the cache automatically.