OpenSPG
开发者模式的案例，无法在前端配置llm
Search before asking
- [x] I had searched in the issues and found no similar issues.
Operating system information
Linux
What happened
在点开知识问答时，显示与数据库的连接超时：
Error querying database. Cause: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 62,966,863 milliseconds ago. The last packet sent successfully to the server was 62,966,864 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem. ### The error may exist in class path resource [mapper2/ReasonSessionDOMapper.xml] ### The error may involve com.antgroup.openspgapp.infra.dao.mapper.ReasonSessionDOMapper.selectByExampleWithBLOBs-Inline ### The error occurred while setting parameters ### SQL: SELECT count(0) FROM kg_reason_session WHERE (project_id = ? AND user_id = ?) ### Cause: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 62,966,863 milliseconds ago. The last packet sent successfully to the server was 62,966,864 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem. ; The last packet successfully received from the server was 62,966,863 milliseconds ago. The last packet sent successfully to the server was 62,966,864 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.; nested exception is com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 62,966,863 milliseconds ago. The last packet sent successfully to the server was 62,966,864 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.
我又去添加llm发现无法添加。
How to reproduce
1.测试集为：医疗图谱 2.我事先在全局配置中已经添加了llm，并且我新建一个test的测试，发现llm可用。 3.我在开发者模式下，用后台且按照官方给定步骤上载了医疗图谱（medicine），发现模型配置的ollama以及mass为空，并且我无法添加llm。
Are you willing to submit PR?
- [x] Yes I am willing to submit a PR!
Search before asking
- [x] I had searched in the issues and found no similar issues.
Operating system information
Linux
What happened
在点开知识问答时，显示与数据库的连接超时：
Error querying database. Cause: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 62,966,863 milliseconds ago. The last packet sent successfully to the server was 62,966,864 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem. ### The error may exist in class path resource [mapper2/ReasonSessionDOMapper.xml] ### The error may involve com.antgroup.openspgapp.infra.dao.mapper.ReasonSessionDOMapper.selectByExampleWithBLOBs-Inline ### The error occurred while setting parameters ### SQL: SELECT count(0) FROM kg_reason_session WHERE (project_id = ? AND user_id = ?) ### Cause: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 62,966,863 milliseconds ago. The last packet sent successfully to the server was 62,966,864 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem. ; The last packet successfully received from the server was 62,966,863 milliseconds ago. The last packet sent successfully to the server was 62,966,864 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.; nested exception is com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 62,966,863 milliseconds ago. The last packet sent successfully to the server was 62,966,864 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.
我又去添加llm发现无法添加。
How to reproduce
1.测试集为：医疗图谱 2.我事先在全局配置中已经添加了llm，并且我新建一个test的测试，发现llm可用。 3.我在开发者模式下，用后台且按照官方给定步骤上载了医疗图谱（medicine），发现模型配置的ollama以及mass为空，并且我无法添加llm。
Are you willing to submit PR?
- [x] Yes I am willing to submit a PR!
The error is com.mysql.jdbc.exceptions.jdbc4.CommunicationsExceptio , does your local mysql container still working ?
@caszkgui 感谢您的回复！ 请问我应该怎么确认 mysql 容器是否在工作？手册中我没看到哪一章节提到mysql 容器以及应该如何调整？
@caszkgui 感谢您的回复！ 请问我应该怎么确认 mysql 容器是否在工作？手册中我没看到哪一章节提到mysql 容器以及应该如何调整？
You can test mysql accessibility by telnet release-openspg-mysql 3306 in openspg-server container.
You can test mysql accessibility by
telnet release-openspg-mysql 3306in openspg-server container.
@xiaozhou123-oos ：
Could you test mysql accessibility by telnet release-openspg-mysql 3306 in openspg-server container ？
1、run docker ps |grep openspg and check whether the containers are ready
2、step into openspg-server container by docker exec -it release-openspg-server
3、check accessibility of release-openspg-mysql in release-openspg-mysql by telnet release-openspg-mysql 3306
To my knowledge, strictly following the user manual for operation is unlikely to cause any problems.
您可以通过在 openspg-server 容器中测试 mysql 可访问性。
telnet release-openspg-mysql 3306您可以通过在 openspg-server 容器中测试 mysql 可访问性吗？
telnet release-openspg-mysql 33061、运行并检查容器是否准备好 2、通过 3 步进入 openspg-server 容器、通过 release-openspg-mysql 检查 release-openspg-mysql 的可访问性
docker ps |grep openspg``docker exec -it release-openspg-server``telnet release-openspg-mysql 3306据我所知，严格按照用户手册进行作不太可能造成任何问题。 我在医疗图谱中是可以实现知识问答的，但是我在供应链这一案例无法进行知识问答，我会按照你的方法再测试一下