My configuration:
zookeeper: 3.4.10
os: ubuntu 16.04
python: 2.7
kazoo: 2.3.1
The code I run in IPython:
When I restarted zookeeper, with bin/zkServer.sh restart, the shell shows the exception as below:
If I delete the watch and replace with a listener, the listener works well.
I don't know why, and I read the info from google and github/kazoo, but I found no explanation of how to solve the problem.
P.S.: Someone said because the session of the client connection expired and was lost, the session_id is not the same with the retry connection when the zookeeper restarts
I believe this is related to a bug that was introduced in 2.3.1 from the following PR:
https://github.com/python-zk/kazoo/pull/305
This is being looked into, and may be rolled back. In the meantime, try using a pre 2.3 version of kazoo.
Related
I am trying to edit my jupyter notebook which is in Azure ML Workspace. I use the 'edit-in vscode' option, it opens the vs-code or when I try to connect to compute instance directly from vs code, then I am getting the following error:
[Info - 2021-11-08 07:06:06.885] Using commit id "b3318bc0524af3d74034b8bb8a64df0ccf35549a" and quality "stable" for server
[Error - 2021-11-08 07:06:06.971] Invalid response: 405 Method Not Allowed
[Error - 2021-11-08 07:06:06.971] Cannot communicate with the Jupyter endpoint.
[Error - 2021-11-08 07:06:07.981] Maximum retries exhausted. Could not install VS Code server on saksham-dubey: Cannot communicate with the Jupyter endpoint.
Earlier it was working fine and I had no issues with vs-code, I was able to edit/run files directly but without changing anything, it started giving me problem.
So far, I have tried uninstalling/removing vscode completely, reinstall it, deleting Azure compute instance and creating a fresh instance but nothing worked, I am still facing the issue.
What is the problem here and how to resolve this?
ps- saksham-dubey is my compute instance name, which is a Azure Compute Instance (Nvidia Tesla K80 GPU)
Been dealing with the same issue since Friday, tried pretty much anything to no avail.
Luckily I found a workaround by enabling SSH on a new GPU instance & connecting to the instance through Remote SSH from VS Code.
Will keep posted if I found a solution for the UI access.
I found the fix to the problem.
The problem was caused due to some backend error in the 'Azure Machine Learning' vs-code extension.
The issue was caused in the version: 0.6.26
The fix was implemented on the version: 0.6.27
Updating your vs-code extension will make it work.
For any further information you can refer: Github Link to vscode-tools-for-ai
Also you can open an issue on same Github page, if anything like this happens again.
I'm coding a discord bot in python. Whenever I try to connect to a specific site, on my EC2 instance running Amazon Linux 2, the script returns the following error:
discord.ext.commands.errors.CommandInvokeError: Command raised an exception: ClientConnectorSSLError: Cannot connect to host secure.site.here:443 ssl:None [[SSL: WRONG_SIGNATURE_TYPE] wrong signature type (_ssl.c:1076)]
(actual url snipped.)
The bot itself is dockerized, running python:3.7.4-slim-buster. The error is not present when built with image python:3.7.4-slim-stretch.
I've also tested the same script built with base image -buster on MacOS and also a GCP Compute Engine instance, both are error free.
What am I missing? Any tips welcome.
First of all I checked the current tls version used by connection to the site. It was 1.2.
I got same error with wget so I understand that problem not in python itself, but somewhere in openssl and system settings.
On Ubuntu 20.04.1 LTS I upgrade openssl from 1.1.1f to 1.1.1g - it solves the issue for me. I followed this manual.
I've set up Apache Mesos 0.21.2 on a virtual machine. The installation was performed by downloading the sources, compiling it and applying make install.
On another virtual machine I've copied the build directory in order to use it as a slave system.
I wanted to start with a small 'hello world' framework as showed in http://jamesporter.me/2014/11/15/hello-mesos.html
however, when I'm executing the python framework with
python hello_mesos.py
I get the following log:
I1227 19:16:02.790803 1678 sched.cpp:137] Version: 0.21.1
2015-12-27 19:16:02,790:1678(0x7f6b1e3de700):ZOO_INFO#log_env#712: Client
environment:zookeeper.version=zookeeper C client 3.4.5
...
2015-12-27
19:17:09,526:1678(0x7f6b1bf7e700):ZOO_ERROR#handle_socket_error_msg#1697:
Socket [127.0.0.1:2181] zk retcode=-4, errno=111(Connection refused): server
refused to accept the client
What can be the source that triggers this error? Is there any other way to get more information?
Thank you in advance for any hints and
with best regards
I'd recommend that you use a recent Mesos version, 0.21.2 is quite old as 0.26.0 is out. There are also precompiled packages available.
Concerning your actual problem, it appears that either
ZooKeeper is not started on the host you're trying to execute your framework on
If you're trying to reach ZK from another host, you need to set the actual IP
Today when I attempted to launch the appengine SDK (python) I saw the error "Errors occurred" - see image below. More details:
The log file referenced in the error message does not exist at that location
I tried uninstalling the SDK entirely, and re-installing 1.9.13.msi (python)
It's on Windows 7, 74 Pro, python 2.7
I tried renaming the app files at %APPDATA%/local/temp/appengine.*
I'd been using app engine fine for weeks on this machine. Yesterday my machine failed to go to sleep properly, as it often does. At power up it booted into a new/clean Windows - ie. it crashed and lost all its state. (Warning dont buy a Thinkpad T440s for Windows until they have this fixed..). I suspect that something was corrupted when the machine crashed.
I tried restarting Windows, of course ;)
Any ideas on how to fix this?
Found the answer here: https://groups.google.com/forum/#!msg/google-appengine/Uphb04hV2tg/K6vL4osY_xgJ
I renamed the file 'google_appengine_launcher.ini' at users/[my profile]/Goolge
After upgrading GAE to 1.7.6 on OS X Lion, I'm getting an error I can't resolve when I run dev_appserver.py. It was working fine in the previous version. Initially the error said I needed to install PyObjC and PIL, which I did, using pip. Now, it says can't open file '/usr/local/bin/_python_runtime.py': [Errno 2] No such file or directory. Here is the full error:
INFO 2013-04-01 23:01:15,091 sdk_update_checker.py:244] Checking for updates to the SDK.
INFO 2013-04-01 23:01:15,660 sdk_update_checker.py:272] The SDK is up to date.
INFO 2013-04-01 23:01:15,705 api_server.py:152] Starting API server at: http://localhost:50096
INFO 2013-04-01 23:01:15,721 dispatcher.py:98] Starting server "default" running at: http://localhost:8080
INFO 2013-04-01 23:01:15,759 admin_server.py:117] Starting admin server at: http://localhost:8000
/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python: can't open file '/usr/local/bin/_python_runtime.py': [Errno 2] No such file or directory
ERROR 2013-04-01 23:01:15,785 http_runtime.py:221] unexpected port response from runtime ['']; exiting the development server
INFO 2013-04-01 23:01:16,775 api_server.py:517] Applying all pending transactions and saving the datastore
INFO 2013-04-01 23:01:16,775 api_server.py:520] Saving search indexes
Exception in thread Thread-1 (most likely raised during interpreter shutdown)
I found a similar post about this here, but it was on a Windows 7 machine and it doesn't appear he's found a solution (or perhaps he did and didn't follow up). Any ideas?
Edit: It works with the GoogleAppEngineLauncher GUI but not the command line. Not sure why.
From my response to Fat Lotus, here's what worked for me:
I updated GAE Launcher again which recreated the symlinks and now it works fine. The current symlink that /usr/local/bin/_python_runtime.py links to is /Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/_python_runtime.py
I've been having this problem as well (related to a Homebrew install); I've managed to get things working by using the following:
ln -s /usr/local/Cellar/google-app-engine/1.7.5/share/google-app-engine/_python_runtime.py /usr/local/bin/_python_runtime.py
I saw the same error in regards to _python_runtime.py not being found. It was caused by not running the GoogleAppEngineLauncher by first copying the application to the local drive.
Make sure you read the error messages carefully, as I didn't read all of them at first. Running the installer from the local disk resolved this issue, at least for me.