-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
cassandra err="line 1:13 no viable alternative at input '(' (INSERT INTO [(]...)" #1930
Comments
We might need to run a custom image with more debug log? Have you tried adding debug level already? Could a bad character. |
Yea interestingly when I run at a debug level these logs do not show up at all. Then resetting the log level to default and they show up again. |
This issue has been automatically marked as stale because it has not had any activity in the past 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
I have the same issue with 1.4.1. |
I had the same issue, until I found this issue 1769 and 1503. I set chunks prefix and period, then restarted loki. the error gone and the problem is fixed. Everything works perfectly now. something like below should fix yours schema_config:
configs:
- from: 2018-04-15
store: cassandra
object_store: cassandra
schema: v11
index:
prefix: cassandra_index_
period: 168h
chunks:
prefix: cassandra_chunk_
period: 168h |
This issue has been automatically marked as stale because it has not had any activity in the past 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
Hey,
I've used the helm loki-stack chart to deploy loki over kubernetes.
I'm using cassandra for both chunk and index storage.
My config in the values.yaml is as follows:
Everything is up and running and for all intensive purposes I can ingest and query logs.
However I am noticing the logs are spamming with these errors:
I am using the default user cassandra, so I wouldn't think this should be any form of permission issue?
They look related to cassandra but I am at a loss for what the issue is.
The text was updated successfully, but these errors were encountered: