unexpected end of JSON input

[ssantrosyan777]

Hey,

After updating my notification-controller image version to 1.4.0 started to get this kind of errors.

What's the issue and how can I fix it ?

{"level":"error","ts":"2024-11-07T17:04:10.160Z","logger":"event-server","msg":"decoding the request body failed","error":"unexpected end of JSON input"}
{"level":"info","ts":"2024-11-07T17:05:03.650Z","logger":"event-server","msg":"discarding event, no alerts found for the involved object","eventInvolvedObject":{"kind":"Kustomization","namespace":"flux-system","name":"flux-system","uid":"f4758fc5-ddce-469f-8308-e0890de832aa","apiVersion":"kustomize.toolkit.fluxcd.io/v1","resourceVersion":"76164778"}}

[stefanprodan]

Can you please post here the output of flux check

[darkowlzz]

Nudging this for more information.

I went through the notification-controller eventMiddleware() code which logs this error and couldn't see any recent change in the Event type which would cause such decoding failure. Also looked at kustomize-controller as the shared log belongs to a Kustomization but couldn't find anything relevant. kustomize-controller uses the same event recorder that all the other components use. Can't think of any reason for sending a badly JSON payload using the event recorder.
Looking at the log timestamp carefully, it seems that the error and the Kustomization info log are about a minute apart. So they are likely unrelated.

We would need more information about the version of the flux components to be able to debug this.

[npapapietro]

I had this same issue in notification-controller:1.40. The cause was a bad token for a provider that was giving a non-json response from the endpoint. Github in my case.

Hope this helps