Skip to content
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.

Sign up for GitHub

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

Jump to bottom

invalid schema config: must specify at least one schema configuration #2906

Closed
AdieOlami opened this issue Nov 10, 2020 · 8 comments
Closed

invalid schema config: must specify at least one schema configuration #2906

AdieOlami opened this issue Nov 10, 2020 · 8 comments
Labels
stale A stale issue or PR that will automatically be closed.

Comments

@AdieOlami
Copy link

I installed logcli from the release and I keep getting this error

level=error ts=2020-11-10T09:20:39.867654699Z caller=main.go:85 msg="validating config" err="invalid schema config: must specify at least one schema configuration"

Does not matter which query I run I get that error.
@ctodea
Copy link

ctodea commented Nov 19, 2020

Are you sure you downloaded logcli and not the loki binary?

@cameronbraid
Copy link

Glad to see this issue, as I fell for the same trick !

@stale
Copy link

stale bot commented Jan 9, 2021

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.

@stale stale bot added the stale A stale issue or PR that will automatically be closed. label Jan 9, 2021
@stale stale bot closed this as completed Jan 17, 2021
@danie1k
Copy link

danie1k commented Jan 31, 2021

Just for the record - I faced the same error message.
I found that I just ran:

$ loki -verify-config /path/to/loki.yaml

when it should be:

$ loki -verify-config -config.file /path/to/loki.yaml

cyriltovena pushed a commit to cyriltovena/loki that referenced this issue Jun 11, 2021
@gouthamve @pstibrany
Move regex opt to after lookup (grafana#2973)
a98cfa4 
* Move regex opt to after lookup

fixes grafana#2906

When we use the caching client (which is what is used in most cases), we
load the entire row (tableName+HashKey) irrespective of what the
rangeKey parameters are. Which means with the optimisation, we are
loading the same row multiple times and then operating on the same data.
This PR moves the optimisation to after the data is loaded which should
be faster.

Signed-off-by: Goutham Veeramachaneni <gouthamve@gmail.com>

* Add benchmark

Signed-off-by: Goutham Veeramachaneni <gouthamve@gmail.com>

* Add changelog entry

Signed-off-by: Goutham Veeramachaneni <gouthamve@gmail.com>

* Address feedback

Signed-off-by: Goutham Veeramachaneni <gouthamve@gmail.com>

Co-authored-by: Peter Štibraný <peter.stibrany@grafana.com>
@benjoEK1337
Copy link

I had the same issue on windows. There was an empty space at the beginning of the config file which was causing the issue.

@MMaw02
Copy link

MMaw02 commented Oct 27, 2023

I had the same issue on windows. There was an empty space at the beginning of the config file which was causing the issue.

Exactly, your comment helped me. It was also calling a configuration file that was empty.

@deb3268
Copy link

deb3268 commented Dec 3, 2023

I had the same issue on windows. There was an empty space at the beginning of the config file which was causing the issue.

can you please paste your config file yaml as i am also getting the error and i have no space issues.It looks as below
auth_enabled: false
server:
http_listen_port: 3100
ingester:
lifecycler:
address: 0.0.0.0
ring:
kvstore:
store: inmemory
chunk_idle_period: 15m
chunk_retain_period: 5m
schema_config:
configs:
- from: 2021-01-01
store: boltdb
object_store: filesystem
schema: v11
index:
prefix: index_
period: 24h
storage_config:
boltdb:
directory: /tmp/loki/index

@NielsJanssen90
Copy link

I had the same issue on windows. There was an empty space at the beginning of the config file which was causing the issue.

Lol thanks for your comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
stale A stale issue or PR that will automatically be closed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@cameronbraid @danie1k @ctodea @AdieOlami @benjoEK1337 @deb3268 @MMaw02 @NielsJanssen90