Mysql使用报错not suittable
-
检查了url格式是正确的
用的本地127.0.0.1:3306
既然说是没有驱动...那就什么都不用了
直接用了jdk里面的
崩
用原生的也不行 显示 not suittable
网上的办法如 bin/ext放入驱动或者论坛中plugin丢驱动都尝试了
就是不加载jdbc 是构建问题还是其他?
使用的是mirai的插件 -
- 你没带mysql的jdbc
- 不建议使用bugjson
-
此回复已被删除! -
@Karlatemp
还是有些问题...
检查了url感觉没问题...是不是不应该用HikariPC -
说了你忘带mysql的jdbc驱动
-
你忘带mysql的jdbc驱动
hikaricp只是连接池而已并不是驱动 -
此回复已被删除! -
完整系统日志咧(config/Console/Logger.yml),还有console版本多少,还有为啥不用Ctrl CV粘贴日志而是用截图
-
@Karlatemp ```
[91m2022-07-01 02:05:27 W/stderr: java.sql.SQLException: No suitable driver found for jdbc:mysql://localhost:3306/plugins
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at java.sql/java.sql.DriverManager.getConnection(Unknown Source)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at java.sql/java.sql.DriverManager.getConnection(Unknown Source)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at DataChech-1.0-SNAPSHOT.mirai.jar//org.moo.repository.MysqlData.getConn(MysqlData.java:26)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at DataChech-1.0-SNAPSHOT.mirai.jar//org.moo.repository.MysqlData.getPoints(MysqlData.java:36)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at DataChech-1.0-SNAPSHOT.mirai.jar//org.moo.DataChech.set(DataChech.java:29)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at DataChech-1.0-SNAPSHOT.mirai.jar//org.moo.DataChech.onEnable(DataChech.java:23)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at net.mamoe.mirai.console.internal.plugin.JvmPluginInternal.internalOnEnable$mirai_console(JvmPluginInternal.kt:119)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at net.mamoe.mirai.console.internal.plugin.BuiltInJvmPluginLoaderImpl.enable(BuiltInJvmPluginLoaderImpl.kt:262)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at net.mamoe.mirai.console.internal.plugin.BuiltInJvmPluginLoaderImpl.enable(BuiltInJvmPluginLoaderImpl.kt:34)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at net.mamoe.mirai.console.plugin.jvm.JvmPluginLoader$BuiltIn.enable(JvmPluginLoader.kt)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at net.mamoe.mirai.console.plugin.jvm.JvmPluginLoader$BuiltIn.enable(JvmPluginLoader.kt:50)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at net.mamoe.mirai.console.plugin.PluginManager.enablePlugin(PluginManager.kt:173)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at net.mamoe.mirai.console.internal.plugin.PluginManagerImpl.enableAllLoadedPlugins$mirai_console(PluginManagerImpl.kt:183)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at net.mamoe.mirai.console.internal.MiraiConsoleImplementationBridge.doStart$mirai_console(MiraiConsoleImplementationBridge.kt:231)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at net.mamoe.mirai.console.MiraiConsoleImplementation$Companion.start(MiraiConsoleImplementation.kt:444)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader.startAsDaemon(MiraiConsoleTerminalLoader.kt:159)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader.startAsDaemon$default(MiraiConsoleTerminalLoader.kt:158)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader.main(MiraiConsoleTerminalLoader.kt:46)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at java.base/java.lang.reflect.Method.invoke(Unknown Source)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at org.itxtech.mcl.Utility.bootJars(Utility.java:89)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at org.itxtech.mcl.Utility.bootJars(Utility.java:79)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at org.itxtech.mcl.Utility.bootMirai(Utility.java:101)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at org.itxtech.mcl.module.builtin.Boot.boot(Boot.java:109)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at org.itxtech.mcl.module.ModuleManager.phaseBoot(ModuleManager.java:148)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at org.itxtech.mcl.Loader.lambda$start$4(Loader.java:189)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at org.itxtech.mcl.Loader.tryCatching(Loader.java:146)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at org.itxtech.mcl.Loader.start(Loader.java:189)
[0m[m
[91m2022-07-01 02:05:27 W/stderr: at org.itxtech.mcl.Loader.main(Loader.java:79)
[0m[m
[92m2022-07-01 02:05:27 I/stdout: 0
[0m[m
[92m2022-07-01 02:05:27 I/HuYanSession: SessionData 已加载![0m[m
[91m2022-07-01 02:05:27 W/net.mamoe.mirai-api-http: USING INITIAL KEY, please edit the key[0m[m
[92m2022-07-01 02:05:27 I/Mirai HTTP API: ********************************************************[0m[m
[92m2022-07-01 02:05:27 I/http adapter: >>> [http adapter] is listening at http://localhost:8080[0m[m
[92m2022-07-01 02:05:27 I/Mirai HTTP API: Http api server is running with verifyKey: INITKEYamZpzC95[0m[m
[92m2022-07-01 02:05:27 I/Mirai HTTP API: adaptors: [http][0m[m
[92m2022-07-01 02:05:27 I/Mirai HTTP API: ********************************************************[0m[m
[92m2022-07-01 02:05:27 I/MCL Addon: iTXTech MCL Version: 2.1.0-71ec418[0m[m
[91m2022-07-01 02:05:27 W/MCL Addon: iTXTech Soyuz 未安装,Soyuz MCL Handler 特性已禁用[0m[m
[92m2022-07-01 02:05:27 I/main: 4 plugin(s) enabled.[0m[m控制台不知道为什么无法选中 这段是log里面的提示
-
@Moo-OvO 已经解决了 虽然不知道怎么解决的
只是虚拟机环境换成本机环境随便跑了下 然后再丢vps就成功了 悲