Hello,
This is a follow-up to a thread that I started a few weeks back (What are port requirements for remote lisp?).
I run Msys2's Emacs on a corporate laptop running windows 10, and I don't have administrator privileges. I am using Sly and Spacemacs.
My problem is that sly-connect times out when trying to connect to the swank server.
With Martin's help, I was able to establish a tunnel, start swank, and with a telnet session on the laptop verify that I can send commands to swank (see that other thread for details).
Nevertheless, sly-connect still fails. Stepping through the code, I came to a call to make-network-process, which is a C function.
The error message is "make client process failed", "Connection timed out", :name, "sly-4", :buffer, nil, :host, "hal9000.us.tel.com", :service, 4005, :nowait, nil, :tls-parameters, nil
I need help in figuring out the cause of the problem so that I can ask our IT department for specific help.
My emacs can connect to the internet - for instance, org-ref (orgmode+bibtex) can fetch journal article citations using DOI's. So, why is make-network-process failing in this instance?
I am looking for some simple tests of make-network proces that can narrow down the cause of failure when connecting to swank.
I was going to ask on the emacs mailing list, but I thought it best to start here first.
Thank you,
Mirko
On Sun, Apr 19, 2020 at 3:08 AM Mirko Vukovic mirko.vukovic@gmail.com wrote:
I am using Sly
This is a Slime mailing list, not Sly.
On Sat, Apr 18, 2020 at 8:10 PM Stas Boukarev stassats@gmail.com wrote:
On Sun, Apr 19, 2020 at 3:08 AM Mirko Vukovic mirko.vukovic@gmail.com wrote:
I am using Sly
This is a Slime mailing list, not Sly.
I posted here as I did not find a sly mailing list.
I understand that sly shares quite a bit of code with slime, and was hoping to get help here.
They have a bug tracker.
On Sun, Apr 19, 2020 at 3:13 AM Mirko Vukovic mirko.vukovic@gmail.com wrote:
On Sat, Apr 18, 2020 at 8:10 PM Stas Boukarev stassats@gmail.com wrote:
On Sun, Apr 19, 2020 at 3:08 AM Mirko Vukovic mirko.vukovic@gmail.com wrote:
I am using Sly
This is a Slime mailing list, not Sly.
I posted here as I did not find a sly mailing list.
I understand that sly shares quite a bit of code with slime, and was hoping to get help here.
I moved from spacemacs/sly/slynk to spacemacs/slime/swank - the issue remains.
I fixed my original post to reflect this change.
On Sat, Apr 18, 2020 at 8:06 PM Mirko Vukovic mirko.vukovic@gmail.com wrote:
Hello,
This is a follow-up to a thread that I started a few weeks back (What are port requirements for remote lisp?).
I run Msys2's Emacs on a corporate laptop running windows 10, and I don't have administrator privileges. I am using Sly and Spacemacs.
I now use slime/swank on Spacemacs
My problem is that sly-connect times out when trying to connect to the swank server.
Slime-connect times out
With Martin's help, I was able to establish a tunnel, start swank, and with a telnet session on the laptop verify that I can send commands to swank (see that other thread for details).
Nevertheless, sly-connect still fails. Stepping through the code, I came to a call to make-network-process, which is a C function.
Slime-connect times out. The low-level function making the call is
make-network-process
The error message is "make client process failed", "Connection timed out", :name, "sly-4", :buffer, nil, :host, "hal9000.us.tel.com", :service, 4005, :nowait, nil, :tls-parameters, nil
I need help in figuring out the cause of the problem so that I can ask our IT department for specific help.
My emacs can connect to the internet - for instance, org-ref (orgmode+bibtex) can fetch journal article citations using DOI's. So, why is make-network-process failing in this instance?
I am looking for some simple tests of make-network proces that can narrow down the cause of failure when connecting to swank.
I was going to ask on the emacs mailing list, but I thought it best to start here first.
Thank you,
Mirko
On Sun, 19 Apr 2020 at 01:08, Mirko Vukovic mirko.vukovic@gmail.com wrote:
With Martin's help, I was able to establish a tunnel, start swank, and with a telnet session on the laptop verify that I can send commands to swank (see that other thread for details).
Nevertheless, sly-connect still fails. Stepping through the code, I came to a call to make-network-process, which is a C function.
The error message is "make client process failed", "Connection timed out", :name, "sly-4", :buffer, nil, :host, "hal9000.us.tel.com", :service, 4005, :nowait, nil, :tls-parameters, nil
Does telneting to hal9000.us.tel.com port 4005 work? Why don't you connect to SWANK via the SSH tunnel you've established?
On Sun, Apr 19, 2020 at 2:18 PM Luís Oliveira luismbo@gmail.com wrote:
On Sun, 19 Apr 2020 at 01:08, Mirko Vukovic mirko.vukovic@gmail.com wrote:
With Martin's help, I was able to establish a tunnel, start swank, and
with a telnet session on the laptop verify that I can send commands to swank (see that other thread for details).
Nevertheless, sly-connect still fails. Stepping through the code, I came
to a call to make-network-process, which is a C function.
The error message is "make client process failed", "Connection timed out", :name, "sly-4",
:buffer, nil, :host, "hal9000.us.tel.com", :service, 4005, :nowait, nil, :tls-parameters, nil
Does telneting to hal9000.us.tel.com port 4005 work?
I have a swank server listening on port 4005. telnet times out:
telnet hal9000 4005
Trying 172.17.57.205... telnet: Unable to connect to remote host: Connection timed out
Why don't you connect to SWANK via the SSH tunnel you've established?
If you mean by slime-connect, it times out.
If you mean by telnet, it works:
telnet localhost 4005
Trying ::1... Connected to localhost. Escape character is '^]'.
Have you tried M-x slime-connect to 127.0.0.1?
On Mon, Apr 20, 2020 at 1:23 AM Mirko Vukovic mirko.vukovic@gmail.com wrote:
On Sun, Apr 19, 2020 at 2:18 PM Luís Oliveira luismbo@gmail.com wrote:
On Sun, 19 Apr 2020 at 01:08, Mirko Vukovic mirko.vukovic@gmail.com wrote:
With Martin's help, I was able to establish a tunnel, start swank, and with a telnet session on the laptop verify that I can send commands to swank (see that other thread for details).
Nevertheless, sly-connect still fails. Stepping through the code, I came to a call to make-network-process, which is a C function.
The error message is "make client process failed", "Connection timed out", :name, "sly-4", :buffer, nil, :host, "hal9000.us.tel.com", :service, 4005, :nowait, nil, :tls-parameters, nil
Does telneting to hal9000.us.tel.com port 4005 work?
I have a swank server listening on port 4005. telnet times out:
telnet hal9000 4005
Trying 172.17.57.205... telnet: Unable to connect to remote host: Connection timed out
Why don't you connect to SWANK via the SSH tunnel you've established?
If you mean by slime-connect, it times out.
If you mean by telnet, it works:
telnet localhost 4005
Trying ::1... Connected to localhost. Escape character is '^]'.
-- Luís Oliveira http://kerno.org/~luis/
Mirko Vukovic mirko.vukovic@gmail.com writes:
On Sun, 19 Apr 2020 at 01:08, Mirko Vukovic mirko.vukovic@gmail.com wrote:
Nevertheless, sly-connect still fails. Stepping through the code, I came
to a call to make-network-process, which is a C function.
The error message is "make client process failed", "Connection timed out", :name, "sly-4",
:buffer, nil, :host, "hal9000.us.tel.com", :service, 4005, :nowait, nil, :tls-parameters, nil
Does telneting to hal9000.us.tel.com port 4005 work?
I have a swank server listening on port 4005. telnet times out:
telnet hal9000 4005
Trying 172.17.57.205... telnet: Unable to connect to remote host: Connection timed out
Why don't you connect to SWANK via the SSH tunnel you've established?
If you mean by slime-connect, it times out.
If you mean by telnet, it works:
telnet localhost 4005
Trying ::1... Connected to localhost. Escape character is '^]'.
You need to figure out what arguments are being passed to make-network-process and then try to reproduce by calling make-network-process directly (see Section 38.17.1 ‘make-network-process’ of the elisp Info manual).
One possible problem could be that SLIME is trying to connect to 127.0.0.1 instead of localhost, which is the IPv6 ::1 loopback address on your system.
-- Vladimir Sedach Software engineering services in Los Angeles https://oneofus.la
-
Luís Oliveira -
Mirko Vukovic -
Stas Boukarev -
Vladimir Sedach