You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dashb-mb.cern.ch is messaging server that forwards documents to Elasticsearch, so should easilt handle the load. I will try to get a confirmation from CERN IT.
If dashb-mb.cern.ch is unreachable, google.com is used as an endpoint.
In case of DNS problem, nc output should look similar to this:
nc: getaddrinfo: Name or service not known
In case of closed port or other connectivity problem, nc output should look similar to this:
nc: connect to dashb-mb.cern.ch port 80 (tcp) timed out: Operation now in progress
Hallo Rokas,
DNS resolution can take up to 10 sec before reaching a timeout.
I would add another second or two for the connection attempt.
Thanks,
cheers, Stephan
Activity
bbockelm commentedon Jun 21, 2017
Maybe even want to switch to
curlifncis too basic?We also should review the debugging levels.
bbockelm commentedon Jun 21, 2017
Another idea would be to test DNS functionality -- or just should be happy with the error message from
nc?[-]Review test_connection.sh[/-][+][PSST] Review test_connection.sh[/+]roksys commentedon Jun 26, 2017
Please take a look at connectivity test.
dashb-mb.cern.ch is messaging server that forwards documents to Elasticsearch, so should easilt handle the load. I will try to get a confirmation from CERN IT.
If dashb-mb.cern.ch is unreachable, google.com is used as an endpoint.
In case of DNS problem,
ncoutput should look similar to this:In case of closed port or other connectivity problem,
ncoutput should look similar to this:Are 5 seconds for timeout okay?
stlammel commentedon Jun 26, 2017
roksys commentedon Jun 26, 2017
Hi Stephan,
I set timeout to 15 sec. Should be okay now.
roksys commentedon Jun 27, 2017
For me it looks as solved issue.
@bbockelm, @stlammel, can I close it?