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.

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

Error while using regex parser. #42

Closed
dhope-nagesh opened this issue Feb 26, 2021 · 4 comments
Closed

Error while using regex parser. #42

dhope-nagesh opened this issue Feb 26, 2021 · 4 comments
Assignees

Comments

@dhope-nagesh
Copy link

dhope-nagesh commented Feb 26, 2021

I am trying to deploy regex-parser example https://github.com/kubesphere/fluentbit-operator/tree/master/manifests/regex-parser
But i am getting following error

[2021/02/26 12:28:40] [ info] [engine] started (pid=87)
[2021/02/26 12:28:40] [ info] [storage] version=1.0.6, initializing...
[2021/02/26 12:28:40] [ info] [storage] in-memory
[2021/02/26 12:28:40] [ info] [storage] normal synchronization mode, checksum disabled, max_chunks_up=128
[2021/02/26 12:28:40] [error] [sqldb] cannot open database /fluent-bit/tail/pos.db
[2021/02/26 12:28:40] [error] [input:tail:tail.0] could not open/create database
[2021/02/26 12:28:40] [error] [filter:parser:parser.0] requested parser 'my-regex' not found
[2021/02/26 12:28:40] [error] [filter:parser:parser.0] Invalid 'parser'
[2021/02/26 12:28:40] [error] Failed initialize filter parser.0
[2021/02/26 12:28:40] [ info] [input] pausing tail.0
[2021/02/26 12:28:40] [error] [lib] backend failed
level=error msg="Fluent bit exited" error="exit status 255"
@benjaminhuo
Copy link
Member

@wanjunlei Pls help to take a look at this issue

@wanjunlei
Copy link
Collaborator

Ok, I had fixed this bug, you can fix this bug by update the fluent-bit image.

Run this command,

kubectl edit fluentbits.logging.kubesphere.io -n kubesphere-logging-system fluent-bit

and add the following part.

spec:
  imagePullPolicy: Always

This will restart the fluent bit.

@FeynmanZhou
Copy link
Member

@dhope-nagesh Has this issue been resolved?

@kakaNo1
Copy link

kakaNo1 commented Nov 1, 2023

I think this problem still exists. We encountered the same error message. link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants