Can't get cqlsh to run - cassandra

I've installed DSE 5.1.10 + the DSE demos as per these instructions on ubuntu.
Apparently it doesn't come with cqlsh so I went about installing it myself.
I've tried various methods the latest of which being
pip3 install cqlsh
this completed successfully and I can now run
cqlsh -version
and get
cqlsh 5.0.1
when running
cqlsh
I get the following error
Traceback (most recent call last):
File "/usr/bin/dsecqlsh.py", line 510, in <module>
cqlsh.main(*cqlsh.read_options(sys.argv[1:], os.environ))
File "/usr/bin/cqlsh.py", line 2447, in main
encoding=options.encoding)
File "/usr/bin/dsecqlsh.py", line 383, in __init__
connect_timeout=connect_timeout)
File "/usr/bin/cqlsh.py", line 528, in __init__
self.get_connection_versions()
File "/usr/bin/cqlsh.py", line 645, in get_connection_versions
if result['dse_version']:
KeyError: 'dse_version'
Any ideas what I'm doing wrong?
Thanks

I'm curious as to your source of information that says DSE does not include the cqlsh command line. As far as I am aware all versions of DSE will install this.
To me it looks like you have clobbered your cqlsh install with the pip3 install command. You've likely installed the OSS version of cqlsh, hence the error complaining about the dse_version above.
I would say at first try uninstalling the pip3 version and see if that helps and then uninstall DSE and reinstall.

Not sure what was wrong, resorted to removing everything and installing from tarball instead following https://docs.datastax.com/en/install/doc/install60/installTARdse.html

Related

Using pyspark on Windows not working- py4j

I installed Zeppelin on Windows using this tutorial and this.
I also installed java 8 to avoid problems.
I'm now able to start the Zeppelin server, and I'm trying to run this code -
%pyspark
a=5*4
print("value = %i" % (a))
sc.version
I'm getting this error, related to py4j. I had other problems with this library before (same as here), and to avoid them I replaced the library of py4j in the Zeppelin and Spark on my computer with the latest version- py4j 0.10.7.
This is the error I get-
Traceback (most recent call last):
File "C:\Users\SHIRM~1.ARG\AppData\Local\Temp\zeppelin_pyspark-1240802621138907911.py", line 309, in <module>
sc = _zsc_ = SparkContext(jsc=jsc, gateway=gateway, conf=conf)
File "C:\Users\SHIRM.ARGUS\spark-2.3.2\spark-2.3.2-bin-hadoop2.7\python\pyspark\context.py", line 118, in __init__
conf, jsc, profiler_cls)
File "C:\Users\SHIRM.ARGUS\spark-2.3.2\spark-2.3.2-bin-hadoop2.7\python\pyspark\context.py", line 189, in _do_init
self._javaAccumulator = self._jvm.PythonAccumulatorV2(host, port, auth_token)
File "C:\Users\SHIRM.ARGUS\Documents\zeppelin-0.8.0-bin-all\interpreter\spark\pyspark\py4j-0.10.7-src.zip\py4j\java_gateway.py", line 1525, in __call__
File "C:\Users\SHIRM.ARGUS\Documents\zeppelin-0.8.0-bin-all\interpreter\spark\pyspark\py4j-0.10.7-src.zip\py4j\protocol.py", line 332, in get_return_value
py4j.protocol.Py4JError: An error occurred while calling None.org.apache.spark.api.python.PythonAccumulatorV2. Trace:
I googled it, but couldn't find anyone that it had happened to.
Does anyone have an idea how can I solve this?
Thanks
I feel you have installed Java 9 or 10. Uninstall either of those versions and install a fresh copy of Java 8 from here: https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
And set JAVA_HOME inside hadoop_env.cmd (open with any text-editor).
Note: Java 8 or 7 are stable versions to use and uninstall any existing versions of JAVA. Make sure you add JDK (not JRE) in JAVA_HOME.
I faced the same problem today, and I fixed it by adding PYTHONPATH in the system environment like:
%SPARK_HOME%\python\lib\py4j;%SPARK_HOME%\python\lib\pyspark

Error when running Anaconda navigator

I get this error when running anaconda-navigator on Linux Mint 18.1:
QApplication: invalid style override passed, ignoring it.
2018-03-20 19:54:36,039 - ERROR anaconda_api.is_vscode_available:871
''
Traceback (most recent call last):
File "/home/daniel/anaconda3/lib/python3.5/site-packages/anaconda_navigator/
api/anaconda_api.py", line 368, in _conda_info_processed
processed_info = self._process_conda_info(info)
File "/home/daniel/anaconda3/lib/python3.5/site-packages/anaconda_navigator/
api/anaconda_api.py", line 479, in _process_conda_info
processed_info = info.copy()
AttributeError: 'bytes' object has no attribute 'copy'
...
I updated using:
conda update conda
conda update anaconda-navigator
conda update navigator-updater
The versions are:
conda 4.5.0
anaconda Command line client (version 1.6.14)
I have no idea how or why this works, but if you delete the .condarc file in your user folder, it starts to work fine. At least for me and some users here:
https://github.com/ContinuumIO/anaconda-issues/issues/11734#issuecomment-638591004
Putting this here in case anyone else runs into the same problem.
For me, It was only the fact that I modified too much my file .condarc.
I restored back and solved my issue

Xcode 9.1 export fails with "The /usr/bin/xattr tool may be damaged"

Xcode 9.0.1 crash when export ipa or upload to App Store in MacOS 10.13.1.
After upgraded to Xcode 9.1 (9B55), it shows error as below when export.
Stripping extended attributes failed.
"/usr/bin/xattr -crs /var/folders/mm/h01jykrs7gv9w7jjb0yt609w0000gp/T/XcodeDistPipeline.Uay/Root/Payload/GitSmartHome.app" exited with a non-zero status. The /usr/bin/xattr tool may be damaged.
It seems xattr was damaged, and when run xattr in Terminal, it prompts below error.
xattr
Traceback (most recent call last):
File "/usr/bin/xattr-2.7", line 7, in <module>
from pkg_resources import load_entry_point
File "build/bdist.macosx-10.13-intel/egg/pkg_resources/__init__.py", line 3019, in <module>
File "build/bdist.macosx-10.13-intel/egg/pkg_resources/__init__.py", line 3003, in _call_aside
File "build/bdist.macosx-10.13-intel/egg/pkg_resources/__init__.py", line 3032, in _initialize_master_working_set
File "build/bdist.macosx-10.13-intel/egg/pkg_resources/__init__.py", line 655, in _build_master
File "build/bdist.macosx-10.13-intel/egg/pkg_resources/__init__.py", line 963, in require
File "build/bdist.macosx-10.13-intel/egg/pkg_resources/__init__.py", line 849, in resolve
pkg_resources.DistributionNotFound: The 'xattr==0.6.4' distribution was not found and is required by the application
How to fix it or re-install xattr?
Xcode always looks at /usr/bin/xattr, regardless of your paths (as you might have a working xattr installed elsewhere).
Typing in /usr/bin/xattr gave this output:
/usr/bin/xattr
Traceback (most recent call last):
File "/usr/bin/xattr-2.7", line 7, in <module>
from pkg_resources import load_entry_point
File "build/bdist.macosx-10.12-intel/egg/pkg_resources/__init__.py", line 72, in <module>
File "build/bdist.macosx-10.12-intel/egg/packaging/requirements.py", line 59, in <module>
TypeError: __call__() takes exactly 2 arguments (1 given)
You need to get your system's python happy again. I seem to have broken mine at some point. Not sure how.
I ran the following and got a screen full of errors.
/usr/bin/python -m pip install -U setuptools
Afterwards, I ran /usr/bin/xattr again it it was silent. This seems to be the test for whether it's healthy.
My XCode exports now without the error.
The crux is that your /usr/bin/xattr will give you some kind of error, whether it's permissions or some other python/setup issue. You need to fix that to have your builds working again.
Edit:
For those with permission issues, run this:
sudo chown -R $USER:$(id -g) /Users/$USER/Library/Python
I had this problem too. It turned out that this started happening after I zapped /Library/Python/2.7 and with it I deleted /Library/Python/2.7/site-packages/Extras.pth. Here's what was in it:
/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python
/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/PyObjC
The first of these directories contains an old version of xattr that still supports -c option (something I could not resolve by installing xattr v0.6.4 myself).
➜ /usr/bin/xattr
python version 2.7.14 can't run /usr/bin/xattr. Try the alternative(s):
/usr/bin/xattr-2.6 (uses python 2.6)
/usr/bin/xattr-2.7 (uses python 2.7)
Run "man python" for more information about multiple version support in
Mac OS X.
➜ cd /usr/bin
➜ sudo rm xattr
➜ sudo ln -s xattr-2.7 xattr
➜ /usr/bin/xattr
#Ren gave a good hint, following his thought, with the help of Ned Deli's Answer, solved the problem here.
My situation: python 2.7 as default system version(use pyenv normally). /usr/bin/xattr always tempts to call /usr/bin/xattr-2.7, which won't be successful. Calling xattr-2.6 works fine, forcing /usr/bin/xattr call xattr-2.6 leads to "option -c not recognized" while the XCode trying to call xattr -crs ....
Solution: After using command: $defaults write com.apple.versioner.python Version 2.6 Xcode can finally distribute my app.
You can set your system default python whenever you like back to 2.7 with:
$unset VERSIONER_PYTHON_VERSION
If your mac throws you an error like "option -c not recognized" you can still try to launch the original source code "xattr python tool" using a command like this:
sudo python /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/xattr/tool.pyc -cr /Applications/[Application].app
It works for me ;)
I just ran into the same issue and resolved it with:
/usr/bin/python -m pip install xattr==0.6.4
reinstall xcode-select, open terminal and type
xcode-select --install

Unable to launch anaconda navigator in windows after tensor flow installation

I tried to install tensor flow library in anaconda and after that I am unable to launch anaconda navigator. I am using windows machine and anaconda was working fine before. Error is as below:
An unexpected error occurred on Navigator start-up
Psutil.AccessDenied(pid=9636)
Traceback (most recent call last):
File "C:\Users\india\AppData\Local\Continuum\Anaconda3\lib\site-packages\psutil\_pswindows.py", line 620, in wrapper
return fun(self, *args, **kwargs)
File "C:\Users\india\AppData\Local\Continuum\Anaconda3\lib\site-packages\psutil\_pswindows.py", line 690, in cmdline
ret = cext.proc_cmdline(self.pid)
PermissionError: [WinError 5] Access is denied
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\india\AppData\Local\Continuum\Anaconda3\lib\site-packages\anaconda_navigator\exceptions.py", line 75, in exception_handler
return_value = func(*args, **kwargs)
File "C:\Users\india\AppData\Local\Continuum\Anaconda3\lib\site-packages\anaconda_navigator\app\start.py", line 108, in start_app
if misc.load_pid() is None: # A stale lock might be around
File "C:\Users\india\AppData\Local\Continuum\Anaconda3\lib\site-packages\anaconda_navigator\utils\misc.py", line 384, in load_pid
cmds = process.cmdline()
File "C:\Users\india\AppData\Local\Continuum\Anaconda3\lib\site-packages\psutil\__init__.py", line 701, in cmdline
return self._proc.cmdline()
File "C:\Users\india\AppData\Local\Continuum\Anaconda3\lib\site-packages\psutil\_pswindows.py", line 623, in wrapper
raise AccessDenied(self.pid, self._name)
psutil.AccessDenied: psutil.AccessDenied (pid=9636)
I have uninstalled and then installed anaconda, still facing same issue.
I could fix it by simply resetting the navigator via Command Prompt:
C:\Anaconda3\anaconda-navigator --reset
I use the anaconda in win10 x64 (python3.x) and I got this problem this morning as well. All the things had been done in anaconda was that I installed a package called pywinauto, then I turned off the computer and went home.
I follow the suggestion from https://groups.google.com/a/continuum.io/forum/#!topic/anaconda/4hBTDOcDzgo by lan, I update the anaconda by using the command.
conda update anaconda-navigator
However, the error occurred the same.
Then I reboot the computer and restart the anaconda, magic thing happens! the anaconda works fine!
I think maybe some configuration has been changed when I install the new package, and this change is conflicted with the current configuration which you need to reboot the computer to take effect. you should note that turn off computer then restart it is not equal to reboot it.
So, just reboot the computer and it will be fine.
I solved this issue by running in the anaconda prompt :
anaconda-navigator --reset

Using virtualenv with python3 in openSuSE

I am experiencing a problem when using virtualenv in openSuSE 12.3 with Python3:
I installed the python3 and python3-devel packages.
Then I installed the newest distribute and pip and finally virtualenv using pip.
When I try to create a virtualenv I get the following error:
$ virtualenv-3.3 venv01
Using base prefix '/usr'
New python executable in venv01/bin/python3.3
Also creating executable in venv01/bin/python
Installing distribute.........................................................................................................................................................................................................................................................................................................................................................................................................done.
Installing pip....
Complete output from command /home/user/venv01/bin/python3.3 -x /home/user/venv01/bin/easy_install /usr/local/lib/pytho...ort/pip-1.3.1.tar.gz:
/home/user/venv01/bin/python3.3: can't open file '/home/user/venv01/bin/easy_install': [Errno 2] No such file or directory
----------------------------------------
...Installing pip...done.
Traceback (most recent call last):
File "/usr/local/bin/virtualenv-3.3", line 9, in <module>
load_entry_point('virtualenv==1.9.1', 'console_scripts', 'virtualenv-3.3')()
File "/usr/local/lib/python3.3/site-packages/virtualenv.py", line 979, in main
no_pip=options.no_pip)
File "/usr/local/lib/python3.3/site-packages/virtualenv.py", line 1094, in create_environment
install_pip(py_executable, search_dirs=search_dirs, never_download=never_download)
File "/usr/local/lib/python3.3/site-packages/virtualenv.py", line 667, in install_pip
filter_stdout=_filter_setup)
File "/usr/local/lib/python3.3/site-packages/virtualenv.py", line 1057, in call_subprocess
% (cmd_desc, proc.returncode))
OSError: Command /home/user/venv01/bin/python3.3 -x /home/user/venv01/bin/easy_install /usr/local/lib/pytho...ort/pip-1.3.1.tar.gz failed with error code 2
Running it with -vvv yields some interesting output that shows that distribute
is extracted to <venv>/local/lib/python3.3/site-packages/.
I wonder why distribute is not installed into <venv>/lib/python3.3/site-packages/?
Does anyone have an idea why this happens and how I can use virtualenv in
openSuSE without compiling python3 myself?
[now fixed in latest patches from opensuse]
[oh! i just realised you are the same person as the original link. sorry. but i will leave this as it is a top result for google search on this issue (was searching myself for any update) so it may help others.]
this is a known issue, discussed at https://forums.opensuse.org/english/get-technical-help-here/applications/484475-using-virtualenv-python-3-a.html and with an open bug at https://bugzilla.novell.com/show_bug.cgi?id=809831
the only work-around i know of is to install everything yourself. it's not so hard, and i describe what is necessary at http://www.acooke.org/cute/GettingPyt0.html
basically:
install python 3.3 from source (do an "altinstall" to install as /usr/local/bin/python3.3)
fix the lib issue (link lib_dynload from /usr/local/lib64/python3.3 to /usr/local/lib/python3.3)
install distutils
install virtualenv
then you can use python3.3 and virtual-env-3.3 etc as expected.

Resources