This is typically less of an OCI data collection issue than an "infrastructure" issue - basically, the Acq(uisition) process is sending data to the OCI server, but it isn't being ingested. The OCI server is throwing a HTTP 500 message, which is a bad thing.
It could be that your OCI server is underpowered, or there could be an OCI bug here.
If you are sending OCI ASUP, PM me the OCI site name, and I can poke around.
If you open a support case, you will want to include the contents of the