[PSST] Review test_connection.sh

[bbockelm]

• We probably shouldn't try connection to http://cern.ch
• nc to google is fine - they can probably handle the load.
• Would be best to just test connection to MONIT.

@roksys @stlammel

[bbockelm]

Maybe even want to switch to curl if nc is too basic?

We also should review the debugging levels.

[bbockelm]

Another idea would be to test DNS functionality -- or just should be happy with the error message from nc?

[roksys]

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, 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

Are 5 seconds for timeout okay?

[stlammel]

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

[roksys]

Hi Stephan,

I set timeout to 15 sec. Should be okay now.

[roksys]

For me it looks as solved issue.
@bbockelm, @stlammel, can I close it?