DataEase 版本2.10.2，安装部署方式是在1panel里直接安装，本次为在1panel里升级出错，dataease提示异常，无法打开。
e[2K1Panel-dataease-aGsb | 10:43:26,133 |-INFO in ch.qos.logback.core.joran.spi.ConfigurationWatchList@a8c1f44 - URL [jar:nested:/opt/apps/app.jar/!BOOT-INF/classes/!/logback-spring.xml] is not of type file
e[2K1Panel-dataease-aGsb | 10:43:26,244 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [STDOUT]
e[2K1Panel-dataease-aGsb | 10:43:26,244 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
e[2K1Panel-dataease-aGsb | 10:43:26,253 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
e[2K1Panel-dataease-aGsb | 10:43:26,283 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [info_log]
e[2K1Panel-dataease-aGsb | 10:43:26,284 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
e[2K1Panel-dataease-aGsb | 10:43:26,301 |-INFO in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy@493944943 - setting totalSizeCap to 10 GB
e[2K1Panel-dataease-aGsb | 10:43:26,306 |-INFO in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy@493944943 - Archive files will be limited to [10 MB] each.
e[2K1Panel-dataease-aGsb | 10:43:26,309 |-INFO in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy@493944943 - No compression will be used
e[2K1Panel-dataease-aGsb | 10:43:26,310 |-INFO in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy@493944943 - Will use the pattern /opt/dataease2.0/logs/dataease/info.%d.%i.log for the active file
e[2K1Panel-dataease-aGsb | 10:43:26,336 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@31024624 - The date pattern is ‘yyyy-MM-dd’ from file name pattern ‘/opt/dataease2.0/logs/dataease/info.%d.%i.log’.
e[2K1Panel-dataease-aGsb | 10:43:26,336 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@31024624 - Roll-over at midnight.
e[2K1Panel-dataease-aGsb | 10:43:26,345 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@31024624 - Setting initial period to 2024-11-13T02:42:23.875Z
e[2K1Panel-dataease-aGsb | 10:43:26,348 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
e[2K1Panel-dataease-aGsb | 10:43:26,352 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[info_log] - Active log file name: /opt/dataease2.0/logs/dataease/info.log
e[2K1Panel-dataease-aGsb | 10:43:26,352 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[info_log] - File property is set to [/opt/dataease2.0/logs/dataease/info.log]
e[2K1Panel-dataease-aGsb | 10:43:26,356 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [error_log]
e[2K1Panel-dataease-aGsb | 10:43:26,356 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
e[2K1Panel-dataease-aGsb | 10:43:26,359 |-INFO in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy@749443480 - setting totalSizeCap to 10 GB
e[2K1Panel-dataease-aGsb | 10:43:26,359 |-INFO in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy@749443480 - Archive files will be limited to [10 MB] each.
e[2K1Panel-dataease-aGsb | 10:43:26,360 |-INFO in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy@749443480 - No compression will be used
e[2K1Panel-dataease-aGsb | 10:43:26,360 |-INFO in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy@749443480 - Will use the pattern /opt/dataease2.0/logs/dataease/error.%d.%i.log for the active file
e[2K1Panel-dataease-aGsb | 10:43:26,361 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@2f7a7219 - The date pattern is ‘yyyy-MM-dd’ from file name pattern ‘/opt/dataease2.0/logs/dataease/error.%d.%i.log’.
e[2K1Panel-dataease-aGsb | 10:43:26,361 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@2f7a7219 - Roll-over at midnight.
e[2K1Panel-dataease-aGsb | 10:43:26,362 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@2f7a7219 - Setting initial period to 2024-11-13T02:42:23.914Z
e[2K1Panel-dataease-aGsb | 10:43:26,362 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
e[2K1Panel-dataease-aGsb | 10:43:26,363 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[error_log] - Active log file name: /opt/dataease2.0/logs/dataease/error.log
e[2K1Panel-dataease-aGsb | 10:43:26,363 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[error_log] - File property is set to [/opt/dataease2.0/logs/dataease/error.log]
e[2K1Panel-dataease-aGsb | 10:43:26,364 |-INFO in ch.qos.logback.classic.model.processor.RootLoggerModelHandler - Setting level of ROOT logger to INFO
e[2K1Panel-dataease-aGsb | 10:43:26,364 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@669513d8 - Propagating INFO level on Logger[ROOT] onto the JUL framework
e[2K1Panel-dataease-aGsb | 10:43:26,366 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [STDOUT] to Logger[ROOT]
e[2K1Panel-dataease-aGsb | 10:43:26,366 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [info_log] to Logger[ROOT]
e[2K1Panel-dataease-aGsb | 10:43:26,366 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [error_log] to Logger[ROOT]
e[2K1Panel-dataease-aGsb | 10:43:26,366 |-INFO in ch.qos.logback.core.model.processor.DefaultProcessor@285d851a - End of configuration.
e[2K1Panel-dataease-aGsb | 10:43:26,366 |-INFO in org.springframework.boot.logging.logback.SpringBootJoranConfigurator@314b8f2d - Registering current configuration as safe fallback point
e[2K1Panel-dataease-aGsb | . ____ _ __ _ _
e[2K1Panel-dataease-aGsb | /\ / ’ __ _ () __ __ _ \ \ \
e[2K1Panel-dataease-aGsb | ( ( )__ | '_ | '| | ’ / ` | \ \ \
e[2K1Panel-dataease-aGsb | \/ )| |)| | | | | || (| | ) ) ) )
e[2K1Panel-dataease-aGsb | ’ || .__|| ||| |_, | / / / /
e[2K1Panel-dataease-aGsb | =========||==============|/=////
e[2K1Panel-dataease-aGsb |
e[2K1Panel-dataease-aGsb | :: Spring Boot :: (v3.3.0)
e[2K1Panel-dataease-aGsb |
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:26.426 e[34mINFO e[0;39m — [kground-preinit] e[36mo.h.validator.internal.util.Version e[0;39m : HV000001: Hibernate Validator 8.0.1.Final
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:26.583 e[34mINFO e[0;39m — [ main] e[36mio.dataease.CoreApplication e[0;39m : Starting CoreApplication v2.10.2 using Java 21.0.3 with PID 1 (/opt/apps/app.jar started by root in /deployments)
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:26.584 e[34mINFO e[0;39m — [ main] e[36mio.dataease.CoreApplication e[0;39m : The following 1 profile is active: “standalone”
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:29.287 e[34mINFO e[0;39m — [ main] e[36m.s.d.r.c.RepositoryConfigurationDelegatee[0;39m : Multiple Spring Data modules found, entering strict repository configuration mode
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:29.291 e[34mINFO e[0;39m — [ main] e[36m.s.d.r.c.RepositoryConfigurationDelegatee[0;39m : Bootstrapping Spring Data LDAP repositories in DEFAULT mode.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:29.382 e[34mINFO e[0;39m — [ main] e[36m.s.d.r.c.RepositoryConfigurationDelegatee[0;39m : Finished Spring Data repository scanning in 81 ms. Found 0 LDAP repository interfaces.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:29.409 e[34mINFO e[0;39m — [ main] e[36m.s.d.r.c.RepositoryConfigurationDelegatee[0;39m : Multiple Spring Data modules found, entering strict repository configuration mode
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:29.410 e[34mINFO e[0;39m — [ main] e[36m.s.d.r.c.RepositoryConfigurationDelegatee[0;39m : Bootstrapping Spring Data Redis repositories in DEFAULT mode.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:29.447 e[34mINFO e[0;39m — [ main] e[36m.s.d.r.c.RepositoryConfigurationDelegatee[0;39m : Finished Spring Data repository scanning in 21 ms. Found 0 Redis repository interfaces.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:30.782 e[31mWARN e[0;39m — [ main] e[36mtrationDelegate$BeanPostProcessorCheckere[0;39m : Bean ‘org.springframework.boot.autoconfigure.jdbc.DataSourceConfiguration$Hikari’ of type [org.springframework.boot.autoconfigure.jdbc.DataSourceConfiguration$Hikari] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [schedulerStarter]? Check the corresponding BeanPostProcessor declaration and its dependencies.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:30.802 e[31mWARN e[0;39m — [ main] e[36mtrationDelegate$BeanPostProcessorCheckere[0;39m : Bean ‘org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration’ of type [org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [schedulerStarter]? Check the corresponding BeanPostProcessor declaration and its dependencies.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:30.806 e[31mWARN e[0;39m — [ main] e[36mtrationDelegate$BeanPostProcessorCheckere[0;39m : Bean ‘stringOrNumberMigrationVersionConverter’ of type [org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration$StringOrNumberToMigrationVersionConverter] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [schedulerStarter]? Check the corresponding BeanPostProcessor declaration and its dependencies.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:30.821 e[31mWARN e[0;39m — [ main] e[36mtrationDelegate$BeanPostProcessorCheckere[0;39m : Bean ‘spring.datasource-org.springframework.boot.autoconfigure.jdbc.DataSourceProperties’ of type [org.springframework.boot.autoconfigure.jdbc.DataSourceProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [schedulerStarter]? Check the corresponding BeanPostProcessor declaration and its dependencies.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:30.833 e[31mWARN e[0;39m — [ main] e[36mtrationDelegate$BeanPostProcessorCheckere[0;39m : Bean ‘org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration$PooledDataSourceConfiguration’ of type [org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration$PooledDataSourceConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [schedulerStarter]? Check the corresponding BeanPostProcessor declaration and its dependencies.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:30.837 e[31mWARN e[0;39m — [ main] e[36mtrationDelegate$BeanPostProcessorCheckere[0;39m : Bean ‘jdbcConnectionDetails’ of type [org.springframework.boot.autoconfigure.jdbc.PropertiesJdbcConnectionDetails] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [schedulerStarter]? Check the corresponding BeanPostProcessor declaration and its dependencies.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:30.862 e[31mWARN e[0;39m — [ main] e[36mtrationDelegate$BeanPostProcessorCheckere[0;39m : Bean ‘dataSource’ of type [com.zaxxer.hikari.HikariDataSource] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [schedulerStarter]? Check the corresponding BeanPostProcessor declaration and its dependencies.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:30.896 e[31mWARN e[0;39m — [ main] e[36mtrationDelegate$BeanPostProcessorCheckere[0;39m : Bean ‘quartz-com.fit2cloud.autoconfigure.QuartzProperties’ of type [com.fit2cloud.autoconfigure.QuartzProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [schedulerStarter]? Check the corresponding BeanPostProcessor declaration and its dependencies.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:30.908 e[31mWARN e[0;39m — [ main] e[36mtrationDelegate$BeanPostProcessorCheckere[0;39m : Bean ‘org.springframework.boot.autoconfigure.jdbc.DataSourceTransactionManagerAutoConfiguration$JdbcTransactionManagerConfiguration’ of type [org.springframework.boot.autoconfigure.jdbc.DataSourceTransactionManagerAutoConfiguration$JdbcTransactionManagerConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [schedulerStarter]? Check the corresponding BeanPostProcessor declaration and its dependencies.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:30.922 e[31mWARN e[0;39m — [ main] e[36mtrationDelegate$BeanPostProcessorCheckere[0;39m : Bean ‘org.springframework.boot.autoconfigure.transaction.TransactionManagerCustomizationAutoConfiguration’ of type [org.springframework.boot.autoconfigure.transaction.TransactionManagerCustomizationAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [schedulerStarter]? Check the corresponding BeanPostProcessor declaration and its dependencies.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:30.929 e[31mWARN e[0;39m — [ main] e[36mtrationDelegate$BeanPostProcessorCheckere[0;39m : Bean ‘transactionExecutionListeners’ of type [org.springframework.boot.autoconfigure.transaction.ExecutionListenersTransactionManagerCustomizer] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [schedulerStarter]? Check the corresponding BeanPostProcessor declaration and its dependencies.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:30.937 e[31mWARN e[0;39m — [ main] e[36mtrationDelegate$BeanPostProcessorCheckere[0;39m : Bean ‘spring.transaction-org.springframework.boot.autoconfigure.transaction.TransactionProperties’ of type [org.springframework.boot.autoconfigure.transaction.TransactionProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [schedulerStarter]? Check the corresponding BeanPostProcessor declaration and its dependencies.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:30.941 e[31mWARN e[0;39m — [ main] e[36mtrationDelegate$BeanPostProcessorCheckere[0;39m : Bean ‘platformTransactionManagerCustomizers’ of type [org.springframework.boot.autoconfigure.transaction.TransactionManagerCustomizers] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [schedulerStarter]? Check the corresponding BeanPostProcessor declaration and its dependencies.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:30.953 e[31mWARN e[0;39m — [ main] e[36mtrationDelegate$BeanPostProcessorCheckere[0;39m : Bean ‘transactionManager’ of type [org.springframework.jdbc.support.JdbcTransactionManager] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [schedulerStarter]? Check the corresponding BeanPostProcessor declaration and its dependencies.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:30.971 e[31mWARN e[0;39m — [ main] e[36mtrationDelegate$BeanPostProcessorCheckere[0;39m : Bean ‘com.fit2cloud.autoconfigure.QuartzAutoConfiguration’ of type [com.fit2cloud.autoconfigure.QuartzAutoConfiguration$$SpringCGLIB$$0] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). The currently created BeanPostProcessor [schedulerStarter] is declared through a non-static factory method on that class; consider declaring it as static instead.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:30.994 e[31mWARN e[0;39m — [ main] e[36mtrationDelegate$BeanPostProcessorCheckere[0;39m : Bean ‘spring.flyway-org.springframework.boot.autoconfigure.flyway.FlywayProperties’ of type [org.springframework.boot.autoconfigure.flyway.FlywayProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [schedulerStarter]? Check the corresponding BeanPostProcessor declaration and its dependencies.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:31.012 e[31mWARN e[0;39m — [ main] e[36mtrationDelegate$BeanPostProcessorCheckere[0;39m : Bean ‘org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration$FlywayConfiguration’ of type [org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration$FlywayConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [schedulerStarter]? Check the corresponding BeanPostProcessor declaration and its dependencies.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:31.028 e[31mWARN e[0;39m — [ main] e[36mtrationDelegate$BeanPostProcessorCheckere[0;39m : Bean ‘flywayConnectionDetails’ of type [org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration$PropertiesFlywayConnectionDetails] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [schedulerStarter]? Check the corresponding BeanPostProcessor declaration and its dependencies.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:31.033 e[31mWARN e[0;39m — [ main] e[36mtrationDelegate$BeanPostProcessorCheckere[0;39m : Bean ‘resourceProviderCustomizer’ of type [org.springframework.boot.autoconfigure.flyway.ResourceProviderCustomizer] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [schedulerStarter]? Check the corresponding BeanPostProcessor declaration and its dependencies.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:31.270 e[31mWARN e[0;39m — [ main] e[36mtrationDelegate$BeanPostProcessorCheckere[0;39m : Bean ‘flyway’ of type [org.flywaydb.core.Flyway] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [schedulerStarter]? Check the corresponding BeanPostProcessor declaration and its dependencies.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:31.316 e[34mINFO e[0;39m — [ main] e[36mcom.zaxxer.hikari.HikariDataSource e[0;39m : HikariPool-1 - Starting…
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:31.591 e[34mINFO e[0;39m — [ main] e[36mcom.zaxxer.hikari.pool.HikariPool e[0;39m : HikariPool-1 - Added connection com.mysql.cj.jdbc.ConnectionImpl@761a0bbd
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:31.594 e[34mINFO e[0;39m — [ main] e[36mcom.zaxxer.hikari.HikariDataSource e[0;39m : HikariPool-1 - Start completed.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:31.655 e[34mINFO e[0;39m — [ main] e[36morg.flywaydb.core.FlywayExecutor e[0;39m : Database: jdbc:mysql://mysql:3306/de_zh46nn (MySQL 5.7)
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:31.695 e[34mINFO e[0;39m — [ main] e[36mo.f.core.internal.database.base.Databasee[0;39m : MySQL 5.7 is outside of Redgate community support. See https://rd.gt/468B6ni for details
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:31.816 e[34mINFO e[0;39m — [ main] e[36mo.f.core.internal.command.DbMigrate e[0;39m : Current version of schema `de_zh46nn`: 3.2
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:31.816 e[31mWARN e[0;39m — [ main] e[36mo.f.core.internal.command.DbMigrate e[0;39m : outOfOrder mode is active. Migration of schema `de_zh46nn` may not be reproducible.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:31.854 e[31mWARN e[0;39m — [ main] e[36mConfigServletWebServerApplicationContexte[0;39m : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘schedulerStarter’: Unsatisfied dependency expressed through field ‘scheduler’: Error creating bean with name ‘flywayInitializer’ defined in class path resource [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]: Schema `de_zh46nn` contains a failed migration to version 2.10.2 !
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:31.854 e[34mINFO e[0;39m — [ main] e[36mcom.zaxxer.hikari.HikariDataSource e[0;39m : HikariPool-1 - Shutdown initiated…
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:31.883 e[34mINFO e[0;39m — [ main] e[36mcom.zaxxer.hikari.HikariDataSource e[0;39m : HikariPool-1 - Shutdown completed.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:31.900 e[34mINFO e[0;39m — [ main] e[36m.s.b.a.l.ConditionEvaluationReportLoggere[0;39m :
e[2K1Panel-dataease-aGsb |
e[2K1Panel-dataease-aGsb | Error starting ApplicationContext. To display the condition evaluation report re-run your application with ‘debug’ enabled.
e[2K1Panel-dataease-aGsb | 2024-11-13 10:43:31.939 e[1;31mERRORe[0;39m — [ main] e[36mo.springframework.boot.SpringApplicatione[0;39m : Application run failed
e[2K1Panel-dataease-aGsb | org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘schedulerStarter’: Unsatisfied dependency expressed through field ‘scheduler’: Error creating bean with name ‘flywayInitializer’ defined in class path resource [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]: Schema `de_zh46nn` contains a failed migration to version 2.10.2 !
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.resolveFieldValue(AutowiredAnnotationBeanPostProcessor.java:787)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:767)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:145)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessProperties(AutowiredAnnotationBeanPostProcessor.java:508)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1421)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:599)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:522)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:337)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:335)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:205)
e[2K1Panel-dataease-aGsb | at org.springframework.context.support.PostProcessorRegistrationDelegate.registerBeanPostProcessors(PostProcessorRegistrationDelegate.java:277)
e[2K1Panel-dataease-aGsb | at org.springframework.context.support.AbstractApplicationContext.registerBeanPostProcessors(AbstractApplicationContext.java:805)
e[2K1Panel-dataease-aGsb | at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:608)
e[2K1Panel-dataease-aGsb | at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:146)
e[2K1Panel-dataease-aGsb | at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:754)
e[2K1Panel-dataease-aGsb | at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:456)
e[2K1Panel-dataease-aGsb | at org.springframework.boot.SpringApplication.run(SpringApplication.java:335)
e[2K1Panel-dataease-aGsb | at org.springframework.boot.SpringApplication.run(SpringApplication.java:1363)
e[2K1Panel-dataease-aGsb | at org.springframework.boot.SpringApplication.run(SpringApplication.java:1352)
e[2K1Panel-dataease-aGsb | at io.dataease.CoreApplication.main(CoreApplication.java:15)
e[2K1Panel-dataease-aGsb | at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
e[2K1Panel-dataease-aGsb | at java.base/java.lang.reflect.Method.invoke(Method.java:580)
e[2K1Panel-dataease-aGsb | at org.springframework.boot.loader.launch.Launcher.launch(Launcher.java:91)
e[2K1Panel-dataease-aGsb | at org.springframework.boot.loader.launch.Launcher.launch(Launcher.java:53)
e[2K1Panel-dataease-aGsb | at org.springframework.boot.loader.launch.PropertiesLauncher.main(PropertiesLauncher.java:574)
e[2K1Panel-dataease-aGsb | Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘flywayInitializer’ defined in class path resource [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]: Schema `de_zh46nn` contains a failed migration to version 2.10.2 !
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1788)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:600)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:522)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:337)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:335)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:200)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:313)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:200)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:254)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1443)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1353)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.resolveFieldValue(AutowiredAnnotationBeanPostProcessor.java:784)
e[2K1Panel-dataease-aGsb | … 25 common frames omitted
e[2K1Panel-dataease-aGsb | Caused by: org.flywaydb.core.internal.command.DbMigrate$FlywayMigrateException: Schema `de_zh46nn` contains a failed migration to version 2.10.2 !
e[2K1Panel-dataease-aGsb | at org.flywaydb.core.internal.command.DbMigrate.migrateGroup(DbMigrate.java:218)
e[2K1Panel-dataease-aGsb | at org.flywaydb.core.internal.command.DbMigrate.lambda$migrateAll$0(DbMigrate.java:139)
e[2K1Panel-dataease-aGsb | at org.flywaydb.database.mysql.MySQLNamedLockTemplate.execute(MySQLNamedLockTemplate.java:58)
e[2K1Panel-dataease-aGsb | at org.flywaydb.database.mysql.MySQLConnection.lock(MySQLConnection.java:150)
e[2K1Panel-dataease-aGsb | at org.flywaydb.core.internal.schemahistory.JdbcTableSchemaHistory.lock(JdbcTableSchemaHistory.java:145)
e[2K1Panel-dataease-aGsb | at org.flywaydb.core.internal.command.DbMigrate.migrateAll(DbMigrate.java:139)
e[2K1Panel-dataease-aGsb | at org.flywaydb.core.internal.command.DbMigrate.migrate(DbMigrate.java:97)
e[2K1Panel-dataease-aGsb | at org.flywaydb.core.Flyway.lambda$migrate$0(Flyway.java:202)
e[2K1Panel-dataease-aGsb | at org.flywaydb.core.FlywayExecutor.execute(FlywayExecutor.java:205)
e[2K1Panel-dataease-aGsb | at org.flywaydb.core.Flyway.migrate(Flyway.java:147)
e[2K1Panel-dataease-aGsb | at org.springframework.boot.autoconfigure.flyway.FlywayMigrationInitializer.afterPropertiesSet(FlywayMigrationInitializer.java:66)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1835)
e[2K1Panel-dataease-aGsb | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1784)
e[2K1Panel-dataease-aGsb | … 37 common frames omitted
这看着报错是数据库的语句执行失败，可以找到这个文件中的这个位置，手动执行下语句试试
数据库版本问题，用mysql8.X重新安装了应用，问题解决。