S3 upload Failed (maybe due to big file)

[AndMerlin]

We faced an issue on both versions 8.10.0 and 9.0.0

The core dump handler is able to see a crash, on 8.10.0

Uploading: var/mnt/core-dump-handler/cores/<>.zip zip size is 10115781 S3 Returned: 200

But there is no file in S3 bucket in 9.0.0 the situation is different

Uploading: var/mnt/core-dump-handler/cores/<>.zip zip size is 10864637 Upload Failed Got HTTP 404 with content ' core-dump-handler-mk4xh coredump-container <Error><Code>NoSuchUpload</Code><Message>The specified upload does not exist. The upload ID may be invalid, or the upload may have been aborted or completed.</Message> <.......> </Error>'

But there is no file in S3 bucket

while testing via kubectl run -i -t segfaulter --image=quay.io/icdh/segfaulter --restart=Never` All works as expected. I see that the dump failed is much bigger than one created while segfaulter crashed.

Does Core-Dump-Handler have limitations? Any suggestions on how to solve it?

[jfcheleno]

I'm running into similar issue. Currently running 8.10.0. It does upload it to S3 with a similar message but the zip file is then corrupted, when trying to unzip it I run into the following error

Archive:  3fb231f9-9b0e-407f-8644-d63ebbdec685.zip
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.

This seems to happen only with large dumps and the zip files always end up with around 6.1GB (not sure if that can be related)

[wmorgan6796]

We also ran into this. We found that it was because we timed out creating and then pushing the file to the object store. We're trying to combat this via disabling compression