Snow-Fox-Data / dss-thread

Dataiku Thread™ Data Catalog Plugin by Snow Fox Data
https://www.snowfoxdata.com/thread-plugin
Other
3 stars 2 forks source link

Failed to post events to event server #27

Closed clayms closed 2 years ago

clayms commented 2 years ago

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.

rymoore commented 2 years ago

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

clayms commented 2 years ago

@rymoore version 1.1.4 fixed the issue.