Re: How do I debug this?

[Michael Albinus]

Mark Geary <address@hidden> writes:

Hi Mark,

> I can see if the sysadmin is willing, though he's on vacation right
> now.

If he's willing, you might convince him to install Emacs 25.2.

Let's go through the debug buffer.

> 09:57:53 tramp-maybe-open-connection (6) # /bin/sh
> 09:57:53 tramp-wait-for-regexp (6) # 
> sh: break: only meaningful in a `for', `while', or `until' loop
> sh: alias: -x: invalid option
> alias: usage: alias [-p] [name[=value] ... ]
> sh: alias: -x: invalid option
> alias: usage: alias [-p] [name[=value] ... ]
> sh: alias: -x: invalid option
> alias: usage: alias [-p] [name[=value] ... ]
> sh: alias: -x: invalid option
> alias: usage: alias [-p] [name[=value] ... ]
> sh: print: command not found
> sh: alias: -x: invalid option
> alias: usage: alias [-p] [name[=value] ... ]
> sh: print: command not found
> sh: alias: -x: invalid option
> alias: usage: alias [-p] [name[=value] ... ]
> sh: print: command not found
> sh: alias: -x: invalid option
> alias: usage: alias [-p] [name[=value] ... ]
> sh: print: command not found
> sh: alias: -x: invalid option
> alias: usage: alias [-p] [name[=value] ... ]
> sh: print: command not found
> sh: print: command not found
> sh: integer: command not found
> sh: typeset: -Z: invalid option
> typeset: usage: typeset [-aAfFilrtux] [-p] name[=value] ...
> sh: set: -A: invalid option
> set: usage: set [--abefhkmnptuvxBCHP] [-o option-name] [arg ...]
> flg0013 0 DING!!:/tmp> 

That's your local shell. Likely not a problem for Tramp, but do you see
the same errors when calling "/bin/sh" locally?

> 09:57:53 tramp-send-command (6) # ssh io   -q -e none -t -t 
> /usr/local/bin/bash && exit || exit
> 09:57:54 tramp-process-actions (6) # 
> address@hidden ~]$ 

The call to your remote machine with the change to bash, as you've
configured. Looks OK.

> 09:57:54 tramp-send-command (6) # exec env ENV='' PROMPT_COMMAND='' PS1='$ ' 
> PS2='' PS3='' /bin/sh
> 09:57:54 tramp-wait-for-regexp (6) # 
> $ 

Tramp doesn't trust (remote) login shells to be POSIX compatible. So it
uses /bin/sh remotely.

> 09:57:54 tramp-send-command (6) # stty -inlcr -echo kill '^U' erase '^H'
> 09:57:54 tramp-wait-for-regexp (6) # 
> stty -inlcr -echo kill '^U' erase '^H'
> $ 
> 09:57:54 tramp-send-command (6) # echo foo
> 09:57:54 tramp-wait-for-regexp (6) # 
> echo foo
> foo
> $ 
> 09:57:54 tramp-send-command (6) # _echostty icanon erase ^H cols 
> 32767_echo
> 09:57:54 tramp-wait-for-regexp (6) # 
> $ 

Some tty settings. Looks OK.

> 09:57:54 tramp-send-command (6) # _echoPS1='
> ///3ada5f533267468984eeb5d8b77f38c3
> '_echo

That's the last command Tramp has sent. It doesn't recognize prompt
"///3ada5f533267468984eeb5d8b77f38c3" in the response, although it's there:

> 10:37:08 tramp-accept-process-output (10) # 
> ///3ada5f533267468984eeb5d8b77f38c3

Hard to say what's up. I fear I would need to debug it with your remote
host, but since it's a company owned host it will be impossible, I guess.

The question is whether you need the pseudoterminals as said to ssh by
the "-t -t" arguments. Maybe you clone your own Tramp method from "ssh"
instead of "sshx".

The other alternative for you is to upgrade Emacs and/or Tramp, but it
isn't guaranteed to fix it. Sorry.

> Mark

Best regards, Michael.