In case of errors or other problems when installing and running LabKey Server, first review installation basics and options linked on the Install LabKey page.
Running a server in "devmode" provides enhanced logging and enables the MiniProfiler. To run the server in devmode, follow these steps. The supported version of tomcat will change over time; replace the # in our examples with the actual version number.
C:\labkey\apps\apache\apache-tomcat-#.#.##\bin
tomcat#w.exe //ES//LabKeyTomcat#
-Ddevmode=true
Learn more about other diagnostic information on the admin console in this topic:
Before installing LabKey Server, you should shut down all other running applications. If you have problems during the installation, try additionally shutting down any virus scanning application, internet security applications, or other applications that run in the background.
Confirm that you are using the supported versions of the required components, as detailed in the Supported Technologies Roadmap. It is possible to have multiple versions of some software, like Java, installed at the same time. Check that LabKey and other applications, such as Tomcat, are configured to use the correct versions.
You may need to remove references to Cygwin from your Windows system path before installing LabKey, due to conflicts with the PostgreSQL installer. The PostgreSQL installer also conflicts with some antivirus or firewall software programs. (see http://wiki.postgresql.org/wiki/Running_%26_Installing_PostgreSQL_On_Native_Windows for more information).
If installation fails to start tomcat (such as with an error like "The specified service already exists."), you may need to manually stop or delete a failing Tomcat service.
To stop the service on Windows, open Control Panel > Administrative Tools > Services. Select the relevant service, such as LabKey Server Apache Tomcat #.0 and click Stop.
To delete, run the following from the command line as an administrator, substituting the major version number for the #:
sc delete LabKeyTomcat#
If your server becomes unresponsive, it could be due to the depletion of available connections to the database. Watch for a Connection Pool Size of 8, which is the Tomcat connection pool default size and insufficient for a production server. To see the connection pool size for the LabKey data source, select (Admin) > Site > Admin Console and check the setting of Connection Pool Size on the Server Information panel. The connection pool size for every data source is also logged at server startup.
To set the connection pool size, edit your labkey.xml configuration file and change the appropriate setting for your LabKey data source to at least 20. Depending on the number of simultaneous users and the complexity of their requests, your deployment may require a larger connection pool size. The setting name depends on your Tomcat version:
The Tomcat data source connection pool settings changed significantly in Tomcat 8, so you must change your data source settings when you upgrade from Tomcat 7 to a later version. The most important change is to replace your "maxActive" setting (used with Tomcat 7) with "maxTotal". Review the Database Connection Pooling section of the Tomcat Migration Guide for more information. See External Schemas and Data Sources for details and data source configuration examples.
If you have encountered prior failed installations, don't have any stored data you need to keep, and want to clean up and start completely from scratch, the following process may be useful:
sc delete LabKeyTomcat7
You can search for problems resolved through community support in the LabKey Installation Forum.
If you don't see your issue listed there, you can post a new question. If the install seems successful, it is often helpful to submit debugging logs for diagnosis.
If the install failed to complete, please include the install.log and install-debug.log from your selected LabKey install directory.
PostgreSQL logs its installation process separately. If PostgreSQL installation/upgrage fails, please locate and include the PostgreSQL install logs as well.
| previousnext |
| expand allcollapse all |
