tidb - how to solve node_exporter up timeout
up vote
0
down vote
favorite
I get this output when using tidb node_exporter up:
fatal: [tidb@172.17.3.226]: FAILED! => "changed": false, "elapsed": 309, "msg": "Timeout when waiting for search string 200 OK in tidb@172.17.3.226:9100"
fatal: [tidb@172.17.3.225]: FAILED! => "changed": false, "elapsed": 309, "msg": "Timeout when waiting for search string 200 OK in tidb@172.17.3.225:9100"
fatal: [tidb@172.17.3.227]: FAILED! => "changed": false, "elapsed": 309, "msg": "Timeout when waiting for search string 200 OK in tidb@172.17.3.227:9100"
fatal: [tidb@172.17.3.228]: FAILED! => "changed": false, "elapsed": 309, "msg": "Timeout when waiting for search string 200 OK in tidb@172.17.3.228:9100"
How would I resolve this?
tidb
edited Nov 9 at 13:00
Maccath
2,48531739
asked Nov 9 at 2:34
Aaron
11
add a comment |
up vote
0
down vote
favorite
I get this output when using tidb node_exporter up:
fatal: [tidb@172.17.3.226]: FAILED! => "changed": false, "elapsed": 309, "msg": "Timeout when waiting for search string 200 OK in tidb@172.17.3.226:9100"
fatal: [tidb@172.17.3.225]: FAILED! => "changed": false, "elapsed": 309, "msg": "Timeout when waiting for search string 200 OK in tidb@172.17.3.225:9100"
fatal: [tidb@172.17.3.227]: FAILED! => "changed": false, "elapsed": 309, "msg": "Timeout when waiting for search string 200 OK in tidb@172.17.3.227:9100"
fatal: [tidb@172.17.3.228]: FAILED! => "changed": false, "elapsed": 309, "msg": "Timeout when waiting for search string 200 OK in tidb@172.17.3.228:9100"
How would I resolve this?
tidb
edited Nov 9 at 13:00
Maccath
2,48531739
asked Nov 9 at 2:34
Aaron
11
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I get this output when using tidb node_exporter up:
fatal: [tidb@172.17.3.226]: FAILED! => "changed": false, "elapsed": 309, "msg": "Timeout when waiting for search string 200 OK in tidb@172.17.3.226:9100"
fatal: [tidb@172.17.3.225]: FAILED! => "changed": false, "elapsed": 309, "msg": "Timeout when waiting for search string 200 OK in tidb@172.17.3.225:9100"
fatal: [tidb@172.17.3.227]: FAILED! => "changed": false, "elapsed": 309, "msg": "Timeout when waiting for search string 200 OK in tidb@172.17.3.227:9100"
fatal: [tidb@172.17.3.228]: FAILED! => "changed": false, "elapsed": 309, "msg": "Timeout when waiting for search string 200 OK in tidb@172.17.3.228:9100"
How would I resolve this?
tidb
edited Nov 9 at 13:00
Maccath
2,48531739
asked Nov 9 at 2:34
Aaron
11
I get this output when using tidb node_exporter up:
fatal: [tidb@172.17.3.226]: FAILED! => "changed": false, "elapsed": 309, "msg": "Timeout when waiting for search string 200 OK in tidb@172.17.3.226:9100"
fatal: [tidb@172.17.3.225]: FAILED! => "changed": false, "elapsed": 309, "msg": "Timeout when waiting for search string 200 OK in tidb@172.17.3.225:9100"
fatal: [tidb@172.17.3.227]: FAILED! => "changed": false, "elapsed": 309, "msg": "Timeout when waiting for search string 200 OK in tidb@172.17.3.227:9100"
fatal: [tidb@172.17.3.228]: FAILED! => "changed": false, "elapsed": 309, "msg": "Timeout when waiting for search string 200 OK in tidb@172.17.3.228:9100"
How would I resolve this?
tidb
tidb
edited Nov 9 at 13:00
Maccath
2,48531739
asked Nov 9 at 2:34
Aaron
11
edited Nov 9 at 13:00
Maccath
2,48531739
asked Nov 9 at 2:34
Aaron
11
edited Nov 9 at 13:00
Maccath
2,48531739
edited Nov 9 at 13:00
Maccath
2,48531739
edited Nov 9 at 13:00
Maccath
2,48531739
2,48531739
asked Nov 9 at 2:34
Aaron
11
asked Nov 9 at 2:34
Aaron
11
asked Nov 9 at 2:34
Aaron
11
11
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
- make sure firewalld service is stopped or you have opened the tcp/9100 port on your target servers.
- check if node_exporter process is running (ps -ef | grep node_exporter)
- check if node_exporter service is healthy (curl http://172.17.3.226:9100/metrics)
answered Nov 12 at 11:55
LinuxGit
461
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
- make sure firewalld service is stopped or you have opened the tcp/9100 port on your target servers.
- check if node_exporter process is running (ps -ef | grep node_exporter)
- check if node_exporter service is healthy (curl http://172.17.3.226:9100/metrics)
answered Nov 12 at 11:55
LinuxGit
461
add a comment |
up vote
1
down vote
- make sure firewalld service is stopped or you have opened the tcp/9100 port on your target servers.
- check if node_exporter process is running (ps -ef | grep node_exporter)
- check if node_exporter service is healthy (curl http://172.17.3.226:9100/metrics)
answered Nov 12 at 11:55
LinuxGit
461
add a comment |
up vote
1
down vote
up vote
1
down vote
- make sure firewalld service is stopped or you have opened the tcp/9100 port on your target servers.
- check if node_exporter process is running (ps -ef | grep node_exporter)
- check if node_exporter service is healthy (curl http://172.17.3.226:9100/metrics)
answered Nov 12 at 11:55
LinuxGit
461
- make sure firewalld service is stopped or you have opened the tcp/9100 port on your target servers.
- check if node_exporter process is running (ps -ef | grep node_exporter)
- check if node_exporter service is healthy (curl http://172.17.3.226:9100/metrics)
answered Nov 12 at 11:55
LinuxGit
461
answered Nov 12 at 11:55
LinuxGit
461
answered Nov 12 at 11:55
LinuxGit
461
answered Nov 12 at 11:55
LinuxGit
461
461
add a comment |
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53219040%2ftidb-how-to-solve-node-exporter-up-timeout%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
