-
Notifications
You must be signed in to change notification settings - Fork 87
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
CQLSH tracing broken since 5.1 #336
Comments
Works for me (5.1.4):
Please post the query that failed, maybe it depends on something. |
I run cqlsh with a hostname, I dont know if that could be a reason:
I just tried with your example:
I think the error is a python error. (Did I mention that hate python? Always causes trouble :-) ) Is it related to any python version installed?
Can I do something to get a proper error/stacktrace? |
Please run DESCRIBE KEYSPACE system_tracing and post the result. Maybe it's out of whack. |
The datacenter matches the one in nodetool status:
|
this function was changed in: which seems like you are having some left over from older release in place try deleting all *.pyc files, form the directory and try it again ? how did you installed scylla, with RPM/DEB ? or other means ? |
Deleting the pyc files did the trick! It works now! Thanks! I installed scylla using apt and updated it via apt. It got updated by changing the apt-url in the sources.list and running apt upgrade. |
We should have handled those better, I think from 5.4 we gonna have cqlsh coming from https://github.com/scylladb/scylla-cqlsh hopefully we are handling it better @syuu1228 I think you addressed something like that in the newer cqlsh, right ? |
Looks like in some version we didn't adhere to the spec: https://www.debian.org/doc/packaging-manuals/python-policy/index.html#modules-byte-compilation |
I'm not sure why this issue is here and not under cqlsh? |
cause 5.1 don't have scylla-cqlsh, but it's coming from this repo |
Also just confirm with 5.4 (that has scylla-cqlsh), it doesn't generate *.pyc files anymore |
Can be closed, I believe. |
Yes, I did not see this problem again. |
Hi,
since the 5.1 upgrade it seems CQLSH is not able to print traces any more.
Instead of the trace I get the following error:
I tried tracing in various environments. 5.0 installations are still working, 5.1 gives this error. (Tried with 5.1.14 and 5.1.11)
All installations are Ubuntu based, installed using the Ubuntu repo.
Christian
The text was updated successfully, but these errors were encountered: