Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: 5.4.1 升级 6.5
|
username: ffeenn
[Test Environment for TiDB]
[TiDB Version]
[Reproduction Path]
[Encountered Issue: Phenomenon and Impact]
After upgrading to version 6.5, alertmanager fails to start. The logs report that the port is occupied, but no occupied port is found on the server. This is very strange.
[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]
I wonder if any of you who have upgraded to 6.5 have encountered the same issue.
No issues encountered with the 6.1.2 upgrade, everything is normal.
Commenting out the specified listener in the configuration made it work, really clueless.
Enabling DEBUG is also here.
What is the listening port of alertmanager after it starts up? It’s not the original one, right?
The error is 9094, but when commented out, it is 9093. There should be no correlation between them. Can you find the configuration file for starting Altermanager now?
However, the specific reason still hasn’t been found. It’s like having a thorn stuck in your throat, very uncomfortable and frustrating 
After commenting it out, is the Altermanager’s alert service still functioning normally? This is a custom configuration for Altermanager. If not needed, you can comment it out: 自定义监控组件的配置 | PingCAP 文档中心
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
|
username: 
|
username: 
|
username: 
|
username: