uptime-kuma: Ping monitoring returns garbled data upon failure
📑 I have found these related issues/pull requests
No related issues found
🛡️ Security Policy
- I agree to have read this project Security Policy
Description
👟 Reproduction steps
A ping monitoring has been configured, and when a fault alarm occurs in the ping monitoring, the returned information is garbled
👀 Expected behavior
Will result in the inability to analyze and determine the specific cause of the malfunction
😓 Actual Behavior
The actual returned code is garbled and cannot determine the specific fault phenomenon
🐻 Uptime-Kuma Version
1.23.12
💻 Operating System and Arch
WindowsServer2012 Installed the relevant environment as required
🌐 Browser
Version 124.0.6367.61 (official version) (64 bit)
🖥️ Deployment Environment
- Runtime: WindowsServer2012 Node.js v20.12.2 npm10.5.0
- Database: sqllite
- Filesystem used to store the database on: ntfs
- number of monitors: 41
📝 Relevant log output
���� Ping IPaddress ���� 56 �ֽڵ�����: ����ʱ�� IPaddress �� Ping ͳ����Ϣ: ���ݰ�: �ѷ��� = 1���ѽ��� = 0����ʧ = 1 (100% ��ʧ)��
About this issue
- Original URL
- State: closed
- Created 2 months ago
- Comments: 16 (11 by maintainers)
I have only made settings for the command prompt. Right click on the command prompt title bar, click on default values, and you can set them in the options. However, this is for the server2012 system, and the settings may be different for other versions of the operating system. Additionally, I did not change all English for the entire operating system.
After testing, this method is feasible and can be used as a reference method. @louislam @CommanderStorm