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.

Sign up for GitHub

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

Jump to bottom

Failed to post events to event server #27

Closed
clayms opened this issue Oct 12, 2022 · 2 comments
Closed

Failed to post events to event server #27

clayms opened this issue Oct 12, 2022 · 2 comments
Labels
bug Something isn't working

Comments

@clayms
Copy link

clayms commented Oct 12, 2022 •
edited
Loading

Describe the bug
Our entire catalog somehow got wiped out.

Now when trying to re-scan the following message pops up on the Thread Public web interface with only an "OK" button:

dss.my-corp.com says:
'to'

The logs show the following over and over over again.

[2022/10/12-21:19:27.347] [Thread-350] [WARN] [dip.http.utils]  - Got response code 502
[2022/10/12-21:19:27.347] [Thread-350] [WARN] [dku.auditmechanism.eventserver]  - Failed to post events to event server
java.io.IOException: Unknown error on command (HTTP code:502):<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>

	at com.dataiku.dip.util.HTTPClientUtils.handleJSONResp(HTTPClientUtils.java:226)
	at com.dataiku.common.rpc.InternalAPIClient.handleJSONResp(InternalAPIClient.java:866)
	at com.dataiku.common.rpc.APIKeyAuthAPIClient.handleJSONResp(APIKeyAuthAPIClient.java:96)
	at com.dataiku.common.rpc.InternalAPIClient.postObject(InternalAPIClient.java:310)
	at com.dataiku.dip.security.audit.targets.EventServerTarget$QueueSender.run(EventServerTarget.java:167)
[2022/10/12-21:19:27.457] [qtp722417467-376348] [DEBUG] [dku.tracing]  - [ct: 0] Start call: /api/futures/get-update [GET] user=user.one [futureId=VOvlVVLf]
[2022/10/12-21:19:27.457] [qtp722417467-376348] [DEBUG] [dku.tracing]  - [ct: 0] Done call: /api/futures/get-update [GET] time=0ms user=user.one [futureId=VOvlVVLf]

To Reproduce
Steps to reproduce the behavior:

  1. re-scan DSS

Expected behavior
The catalog gets rebuilt

Additional context
Add any other context about the problem here.

  • Chrome
  • DSS version 11.0.1
  • Thread™ version 1.1.3
@clayms clayms added the bug Something isn't working label Oct 12, 2022
@rymoore
Copy link
Contributor

rymoore commented Nov 8, 2022

@clayms - can you confirm that this issue has been resolved?

@clayms
Copy link
Author

clayms commented Nov 8, 2022

@rymoore version 1.1.4 fixed the issue.

@clayms clayms closed this as completed Nov 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@clayms @rymoore