[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Transport endpoint is not connected



On Tue, Jul 04, 2023 at 01:40:18PM -0600, D. R. Evans wrote:
> hlyg wrote on 6/28/23 21:32:
> 
> > notification message: Transport endpoint is not connected
> > 
> 
> FWIW, since upgrading to bookworm, I see:
>   sh: 0: getcwd() failed: Transport endpoint is not connected
> when I ssh into the upgraded box.

This seems to be coming from getcwd() (aka get current working
directory, see man page). Asking the intertubes, it seems to
happen often when it or its ancestors are mounted over FUSE.

> I have no idea why. (And, just to be clear, this has never happened before,
> through many releases of debian stable.)
> 
> I'm assuming, for now, that:
>  1. I can use the box as usual despite the message;
>  2. the problem will be fixed at some point soon.
> 
> I haven't seen any other obvious problems if I proceed to use the ssh
> session as normal.

Are you able to access all the directories you expect to? How
is, e.g. the user's $HOME mounted? Its parent?

Cheers
-- 
t

Attachment: signature.asc
Description: PGP signature


Reply to: