FusionAuth
Windows 10 Error launch after fresh installation
Windows 10 Error launch after fresh installation
Description
Windows 10 Error launch after installation
Affects versions
On Windows 10. FusionAuth Version : 1.36.1 https://files.fusionauth.io/products/fusionauth/1.36.1/fusionauth-app-1.36.1.zip
Steps to reproduce
1- I tried to install with Fast Path Install. When I launch http://localhost:9011/, there is an error.
2- So I use FusionAuth App Installation Method. https://fusionauth.io/direct-download https://files.fusionauth.io/products/fusionauth/1.36.1/fusionauth-app-1.36.1.zip
3- I had an error in log : JRE_HOME not existing. I had the JRE_HOME myself. JRE_HOME = C:\Program Files\Java\jre1.8.0_321
4- Now I have this error in .\fusionauth\logs\fusionauthapp_stderr.log :
Unrecognized option: --add-exports=java.base/sun.security.x509=ALL-UNNAMED Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit.
Expected behavior
The app is launch on http://localhost:9011/
Screenshots
No applicable
Platform
- Device: Desktop
- OS: Windows 10
- Browser + version : Chrome + latest
- Database + version : Bug before
Additional context
No one
I have now this on the page http://localhost:9011/admin/setup-wizard
FusionAuth encountered an unexpected error. Please review the troubleshooting guide found in the documentation for assistance and the available support channels.
In TOMCAT windows : GRAVE org.apache.catalina.core.StandardService - Failed to initialize connector [Connector[HTTP/1.1-9012]]
NOTE: Picked up JDK_JAVA_OPTIONS: --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
2022-04-18 3:45:32.785 AM INFOS org.apache.catalina.core.AprLifecycleListener - La librairie Apache Tomcat Native basÚe sur APR qui permet des performances optimales dans les environnements de production n'a pas ÚtÚ trouvÚe sur le java.library.path : [C:\ProgrammesWeb\fusionauth\java\jdk-17.0.1+12\bin;]
2022-04-18 3:45:32.988 AM INFOS org.apache.coyote.http11.Http11NioProtocol - Initialisation du gestionnaire de protocole ["http-nio-9011"]
2022-04-18 3:45:33.020 AM INFOS org.apache.coyote.http11.Http11NioProtocol - Initialisation du gestionnaire de protocole ["http-nio-127.0.0.1-9012"]
2022-04-18 3:45:33.020 AM GRAVE org.apache.catalina.core.StandardService - Failed to initialize connector [Connector[HTTP/1.1-9012]]
2022-04-18 3:45:33.020 AM INFOS org.apache.coyote.http11.Http11NioProtocol - Initialisation du gestionnaire de protocole ["https-jsse-nio-9013"]
2022-04-18 3:45:33.176 AM INFOS org.apache.coyote.ajp.AjpNioProtocol - Initialisation du gestionnaire de protocole ["ajp-nio-127.0.0.1-9019"]
2022-04-18 3:45:33.191 AM INFOS org.apache.catalina.startup.Catalina - Initialization processed in 640 ms
2022-04-18 3:45:33.191 AM INFOS org.apache.catalina.core.StandardService - DÚmarrage du service [Catalina]
2022-04-18 3:45:33.191 AM INFOS org.apache.catalina.core.StandardEngine - DÚmarrage du moteur de Servlets : [Apache Tomcat/8.5.77]
2022-04-18 3:45:35.138 AM INFOS org.apache.jasper.servlet.TldScanner - Au moins un fichier JAR a ÚtÚ analysÚ pour trouver des TLDs mais il n'en contenait pas, le mode "debug" du journal peut Ûtre activÚ pour obtenir une liste complÞte de JAR scannÚs sans succÞs ; Úviter d'analyser des JARs inutilement peut amÚliorer sensiblement le temps de dÚmarrage et le temps de compilation des JSPs
2022-04-18 3:45:38.853 AM INFOS org.apache.coyote.http11.Http11NioProtocol - DÚmarrage du gestionnaire de protocole ["http-nio-9011"]
2022-04-18 3:45:38.869 AM INFOS org.apache.coyote.http11.Http11NioProtocol - DÚmarrage du gestionnaire de protocole ["https-jsse-nio-9013"]
2022-04-18 3:45:38.869 AM INFOS org.apache.coyote.ajp.AjpNioProtocol - DÚmarrage du gestionnaire de protocole ["ajp-nio-127.0.0.1-9019"]
2022-04-18 3:45:38.869 AM INFOS org.apache.catalina.startup.Catalina - Server startup in 5683 ms
Thanks
I had an error in log : JRE_HOME not existing. I had the JRE_HOME myself. JRE_HOME = C:\Program Files\Java\jre1.8.0_321
Using your own JDK is not supported. The correct version of Java should be downloaded when you first start FusionAuth. The latest version of FusionAuth requires Java 17.
If there was an error during this step, please provide those details.
After launch '\fusionauth\bin\startup.bat' in '\fusionauth\logs\fusionauthapp_stdout.log' , I have :
Using CATALINA_BASE: "C:\ProgrammesWeb\fusionauth\fusionauth-app\apache-tomcat"
Using CATALINA_HOME: "C:\ProgrammesWeb\fusionauth\fusionauth-app\apache-tomcat"
Using CATALINA_TMPDIR: "C:\ProgrammesWeb\fusionauth\fusionauth-app\apache-tomcat\temp"
Using JRE_HOME: "C:\ProgrammesWeb\fusionauth\fusionauth-app\apache-tomcat\..\..\java\jdk-17.0.1+12"
Using CLASSPATH: "C:\ProgrammesWeb\fusionauth\fusionauth-app\apache-tomcat\bin\bootstrap.jar;C:\ProgrammesWeb\fusionauth\fusionauth-app\apache-tomcat\bin\tomcat-juli.jar"
Using CATALINA_OPTS: "-Dfusionauth.home.directory=C:\ProgrammesWeb\fusionauth\fusionauth-app\apache-tomcat\.. -Dfusionauth.config.directory=C:\ProgrammesWeb\fusionauth\fusionauth-app\apache-tomcat\..\..\config -Dfusionauth.log.directory=C:\ProgrammesWeb\fusionauth\fusionauth-app\apache-tomcat\..\..\logs -Dfusionauth.plugin.directory=C:\ProgrammesWeb\fusionauth\fusionauth-app\apache-tomcat\..\..\plugins -Xmx512M -Xms512M"
Usage: catalina ( commands ... )
commands:
debug Start Catalina in a debugger
debug -security Debug Catalina with a security manager
jpda start Start Catalina under JPDA debugger
run Start Catalina in the current window
run -security Start in the current window with security manager
start Start Catalina in a separate window
start -security Start in a separate window with security manager
stop Stop Catalina
configtest Run a basic syntax check on server.xml
version What version of tomcat are you running?
I still have in the windows : GRAVE org.apache.catalina.core.StandardService - Failed to initialize connector [Connector[HTTP/1.1-9012]]
2022-04-18 7:53:47.608 PM INFOS org.apache.coyote.http11.Http11NioProtocol - Initialisation du gestionnaire de protocole ["http-nio-9011"]
2022-04-18 7:53:47.644 PM INFOS org.apache.coyote.http11.Http11NioProtocol - Initialisation du gestionnaire de protocole ["http-nio-127.0.0.1-9012"]
2022-04-18 7:53:47.646 PM GRAVE org.apache.catalina.core.StandardService - Failed to initialize connector [Connector[HTTP/1.1-9012]]
2022-04-18 7:53:47.650 PM INFOS org.apache.coyote.http11.Http11NioProtocol - Initialisation du gestionnaire de protocole ["https-jsse-nio-9013"]
2022-04-18 7:53:47.908 PM INFOS org.apache.coyote.ajp.AjpNioProtocol - Initialisation du gestionnaire de protocole ["ajp-nio-127.0.0.1-9019"]
2022-04-18 7:53:47.909 PM INFOS org.apache.catalina.startup.Catalina - Initialization processed in 1027 ms
2022-04-18 7:53:47.918 PM INFOS org.apache.catalina.core.StandardService - DÚmarrage du service [Catalina]
2022-04-18 7:53:47.919 PM INFOS org.apache.catalina.core.StandardEngine - DÚmarrage du moteur de Servlets : [Apache Tomcat/8.5.77]
2022-04-18 7:53:50.640 PM INFOS org.apache.jasper.servlet.TldScanner - Au moins un fichier JAR a ÚtÚ analysÚ pour trouver des TLDs mais il n'en contenait pas, le mode "debug" du journal peut Ûtre activÚ pour obtenir une liste complÞte de JAR scannÚs sans succÞs ; Úviter d'analyser des JARs inutilement peut amÚliorer sensiblement le temps de dÚmarrage et le temps de compilation des JSPs
2022-04-18 7:53:55.323 PM INFOS org.apache.coyote.http11.Http11NioProtocol - DÚmarrage du gestionnaire de protocole ["http-nio-9011"]
2022-04-18 7:53:55.345 PM INFOS org.apache.coyote.http11.Http11NioProtocol - DÚmarrage du gestionnaire de protocole ["https-jsse-nio-9013"]
2022-04-18 7:53:55.349 PM INFOS org.apache.coyote.ajp.AjpNioProtocol - DÚmarrage du gestionnaire de protocole ["ajp-nio-127.0.0.1-9019"]
2022-04-18 7:53:55.352 PM INFOS org.apache.catalina.startup.Catalina - Server startup in 7442 ms
I still have on the page http://localhost:9011/admin/setup-wizard
FusionAuth encountered an unexpected error. Please review the troubleshooting guide found in the documentation for assistance and the available support channels.
For the 'JRE_HOME' error, I think that it is because I have a little internet speed connexion and I don't wait for the jar download.
In '.\fusionauth\fusionauth-app\apache-tomcat\bin\install_java.ps1' You can add echo statement : Write-Output "Dowloading Jar." to inform user that this can take time.