Re: [PATCH v2] kdumpctl: time out after 180 seconds when connecting to ssh host

[Vivek Goyal]

On Wed, Jun 04, 2014 at 11:13:45AM +0800, WANG Chao wrote:

[..]
> > > if [ $_ret -ne 0 ]; then
> > > echo "ssh failed after multiple tries"
> > > echo "Could not create $DUMP_TARGET:$SAVE_PATH, you probably need to run "kdumpctl propagate""  >&2
> >
> > Hold on. So assume that network is up but keys are not propagated or keys
> > are not valid, we will still keep on retyring? That does not sound right.
> >
> > We need to retry only if network interface is not up. If ssh fails because
> > of no keys or wrong keys, then we should not retry.
>
> I'm not sure how can we do this, the return code from ssh is always 255
> in any case of failure, ie. wrong key, no key, network issue.

Hey from DUMP_TARGET, can't we figure out which local network interface
it is routed through and then check the status of that network interface?

Thanks
Vivek