-
Notifications
You must be signed in to change notification settings - Fork 260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
<Anaconda.anaconda_lib.workers.local_worker.LocalWorker object > initial check failed #527
Comments
First of all, did you try to do what the error says? Is really hard to help someone that doesn't provide any kind of information, don't you think so? |
Hi @DamnWidget, I'm having same error on on Linux, I followed the steps and check the
And there is a sock file:
The only thing I see different is the equal ( |
I'm on the latest version of Anaconda (2.0.7) and also getting the error @wqshen posted when I start up Sublime Text with a python file open in the editor. After the first error, the problem goes away and Anaconda works fine. This from my anaconda_jsonserver.log. Not sure if it's related. 2016-09-03 14:39:49,437: DEBUG : bind: address=('localhost', 49677) |
Duplicate of #514 This happens because your systems, for whatever reason, are not able to connect to localhost during 2 seconds for N tries with 0.2s timeout each, that is abnormal, your systems would be able to connect to the loopback interface/unix socket domain in less than 0.2s always. In fact I have never been able to replicate this issue even using a timeout of 0.001s. About the error that @traversw pasted, it is because there is already a JsonServer running and ST3 being unable to connect is asking to start it again (that is weird as well). @RafaAguilar the socket name should not have any equal symbol on it, can you double check it? |
Sublime Text<Anaconda.anaconda_lib.workers.local_worker.LocalWorker object at 0x000001EA4B464FD0> initial check failed because: connection to localhost:51568 timed out after 0.2s. tried to connect 7 times during 2 seconds check that there is Python process executing the anaconda jsonserver.py script running in your system. If there is, check that you can connect to your localhost writing the following script in your Sublime Text 3 console: import socket; socket.socket(socket.AF_INET, socket.SOCK_STREAM).connect(("localhost", 51568)) OKGot same error in my machine, after close message, it continue to work fine. |
+1 for this issue. I'm running windows 10 64 bit. |
I had this issue over the past few days and managed to fix it by changing my build system to the default Anaconda Python Builder. Running the command in the sublime terminal |
Interesting... I am not sure what the build system has to do with anaconda JsonServer startup but I will make some deeper investigation as this piece of information from @Tomvass looks like can lead us to find some kind of weird hidden bug into the new anaconda's startup logic. |
No idea, could just be a quirk with my system and not directly related to this issue but matched mine closely enough. Always got the error on startup and Autoformat PEP8 was failing with the following:
Changing my build system now doesn't seem to be able to reproduce it so might of just been a coincidence and gave something a sufficient kick to start things running as normal again. |
I did some deeper investigation into this and there is no link between the build system and some people systems being slow enough to connect their localhost as to raise this error. I just added a new configuration setting that anyone could use to disable the startup warnings (they still get logged into the ST3 console). /*
Set this option to true if you get warnings about anaconda not
being able to connect to your localhost on ST3 startup but it
works normally after closing the error message.
NOTE: Ignore errors is dangerous do it under your own responsibility
*/
"swallow_startup_errors": false As the note in the comment says, use it at your own discretion. It will be part of the package in version 2.0.8 |
Same here:
I'm using |
The carat is pointing at the first / in the directory. Since receiving that error, Anaconda does not function in any way. I've checked, and the directory needed does exist, but the .sock file does not. I've made the directory world writable (a+rwx), and still nothing. Then, trying the code line, get the invalid syntax error. Any ideas? It used to work, but broke a few months ago. System is macOS Sierra, but the issue was also present on ElCap. Also, it appears that the jsonserver.py isn't loading, but I don't know how to address that. I've also tried uninstalling and reinstalling Anaconda, to no effect. |
Is there any anaconda Python JsonServer in the system? ( Looks like the Unix Domain Sockets are giving us some logistical problems, probably we will get rid of them in next releases. |
Entirety of output of
Nope, there do not appear to be any jsonserver processes running. |
I've gotten this issue a lot over recent versions of Anaconda, I didn't get it up until a few weeks ago. Works completely fine after closing the dialog box. Setting |
please find below the solution if you are using python34(3.4) or above.
|
I would never recommend to modify PyFlakes library if you don't know the implications of what you are doing, btw, I don't see the relation between that and the system being too slow as to start a JsonServer and connect to it. Can you try to explain it please? P.S: btw, that change totally breaks PyFlakes support in Python 2 so please, don't use it |
sublime text build 3126 show this error every startup sublime text. the following error logged in log file.
|
That looks like Windows TCP/IP port exhaustion. Do you know how many instances of anacondas's JsonServer were in the system? Btw, which windows version? |
windows 10 64 bit. full log 2016-10-01 11:56:14,463: INFO : process 1780 does not exists stopping server... 2016-10-01 11:56:36,020: ERROR : Traceback (most recent call last): 2016-10-01 11:56:36,023: ERROR : [Errno 10048] Only one usage of each socket address (protocol/network address/port) is normally permitted On Sat, Oct 1, 2016 at 12:13 AM, Oscar Campos notifications@github.com
Jeffery -odoo expert form kunshan, suzhou, china |
It's like your Windows ran out of socket descriptors, in the logs we can see that anaconda is operating normal just linting your code after a lint request so the connection is already established but there is another JsonServer starting up for the same project/folder name. Are you sure you didn't had two different Sublime Text 3 windows opening the same project/folder? To check in windows about the JsonSever just open the tasks manager and look for |
there is only one window, but running two process. On Sat, Oct 1, 2016 at 7:21 PM, Oscar Campos notifications@github.com
Jeffery -odoo expert form kunshan, suzhou, china |
Even open workspace with only one folder which running one sublime On Sun, Oct 2, 2016 at 11:06 AM, Jeffery jeffery9@gmail.com wrote:
Jeffery -odoo expert form kunshan, suzhou, china |
I'm facing the same problem on both my systems running macOS Sierra. Setting "swallow_startup_errors" to true doesn't help either. |
I wouldn't mind so much about this 'issue' (Anaconda works fine after the error) if |
That's weird @jaydenkieran and @ayushjaiswal as you can see in the code if |
setting swallow_startup_errors to true is not worked for me too. On Wed, Oct 5, 2016 at 6:40 PM, Oscar Campos notifications@github.com
Jeffery -odoo expert form kunshan, suzhou, china |
Try with 2.1.1 please |
moved to 2.1.1, it ok now thanks. On Wed, Oct 5, 2016 at 8:46 PM, Oscar Campos notifications@github.com
Jeffery -odoo expert form kunshan, suzhou, china |
I moved to 2.1.1 too and it works fine for me also. |
cd ~/.cache/jedi |
@laik Can you explain why following that can fix the problem? |
I finally was able to resolve my issue and have been using anaconda successfully for about a month. Based on the previous comments in this thread I assumed it was a problem with my configuration of python and sublime. In order to resolve that I removed anaconda from my plugins, uninstalled sublime, then uninstalled python. After that was done I went through my registry and deleted any key I could find that mentioned python or sublime. After doing that I reinstalled python, then sublime, and added anaconda. Probably a bit overkill but it seemed to work and I have not seen this issue since finishing this process. |
Hello, Got this issue on latest build, which was installed via Package Control. |
I've got this weird error on Sublime startup: I've already run florian 46772 0.0 0.0 4267752 636 s000 R+ 9:12PM 0:00.00 grep jsonserver Reinstalling Anaconda via Package Control didn't help and installing via Environment specifications: |
Exact same situation than @DahlitzFlorian |
same problem as @DahlitzFlorian I tried to run jsonserver with
so I don't know why jsonserver is not running |
Hi all, Check access to files in installed folder and in folder ~/.local/share/anaconda |
I'm on Windows 10 with limited rights to install programs. As such, I'm using a portable version of Sublime and Python. I'm unable to get Anaconda to work due to the fact that jsonserver.py is not running. If I try to run it manually based on @juanromerocortes suggestion, I see:
EDIT: I was able to fix this issue completely with a proper install of Python on my system and a clean install of sublime text (though this may not have been necessary). I still get the error at startup, but i guess it takes a bit of type for the python interpreter to start the jsonserver.py program. Hope this helps a couple people down the road. |
I had this error message and Anaconda did not work with Ubuntu 16.04, sublime text 3.1.1 build 3176, AnacondaST3 v2.1.29 and Python 3.6.5. When I tried
I got the error message
and Anaconda started working as expected after relaunch. I am unsure why Anaconda would require mypy. |
Because you enabled it... |
This change breaks pyflakes in python 2 |
Thank you it Works! |
Had the same issue. In my case Comodo was the culprit. Comodos HIPS blocked anaconda.py and plugin_host.exe. I had to remove them from the blocked apps list and Hips rules list. |
I was recently having this problem, and it was being caused by another package failing in Sublime Text that was causing startup to take too long. |
Minor fix to this for me - didnt like swallowing all the errors and not knowing about failures so... added the following to helpers.py
Changed the following in local_worker.py 33/34
Can submit a patch if you care, but seemed a little more elegant. Let me set a half second timeout in my user config, which was all that was required. |
set: "swallow_startup_errors": true, refer: |
I am also having this issue on OSX 10.13.6 with a VPN and Sentinel One installed (work computer). When I run the json server in debug mode, it works correctly. |
Just curious if anyone's discovered a workaround for this? |
fwiw, |
I tried many methods mentioned above, but none worked. Luckily somehow Sublime automatically backed up many packages and stored them in the same folder as Packages, so I was able to restore to the working version prior to the issue. Attached is the Git diff file between the non-working vs working version. Hope it could help. |
Working on it. Related to #820 |
Working on a macOS Mojave 10.14.5 installation, the following solved the problem for me:
This one is similar to @Antoine25's answer, so thanks a lot! |
this message appears at each Sublime startup, how to fix it?
![failed](https://cloud.githubusercontent.com/assets/12339722/18202544/405cddde-7143-11e6-8bee-9e170cecb325.png)
The text was updated successfully, but these errors were encountered: