Stash Does Not Start - No fonts found

Troubleshooting Installation



アトラシアン コミュニティをご利用ください。



The Stash UI shows the following error when trying to access http://<STASH_URL>:<PORT>. For example:

A fatal error has occurred
The following problem occurred which prevents Atlassian Stash from starting correctly:
The Spring WebApplicationContext could not be started

In the atlassian-stash.log the following can be seen: 

Caused by: java.lang.Error: Probable fatal error:No fonts found.
	at sun.font.FontManager.getDefaultPhysicalFont( ~[na:1.6.0_24]
	at sun.font.FontManager.initialiseDeferredFont( ~[na:1.6.0_24]
	at sun.font.FontManager.findOtherDeferredFont( ~[na:1.6.0_24]
	at sun.font.FontManager.findDeferredFont( ~[na:1.6.0_24]


Stash is using OpenJDK.


Either register installed fonts in the Java font properties and continue using OpenJDK or set JAVA_HOME to a currently Oracle Supported version.

In order to run Stash with OpenJDK:

  1.  To run a java command to register installed fonts in the java font properties and continue using Open JDK:

    cd /usr/lib/jvm/java-6-openjdk-common/jre/lib
    sudo java -jar compilefontconfig.jar fontconfig.config fontconfig.bfc
    If command complains that it couldn't find fontconfig.config.

    locate fontconfig.config (e.g. if it is shown to be in /etc/java-6-openjdk/

    The other file fontconfig.bfc might also be here:

    sudo java -jar compilefontconfig.jar /etc/java-6-openjdk/ fontconfig.bfc

  2. Set your JAVA_HOME

    From <Stash installation directory>/bin/, set the right value for this variable. Below the contents of this file:

    # JAVA_HOME Must point at your Java Development Kit installation.
    # Required to run the with the "debug" argument.
    # JRE_HOME Must point at your Java Runtime installation.
    # Defaults to JAVA_HOME if empty. If JRE_HOME and JAVA_HOME
    # are both set, JRE_HOME is used.
最終更新日: 2016 年 2 月 26 日


Powered by Confluence and Scroll Viewport.