Failed to bind to json
Hi all,
I noticed this message being spammed in my docker logs....
I honestly have no clue where to start....
25 Replies
Important Information
Thank you for getting in touch with your support request. To expedite a swift resolution, could you kindly provide the following information? Rest assured, we will respond promptly, and we greatly appreciate your patience. While you wait, please check the links below to see if this issue has been previously addressed. If you have managed to resolve it, please use run the command
/resolve
or press the green resolve button below.Log Files
If you possess any log files that you believe could be beneficial, please include them at this time. By default, CrowdSec logs to /var/log/, where you will discover a corresponding log file for each component.
Guide Followed (CrowdSec Official)
If you have diligently followed one of our guides and hit a roadblock, please share the guide with us. This will help us assess if any adjustments are necessary to assist you further.
Screenshots
Please forward any screenshots depicting errors you encounter. Your visuals will provide us with a clear view of the issues you are facing.
© Created By WhyAydan for CrowdSec ❤️
The error is sent in the 'main server' docker. It's a distributed setup, and the only bouncers I have active at the moment of errors are Openresty.
So you have a central LAPI that openresty is talking too?
correct
Sorry, my head is all over the place rn. Can't compose a decent sentence
can you check the api logs?
ohh wait your inside a container
it should be the same stdout
When filtering on 'error' these are the only lines I see in the last 5000 logs
Anything else I should look for?
can you grep for "500" status code?
Can't find any
which openresty / remediation version are you on?
looking at the code we return
400
status code not 500Latest normally, lemme check
crowdsec-openresty-bouncer v1.1.1
192.168.202.4 & 192.168.202.5 are my openresty nodes
So we have a little bit of a dilema, we need to enable debug logs on openresty but to do so would need a restart and then the metrics its currently trying to push will be lost so will most likely resolve itself.
So you think a restart of the openrest node should fix the issue? 'Cause that server has been restarted sometimes in the last couple of days
Yeah it should, unless the metrics are completely broken but the same system is within nginx and I have it running / havent encountered this.
I'll fully reboot both servers and follow it up...
After rebooting the issue is back
Can you add
debug
at the end of your error_log
directive and restart openresty ?
This will make the bouncer output debug logs, including the payload sent to LAPI for the metrics (it will spam quite a bit when a request is checked tho)Like so right? In the openresty/nginx config:
yes
Okay, I'm monitoring. Will wait for a new alert to trigger I suppose?
Yes, the bouncer pushes its metrics every 15 minutes
and did you see the error in crowdsec logs at the same time ?
nope
All errors filtered out
Any thoughts?