Linux离线安装部署dataease2.10.5无法访问localhost:8100(重要)

user-aqevhug1yvu · 2025 年2 月 11 日 02:29

我是在openEuler v22.03 (LTS-SP3)系统服务器上安装完后，发现自动创建的dataease和mysql8.4.0的docker镜像没有启动，然后发现是默认自动连外网下载镜像，就手动从安装包中加载了这两个镜像，然后只能启动dataease镜像，启动不了mysql，然后网页还是访问不了localhost:8100。
安装时的提示：
[root@lowair-app64 installer-v2.10.5]# /bin/bash install.sh
当前时间 : Mon Feb 10 11:30:07 AM CST 2025

检查安装环境并初始化环境变量
全新安装
设置运行目录
运行目录 /usr/local/dataease/dataease2.0
配置文件目录 /usr/local/dataease/dataease2.0/conf
初始化运行目录
复制安装文件到运行目录
调整配置文件参数
安装 dectl 命令行工具
安装至 /usr/local/bin/dectl & /usr/bin/dectl
修改操作系统相关设置
关闭 SELINUX
开启防火墙端口 8100
success
success
安装 docker
检测到 Docker 已安装，跳过安装步骤
启动 Docker
安装 docker-compose
离线安装 docker-compose
docker-compose 安装成功
加载 DataEase 镜像
加载镜像 dataease_v2.10.5
加载镜像 mysql_8.4.0
配置 DataEase 服务
配置 dataease Service
配置开机自启动
启动 DataEase 服务
11.Job for dataease.service failed because the control process exited with error code.*
12.See “systemctl status dataease.service” and “journalctl -xeu dataease.service” for details.*
======================= 安装完成 =======================
我把防火墙已关闭，在安装包里只有dataease和mysql这两个镜像但docker的yml文件有5个不知其他3个是否也要docker，然后发现只能启动dataease镜像，mysql镜像无法启动，但localhost:8100还是访问不了。官方的离线安装文档比较简单，还有很多意外情况不知怎么解决，gpt和deepseek都帮不上忙都是ai瞎猜的结果。公司想搭建dataease平台提供可视化，我已经无解了。

IUUI · 2025 年2 月 11 日 02:30

你要先看看 cpu 是什么架构的呀，是不是 arm 下载了 amd 的安装包，然后就是 docker 版本是不是太老了，如果是的话你看看是升级一下 docker 还是卸载系统本身的 docker ，使用我们安装包的 docker。

user-aqevhug1yvu · 2025 年2 月 11 日 02:39

CPU架构不是ARM，是Intel x86_64，Docker版本是version 18.09.0是否会太老，然后刚发现java 版本是1.8，dataease2.10.5的JDK应该是21版本是不是要重新安装21

qianzhao · 2025 年2 月 11 日 03:41

mysql容器没有启动成功可能是端口冲突导致的，可以执行dectl status看下容器状态，然后看下mysql容器的日志
docker logs -f --tail=100 mysql-de

user-aqevhug1yvu · 2025 年2 月 11 日 06:59

DataEase 容器运行状态
WARN[0000] /usr/local/dataease/dataease2.0/docker-compose.yml: the attribute version is obsolete, it will be ignored, please remove it to avoid potential confusion
WARN[0000] /usr/local/dataease/dataease2.0/docker-compose-mysql.yml: the attribute version is obsolete, it will be ignored, please remove it to avoid potential confusion
NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS
mysql-de registry.cn-qingdao.aliyuncs.com/dataease/mysql:8.4.0 “docker-entrypoint.s…” mysql-de 27 hours ago Up 22 hours (healthy) 3306/tcp, 33060/tcp

Docker 目录及文件大小 :
3.4G /var/lib/docker

Docker 目录所在磁盘使用情况 :
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/openeuler-root 74G 6.5G 64G 10% /

日志文件大小 :
4.0K /usr/local/dataease/dataease2.0/logs/dataease/sync-task
36K /usr/local/dataease/dataease2.0/logs/dataease
4.0K /usr/local/dataease/dataease2.0/logs/sync-task
4.0K /usr/local/dataease/dataease2.0/logs/

DataEase 运行目录及文件大小 :
939M /usr/local/dataease

DataEase 运行目录使用情况 :
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/openeuler-root 74G 6.5G 64G 10% /

DataEase 服务状态 : 无法访问

==============================
补充一下，我执行docker ps的结果发现有dataease镜像了但显示unhealthy。如下：
[root@lowair-app64 installer-v2.10.5]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
3e48b96f5113 registry.cn-qingdao.aliyuncs.com/dataease/dataease:v2.10.5 “/deployments/run-ja…” 22 hours ago Up 10 minutes (unhealthy) dataease-v2.10.5
af629d182792 registry.cn-qingdao.aliyuncs.com/dataease/mysql:8.4.0 “docker-entrypoint.s…” 28 hours ago Up 22 hours (healthy) 3306/tcp, 33060/tcp mysql-de
[root@lowair-app64 installer-v2.10.5]#

============================
我刚发现在首次安装时提示的内容：
8. 加载 DataEase 镜像
加载镜像 dataease_v2.10.5
加载镜像 mysql_8.4.0
这两个镜像名称与正在运行的镜像名称不一致，因是我自己另外命名，是否要改为一致？

IUUI · 2025 年2 月 11 日 08:41

你自己查看容器报错日志，dataease 的。

user-aqevhug1yvu · 2025 年2 月 12 日 02:15

dataease容器日志是这样：
{“log”:“2025-02-12 09:42:46.826 \u001b[31mWARN \u001b[0;39m — [ {“log”:“2025-02-12 09:42:46.879 \u001b[31mWARN \u001b[0;39m — [ {“log”:“2025-02-12 09:42:46.888 \u001b[31mWARN \u001b[0;39m — [ {“log”:“2025-02-12 09:42:46.936 \u001b[31mWARN \u001b[0;39m — [ {“log”:“2025-02-12 09:42:46.976 \u001b[31mWARN \u001b[0;39m — [ {“log”:“2025-02-12 09:42:46.989 \u001b[31mWARN \u001b[0;39m — [ {“log”:“2025-02-12 09:42:47.068 \u001b[31mWARN \u001b[0;39m — [ {“log”:“2025-02-12 09:42:47.189 \u001b[31mWARN \u001b[0;39m — [ {“log”:“2025-02-12 09:42:47.217 \u001b[31mWARN \u001b[0;39m — [ {“log”:“2025-02-12 09:42:47.265 \u001b[31mWARN \u001b[0;39m — [ {“log”:“2025-02-12 09:42:47.312 \u001b[31mWARN \u001b[0;39m — [ {“log”:“2025-02-12 09:42:47.353 \u001b[31mWARN \u001b[0;39m — [ {“log”:“2025-02-12 09:42:47.371 \u001b[31mWARN \u001b[0;39m — [ {“log”:“2025-02-12 09:42:47.413 \u001b[31mWARN \u001b[0;39m — [ {“log”:“2025-02-12 09:42:47.498 \u001b[31mWARN \u001b[0;39m — [ {“log”:“2025-02-12 09:42:47.633 \u001b[31mWARN \u001b[0;39m — [ {“log”:“2025-02-12 09:42:47.741 \u001b[31mWARN \u001b[0;39m — [ {“log”:“2025-02-12 09:42:47.800 \u001b[31mWARN \u001b[0;39m — [ {“log”:“2025-02-12 09:42:47.813 \u001b[31mWARN \u001b[0;39m — [ {“log”:“2025-02-12 09:42:48.250 \u001b[31mWARN \u001b[0;39m — [ main] \u001b[36mtrationDelegate$BeanPostProcessorChecker\u001b[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.\n”,“stream”:“stdout”,“time”:“2025-02-12T01:42:46.826930893Z”}
main] \u001b[36mtrationDelegate$BeanPostProcessorChecker\u001b[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.\n”,“stream”:“stdout”,“time”:“2025-02-12T01:42:46.890947439Z”}
main] \u001b[36mtrationDelegate$BeanPostProcessorChecker\u001b[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.\n”,“stream”:“stdout”,“time”:“2025-02-12T01:42:46.891009542Z”}
main] \u001b[36mtrationDelegate$BeanPostProcessorChecker\u001b[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.\n”,“stream”:“stdout”,“time”:“2025-02-12T01:42:46.942936685Z”}
main] \u001b[36mtrationDelegate$BeanPostProcessorChecker\u001b[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.\n”,“stream”:“stdout”,“time”:“2025-02-12T01:42:46.97696023Z”}
main] \u001b[36mtrationDelegate$BeanPostProcessorChecker\u001b[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.\n”,“stream”:“stdout”,“time”:“2025-02-12T01:42:46.993925521Z”}
main] \u001b[36mtrationDelegate$BeanPostProcessorChecker\u001b[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.\n”,“stream”:“stdout”,“time”:“2025-02-12T01:42:47.069926598Z”}
main] \u001b[36mtrationDelegate$BeanPostProcessorChecker\u001b[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.\n”,“stream”:“stdout”,“time”:“2025-02-12T01:42:47.196969523Z”}
main] \u001b[36mtrationDelegate$BeanPostProcessorChecker\u001b[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.\n”,“stream”:“stdout”,“time”:“2025-02-12T01:42:47.222060646Z”}
main] \u001b[36mtrationDelegate$BeanPostProcessorChecker\u001b[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.\n”,“stream”:“stdout”,“time”:“2025-02-12T01:42:47.276156781Z”}
main] \u001b[36mtrationDelegate$BeanPostProcessorChecker\u001b[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.\n”,“stream”:“stdout”,“time”:“2025-02-12T01:42:47.319902585Z”}
main] \u001b[36mtrationDelegate$BeanPostProcessorChecker\u001b[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.\n”,“stream”:“stdout”,“time”:“2025-02-12T01:42:47.353430353Z”}
main] \u001b[36mtrationDelegate$BeanPostProcessorChecker\u001b[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.\n”,“stream”:“stdout”,“time”:“2025-02-12T01:42:47.377442848Z”}
main] \u001b[36mtrationDelegate$BeanPostProcessorChecker\u001b[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.\n”,“stream”:“stdout”,“time”:“2025-02-12T01:42:47.416903378Z”}
main] \u001b[36mtrationDelegate$BeanPostProcessorChecker\u001b[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.\n”,“stream”:“stdout”,“time”:“2025-02-12T01:42:47.5076024Z”}
main] \u001b[36mtrationDelegate$BeanPostProcessorChecker\u001b[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.\n”,“stream”:“stdout”,“time”:“2025-02-12T01:42:47.637820317Z”}
main] \u001b[36mtrationDelegate$BeanPostProcessorChecker\u001b[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.\n”,“stream”:“stdout”,“time”:“2025-02-12T01:42:47.749141852Z”}
main] \u001b[36mtrationDelegate$BeanPostProcessorChecker\u001b[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.\n”,“stream”:“stdout”,“time”:“2025-02-12T01:42:47.808966203Z”}
main] \u001b[36mtrationDelegate$BeanPostProcessorChecker\u001b[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.\n”,“stream”:“stdout”,“time”:“2025-02-12T01:42:47.819943474Z”}
main] \u001b[36mtrationDelegate$BeanPostProcessorChecker\u001b[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.\n”,“stream”:“stdout”,“time”:“2025-02-12T01:42:48.250779267Z”}

不知是flyway迁移插件的哪里出的问题？

mysql容器日志是这样：
{“log”:“2025-02-12 01:45:14+00:00 [ERROR] [Entrypoint]: Database is uninitialized and password option is not specified\n”,“stream”:“stderr”,“time”:“2025-02-12T01:45:14.365255852Z”}
{“log”:" You need to specify one of the following as an environment variable:\n",“stream”:“stderr”,“time”:“2025-02-12T01:45:14.365290541Z”}
{“log”:" - MYSQL_ROOT_PASSWORD\n",“stream”:“stderr”,“time”:“2025-02-12T01:45:14.365299585Z”}
{“log”:" - MYSQL_ALLOW_EMPTY_PASSWORD\n",“stream”:“stderr”,“time”:“2025-02-12T01:45:14.365306695Z”}
{“log”:" - MYSQL_RANDOM_ROOT_PASSWORD\n",“stream”:“stderr”,“time”:“2025-02-12T01:45:14.365313947Z”}

mysql我刚执行了一次/bin/bash install.sh就能启动成功，但detaease还是不行
如果想重新安装要怎么卸载，直接执行/bin/bash install.sh是升级。

Janus · 2025 年2 月 12 日 02:55

安装包的 docker 版本是这个，解压的安装包中会有 uninstall 脚本，/bin/sh uninstall.sh

user-aqevhug1yvu · 2025 年2 月 12 日 02:58

好的，docker版本这么高哇，能帮看下上面的dataease日志是什么问题么我看不出来，只能重装么？对了是不是必须按默认路径安装在/opt目录下面

IUUI · 2025 年2 月 12 日 03:51

没有，路径可以自定义，你用户有权限就行。

user-aqevhug1yvu · 2025 年2 月 12 日 08:33

我的系统是openEuler 22.03，支持最高docker是26.1.4已装好；
我先卸载dataease再重装后依然是只能启动mysql的docker，启动不了dataease的docker；
另外发现官方安装文档中的lower_case_table_names=1配置是个错误，不能开启否则无法启动mysql的docker；

以下是dataease的启动日志：
2025-02-12 15:43:41.078 WARN — [ main] ConfigServletWebServerApplicationContext : 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]: Unable to obtain connection from database: Access denied for user ‘root’@‘18.18.18.18’ (using password: YES)

SQL State : 28000
Error Code : 1045
Message : Access denied for user ‘root’@‘18.18.18.18’ (using password: YES)
2025-02-12 15:43:41.109 INFO — [ main] .s.b.a.l.ConditionEvaluationReportLogger :
Error starting ApplicationContext. To display the condition evaluation report re-run your application with ‘debug’ enabled.

意思好像是dataease的docker在启动时无法连接到MySQL数据库，因MySQL拒绝了来自 18.18.18.18 地址的 root 用户的连接。(18.18.18.18是我为了发帖而修改的ip)
我想应该不是权限问题，应该是我安装时把默认密码改了，是不是dataease程序中的默认密码要保持一致，想问下dataease访问数据库的默认密码是多少？

IUUI · 2025 年2 月 12 日 08:53

你看看配置文件，默认密码就在配置文件中。

user-aqevhug1yvu · 2025 年2 月 12 日 08:59

密码我解决了，现在提示这个：

这个问题好像解决了修改了mysql数据目录的权限

现在出现flyway与mysql版本的兼容问题如下日志：

因我的系统是openEuler v22，docker最高只能升到v26.1.4，这个警告不知是否跟docker版本有关系，是否够用，因前面有个技术回复的是v27.2.0

IUUI · 2025 年2 月 13 日 02:11

这个你把数据库中的表都删除之后，然后再启动。

IUUI · 2025 年2 月 13 日 02:11

清空库中的所有的表。

user-aqevhug1yvu · 2025 年2 月 13 日 02:12

看过dataease库中show tables;原本一个表都没有，显示Empty set (0.01 sec)，也就是说初始化时创建dataease库成功了，但没有建过表，下一步该做什么

IUUI · 2025 年2 月 13 日 02:39

你的问题 最可能的原因 是：

磁盘空间不足
InnoDB 表空间损坏
InnoDB 不是默认存储引擎
MySQL 目录权限错误

建议先检查 磁盘空间 (df -h)，然后查看 MySQL 错误日志 (/var/log/mysql/error.log)，如果是 InnoDB 相关错误，可以尝试修复表空间。你自己检查一下你的mysql是不是有什么问题。

user-aqevhug1yvu · 2025 年2 月 13 日 02:42

这些问题我都查过了没有问题，不是这4个问题，我查了mysql的启动日志如下：
{“log”:“2025-02-13T02:33:58.564217Z 0 [Warning] [MY-013242] [Server] --character-set-server: ‘utf8’ is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.\n”,“stream”:“stderr”,“time”:“2025-02-13T02:33:58.566751821Z”}
{“log”:“2025-02-13T02:34:00.623197Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.\n”,“stream”:“stderr”,“time”:“2025-02-13T02:34:00.623425793Z”}
{“log”:“2025-02-13T02:34:00.626894Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location ‘/var/run/mysqld’ in the path is accessible to all OS users. Consider choosing a different directory.\n”,“stream”:“stderr”,“time”:“2025-02-13T02:34:00.627057717Z”}

以下是GPT给我的分析：

关于 --character-set-server 参数的警告：
警告解释：当前 utf8 是 UTF8MB3 的别名，但在未来版本中，它将被作为 UTF8MB4 的别名。UTF8MB4 是对 UTF-8 的更完整支持，它能够存储所有 Unicode 字符，包括 Emoji 等。
建议：建议在 MySQL 配置中使用 utf8mb4 代替 utf8，这样可以确保你使用的是支持所有字符的完整 Unicode 集合。
修改 my.cnf 或 MySQL 配置文件中的 character-set-server 为 utf8mb4：
[mysqld]
character-set-server = utf8mb4
collation-server = utf8mb4_unicode_ci
关于自签名证书的警告：
警告解释：这个警告指出 MySQL 使用的是一个自签名的 CA（证书颁发机构）证书。这意味着 MySQL 使用的是由自己生成的证书，而不是由受信任的第三方机构签发的证书。
建议：如果你的 MySQL 实例需要进行生产环境中的加密通信，建议使用由受信任的 CA 签发的证书，避免自签名证书带来的安全隐患。
关于 --pid-file 的不安全配置警告：
警告解释：这个警告提醒你 /var/run/mysqld 目录对所有操作系统用户都是可访问的，这可能会导致安全风险，特别是如果没有足够的权限控制的话。
建议：为了提高安全性，建议将 --pid-file 设置为一个更为安全的目录，只有 MySQL 用户可以访问。例如，你可以将其设置为 /var/lib/mysql/mysqld.pid 或其他只有 MySQL 用户能访问的目录。

我刚修改了/opt/dataease2.0/conf/my.cnf的配置，将utf8的地方都改为了utf8mb4，又增加了collation-server=utf8mb4_0900_ai_ci项，重启mysql-de后第一个警告就没了，但再启动dataease依然是报之前的flyway与mysql兼容问题，还是没解决

IUUI · 2025 年2 月 13 日 06:06

那是 warn 不是 error，你去看看我们的源码部署的文档，或者是知识库，https://kb.fit2cloud.com/?p=b0c9abc1-2ec8-4301-acac-cff50b2a50be,https://dataease.io/docs/v2/installation/deployment_installation/.

user-aqevhug1yvu · 2025 年2 月 13 日 06:22

是的就是日志只能看到这些warn信息，卡在这一直启动不成功，你的意思是放弃用服务器端安装包来安装，改用源码来打包成jar包在服务器跑是吧，有道理我试试吧，但有没有人遇到我现在这样的问题想尽量不用源码，我们的开发环境都很老怕要花更多时间在源码上，最好是用服务器安装包的方式。