Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] After calling the group message history list interface, the openim-rpc-msg service hangs up. #2840

Open
leejunl opened this issue Nov 7, 2024 · 4 comments
Assignees
Labels
bug Categorizes issue or PR as related to a bug.

Comments

@leejunl
Copy link

leejunl commented Nov 7, 2024

OpenIM Server Version

3.8.1

Operating System and CPU Architecture

Linux (AMD)

Deployment Method

Source Code Deployment

Bug Description and Steps to Reproduce

1
2

Screenshots Link

No response

@leejunl leejunl added the bug Categorizes issue or PR as related to a bug. label Nov 7, 2024
@OpenIM-Robot OpenIM-Robot changed the title [BUG] 调用群消息历史列表接口后,导致openim-rpc-msg 这个服务挂掉 [BUG] After calling the group message history list interface, the openim-rpc-msg service hangs up. Nov 7, 2024
@OpenIM-Robot
Copy link

Hello! Thank you for filing an issue.

If this is a bug report, please include relevant logs to help us debug the problem.

Join slack 🤖 to connect and communicate with our developers.

@skiffer-git
Copy link
Member

Give mage check a run to check it out.

@OpenIM-Robot
Copy link

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


Give mage check a run to check it out.

@withchao
Copy link
Contributor

A large number of errors in the log are caused by non-existent records. When calling SearchMessage, it crashed, and the specific reason was not shown in the log. Under normal circumstances, administrator calls will not cause errors such as non-existent records. Have you modified the database yourself?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

4 participants