indirect PING details to log

[neopaf]

Currently indirect PING can cause this message:

            log.info('Could not reach node: %s - %s', uri,
                opts.STATUS_NAMES[opts.SUSPECT]
            )

Which does not contain the reason for fail, all we know is that direct PING failed (if it succeeded, control would not reach this log line).

Please add important through_uri information to this log line. It was that node that failed indirect PING.

We've faced situation where 1 node out of 10 in cluster had some serious network issues.
Seeing that same node in logs would have helped to diagnose those issues much sooner (spent 2 months totally ;)

Only after collating "reach" logs into this pivot table we found out that 01 node is seriously ill:

[neopaf]

[09:04]hermes@rd-hmstnt01 ~$ tarantool -v
Tarantool 2.10.6-0-g3990f976b

Not sure if you're working on this branch though...

[neopaf]

[09:39]hermes@rd-hmstnt01 hermes_cluster$ tarantoolctl rocks list|grep membership -A1
membership
   2.4.0-1 (installed) - /tarantool_app/hermes_cluster/.rocks/share/tarantool/rocks
[09:39]hermes@rd-hmstnt01 hermes_cluster$ 

[neopaf]

2.4.6 is same here, so no use upgrading :(