You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Yes, we have seen different issue after hitting "BUG BUG BUG reconnection function is nil" in the log, e.g. agent won't send metric to the control plane, or "404 policy not found". The work around we use is to restart the agent a few times(systemctl restart ) to get things back to normal
{"level":"error","ts":"2024-01-26T00:59:21.631Z","caller":"agent/logging.go:49","msg":"ERROR mqtt log","payload":["[client] ","BUG BUG BUG reconnection function is nil",null]}
Describe the solution you'd like
already spoke w Shannon in this case we would like the container to exit/die right away and with the docker configure set to restart: always it will auto start up new container
Describe alternatives you've considered
restart manually like mention above
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Yes, we have seen different issue after hitting "BUG BUG BUG reconnection function is nil" in the log, e.g. agent won't send metric to the control plane, or "404 policy not found". The work around we use is to restart the agent a few times(systemctl restart ) to get things back to normal
{"level":"error","ts":"2024-01-26T00:59:21.631Z","caller":"agent/logging.go:49","msg":"ERROR mqtt log","payload":["[client] ","BUG BUG BUG reconnection function is nil",null]}
Describe the solution you'd like
already spoke w Shannon in this case we would like the container to exit/die right away and with the docker configure set to restart: always it will auto start up new container
Describe alternatives you've considered
restart manually like mention above
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: