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

Logs Exploding with 502 errors #12

Closed
probably-not opened this issue Oct 2, 2022 · 5 comments · Fixed by #14
Closed

Logs Exploding with 502 errors #12

probably-not opened this issue Oct 2, 2022 · 5 comments · Fixed by #14
Assignees
Labels
bug Something isn't working

Comments

@probably-not
Copy link

Starting in the last few days, my logs have exploded with the following error:

ERR! <CommunicationApiListener> An error occured on socket connection: Unexpected server response: 502 undefined

This error happens every 5 seconds.

I can't tell exactly when it started since it has been happening so much that it has caused older logs to be deleted (our log storage rolls based on storage space).

@boroskoyo boroskoyo added the bug Something isn't working label Oct 3, 2022
@boroskoyo
Copy link
Contributor

We have found out the root cause and working on a fix to avoid log explosions for all our agents. I'll get back to you when it is solved

@bcaglayan bcaglayan linked a pull request Oct 5, 2022 that will close this issue
@probably-not
Copy link
Author

Hey @serkan-ozal I see that you've closed this issue. Does this mean that the 502 errors have been fixed or that only the log explosion has been fixed?

@serkan-ozal serkan-ozal reopened this Oct 9, 2022
@serkan-ozal
Copy link

serkan-ozal commented Oct 9, 2022

Hi @probably-not, it has been closed automatically by Github when I merge the associated PR. I think @boroskoyo can give you more details about the issue

@boroskoyo
Copy link
Contributor

Hi @probably-not, we have fixed log explosions in the agent. In case of 502 error, we haven't found anything more than one time connectivity problem. We will take further action if we encounter this problem again.

@probably-not
Copy link
Author

Closing this as solved, there was on issue on the Sidekick side, an incorrect configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

Successfully merging a pull request may close this issue.

4 participants