Re: Transport endpoint is not connected
On Wed, Jul 05, 2023 at 04:49:04PM +0200, tomas@tuxteam.de wrote:
> On Wed, Jul 05, 2023 at 08:15:14AM -0600, D. R. Evans wrote:
> > tomas@tuxteam.de wrote on 7/4/23 22:23:
> >
> > > >
> > > > 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.
> > >
> >
> > This is a plain ol' ssh login, so I don't think that FUSE is involved.
>
> I think this happens "next", after login and hasn't much to do with
> ssh. Somethingsomething session [1] (waves hands).
>
> Anything in the logs?
I'm still waiting for setup details to be provided. Is "sh" the user's
login shell, or is it some kind of transient shell that's being used
internally by ssh, e.g. to set up privilege separation? (I somehow
doubt a shell is used there, but I'm grasping at straws because we're
being given no useful details at all.)
Is /bin/sh a symlink to dash, or to bash?
If I remember correctly, bash has to do a getcwd() at startup time to
set up certain variables for POSIX conformance. But I'm going off of
memories from years ago. And I don't know whether other shells do things
the same way.
> > > Are you able to access all the directories you expect to? How
> > > is, e.g. the user's $HOME mounted? Its parent?
> >
> > Yep...
See, this is not a complete answer.
Is $HOME on an NFS server? An iSCSI disk? An sshfs mount? Is autofs
or another automounter involved in any way?
Show us the relevant line(s) in fstab and in the output of "mount"?
Is "sh" the user's shell, or is their shell /bin/bash or something else?
Anything you could tell us would be better than just "Yep".
Reply to: