Timeout when starting blackbox_exporter during tiup deployment

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: tiup部署的时候blackbox_exporter启动超时

| username: 我家有个臭皮崽

When deploying a cluster with tiup, there is a timeout issue when starting the blackbox_exporter component. How can this component be disabled?

2
| username: Kongdom | Original post link

You should remove this configuration.

This is a monitoring node, it is not recommended to disable it.

3
| username: WalterWj | Original post link

First, check the reason why it cannot start. Generally, it is because someone else has deployed similar monitoring on the server, occupying the port.

  1. Either close the monitoring that is not deployed by TiDB.
  2. Or modify the yaml file of tiup cluster and manually add the ignore_exporter parameter to skip the alarm. However, you need to configure ignore_exporter for all components of this IP node. After configuration, the monitoring components will be skipped, resulting in a lack of monitoring for server resource usage, disk, network, etc.
4
| username: ljluestc | Original post link

If you encounter a timeout issue when starting the blackbox_exporter component during the TiUP cluster deployment process, you can skip this component by following these steps:

- component: blackbox_exporter
  host: 172.16.0.3
  port: 9115
  config:
    "collectors": "icmp"

Add a “#” character at the beginning of each line in this section to comment it out.
Deploy the cluster using the TiUP command as usual. The blackbox_exporter component will be skipped during the deployment process.
By following the above steps, you can skip the blackbox_exporter component during the TiUP cluster deployment to avoid timeout issues.

5
| username: 我家有个臭皮崽 | Original post link

Thank you.

6
| username: Kongdom | Original post link

:handshake: :handshake: :handshake: