- 问问题请带上 DataEase 版本信息、安装部署方式信息、详细错误信息，减少不必要的来回沟通！
-
不要重复发帖！
升级到1.18.27启动失败
[root@iZ2ze0xc1pcwgd6e9xp6scZ ~]# docker image ls
REPOSITORY TAG IMAGE ID CREATED SIZE
registry.cn-qingdao.aliyuncs.com/dataease/dataease v1.18.27 1de16a9a957e 8 days ago 1.34GB
registry.cn-qingdao.aliyuncs.com/dataease/dataease v1.18.24 729859401f97 3 months ago 1.34GB
registry.cn-qingdao.aliyuncs.com/dataease/dataease v1.18.23 c795e1cca8f8 5 months ago 1.34GB
registry.cn-qingdao.aliyuncs.com/dataease/dataease v1.18.22 8d1087acb486 6 months ago 1.34GB
registry.cn-qingdao.aliyuncs.com/dataease/mysql 8.3.0 82563e0cbf18 9 months ago 632MB
[root@iZ2ze0xc1pcwgd6e9xp6scZ ~]# dectl status
DataEase 容器运行状态
NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS
dataease registry.cn-qingdao.aliyuncs.com/dataease/dataease:v1.18.27 “/deployments/run-ja…” dataease 22 minutes ago Up 6 seconds (health: starting) 0.0.0.0:8200->8081/tcp, :::8200->8081/tcp
mysql registry.cn-qingdao.aliyuncs.com/dataease/mysql:8.3.0 “docker-entrypoint.s…” mysql 22 minutes ago Up 22 minutes (healthy) 33060/tcp, 0.0.0.0:3307->3306/tcp, :::3307->3306/tcp
Docker 目录及文件大小 :
5.3G /var/lib/docker
Docker 目录所在磁盘使用情况 :
文件系统 容量 已用 可用 已用% 挂载点
/dev/vda1 43G 20G 23G 47% /
日志文件大小 :
0 /opt/dataease/logs/be
0 /opt/dataease/logs/fe
184M /opt/dataease/logs/dataease/history
5.2M /opt/dataease/logs/dataease
4.0K /opt/dataease/logs/
DataEase 运行目录及文件大小 :
7.0G /opt
DataEase 运行目录使用情况 :
文件系统 容量 已用 可用 已用% 挂载点
/dev/vda1 43G 20G 23G 47% /
DataEase 服务状态 : 正在启动 … 88s
DataEase 服务状态 : 无法访问
[root@iZ2ze0xc1pcwgd6e9xp6scZ ~]# dectl reload
[+] Running 2/2
Container mysql Healthy 0.0s
Container dataease Started 0.0s
DataEase 服务状态 : 正在启动 … 90s
【警告】服务在等待时间内未完全启动！请稍后使用 dectl status 检查服务运行状况。
下面是报错日志：
2024-12-26 14:06:25,438 INFO com.alibaba.druid.pool.DruidDataSource: 998 - {dataSource-2} inited
2024-12-26 14:06:25,441 INFO com.alibaba.druid.pool.DruidDataSource: 998 - {dataSource-1} inited
2024-12-26 14:06:25,787 ERROR agnostics.LoggingFailureAnalysisReporter: 40 -
APPLICATION FAILED TO START
Description:
A component required a bean of type ‘io.dataease.plugins.xpack.official.dao.display.mapper.XpackSysParamAssistMapper’ that could not be found.
Action:
Consider defining a bean of type ‘io.dataease.plugins.xpack.official.dao.display.mapper.XpackSysParamAssistMapper’ in your configuration.
2024-12-26 14:06:26,188 WARN ConfigServletWebServerApplicationContext:1060 - Exception thrown from ApplicationListener handling ContextClosedEvent
java.lang.ClassCastException: class java.util.LinkedHashMap$LinkedValues cannot be cast to class java.util.List (java.util.LinkedHashMap$LinkedValues and java.util.List are in module java.base of loader ‘bootstrap’)
at io.dataease.service.datasource.DatasourceService.releaseDsconnections(DatasourceService.java:665)
at io.dataease.service.datasource.DatasourceService$$FastClassBySpringCGLIB$$2ccad08e.invoke()
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:779)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:750)
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:750)
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:692)
at io.dataease.service.datasource.DatasourceService$$EnhancerBySpringCGLIB$$f1c17b9b.releaseDsconnections()
at io.dataease.service.datasource.DatasourceService$$FastClassBySpringCGLIB$$2ccad08e.invoke()
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:688)
at io.dataease.service.datasource.DatasourceService$$EnhancerBySpringCGLIB$$871e80f9.releaseDsconnections()
at io.dataease.listener.ApplicationCloseEventListener.onApplicationEvent(ApplicationCloseEventListener.java:27)
at io.dataease.listener.ApplicationCloseEventListener.onApplicationEvent(ApplicationCloseEventListener.java:14)
at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:176)
at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:169)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:143)
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:420)
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:377)
at org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:1057)
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.doClose(ServletWebServerApplicationContext.java:171)
at org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:1020)
at org.springframework.boot.SpringApplication.handleRunFailure(SpringApplication.java:823)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:344)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1311)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1300)
at io.dataease.Application.main(Application.java:22)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:107)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:58)
at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:88)
2024-12-26 14:06:26,194 INFO g.simp.broker.SimpleBrokerMessageHandler: 137 - Stopping…
2024-12-26 14:06:26,194 INFO g.simp.broker.SimpleBrokerMessageHandler: 137 - BrokerAvailabilityEvent[available=false, SimpleBrokerMessageHandler [org.springframework.messaging.simp.broker.DefaultSubscriptionRegistry@ba27ce6]]
2024-12-26 14:06:26,194 INFO g.simp.broker.SimpleBrokerMessageHandler: 137 - Stopped.
Loading class com.mysql.jdbc.Driver'. This is deprecated. The new driver class is com.mysql.cj.jdbc.Driver’. The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary.
2024-12-26 14:06:26,255 INFO duling.concurrent.ThreadPoolTaskExecutor: 218 - Shutting down ExecutorService ‘taskExecutor’
2024-12-26 14:06:26,260 INFO uling.concurrent.ThreadPoolTaskScheduler: 218 - Shutting down ExecutorService ‘messageBrokerTaskScheduler’
2024-12-26 14:06:26,280 INFO duling.concurrent.ThreadPoolTaskExecutor: ? - Shutting down ExecutorService ‘brokerChannelExecutor’
2024-12-26 14:06:26,280 INFO duling.concurrent.ThreadPoolTaskExecutor: 218 - Shutting down ExecutorService ‘clientOutboundChannelExecutor’
2024-12-26 14:06:26,281 INFO duling.concurrent.ThreadPoolTaskExecutor: 218 - Shutting down ExecutorService ‘clientInboundChannelExecutor’
2024-12-26 14:06:26,290 INFO k.scheduling.quartz.SchedulerFactoryBean: 845 - Shutting down Quartz Scheduler
2024-12-26 14:06:26,290 INFO org.quartz.core.QuartzScheduler: 666 - Scheduler clusterScheduler_$711cf552e5361735193155817 shutting down.
2024-12-26 14:06:26,291 INFO org.quartz.core.QuartzScheduler: 585 - Scheduler clusterScheduler$711cf552e5361735193155817 paused.
2024-12-26 14:06:26,291 INFO org.quartz.core.QuartzScheduler: 740 - Scheduler clusterScheduler$_711cf552e5361735193155817 shutdown complete.
2024-12-26 14:06:26,304 INFO com.zaxxer.hikari.HikariDataSource: 350 - DatebookHikariCP - Shutdown initiated…
2024-12-26 14:06:26,319 INFO com.zaxxer.hikari.HikariDataSource: 352 - DatebookHikariCP - Shutdown completed.
2024-12-26 14:07:21,515 INFO k.scheduling.quartz.SchedulerFactoryBean: 748 - Starting Quartz Scheduler now, after delay of 60 seconds
Exception in thread “Quartz Scheduler [clusterScheduler]” org.springframework.scheduling.SchedulingException: Could not start Quartz Scheduler after delay; nested exception is org.quartz.SchedulerException: The Scheduler cannot be restarted after shutdown() has been called.
at org.springframework.scheduling.quartz.SchedulerFactoryBean$1.run(SchedulerFactoryBean.java:754)
Caused by: org.quartz.SchedulerException: The Scheduler cannot be restarted after shutdown() has been called.
at org.quartz.core.QuartzScheduler.start(QuartzScheduler.java:529)
at org.quartz.impl.StdScheduler.start(StdScheduler.java:142)
at org.springframework.scheduling.quartz.SchedulerFactoryBean$1.run(SchedulerFactoryBean.java:751)
2024-12-26 14:07:21,671 ERROR org.quartz.core.QuartzScheduler: 566 - Unable to start scheduler after startup delay.
org.quartz.SchedulerException: The Scheduler cannot be restarted after shutdown() has been called.
at org.quartz.core.QuartzScheduler.start(QuartzScheduler.java:529)
at org.quartz.core.QuartzScheduler$1.run(QuartzScheduler.java:564)
at java.base/java.lang.Thread.run(Thread.java:829)