Why does this happen

li si March 10, 2022

When I enter localhost:8090 in the browser, the following occurs截图1.png

2 answers

0 votes
li si March 13, 2022

i want to chat with you, Are you ok!!

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 10, 2022

It is exactly what it says it is - Jira cannot connect to the database you have told it to use.

The "learn more" it links to can be very useful, but this really does mean you should have a quick look at the log to see if it gives you a bit more information about the exact error (it might not tell you a lot more, depending on the problem), and then you'll need to revise the settings, your network, and check your database is running and configured correctly.

Click the "learn more" to avoid us having to copy and paste it all here for you to read and follow.

li si March 10, 2022

I installed it on my native windows,

ping 127.0.0.1 also works

Do you need log, I see “learn more”, I have no problem

li si March 10, 2022

can you give a solution method?

li si March 10, 2022

can i chat with you online

Or can you help me remotelylogs.png

li si March 10, 2022

which log file

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 11, 2022

Sorry, I should have said - you need the application log file (the catalina logs are the application-server log files, which may also have errors when Jira is failing, but the error you are seeing is Jira failing, not Tomcat, so there's a 99.99% chance the useful log will be the application log)

The application logs are in <jira home>/logs and the very first one to read is atlassian-jira.log

For database errors like the one you have above, it's likely to say "can't use database", but it often tells you more about why it can't.  The usual culprits are

  • Can't connect to database server (database is not reachable over your network, or isn't running)
  • Can't log into database (usually the wrong credentials)
  • Can't use the database properly (usually the database user is set up incorrectly and can't write to it, or the collation or other settings are wrong)
li si March 11, 2022

i want to contact you,please tell me how to contact you

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 11, 2022

Ask your questions here - that way, you'll get more attention from people other than me.

What does your log file tell you the problem is?

li si March 12, 2022

This is my log:

2022-02-09 19:26:58,066+0800 JIRA-Bootstrap INFO [c.a.plugin.manager.DefaultPluginManager] Plugin system earlyStartup begun
2022-02-09 19:27:00,444+0800 FelixStartLevel WARN [o.e.g.b.e.internal.support.ExtenderConfiguration] Gemini Blueprint extensions bundle not present, annotation processing disabled.
2022-02-09 19:27:01,391+0800 JIRA-Bootstrap INFO [c.a.plugin.loaders.ScanningPluginLoader] No plugins found to be deployed
2022-02-09 19:27:01,643+0800 ThreadPoolAsyncTaskExecutor::Thread 3 WARN [c.a.p.s.scanner.util.ProductFilterUtil] Couldn't detect product, no known services found: will use ProductFilter.ALL
2022-02-09 19:27:01,705+0800 JIRA-Bootstrap INFO [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (3): [com.atlassian.plugins.less-transformer-plugin, com.atlassian.jira.jira-less-integration, com.atlassian.soy.soy-template-plugin], 300 seconds remaining
2022-02-09 19:27:03,072+0800 JIRA-Bootstrap INFO [c.a.plugin.manager.DefaultPluginManager] Plugin system earlyStartup ended
2022-02-09 19:27:03,078+0800 JIRA-Bootstrap INFO [c.a.jira.i18n.CachingI18nFactory] [i18n-caching-factory] Starting
2022-02-09 19:27:03,214+0800 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from C:\Users\li si\Atlassian\Application Data\Jira\dbconfig.xml
2022-02-09 19:27:03,233+0800 JIRA-Bootstrap INFO [c.a.j.instrumentation.external.DatabaseExternalGauges] Installing DBCP monitoring instruments: DatabaseExternalGauges.JiraDbcpInstruments[instruments=[DBCP_MAX, DBCP_ACTIVE, DBCP_IDLE],objectName=com.atlassian.jira:name=BasicDataSource]
2022-02-09 19:27:03,265+0800 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] Running Jira startup checks.
2022-02-09 19:27:03,266+0800 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] Jira pre-database startup checks completed successfully.
2022-02-09 19:27:03,325+0800 JIRA-Bootstrap INFO [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database is not yet configured. Enqueuing Database Checklist Launcher on post-database-configured-but-pre-database-activated queue
2022-02-09 19:27:03,326+0800 JIRA-Bootstrap INFO [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database is not yet configured. Enqueuing Post database-configuration launchers on post-database-activated queue
2022-02-09 19:27:03,342+0800 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Startup is complete. Jira is ready to serve.
2022-02-09 19:27:03,346+0800 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:

li si March 12, 2022

this is my full log:

2022-03-12 18:37:42,134 localhost-startStop-1 INFO [c.a.jira.startup.JiraHomeStartupCheck] The jira.home directory 'C:\Users\li si\Atlassian\Application Data\JIRA' is validated and locked for exclusive use by this instance.
2022-03-12 18:37:42,455 localhost-startStop-1 WARN [o.a.catalina.util.SessionIdGeneratorBase] Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [314] milliseconds.
2022-03-12 18:37:42,478 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger]

****************
JIRA starting...
****************

2022-03-12 18:37:42,687 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger]

___ Environment _____________________________

JIRA Build : 8.4.1#804002-sha1:94e96d6294939fc41f873484cf96b18ab6f2be0a
Build Date : Mon Sep 16 00:00:00 CST 2019
JIRA Installation Type : Standalone
Application Server : Apache Tomcat/8.5.42 - Servlet API 3.1
Java Version : 1.8.0_202 - AdoptOpenJdk
Current Working Directory : D:\LenovoSoftstore\Install\Jira\JIRA Software
Maximum Allowable Memory : 1820MB
Total Memory : 420MB
Free Memory : 275MB
Used Memory : 145MB
Memory Pool: Code Cache : Code Cache: init = 33554432(32768K) used = 11522944(11252K) committed = 33554432(32768K) max = 536870912(524288K)
Memory Pool: Metaspace : Metaspace: init = 0(0K) used = 21089576(20595K) committed = 21757952(21248K) max = -1(-1K)
Memory Pool: Compressed Class Space : Compressed Class Space: init = 0(0K) used = 2353472(2298K) committed = 2621440(2560K) max = 1073741824(1048576K)
Memory Pool: PS Eden Space : PS Eden Space: init = 100663296(98304K) used = 130473264(127415K) committed = 154664960(151040K) max = 679477248(663552K)
Memory Pool: PS Survivor Space : PS Survivor Space: init = 16777216(16384K) used = 2307840(2253K) committed = 17825792(17408K) max = 17825792(17408K)
Memory Pool: PS Old Gen : PS Old Gen: init = 268435456(262144K) used = 20695944(20210K) committed = 268435456(262144K) max = 1431830528(1398272K)
JVM Input Arguments : -Djava.util.logging.config.file=D:\LenovoSoftstore\Install\Jira\JIRA Software\conf\logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xms384m -Xmx2048m -XX:InitialCodeCacheSize=32m -XX:ReservedCodeCacheSize=512m -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory -XX:-OmitStackTraceInFastThrow -Djava.locale.providers=COMPAT -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Xloggc:D:\LenovoSoftstore\Install\Jira\JIRA Software\bin\..\logs\atlassian-jira-gc-%t.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=20M -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+PrintGCCause -Dignore.endorsed.dirs= -Dcatalina.base=D:\LenovoSoftstore\Install\Jira\JIRA Software -Dcatalina.home=D:\LenovoSoftstore\Install\Jira\JIRA Software -Djava.io.tmpdir=D:\LenovoSoftstore\Install\Jira\JIRA Software\temp
Java Compatibility Information : JIRA version = 8.4.1, Java Version = 1.8.0_202

___ Java System Properties ________________

atlassian.standalone : JIRA
awt.toolkit : sun.awt.windows.WToolkit
catalina.base : D:\LenovoSoftstore\Install\Jira\JIRA Software
catalina.home : D:\LenovoSoftstore\Install\Jira\JIRA Software
catalina.useNaming : true
common.loader : "${catalina.base}/lib",
"${catalina.base}/lib/*.jar",
"${catalina.home}/lib",
"${catalina.home}/lib/*.jar"
file.encoding : GBK
file.encoding.pkg : sun.io
ignore.endorsed.dirs :
java.awt.graphicsenv : sun.awt.Win32GraphicsEnvironment
java.awt.headless : true
java.awt.printerjob : sun.awt.windows.WPrinterJob
java.class.version : 52.0
java.home : D:\LenovoSoftstore\Install\Jira\JIRA Software\jre
java.io.tmpdir : D:\LenovoSoftstore\Install\Jira\JIRA Software\temp
java.locale.providers : COMPAT
java.naming.factory.initial : org.apache.naming.java.javaURLContextFactory
java.naming.factory.url.pkgs : org.apache.naming
java.protocol.handler.pkgs : org.apache.catalina.webresources
java.runtime.name : OpenJDK Runtime Environment
java.runtime.version : 1.8.0_202-b08
java.specification.name : Java Platform API Specification
java.specification.vendor : Oracle Corporation
java.specification.version : 1.8
java.util.concurrent.ForkJoinPool.common.threadFactory : org.apache.catalina.startup.SafeForkJoinWorkerThreadFactory
java.util.logging.config.file : D:\LenovoSoftstore\Install\Jira\JIRA Software\conf\logging.properties
java.util.logging.manager : org.apache.juli.ClassLoaderLogManager
java.vendor : AdoptOpenJdk
java.vendor.url : https://adoptopenjdk.net/
java.vendor.url.bug : https://github.com/AdoptOpenJDK/openjdk-build/issues
java.version : 1.8.0_202
java.vm.info : mixed mode
java.vm.name : OpenJDK 64-Bit Server VM
java.vm.specification.name : Java Virtual Machine Specification
java.vm.specification.vendor : Oracle Corporation
java.vm.specification.version : 1.8
java.vm.vendor : Oracle Corporation
java.vm.version : 25.202-b08
jdk.tls.ephemeralDHKeySize : 2048
mail.mime.decodeparameters : true
org.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER : true
org.dom4j.factory : com.atlassian.core.xml.InterningDocumentFactory
os.arch : amd64
os.name : Windows 10
os.version : 10.0
package.access : sun.,
org.apache.catalina.,
org.apache.coyote.,
org.apache.jasper.,
org.apache.tomcat.
package.definition : sun.,
java.,
org.apache.catalina.,
org.apache.coyote.,
org.apache.jasper.,
org.apache.naming.,
org.apache.tomcat.
server.loader :
shared.loader :
sun.arch.data.model : 64
sun.boot.library.path : D:\LenovoSoftstore\Install\Jira\JIRA Software\jre\bin
sun.cpu.endian : little
sun.cpu.isalist : amd64
sun.desktop : windows
sun.io.unicode.encoding : UnicodeLittle
sun.java.command : org.apache.catalina.startup.Bootstrap start
sun.java.launcher : SUN_STANDARD
sun.jnu.encoding : GBK
sun.management.compiler : HotSpot 64-Bit Tiered Compilers
sun.os.patch.level :
sun.stderr.encoding : ms936
sun.stdout.encoding : ms936
tomcat.util.buf.StringCache.byte.enabled : true
tomcat.util.scan.StandardJarScanFilter.jarsToScan : log4j-taglib*.jar,
log4j-web*.jar,
log4javascript*.jar,
slf4j-taglib*.jar
tomcat.util.scan.StandardJarScanFilter.jarsToSkip : annotations-api.jar,
ant-junit*.jar,
ant-launcher.jar,
ant.jar,
asm-*.jar,
aspectj*.jar,
bootstrap.jar,
catalina-ant.jar,
catalina-ha.jar,
catalina-jmx-remote.jar,
catalina-storeconfig.jar,
catalina-tribes.jar,
catalina-ws.jar,
catalina.jar,
cglib-*.jar,
cobertura-*.jar,
commons-beanutils*.jar,
commons-codec*.jar,
commons-collections*.jar,
commons-daemon.jar,
commons-dbcp*.jar,
commons-digester*.jar,
commons-fileupload*.jar,
commons-httpclient*.jar,
commons-io*.jar,
commons-lang*.jar,
commons-logging*.jar,
commons-math*.jar,
commons-pool*.jar,
dom4j-*.jar,
easymock-*.jar,
ecj-*.jar,
el-api.jar,
geronimo-spec-jaxrpc*.jar,
h2*.jar,
hamcrest-*.jar,
hibernate*.jar,
httpclient*.jar,
icu4j-*.jar,
jasper-el.jar,
jasper.jar,
jaspic-api.jar,
jaxb-*.jar,
jaxen-*.jar,
jdom-*.jar,
jetty-*.jar,
jmx-tools.jar,
jmx.jar,
jsp-api.jar,
jstl.jar,
jta*.jar,
junit-*.jar,
junit.jar,
log4j*.jar,
mail*.jar,
objenesis-*.jar,
oraclepki.jar,
oro-*.jar,
servlet-api-*.jar,
servlet-api.jar,
slf4j*.jar,
taglibs-standard-spec-*.jar,
tagsoup-*.jar,
tomcat-api.jar,
tomcat-coyote.jar,
tomcat-dbcp.jar,
tomcat-i18n-*.jar,
tomcat-jdbc.jar,
tomcat-jni.jar,
tomcat-juli-adapters.jar,
tomcat-juli.jar,
tomcat-util-scan.jar,
tomcat-util.jar,
tomcat-websocket.jar,
tools.jar,
websocket-api.jar,
wsdl4j*.jar,
xercesImpl.jar,
xml-apis.jar,
xmlParserAPIs-*.jar,
xmlParserAPIs.jar,
xom-*.jar
user.country : CN
user.dir : D:\LenovoSoftstore\Install\Jira\JIRA Software
user.home : C:\Users\li si
user.language : zh
user.name : li si
user.script :
user.timezone : Asia/Shanghai
user.variant :

2022-03-12 18:37:43,084 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from C:\Users\li si\Atlassian\Application Data\Jira\dbconfig.xml
2022-03-12 18:37:43,164 JIRA-Bootstrap INFO [c.a.j.config.database.DatabaseConfigHandler] Trying to get encrypted password from xml and decrypt it
2022-03-12 18:37:43,166 JIRA-Bootstrap INFO [c.a.j.config.database.DatabaseConfigHandler] Database password decryption not performed.
2022-03-12 18:37:43,257 JIRA-Bootstrap WARN [c.a.jira.health.HealthChecks] Custom changes have not been carried over
2022-03-12 18:37:43,257 JIRA-Bootstrap WARN [c.a.jira.health.HealthChecks] The listed configuration files contain custom changes. To keep your current configuration, re-apply these custom changes to the new version of the files during upgrade.
- atlassian-jira\WEB-INF\classes\jira-application.properties

Note: Make sure you only copy over the changes not the entire files.

2022-03-12 18:37:43,501 JIRA-Bootstrap ERROR [c.a.config.bootstrap.DefaultAtlassianBootstrapManager] Could not successfully test your database:
org.h2.jdbc.JdbcSQLException: IO Exception: "java.io.IOException: 文件名、目录名或卷标语法不正确。"; "retry:C:/Users/li si/Atlassian/Application Data/Jira/database/h2db.mv.db" [90031-185]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:168)
at org.h2.message.DbException.convertIOException(DbException.java:330)
at org.h2.store.fs.FilePathDisk.toRealPath(FilePathDisk.java:204)
at org.h2.store.fs.FilePathDisk.toRealPath(FilePathDisk.java:34)
at org.h2.store.fs.FileUtils.toRealPath(FileUtils.java:77)
at org.h2.engine.ConnectionInfo.getName(ConnectionInfo.java:410)
at org.h2.engine.Engine.openSession(Engine.java:45)
at org.h2.engine.Engine.openSession(Engine.java:167)
at org.h2.engine.Engine.createSessionAndValidate(Engine.java:145)
at org.h2.engine.Engine.createSession(Engine.java:128)
at org.h2.engine.Engine.createSession(Engine.java:26)
at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:347)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:108)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:92)
at org.h2.Driver.connect(Driver.java:72)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:247)
at com.atlassian.config.bootstrap.DefaultAtlassianBootstrapManager.getTestDatabaseConnection(DefaultAtlassianBootstrapManager.java:347)
at com.atlassian.jira.config.database.JdbcDatasource.getConnection(JdbcDatasource.java:219)
at com.atlassian.jira.config.database.DatabaseConfig.testConnection(DatabaseConfig.java:88)
at com.atlassian.jira.health.checks.DbConfigurationAndConnectionCheck.doPerform(DbConfigurationAndConnectionCheck.java:60)
at com.atlassian.jira.health.HealthCheckTemplate.perform(HealthCheckTemplate.java:23)
at com.atlassian.jira.health.DefaultHealthCheckExecutor.runCheck(DefaultHealthCheckExecutor.java:74)
at com.atlassian.jira.health.DefaultHealthCheckExecutor.lambda$applyAndCollectExceptions$1(DefaultHealthCheckExecutor.java:53)
at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
at java.util.Iterator.forEachRemaining(Iterator.java:116)
at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
at com.atlassian.jira.health.DefaultHealthCheckExecutor.applyAndCollectExceptions(DefaultHealthCheckExecutor.java:53)
at com.atlassian.jira.health.DefaultHealthCheckExecutor.performHealthChecks(DefaultHealthCheckExecutor.java:42)
at com.atlassian.jira.health.HealthChecks.executeChecksAndRecordResults(HealthChecks.java:164)
at com.atlassian.jira.health.HealthChecks.runHealthChecks(HealthChecks.java:154)
at com.atlassian.jira.health.HealthChecks.runHealthChecks(HealthChecks.java:66)
at com.atlassian.jira.startup.BootstrapContainerLauncher.start(BootstrapContainerLauncher.java:48)
at com.atlassian.jira.startup.DefaultJiraLauncher.preDbLaunch(DefaultJiraLauncher.java:117)
at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:103)
at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)
at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:102)
at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:154)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: 文件名、目录名或卷标语法不正确。
at java.io.WinNTFileSystem.canonicalize0(Native Method)
at java.io.WinNTFileSystem.canonicalize(WinNTFileSystem.java:428)
at java.io.File.getCanonicalPath(File.java:618)
at org.h2.store.fs.FilePathDisk.toRealPath(FilePathDisk.java:201)
... 43 more
2022-03-12 18:37:43,507 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA couldn't connect to your database
2022-03-12 18:37:43,507 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA failed to establish a connection to your database.
This could be because:
- Your database isn't running
- The configuration of your dbconfig.xml file is incorrect (user, password, or database URL etc.)
- There is a network issue between JIRA and your database (e.g. firewall, database doesn't allow remote access etc.)

There are several other solutions you can try, review our documentation and see what works for you.

2022-03-12 18:37:43,512 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] Running JIRA startup checks.
2022-03-12 18:37:43,512 JIRA-Bootstrap FATAL [c.a.jira.startup.JiraStartupLogger] Startup check failed. JIRA will be locked.
2022-03-12 18:37:43,636 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:
---------------------------------------------------------------------------------
Heap memory : Used: 116 MiB. Committed: 417 MiB. Max: 2031 MiB
Non-heap memory : Used: 40 MiB. Committed: 64 MiB. Max: 1536 MiB
---------------------------------------------------------------------------------
TOTAL : Used: 156 MiB. Committed: 481 MiB. Max: 3567 MiB
---------------------------------------------------------------------------------

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 12, 2022

You need to find the part of it where it says it can't connect to the database.

li si March 12, 2022

2022-03-12 18:37:43,501 JIRA-Bootstrap ERROR [c.a.config.bootstrap.DefaultAtlassianBootstrapManager] Could not successfully test your database:
org.h2.jdbc.JdbcSQLException: IO Exception: "java.io.IOException: 文件名、目录名或卷标语法不正确。"; "retry:C:/Users/li si/Atlassian/Application Data/Jira/database/h2db.mv.db" [90031-185]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:168)
at org.h2.message.DbException.convertIOException(DbException.java:330)
at org.h2.store.fs.FilePathDisk.toRealPath(FilePathDisk.java:204)
at org.h2.store.fs.FilePathDisk.toRealPath(FilePathDisk.java:34)
at org.h2.store.fs.FileUtils.toRealPath(FileUtils.java:77)
at org.h2.engine.ConnectionInfo.getName(ConnectionInfo.java:410)
at org.h2.engine.Engine.openSession(Engine.java:45)
at org.h2.engine.Engine.openSession(Engine.java:167)
at org.h2.engine.Engine.createSessionAndValidate(Engine.java:145)
at org.h2.engine.Engine.createSession(Engine.java:128)
at org.h2.engine.Engine.createSession(Engine.java:26)
at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:347)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:108)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:92)
at org.h2.Driver.connect(Driver.java:72)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:247)
at com.atlassian.config.bootstrap.DefaultAtlassianBootstrapManager.getTestDatabaseConnection(DefaultAtlassianBootstrapManager.java:347)
at com.atlassian.jira.config.database.JdbcDatasource.getConnection(JdbcDatasource.java:219)
at com.atlassian.jira.config.database.DatabaseConfig.testConnection(DatabaseConfig.java:88)
at com.atlassian.jira.health.checks.DbConfigurationAndConnectionCheck.doPerform(DbConfigurationAndConnectionCheck.java:60)
at com.atlassian.jira.health.HealthCheckTemplate.perform(HealthCheckTemplate.java:23)
at com.atlassian.jira.health.DefaultHealthCheckExecutor.runCheck(DefaultHealthCheckExecutor.java:74)
at com.atlassian.jira.health.DefaultHealthCheckExecutor.lambda$applyAndCollectExceptions$1(DefaultHealthCheckExecutor.java:53)
at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
at java.util.Iterator.forEachRemaining(Iterator.java:116)
at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
at com.atlassian.jira.health.DefaultHealthCheckExecutor.applyAndCollectExceptions(DefaultHealthCheckExecutor.java:53)
at com.atlassian.jira.health.DefaultHealthCheckExecutor.performHealthChecks(DefaultHealthCheckExecutor.java:42)
at com.atlassian.jira.health.HealthChecks.executeChecksAndRecordResults(HealthChecks.java:164)
at com.atlassian.jira.health.HealthChecks.runHealthChecks(HealthChecks.java:154)
at com.atlassian.jira.health.HealthChecks.runHealthChecks(HealthChecks.java:66)
at com.atlassian.jira.startup.BootstrapContainerLauncher.start(BootstrapContainerLauncher.java:48)
at com.atlassian.jira.startup.DefaultJiraLauncher.preDbLaunch(DefaultJiraLauncher.java:117)
at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:103)
at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)
at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:102)
at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:154)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: 文件名、目录名或卷标语法不正确。
at java.io.WinNTFileSystem.canonicalize0(Native Method)
at java.io.WinNTFileSystem.canonicalize(WinNTFileSystem.java:428)
at java.io.File.getCanonicalPath(File.java:618)
at org.h2.store.fs.FilePathDisk.toRealPath(FilePathDisk.java:201)
... 43 more

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 12, 2022

Sorry, my last comment crossed over with your posting of the log you actually needed to show us.

So, yes, that's pretty clear.  Your Jira is configured to use the dev/test h2 database rather than a proper one for any serious use.

h2 is a file based database, and Jira reads the files from it as it starts up.  For some reason, it is unable to read the database files, so it cannot start up properly.

You'll need to check that the database files are there and have the right permissions for the Jira user to read and write it, but I'm afraid the most likely problem is that the files are damaged.

If the permissions on the database files are ok, then it's likely that you've had a massive failure and your only option is to restore from the last backup.

h2 is only used for dev/test activity because it can fail without warning, especially when under heavier usage.  When it fails, it's usually catastrophic, not a couple of corrupt lines, but a complete loss of everything.

If you do have to restore from a backup, your next task should be to drop everything else and migrate to a supported database.

li si March 12, 2022

where is this database file

li si March 12, 2022

my confluence occurs a problemconfluence.png

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 12, 2022

The database file is the one given in the error message (with h2db in its name)

The SQL error you are getting is there because your database is corrupt

li si March 12, 2022

You can talk about how to solve this problem of jira, confluence and jira are independent, both of them have problems, the screenshot I gave you above is from confluence

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 12, 2022

Ah, ok, I see that now, but I don't understand why you've suddenly changed the subject from one system to another.

It does not help that the error you are seeing in Confluence can be caused by the same problem you have with your Jira - I have conflated the two together because both problems you are talking about now could easily be caused by the same thing - a corrupted (h2) database.

li si March 13, 2022

how to solve jira problem,please tell me detail,what should i do 

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 13, 2022

As above, check the permissions on the database files and correct them if necessary.  If it's not the permissions, then you will need to go bak to a backup because the database is corrupt.

li si March 13, 2022

i want to chat with you,Are you OK! i I can't solve my problem

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 14, 2022

What have you tried to do to fix the problem?  Restored from a backup?

li si March 17, 2022

Does Atlassian have an online support tool like slack or Microsoft Team, it is too inconvenient to communicate on this, please help me join in, or give me a link, I will join myself

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 17, 2022

Yes, it's the Community for smaller users (free/starter/etc), and the support portals for the medium/large users, up until the size where you get a TAM (technical account manager), where you can just contact that human.

If you do connect that way, be prepared to answer the same questions I've asked of you - there are reasons I asked them.

li si March 17, 2022

please see this log,what meaing?

my mysq server version is 5.5.25,

Does it match this?

截屏.png

li si March 18, 2022

jira's problem is solvd , i want to ask conflence,please see it

StatementCallback; bad SQL grammar

[CREATE TRIGGER denormalised_space_trigger_on_update AFTER UPDATE ON SPACES FOR EACH ROW sp: BEGIN DECLARE isServiceDisabled BOOL DEFAULT TRUE; CALL space_procedure_for_denormalised_permissions(isServiceDisabled); IF (isServiceDisabled) THEN LEAVE sp; END IF; IF (NEW.LOWERSPACEKEY = OLD.LOWERSPACEKEY) THEN LEAVE sp; END IF; INSERT INTO DENORMALISED_SPACE_CHANGE_LOG(SPACE_ID) VALUES (NEW.SPACEID); END;];

nested exception is com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'confluence.spaces' doesn't exist

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 18, 2022

This also looks like a damaged database, or possibly a mis-configured one.  I'd want to run throug the same debugging you did for Jira.

Suggest an answer

Log in or Sign up to answer