Running a server in "devmode" provides enhanced logging, enables the MiniProfiler, and provides resource reloading without the need to restart or rebuild the server. To run the server in devmode (using Tomcat 7):
C:\Program Files (x86)\LabKey Server\apache-tomcat-7.0.xx\bin
tomcat7w.exe //ES//LabKeyTomcat7
-Ddevmode=trueBefore 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 other applications, such as Tomcat, are configured to use the correct versions.
You can only install one instance of PostgreSQL on your computer at a time.
If you are running a non-English version of Windows, please use the manual install process, not the Windows Graphical Installer.
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 7.0 and click Stop.
To delete, from the command line (may need to run as administrator):
sc delete LabKeyTomcat7
When you upgrade to Java 8, be sure to remove the setting of MaxPermSize. If your CATALINA_OPTS or other configuration files include something like "-XX:MaxPermSize=256M" you may have errors when starting your server.
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 Tomcat 8/9. The most important change is to replace your "maxActive" setting (used with Tomcat 7) with "maxTotal" (Tomcat 8/9). 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
C:\Program Files\LabKey Server
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 (Note: you may wish to sanitize the logs of any database login information you provided to the installer). PostgreSQL logs its installation process separately. If the installer indicates that PostgreSQL installation/upgrage failed, please locate and include the postgres install logs as well.
| previousnext |
| expand allcollapse all |
