Bug: Log file appear garbled

[luhaoling]

What happened?

The log file have garbled.
The file name is vim OpenIM.log.all.2023-11-15.
The garbled is here:
2023-11-15 16:11:15.808 ^[[37mDEBUG^[[0m ^[[37m[PID:23207]^[[0m ^[[37mmsgGateway^[[0m [msggateway/hub_server.go:140] push user not online {"operationID": "1646445464564", "userID": "1223"}
2023-11-15 16:11:15.808 ^[[37mDEBUG^[[0m ^[[37m[PID:23207]^[[0m ^[[37mmsgGateway^[[0m [msggateway/hub_server.go:140] push user not online {"operationID": "1646445464564", "userID": "1224"}
2023-11-15 16:11:15.808 ^[[34mINFO^[[0m ^[[34m[PID:23207]^[[0m ^[[34mmsgGateway^[[0m [mw/rpc_server_interceptor.go:112] rpc server resp {"operationID": "1646445464564", "funcName": "/OpenIMServer.msggateway.msgGateway/SuperGroupOnlineBatchPushOneMsg", "resp": "singlePushResult:{userID:"122"} singlePushResult:{userID:"1223"} singlePushResult:{userID:"1224"}"}
2023-11-15 16:11:15.808 ^[[34mINFO^[[0m ^[[34m[PID:22095]^[[0m ^[[34mpush^[[0m [mw/rpc_client_interceptor.go:55] rpc client resp {"operationID": "1646445464564", "funcName": "/OpenIMServer.msggateway.msgGateway/SuperGroupOnlineBatchPushOneMsg", "resp": "singlePushResult:{userID:"122"} singlePushResult:{userID:"1223"} singlePushResult:{userID:"1224"}"}
2023-11-15 16:11:15.808 ^[[37mDEBUG^[[0m ^[[37m[PID:22095]^[[0m ^[[37mpush^[[0m [push/push_to_client.go:277] push result {"operationID": "1646445464564", "reply": "singlePushResult:{userID:"122"} singlePushResult:{userID:"1223"} singlePushResult:{userID:"1224"}"}
2023-11-15 16:11:15.808 ^[[37mDEBUG^[[0m ^[[37m[PID:22095]^[[0m ^[[37mpush^[[0m [push/push_to_client.go:198] get conn and online push success {"operationID": "1646445464564", "result": [{"userID":"122","resp":null,"onlinePush":false},{"userID":"1223","resp":null,"onlinePush":false},{"userID":"1224","resp":null,"onlinePush":false}], "msg": "sendID:"1223" recvID:"xadaxa12" groupID:"xadaxa12" clientMsgID:"280e3a0eef7ce535901697d59d024164" serverMsgID:"3bbd56f83148ab2b1c88bc4c8b4c2a3e" sessionType:3 msgFrom:200 contentType:1501 content:"{\"detail\":\"{\\\"group\\\":{\\\"groupID\\\":\\\"xadaxa12\\\",\\\"groupName\\\":\\\"yourg group name\\\",\\\"notification\\\":\\\"notification\\\",\\\"introduction\\\":\\\"introduction\\\",\\\"faceURL\\\":\\\"faceURL url\\\",\\\"ownerUserID\\\":\\\"1223\\\",\\\"createTime\\\":1700035875634,\\\"memberCount\\\":3,\\\"ex\\\":\\\"ex\\\",\\\"status\\\":0,\\\"creatorUserID\\\":\\\"\\\",\\\"groupType\\\":2,\\\"needVerification\\\":0,\\\"lookMemberInfo\\\":0,\\\"applyMemberFriend\\\":0,\\\"notificationUpdateTime\\\":0,\\\"notificationUserID\\\":\\\"\\\"},\\\"opUser\\\":{\\\"groupID\\\":\\\"xadaxa12\\\",\\\"userID\\\":\\\"1223\\\",\\\"roleLevel\\\":100,\\\"joinTime\\\":1700035875635,\\\"nickname\\\":\\\"yourNickname\\\",\\\"faceURL\\\":\\\"\\\",\\\"appMangerLevel\\\":1,\\\"joinSource\\\":2,\\\"operatorUserID\\\":\\\"1223\\\",\\\"ex\\\":\\\"\\\",\\\"muteEndTime\\\":0,\\\"inviterUserID\\\":\\\"1223\\\"},\\\"memberList\\\":[{\\\"groupID\\\":\\\"xadaxa12\\\",\\\"userID\\\":\\\"1223\\\",\\\"roleLevel\\\":100,\\\"joinTime\\\":1700035875635,\\\"nickname\\\":\\\"yourNickname\\\",\\\"faceURL\\\":\\\"\\\",\\\"appMangerLevel\\\":1,\\\"joinSource\\\":2,\\\"operatorUserID\\\":\\\"1223\\\",\\\"ex\\\":\\\"\\\",\\\"muteEndTime\\\":0,\\\"inviterUserID\\\":\\\"1223\\\"}],\\\"operationTime\\\":1700035875634,\\\"groupOwnerUser\\\":{\\\"groupID\\\":\\\"xadaxa12\\\",\\\"userID\\\":\\\"1223\\\",\\\"roleLevel\\\":100,\\\"joinTime\\\":1700035875635,\\\"nickname\\\":\\\"\\\",\\\"faceURL\\\":\\\"\\\",\\\"appMangerLevel\\\":1,\\\"joinSource\\\":2,\\\"operatorUserID\\\":\\\"1223\\\",\\\"ex\\\":\\\"\\\",\\\"muteEndTime\\\":0,\\\"inviterUserID\\\":\\\"1223\\\"}}\"}" sendTime:1700035875648 createTime:1700035875648 options:{key:"conversationUpdate" value:false} options:{key:"history" value:false} options:{key:"isNotNotification" value:false} options:{key:"isSendMsg" value:true} options:{key:"notPrivate" value:false} options:{key:"offlinePush" value:false} options:{key:"persistent" value:false} options:{key:"reactionFromCache" value:false} options:{key:"senderConversationUpdate" value:false} options:{key:"senderNotificationPush" value:false} options:{key:"senderSync" value:false} options:{key:"unreadCount" value:false} offlinePushInfo:{}"}

What did you expect to happen?

Repair it.

How can we reproduce it (as minimally and precisely as possible)?

git clone the server project, and run it.

Anything else we need to know?

No response

version

```console $ {name} version # paste output here ```

Cloud provider

OS version

```console # On Linux: $ cat /etc/os-release # paste output here $ uname -a # paste output here # On Windows: C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture # paste output here ```

Install tools

[cubxxw]

Based on the provided information, it seems that the log file appears garbled in the OpenIM application. To resolve this issue, you can try the following steps:

Check the encoding of the log file: Ensure that the log file is encoded correctly, preferably using UTF-8 encoding. Garbled characters can occur if the encoding is not set correctly.

Verify the log file format: Confirm that the log file format is compatible with the OpenIM application. It's possible that the log file format is not supported, leading to garbled output.

Update dependencies: Make sure that all dependencies and libraries used by OpenIM are up to date. Sometimes, compatibility issues between different versions can cause garbled log output.

Validate the log file content: Double-check the content of the log file for any irregularities or unexpected characters. It's possible that there are specific entries or characters causing the garbled output.

[kubbot]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[cubxxw]

/invite

[kubbot]

We value close connections with our users, developers, and contributors here at Open-IM-Server. With a large community and maintainer team, we're always here to help and support you. Whether you're looking to join our community or have any questions or suggestions, we welcome you to get in touch with us.

Our most recommended way to get in touch is through Slack. Even if you're in China, Slack is usually not blocked by firewalls, making it an easy way to connect with us. Our Slack community is the ideal place to discuss and share ideas and suggestions with other users and developers of Open-IM-Server. You can ask technical questions, seek help, or share your experiences with other users of Open-IM-Server.

In addition to Slack, we also offer the following ways to get in touch:

• We also have Slack channels for you to communicate and discuss. To join, visit https://slack.com/ and join our 👀 Open-IM-Server slack team channel.
• Get in touch with us on Gmail. If you have any questions or issues that need resolving, or any suggestions and feedback for our open source projects, please feel free to contact us via email.
• Read our blog. Our blog is a great place to stay up-to-date with Open-IM-Server projects and trends. On the blog, we share our latest developments, tech trends, and other interesting information.
• Add Wechat and indicate that you are a user or developer of Open-IM-Server. We will process your request as soon as possible.

[kubbot]

🤖 Auto-closing issue, if you still need help please reopen the issue or ask for help in the community above