“stdin: is not a tty” error, trying to rsync from a dedicated to shared with ssh jail root access

AdultFoundry · 06-10-2016, 11:04 AM

I am trying to run rsync from a dedicated server to a shared server with jail root access restricted to my home directory there (/home/user_name). I am able to ssh from the dedicated to the shared server, but when I run rsync (and try to pull some test files from there), I get the following error:

Code:

stdin: is not a tty

I've already added

Code:

[ -z "$PS1" ] && return

to the top of the .bashrc file, but it still does not work (I get the same error).

I was also trying to ssh from the shared to the dedicated, but the ssh connection times out, and it does not work. I can figure out why. I was trying to do this as I can rsync from any of the directions, but that does not work too, so basically I am not able to rsync the test files.

Thanks.

jpollard · 06-10-2016, 12:42 PM

You will have to show the commands you are actually using.

One way this occurs is if you have some commands in a .login/.bashrc file that require a terminal, but don't have the files check for that first. Using ssh doesn't necessarily require a terminal.

AdultFoundry · 06-10-2016, 12:50 PM

I am trying to figure out why the connection from SHARED to DEDICATED times out, I can log in to both machine. How would I check the reason for it on the DEDICATED system? This is Centos 7 machine, I run yum update && yum upgrade today.

EDIT:
I am able to connect from the DEDICATED to the SHARED now. When I figure out why it times out, I can still be getting the "stdin: is not a tty" from the other one too, so it could be the best to address that, I am not sure. Either way, I've been stuck all day on this now.

jpollard · 06-10-2016, 02:17 PM

Well, we can't tell what you are doing.

My suspicion is that you have done something to your .login or .bashrc or some such. But I don't know.

Why don't you provide a log of what commands you are using and the responses.

Turbocapitalist · 06-10-2016, 08:53 PM

Are you connecting with "ssh" and then running "rsync" on the remote machine with both the source and target over there? Or are you trying to transfer between the remote machine and a local machine. If the former, then "ssh -t" might be a temporary workaround. If the latter, then you can try the same with "rsync -e 'ssh -t' ..." If they work they are only workarounds and don't address the underlying problem that needs to be fixed.

But either way it would help to know more about the commands, as jpollard has asked above. You don't have to keep the machine names or directory names the same, they can be sanitized.