PeerActor log_assert! can have no-route-to-host error

[robin-near]

Description

thread 'actix-rt|system:0|arbiter:928' panicked at chain/network/src/peer/peer_actor.rs:1606:9:
unexpected closing reason: send: IO error: No route to host (os error 113)
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: <near_network::peer::peer_actor::PeerActor as actix::handler::Handler<near_network::peer::stream::Error>>::handle
   3: <actix::address::envelope::SyncEnvelopeProxy<M> as actix::address::envelope::EnvelopeProxy<A>>::handle
   4: actix::mailbox::Mailbox<A>::poll
   5: <actix::contextimpl::ContextFut<A,C> as core::future::future::Future>::poll
   6: tokio::runtime::task::harness::Harness<T,S>::poll
   7: tokio::task::local::LocalSet::tick
   8: tokio::task::local::LocalSet::run_until::{{closure}}
   9: tokio::runtime::scheduler::current_thread::Context::enter
  10: tokio::runtime::context::scoped::Scoped<T>::set
  11: tokio::runtime::scheduler::current_thread::CoreGuard::block_on
  12: tokio::runtime::context::runtime::enter_runtime
  13: tokio::runtime::runtime::Runtime::block_on

encountered on a dev-release build.