Timed out after 20.0 seconds while waiting for python script to connect.

[MilanV]

Hi,

in my team one member which have Windows 8.1(with Java 6 and Java 7) has a problem that degugger once started try to switch to degugger mode for 20 seconds and then reports with one pop up message:

     Timed out after 20.0 seconds while waiting for python script to connect.
     Accept timed out​


before that message is shown one can see in console window, and in frame(down, right) of Liclipse following massage:

     Launching Waiting For Connection

as other team members have to change to Windows 8.1 we need ASAP support or we need to buy some other SW which does not have this problem.

So please Help!


Best regards,
MilanV

[Fabio Zadrozny]

Hi MilanV,

This shouldn't be an issue related to windows 8.1 (I use Windows 8.1 myself without any issues).

The common issue in this case is that there's some active firewall preventing the communication from happening between LiClipse and the debugger which runs in the Python process.

A simple test would be disabling the firewall and checking if it works (and if it does, reenable it and add the appropriate exception).

If that does not solve it, please create an entry in https://sw-brainwy.rhcloud.com/tracker/LiClipse adding details on the contents you have in the error log.

Best regards,

Fabio

--
You received this message because you are subscribed to the Google Groups "LiClipse" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liclipse+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[MilanV]

Hi Fabio,

could you please help me locate that debugger process. The Laptop we are using are office laptops so I need to explain to IT what exactly should be excluded from the firewall. So is it correct that LiClipse is one process and debugger is another one ?..by the way why the are separated processes ? I probably need for IT info what is exactly debugger process name where it is located and over which IP/port/protocoll it is communicating with LiClipse ?

Best regards,

MilanV 

[Fabio Zadrozny]

The related processes are LiClipse.exe, javaw.exe and python.exe.

They are separate processe because LiClipse is communicating with the python which is executing your code (debugger).

As for the port, it's not pre-determined (it'll find a free port using a server socket with '0' and use that port). So, in short, it should allow the processes above to connect to 127.0.0.1 in any port without restrictions (outbound connections to other ips don't need to be allowed -- unless you plan on using the remote debugger from different machines, in which case the default port would be 5678).

Best Regards,

Fabio

[MilanV]

Hi Fabio,

I turned off complete Firewall but still the problem is present (first after 5th debbuging sessions). Is there any log file where Li(E)clipse writes in more details what is really happening ?

Best regards,
Milan.

[Fabio Zadrozny]

Hi Milan,

The error log may contain more details (window > show view > general > error log) and there's also a log file which resides at your_workspace/.metadata/.log.

If you pass me the contents of that file I may be able to give you more information.

Best Regards,

Fabio

[MilanV]

Hi Fabio,

as we are using Liclipse and Eclipse in project I am not sure if collegue send me log file from Eclipse or Liclipse.

Thanks,
MilanV

[Fabio Zadrozny]

Hi Milan,

Really strange... in this case it's usually either a firewall or some misconfigured network, as you said that the firewall is down, let's check the other route... 

So, a question here: do you have ipv4 properly configured there? (it could be that you only have ipv6 for some reason) -- what PyDev does is create a port and try to connect to 127.0.0.1 using that port.

Can you try running the code I'm attaching in that machine and say which is the output you have? (i.e.: python.exe snippet.py)

Best Regards,

Fabio

[MilanV]

Hi Fabio,

it seems we are having only IPv4 on our PCs.
I runned your script and sommetimes it returned:

DEMUCN02222.pfad.biz - - [16/Feb/2015 15:55:51] "POST / HTTP/1.1" 200 -

Worked

and sometimes(probably this trials is causing as problems!):

Traceback (most recent call last):

  File "<string>", line 4, in <module>

  File "C:\PYTHON27\lib\xmlrpclib.py", line 1224, in __call__

    return self.__send(self.__name, args)

  File "C:\PYTHON27\lib\xmlrpclib.py", line 1578, in __request

    verbose=self.__verbose

  File "C:\PYTHON27\lib\xmlrpclib.py", line 1264, in request

    return self.single_request(host, handler, request_body, verbose)

  File "C:\PYTHON27\lib\xmlrpclib.py", line 1292, in single_request

    self.send_content(h, request_body)

  File "C:\PYTHON27\lib\xmlrpclib.py", line 1439, in send_content

    connection.endheaders(request_body)

  File "C:\PYTHON27\lib\httplib.py", line 954, in endheaders

    self._send_output(message_body)

  File "C:\PYTHON27\lib\httplib.py", line 814, in _send_output

    self.send(msg)

  File "C:\PYTHON27\lib\httplib.py", line 776, in send

    self.connect()

  File "C:\PYTHON27\lib\httplib.py", line 757, in connect

    self.timeout, self.source_address)

  File "C:\PYTHON27\lib\socket.py", line 571, in create_connection

    raise err

socket.error: [Errno 10060] A connection attempt failed because the connected party did not properly respond after a period of time or established connection failed because connected host has failed to respond

best regards,
Milan

[Fabio Zadrozny]

Hi Milan,

Well, it seems it's something strange in your system (if it fails even in such a simple script).

After searching a bit I found a reference which may help you in solving it:

https://support.microsoft.com/kb/811087?wa=wsignin1.0

Besides that, I'm not sure there's something I can change in LiClipse itself... maybe you're redirecting the traffic from your computer through some proxy which is delaying things? Although it's really strange that something like this would happen when connecting to 127.0.0.1... if it's not the firewall, maybe an antivirus is doing that -- or maybe even a virus?

Best Regards,

Fabio

[Gustin Johnson]

Kaspersky used to give us tons of grief with their ndis driver shim, essentially placing them inline in the TCP/IP stack.  Definitely a good idea to check your AV solution.

Also, are you *sure* that the microsoft firewall has been completely disabled?  You can check from the command line with (everything between the quotes): "netsh advfirewall show currentprofile"  If it returns a state of "ON" then this could still be a problem for you.

You might also ask your IT team if they are utilizing applocker or some similar technology.

Hth,