Dinky 登录页面可以打开 但是无法登录进去

排查路线

1：查看dinky的dinky.log日志 发现以下报错 java.sql.SQLException: The table ‘dinky_sys_operate_log’ is full 发现 dinky_sys_operate_log表所在的 表空间 / 磁盘 / 引擎限制已满，无法再插入数据

[dinky] 2025-12-23 17:59:33 CST ERROR org.dinky.aop.LogAspect 144 handleCommonLogic - pre doAfterThrowing Exception: org.springframework.jdbc.UncategorizedSQLException: 
### Error updating database.  Cause: java.sql.SQLException: The table 'dinky_sys_operate_log' is full
### The error may exist in org/dinky/mapper/OperateLogMapper.java (best guess)
### The error may involve org.dinky.mapper.OperateLogMapper.insert-Inline
### The error occurred while setting parameters
### SQL: INSERT INTO dinky_sys_operate_log (module_name, business_type, method, request_method, operate_name, operate_user_id, operate_url, operate_ip, operate_param, json_result, status, operate_time) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
### Cause: java.sql.SQLException: The table 'dinky_sys_operate_log' is full
; uncategorized SQLException; SQL state [HY000]; error code [1114]; The table 'dinky_sys_operate_log' is full; nested exception is java.sql.SQLException: The table 'dinky_sys_operate_log' is full
	at org.mybatis.spring.MyBatisExceptionTranslator.translateExceptionIfPossible(MyBatisExceptionTranslator.java:93) ~[mybatis-spring-2.1.2.jar:2.1.2]
	at org.mybatis.spring.SqlSessionTemplate$SqlSessionInterceptor.invoke(SqlSessionTemplate.java:439) ~[mybatis-spring-2.1.2.jar:2.1.2]
	at com.sun.proxy.$Proxy163.insert(Unknown Source) ~[?:?]
	at org.mybatis.spring.SqlSessionTemplate.insert(SqlSessionTemplate.java:272) ~[mybatis-spring-2.1.2.jar:2.1.2]
	at com.baomidou.mybatisplus.core.override.MybatisMapperMethod.execute(MybatisMapperMethod.java:59) ~[mybatis-plus-core-3.5.7.jar:3.5.7]
	at com.baomidou.mybatisplus.core.override.MybatisMapperProxy$PlainMethodInvoker.invoke(MybatisMapperProxy.java:152) ~[mybatis-plus-core-3.5.7.jar:3.5.7]
	at com.baomidou.mybatisplus.core.override.MybatisMapperProxy.invoke(MybatisMapperProxy.java:89) ~[mybatis-plus-core-3.5.7.jar:3.5.7]
	at com.sun.proxy.$Proxy277.insert(Unknown Source) ~[?:?]
	at org.dinky.service.impl.OperateLogServiceImpl.saveLog(OperateLogServiceImpl.java:40) ~[dinky-admin-1.2.4.jar:?]
	at org.dinky.service.impl.OperateLogServiceImpl$$FastClassBySpringCGLIB$$23c42a01.invoke(<generated>) ~[dinky-admin-1.2.4.jar:?]
	at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218) ~[spring-core-5.3.31.jar:5.3.31]
	at org.springframework.aop.framework.CglibAopProxy.invokeMethod(CglibAopProxy.java:386) ~[spring-aop-5.3.31.jar:5.3.31]
	at org.springframework.aop.framework.CglibAopProxy.access$000(CglibAopProxy.java:85) ~[spring-aop-5.3.31.jar:5.3.31]
	at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:703) ~[spring-aop-5.3.31.jar:5.3.31]

2 /dev/mapper/centos-root 磁盘目录已经被打满 想起来昨天在kafka里面刷了两千万条的测试数据

df -h
du -sh /* 2>/dev/null | sort -hr | head -n 20


根分区 / 已经 100% 满了
而 MySQL / Dinky 默认都在根分区（/var/lib/mysql、/var/log、/opt/dinky 等）
所以：
❌ MySQL 无法再向 dinky_sys_operate_log 写任何一条数据
❌ Dinky 的 AOP 日志 insert 失败
❌ 所有页面、接口连锁报错

3 查看kafka日志数据所属目录 kafka 的数据不在 /home，而是在 /var /var 占了 41G，把 / 根分区打满了

解决方案： 先停止CDH中所有的服务 然后删除旧有kafka数据目录的数据 删除具体的Topic 三台节点都需要删除kafka数据目录

解决方案： 修改kafka数据目录存储地址 修改到home目录下 /home/data/kafka/logs/data 三台机器都需要建立这个目录

修改成功

结果 Dinky成功登录