没有解决。没有找到报错” Schema dataease contains a failed migration to version“，不过确实是缺少数据，但是我不知道执行哪个SQL。
log中error下的报错
2023-11-30 15:41:42,470 [qtp1101786725-303] ERROR i.d.c.handler.GlobalExceptionHandler 53 - Fail to proceed /chart/view/getData/ad9fffea-8f4e-11ee-be15-fefcfe92f9fe/ccddc2b6-208b-4f2e-ac1b-4525209ba789
java.lang.RuntimeException: 无效数据源
2023-11-30 15:41:42,467 [qtp1101786725-303] ERROR i.d.a.aop.DePermissionProxyHandler 167 - Method[proxyAround][无效数据源]
java.lang.RuntimeException: 无效数据源
源码部署，显示无效数据源。
数据源界面校验，报错：
Datasource is invalid: Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
后端日志报错：
2023-11-30 16:54:04,073 WARN org.eclipse.jetty.server.HttpChannel: 677 - /dataset/table/getPreviewData/1/1000
org.springframework.web.util.NestedServletException: Request processing failed; nested exception is java.lang.RuntimeException: 无效数据源
发现之前是没有在数据源界面设置服务器地址，设置后数据源demo校验成功。但是数据集仍然不能展示，数据集报错为
Error querying database. Cause: java.sql.SQLSyntaxErrorException: Unknown column ‘v_auth_model.level’ in ‘field list’ ### The error may exist in io/dataease/base/mapper/ext/ExtVAuthModelMapper.xml ### The error may involve defaultParameterMap ### The error occurred while setting parameters ### SQL: SELECT v_auth_model.id, v_auth_model.name, v_auth_model.label, v_auth_model.pid, v_auth_model.node_type, v_auth_model.model_type, v_auth_model.model_inner_type, v_auth_model.auth_type, v_auth_model.create_by, v_auth_model.level, v_auth_model.mode, v_auth_model.data_source_id, authInfo.PRIVILEGES AS privileges FROM ( SELECT GET_V_AUTH_MODEL_ID_P_USE ( ?, ? ) cids ) t, v_auth_model LEFT JOIN ( SELECT auth_source, group_concat( DISTINCT sys_auth_detail.privilege_extend ) AS privileges FROM ( sys_auth LEFT JOIN sys_auth_detail ON (( sys_auth.id = sys_auth_detail.auth_id ))) WHERE sys_auth_detail.privilege_value = 1 AND sys_auth.auth_source_type = ? AND ( ( sys_auth.auth_target_type = ‘dept’ AND sys_auth.auth_target IN ( SELECT dept_id FROM sys_user WHERE user_id = ? ) ) OR ( sys_auth.auth_target_type = ‘user’ AND sys_auth.auth_target = ? ) OR ( sys_auth.auth_target_type = ‘role’ AND sys_auth.auth_target IN ( SELECT role_id FROM sys_users_roles WHERE user_id = ? ) ) ) GROUP BY sys_auth.auth_source ) authInfo ON v_auth_model.id = authInfo.auth_source WHERE FIND_IN_SET( v_auth_model.id, cids ) and v_auth_model.model_type = ? ORDER BY v_auth_model.node_type desc, CONVERT(v_auth_model.label using gbk) asc ### Cause: java.sql.SQLSyntaxErrorException: Unknown column ‘v_auth_model.level’ in ‘field list’ ; bad SQL grammar []; nested exception is java.sql.SQLSyntaxErrorException: Unknown column ‘v_auth_model.level’ in ‘field list’
仪表盘可以正常使用
文档没有解决我的问题，错误是因为表 v_auth_model 中缺少一个名为 level 的列。这个数据该去哪里找？
这个不是个表，是个视图。
每次版本有新的 SQL 都会在这个位置有个新的 SQL 文件，会在程序启动时自动执行。
这个表会记录自动执行是否成功，可以对照自己的记录看下，是不是哪里执行有问题了。这个文章也有相关说明可以参考：【常见问题】DataEase Flyway 报错解决方法 - FIT2CLOUD 知识库
v1.8 确实太老了，建议使用 v1.18 分支。
用docker安装1.18.12版本了，安装最后出现报错：
dataease Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. 0.0s
dependency failed to start: container mysql exited (1)
gpt分析为：“这个错误表明 Docker 在启动容器时无法找到 swap 限制的内核支持或者 cgroup 未挂载。这可能会导致容器无法正常启动。”
但是没有确切的给出解决方法，我该如何解决？
执行下 docker logs -f mysql --tail=300 看看，上面的那个报错应该没有太大影响。
执行后 docker logs -f mysql --tail=300，报错：
@bi:/var/lib/mysql$ docker logs -f mysql --tail=300
2023-12-06 03:26:16+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.1.0-1.el8 started.
2023-12-06 03:26:17+00:00 [Note] [Entrypoint]: Switching to dedicated user ‘mysql’
2023-12-06 03:26:17+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.1.0-1.el8 started.
2023-12-06 03:26:17+00:00 [Note] [Entrypoint]: Initializing database files
2023-12-06T03:26:17.247096Z 0 [System] [MY-015017] [Server] MySQL Server Initialization - start.
2023-12-06T03:26:17.249203Z 0 [Warning] [MY-011068] [Server] The syntax ‘–skip-host-cache’ is deprecated and will be removed in a future release. Please use SET GLOBAL host_cache_size=0 instead.
2023-12-06T03:26:17.249344Z 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 8.1.0) initializing of server in progress as process 81
2023-12-06T03:26:17.251286Z 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.
2023-12-06T03:26:17.251336Z 0 [ERROR] [MY-010457] [Server] --initialize specified but the data directory has files in it. Aborting.
2023-12-06T03:26:17.251343Z 0 [ERROR] [MY-013236] [Server] The designated data directory /var/lib/mysql/ is unusable. You can remove all files that the server added to it.
2023-12-06T03:26:17.251403Z 0 [ERROR] [MY-010119] [Server] Aborting
2023-12-06T03:26:17.251817Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.1.0) MySQL Community Server - GPL.
2023-12-06T03:26:17.252051Z 0 [System] [MY-015018] [Server] MySQL Server Initialization - end.
我尝试过
sudo rm -rf /var/lib/mysql/*
sudo mysqld --initialize --datadir=/var/lib/mysql --user=当前用户名
执行成功，但是执行 docker logs -f mysql --tail=300后，还是报相同错误
将 /opt/dataease/data/mysql 下的东西删除了试试
没有解决，并且执行dectl reload后/opt/dataease/data/mysql文件夹又出现了。
执行dectl status
@bi:/opt/dataease/data/mysql$ sudo dectl status
DataEase 容器运行状态
NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS
WARNING: No swap limit support
Docker 目录及文件大小 :
2.7G /var/lib/docker
Docker 目录所在磁盘使用情况 :
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/ubuntu–vg-ubuntu–lv 105G 23G 77G 23% /
日志文件大小 :
4.0K /opt/dataease/logs/fe
4.0K /opt/dataease/logs/be
8.0K /opt/dataease/logs/
DataEase 运行目录及文件大小 :
320M /opt
DataEase 运行目录使用情况 :
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/ubuntu–vg-ubuntu–lv 105G 23G 77G 23% /
DataEase 服务状态 : 正在启动（一直处于启动状态）
执行docker logs -f mysql --tail=300，报错为
2023-12-06T05:57:30.934255Z 1 [ERROR] [MY-012576] [InnoDB] Unable to create temporary file inside “/tmp”; errno: 13
2023-12-06T05:57:30.934313Z 1 [ERROR] [MY-012929] [InnoDB] InnoDB Database creation was aborted with error Generic error. You may need to delete the ibdata1 file before trying to start up again.
2023-12-06T05:57:30.934574Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2023-12-06T05:57:30.934607Z 0 [ERROR] [MY-013236] [Server] The designated data directory /var/lib/mysql/ is unusable. You can remove all files that the server added to it.
2023-12-06T05:57:30.934732Z 0 [ERROR] [MY-010119] [Server] Aborting
我尝试过
sudo chmod 1777 /tmp
sudo mysqld --initialize --datadir=/var/lib/mysql --user=mysql
报错
2023-12-06T06:06:48.109245Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2023-12-06T06:06:48.111701Z 0 [ERROR] Could not open file ‘/var/log/mysql/error.log’ for error logging: Permission denied
2023-12-06T06:06:48.111738Z 0 [ERROR] Aborting
2.0, .1.18, 1.8Linux单机都没有部署成功，只有之前Windows源码部署1.8成功
执行 umask 0022 && dectl uninstall && rm -rf /opt/dataease，
然后再重新安装试试