Failed to start: 10.142.100.84 blackbox_exporter-9115.service

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

Original topic: failed to start: 10.142.100.84 blackbox_exporter-9115.service

| username: 林中小草

[TiDB Usage Environment] Production Environment / Testing / Poc
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Problem Phenomenon and Impact]
When executing cluster machine checks, the following exception occurred and could not be fixed through repair:
epoll-exclusive Fail epoll exclusive is not supported

According to previous posts, this does not affect and can be ignored, said to be an operating system kernel issue.
Checked the operating system version as follows:
Linux 3.10.0-327.el7.x86_64

When starting the cluster, the following exception occurred:
Error: failed to start: 10.142.100.84 blackbox_exporter-9115.service, please check the instance’s log() for more detail.: timed out waiting for port 9115 to be started after 2m0s

Checked the debug log of the machine running tiup as follows, not much information:
2022-11-30T17:31:02.584+0800 DEBUG retry error {“error”: “operation timed out after 2m0s”}
2022-11-30T17:31:02.584+0800 DEBUG TaskFinish {“task”: “StartCluster”, “error”: “failed to start: 10.142.100.84 blackbox_exporter-9115.service, please check the instance’s log() for more detail.: timed out waiting for port 9115 to be started after 2m0s”, “errorVerbose”: “timed out waiting for port 9115 to be started after 2m0s\ngithub.com/pingcap/tiup/pkg/cluster/module.(*WaitFor).Execute\n\tgithub.com/pingcap/tiup/pkg/cluster/module/wait_for.go:91\ngithub.com/pingcap/tiup/pkg/cluster/spec.PortStarted\n\tgithub.com/pingcap/tiup/pkg/cluster/spec/instance.go:119\ngithub.com/pingcap/tiup/pkg/cluster/operation.systemctlMonitor.func1\n\tgithub.com/pingcap/tiup/pkg/cluster/operation/action.go:336\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.0.0-20220819030929-7fc1605a5dde/errgroup/errgroup.go:75\nruntime.goexit\n\truntime/asm_amd64.s:1594\nfailed to start: 10.142.100.84 blackbox_exporter-9115.service, please check the instance’s log() for more detail.”}
2022-11-30T17:31:02.584+0800 INFO Execute command finished {“code”: 1, “error”: “failed to start: 10.142.100.84 blackbox_exporter-9115.service, please check the instance’s log() for more detail.: timed out waiting for port 9115 to be started after 2m0s”, “errorVerbose”: “timed out waiting for port 9115 to be started after 2m0s\ngithub.com/pingcap/tiup/pkg/cluster/module.(*WaitFor).Execute\n\tgithub.com/pingcap/tiup/pkg/cluster/module/wait_for.go:91\ngithub.com/pingcap/tiup/pkg/cluster/spec.PortStarted\n\tgithub.com/pingcap/tiup/pkg/cluster/spec/instance.go:119\ngithub.com/pingcap/tiup/pkg/cluster/operation.systemctlMonitor.func1\n\tgithub.com/pingcap/tiup/pkg/cluster/operation/action.go:336\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.0.0-20220819030929-7fc1605a5dde/errgroup/errgroup.go:75\nruntime.goexit\n\truntime/asm_amd64.s:1594\nfailed to start: 10.142.100.84 blackbox_exporter-9115.service, please check the instance’s log() for more detail.”}

Through the command sudo journalctl -u blackbox_exporter-9115, the following exception was seen:
Failed at step CAPABILITIES spawning /bin/bash: Invalid argument

[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]

| username: TI表弟 | Original post link

Ignore this issue, it doesn’t matter. As long as the node_exporter-9100 process exists, it’s fine.

| username: 林中小草 | Original post link

However, starting it this way does not output a password.

| username: TI表弟 | Original post link

tiup cluster display tidb-cluster-test

Check if the main nodes are functioning properly?

| username: 林中小草 | Original post link

I didn’t see any anomalies, and I could see all the node information.

| username: TI表弟 | Original post link

So your question is whether there is no root login password?

| username: 林中小草 | Original post link

Not sure if the cluster is functioning properly? You can modify it without a password.

| username: 林中小草 | Original post link

This is just the display

| username: 林中小草 | Original post link

| username: TI表弟 | Original post link

Ignore this issue, don’t worry about it. I upgraded to TiDB 6.1.2 and ultimately ignored these problems.

| username: dba-kit | Original post link

It looks like your operating system is still CentOS 7.2, which might prevent the use of certain kernel features. Is it possible for you to upgrade to 7.3 or 8.X?

| username: 我是咖啡哥 | Original post link

I agree with this expert’s opinion. If some underlying environments are not set up according to recommendations, some issues can be very difficult to troubleshoot.

| username: 裤衩儿飞上天 | Original post link

Was the cluster upgraded from a previous version or directly installed as the current version?

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.