With OpenSuse Leap 42 as the destination machine, Ubuntu 16.04.1 LTS as
the originating machine:
I can login with x2go as root fine, but if I try as any other user I
get standard input inappropriate ioctl for device.
I can ssh with the same user and get no error.
I have made sure I don't have mesg or stty in my .profile and .kshrc
(I am using ksh as the login shell) and if I did it would also cause the same issue with ssh login.
Can anybody tell me what else to check?
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
Am 22.01.2017 um 11:52 schrieb Robert Dinse:
I have made sure I don't have mesg or stty in my .profile and .kshrc
(I am using ksh as the login shell) and if I did it would also cause the same issue with ssh login.
Can anybody tell me what else to check?
What happens if you set your login shell to bash, just to test? Does it throw the same error or does it go away?
-Stefan
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
On Sun, 22 Jan 2017, Stefan Baur wrote:
Am 22.01.2017 um 11:52 schrieb Robert Dinse:
I have made sure I don't have mesg or stty in my .profile and .kshrc
(I am using ksh as the login shell) and if I did it would also cause the same issue with ssh login.
Can anybody tell me what else to check?
What happens if you set your login shell to bash, just to test? Does it throw the same error or does it go away?
-Stefan
It throws exactly the same error:
Connection failed. stty: standard input: Inappropriate ioctl for
device stty: standard input: Inappropriate ioctl for device
This error shows in a pop-up.
I do not have an stty in my .profile, .kshrc, or .bashrc.
It does not throw this error if I just ssh to the machine. I previously
has OpenSuse 13.2 on this machine and did not get this error.
Am 22.01.2017 um 12:29 schrieb Robert Dinse:
What happens if you set your login shell to bash, just to test? Does it throw the same error or does it go away?
-Stefan
It throws exactly the same error: Connection failed. stty: standard input: Inappropriate ioctl for device stty: standard input: Inappropriate ioctl for device This error shows in a pop-up. I do not have an stty in my .profile, .kshrc, or .bashrc. It does not throw this error if I just ssh to the machine. I
previously has OpenSuse 13.2 on this machine and did not get this error.
Did you check /etc/bash.bashrc, and whatever system-wide files belong to the group of "usual suspects" as well?
-Stefan
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
On Sun, 22 Jan 2017, Stefan Baur wrote:
What happens if you set your login shell to bash, just to test? Does it throw the same error or does it go away?
-Stefan
It throws exactly the same error: Connection failed. stty: standard input: Inappropriate ioctl for device stty: standard input: Inappropriate ioctl for device This error shows in a pop-up. I do not have an stty in my .profile, .kshrc, or .bashrc. It does not throw this error if I just ssh to the machine. I
previously has OpenSuse 13.2 on this machine and did not get this error.
Did you check /etc/bash.bashrc, and whatever system-wide files belong to the group of "usual suspects" as well?
-Stefan
I did this:
find /etc -type f -exec grep stty {} /dev/null \;
And examined each file that resulted. All of them were wrapped and
checked for either EMACS shell mode or SSH_TTY, neither of these environmental variables are set in my environment.
Also, the fact that I don't get this error when I simply ssh to the site
with the same username, which would also execute these scripts, tells me that is not the issue.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Sun, 22 Jan 2017, Robert Dinse wrote:
Date: Sun, 22 Jan 2017 03:50:20 -0800 (PST) From: Robert Dinse <nanook@eskimo.com> To: Stefan Baur <X2Go-ML-1@baur-itcs.de> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] OpenSuse Leap 42
On Sun, 22 Jan 2017, Stefan Baur wrote:
What happens if you set your login shell to bash, just to test? Does it throw the same error or does it go away?
-Stefan
It throws exactly the same error: Connection failed. stty: standard input: Inappropriate ioctl for device stty: standard input: Inappropriate ioctl for device This error shows in a pop-up. I do not have an stty in my .profile, .kshrc, or .bashrc. It does not throw this error if I just ssh to the machine. I
previously has OpenSuse 13.2 on this machine and did not get this error.
Did you check /etc/bash.bashrc, and whatever system-wide files belong to the group of "usual suspects" as well?
-Stefan
I did this:
find /etc -type f -exec grep stty {} /dev/null \;
And examined each file that resulted. All of them were wrapped and
checked for either EMACS shell mode or SSH_TTY, neither of these environmental variables are set in my environment.
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
Am 22.01.2017 um 12:54 schrieb Robert Dinse:
Also, the fact that I don't get this error when I simply ssh to the
site with the same username, which would also execute these scripts, tells me that is not the issue.
Since you can use if-clauses in such scripts, I wouldn't have wanted to rule that out before checking. Also, connecting interactively with plain ssh does do things differently - wait: what happens when you do this:
ssh user@host echo
ssh -T user@host echo
ssh -t user@host echo
Any difference between the three outputs?
-Stefan
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
On Sun, 22 Jan 2017, Stefan Baur wrote:
Date: Sun, 22 Jan 2017 12:58:20 +0100 From: Stefan Baur <X2Go-ML-1@baur-itcs.de> To: Robert Dinse <nanook@eskimo.com> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] OpenSuse Leap 42
Am 22.01.2017 um 12:54 schrieb Robert Dinse:
Also, the fact that I don't get this error when I simply ssh to the
site with the same username, which would also execute these scripts, tells me that is not the issue.
Since you can use if-clauses in such scripts, I wouldn't have wanted to rule that out before checking. Also, connecting interactively with plain ssh does do things differently - wait: what happens when you do this:
ssh user@host echo
This logs in normally with no errors:
/home/nanook >ssh nanook@opensuse echo Password:
/home/nanook >hostname opensuse /home/nanook >
ssh -T user@host echo
After I type the password the remote machine immediately closes the
connection with no error message.
ssh -t user@host echo
With this one I get a message stating that the connection was closed
instead of droping directly to my command prompt.
Any difference between the three outputs?
As noted above. Thanks.
-Stefan
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
On 22.01.2017 12:58 PM, Stefan Baur wrote:
Am 22.01.2017 um 12:54 schrieb Robert Dinse: Since you can use if-clauses in such scripts, I wouldn't have wanted to rule that out before checking. Also, connecting interactively with plain ssh does do things differently - wait: what happens when you do this:
ssh user@host echo
ssh -T user@host echo
ssh -t user@host echo
X2Go does things differently, it spawns a non-interactive login shell.
Let's try ssh user@host 'bash -l -c "echo foo"' <&- instead.
Mihai
$ ssh nanook@opensuse.eskimo.com 'bash -l -c "echo foo"' <&- Password: stty: standard input: Inappropriate ioctl for device foo $ hostname nanook $
So it is printing that error message and then disconnecting.
On a machine where x2go works properly (this example is centos7):
$ ssh nanook@centos7.eskimo.com 'bash -l -c "echo foo"' <&- nanook@centos7.eskimo.com's password: foo $ hostname nanook
You can see the only difference is that on the machine that works, it
disconnects without printing an error message, where as with opensuse it prints and error message before disconnecting.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Sun, 22 Jan 2017, Mihai Moldovan wrote:
Date: Sun, 22 Jan 2017 14:18:46 +0100 From: Mihai Moldovan <ionic@ionic.de> To: Stefan Baur <X2Go-ML-1@baur-itcs.de>, Robert Dinse <nanook@eskimo.com> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] OpenSuse Leap 42
On 22.01.2017 12:58 PM, Stefan Baur wrote:
Am 22.01.2017 um 12:54 schrieb Robert Dinse: Since you can use if-clauses in such scripts, I wouldn't have wanted to rule that out before checking. Also, connecting interactively with plain ssh does do things differently - wait: what happens when you do this:
ssh user@host echo
ssh -T user@host echo
ssh -t user@host echo
X2Go does things differently, it spawns a non-interactive login shell.
Let's try ssh user@host 'bash -l -c "echo foo"' <&- instead.
Mihai
On 22.01.2017 02:31 PM, Robert Dinse wrote:
$ ssh nanook@opensuse.eskimo.com 'bash -l -c "echo foo"' <&- Password: stty: standard input: Inappropriate ioctl for device foo
See, that's a problem. If you haven't changed your startup scripts, chances are that OpenSUSE added an unguarded call in their default scripts - if we find it, a downstream bug report is in order.
Please check/show (if possible) all files that might include stuff that might cause this error, most likely /etc/profile* and /etc/bash* including possible sub-directories.
Some of what might cause is are calls like "mesg", "wall", "stty". If you are unsure, just drop everything to the mailing list.
Mihai