I can ssh into a remote machine.
I then try to connect to a jupyter notebook job that I started on one of the nodes of the remote machine:
ssh -L 8069:localhost:8069 me#remote.machine ssh -L 8069:localhost:8069 me#node14
This has always worked fine in the past.
When I execute this lately, nothing happens until I eventually get a time out message. If I cancel it and then try to simply ssh into the remote machine again, it again does nothing until I get the error message:
ssh: connect to host remote.machine port 22: Connection timed out
I am trying to figure out if this is a problem at my end or at the remote machine. If it's the latter I can't understand why I am able to ssh to the remote machine fine until I try the
ssh -L 8069:localhost:8069 me#remote.machine ssh -L 8069:localhost:8069 me#node14
connection.
You are trying to do a double ssh connection: one to remote.machine and then another one to node14.
The problem seems to be the ssh process in the node14 machine. So, you can connect to the first machine but no to the second one. Ask your administrator to enable the sshd process in node14
You can test this case by logging into remote.machine via:
ssh -L 8069:localhost:8069 me#remote.machine.
Once you get shell access you can try the connection to node14 via:
ssh -L 8069:localhost:8069 me#node14.
According to the description, this last try should fail with the timeout.
Related
I would like to start a rpyc server on a machine I'm connected with over ssh. The general SSH connection is working but when starting the server I receive ERRNO 111 Connection refused. When starting the server manually, by logging in via SSH on the machine and starting the py file, I can connect. I tried:
ssh.exec_command("python3 /tmp/recalibration/rpc_service_pictures.py")
ssh.exec_command("python3 /tmp/recalibration/rpc_service_pictures.py &")
ssh.exec_command("nohup python3 /tmp/recalibration/rpc_service_pictures.py &")
ssh.exec_command("nohup python3 /tmp/recalibration/rpc_service_pictures.py > /dev/null 2>&1 &")
but nothing is changing the Connection Problem, any ideas?
Thanks in advance!
Turns out you cant be connected via SSH at the same time.
I had an open SSH session at the same time to debug, and because of that I couldnt connect. Seems obvious when you know it, but if you dont you are completely lost :D
I want to create a directory in my remote system using python script or by socket programming. I have remote system's Username, password and IP address. I am able to do this in my local machine but not in remote. Please help!
Download Putty then connect to remote system) and in terminal write mkdir foldername
To create a directory on a remote machine, you will have to first connect to it.Telnet and SSH and SSH is used to connect to remote machines. Obviously TELNET or SSH service should be running on the remote machine, otherwise you won't be able to connect.Since in case of Telnet,data is transfered in plain text, it's better to use SSH protocol.
Once connected to the remote machine using SSH, you will be able to execute commands on the remote machine.
Now since you want to do everything in Python, you will have to write a complete SSH client in Python. Which is greate for learning, because you will learn about socket programming and cryptography.
If you are in a hurry, you can use a good SSH library.
If you are getting network connection error, please check whether SSH is installed in the remote machine or not. If yes, then check firewall settings.
I am trying to connect to a remote server from a jump server. It connected to the remote server perfectly, but when I try to run a python script on the remote server, it says no directory found. Please help
gateway_session = SSHSession('host',
'unman', password='password').open()
# from jump server, establish connection with a remote server
remote_session = gateway_session.get_remote_session('host',
'username',password='password')
print(gateway_session.get_cmd_output('python /Folder/test.py'))
Try first to check where you are:
print(gateway_session.get_cmd_output('pwd;ls -alrth; ls -alrth /'))
That way, you know if there is indeed a Folder at /
The OP adds in the comments:
all I needed was to was separate the commands with a semi colon and run them using the same get output command.
The OP adds:
I just sshpass to a jump server from their, I sshpass to the remote on the same command in a shell script.
I have a Windows machine where I start an IPython kernel (to do some stuff not possible on another machine).
I have a Linux machine from which I would like to connect to the IPython kernel running on the Windows machine.
I can SSH from the Linux machine to the Windows machine (using this solution: https://superuser.com/a/172299).
I have tried following: https://github.com/ipython/ipython/wiki/Cookbook:-Connecting-to-a-remote-kernel-via-ssh. Both the automatic and the manual solution gives the following:
"ERROR: Kernel did not respond"
Using the same solution, I can connect from my Linux machine to an IPython kernel running on a Linux server. Any solution to get this to work with Linux to Windows?
You don’t need SSH to connect to a remote ipython kernel, regardless of whether it’s a ipython kernel running on Windows or Linux or Mac. What you do need is to have the Ip of the remote kernel visible to the terminal from which you are trying to connect from. Here are the steps:
Find out the ip address of the server (the machine on which the ipython kernel is running i.e. where you want the computation to happen) and client (the machine from which you are trying to connect to):
1.1. If you are on Windows, open up the command prompt and do a ipconfig to find out the ip addresses. If the Windows server has a direct Internet connection/lan connection, you should see a couple of ips like 192.168.57.1 and 10.2.3.64 and 127.0.0.1.
1.2. If you are on linux, open up a terminal and type ifconfig or ip addr show. You should again see a couple of ips like 192.168.57.1 and 10.2.3.64 and 127.0.0.1.
1.3. Test that atleast one of your server ip addresses is visible from the client: Ping your server from your client, using the command ping. ping will work on either Windows or Linux terminals. If you are running the windows/Linux as a VM or is behind a firewall, it is very much possible that your client or server is not visible from the other side. You don’t have to ping the ip address 127.0.0.1. This is a loop back address, and is only visible from the same machine where you got this ip address from. For example if you ping 127.0.0.1 from the Windows machine, it will ping the same Windows machine. If your client and server instances are running on the same machine, then its fine to use this address. However, if your client or server is running on a VM or a different machine altogher, then 127.0.0.1 wont work.
Start the remote kernel:
2.1. Once you have figured out which ip address on the server is visible from the client, start a kernel on the machine using ipython kernel. The ipython kernel will startup and show that `To connect another client to this kernel, use:
--existing kernel-1234.json
2.2. Locate the kernel-1234.json file on your server by importing (https://stackoverflow.com/a/35094772/4752883)
In [1]: from jupyter_client import find_connection_file
In [2]: find_connection_file()
Out[2]: 'C:\\Users\\me\\AppData\\Roaming\\jupyter\\runtime\\kernel-1234.json'
This will work either for Linux or Windows.
Start the remote client:
3.1. Once you locate the file, copy it over to your server machine using scp in linux or pscp or winscp in windows SCP w/ ssh: copying a local file from windows to a remote server using scp
3.2. Make sure that you are the same directory as the kernel-1234.json file.
3.3. Open up the kernel-1234.json file using vim or your favorite text editor. You will notice a line saying "ip": "127.0.0.1". Change 127.0.0.1 the ip address from your server that is visible from the client, that you found in step 1.3 and save the json file.
3.4. Start up the remote kernel using jupyter console –existing=kernel-1234.json, while located in the same drive where kernel-1234.json is located.
If you have followed the steps above, you should now be able to connect to the remote ipython kernel regardless of whether the ipython kernel is running on Windows/Linux/Mac.
I tried the manual way on https://github.com/ipython/ipython/wiki/Cookbook%3a-Connecting-to-a-remote-kernel-via-ssh once again and it worked. In detail:
windows-machine$ ipython kernel -f kernel-1234.json
linux-machine$ scp windows-machine:path/to/kernel-1234.json .
linux-machine$ cat kernel-1234.json
{
"stdin_port": 55534,
"ip": "127.0.0.1",
"control_port": 58391,
"hb_port": 60540,
"signature_scheme": "hmac-sha256",
"key": "fa461cf7-f078-4c22-909f-cfa7d2a30596",
"shell_port": 60159,
"transport": "tcp",
"iopub_port": 59207
}
linux-machine$ ssh -f -N -L 55534:127.0.0.1:55534
linux-machine$ ssh -f -N -L 58391:127.0.0.1:58391
linux-machine$ ssh -f -N -L 60540:127.0.0.1:60540
linux-machine$ ssh -f -N -L 60159:127.0.0.1:60159
linux-machine$ ssh -f -N -L 59207:127.0.0.1:59207
linux-machine$ ipython console --existing kernel-1234.json
I want to configure PyCharm 3.0 to use a Remote Python Interpreter.
The Problem is, I have to connect over a SSH Gateway:
MyMachine -> Gateway -> Machine with Python
When I connect via Cygwin I type the following: ssh -t user#gateway.com "ssh user#machineWithPython.com"
Is there a way to achieve this in PyCharm?
Another question, can I forward the X11 server to PyCharm (so that I can view the matplotlib plots on my machine?)
Regards,
m
I was able to the piggyback X11 forwarding through another ssh connection. Try setting the DISPLAY environment variable in your PyCharm run configuration like so:
DISPLAY=localhost:102
Check the value of DISPLAY in the other connection to see exactly what the value should be.
I am not sure I have understood your question correctly, it is maybe more adequate for the UNiX/Linux part.
At you machine:
ssh -fN -L 2222:machinewithPython:22 \ user#gateway.com
This connects port 2222 on your local machine to port 22 on remotemachine, and the ssh tunnnel will remain open until you kill the ssh process.
See the following links here and there.