-
Notifications
You must be signed in to change notification settings - Fork 444
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
facing BAD_INPUT_DATA error while extracting TEI XML #1110
Comments
Attaching a sample file where this happened: |
@bhargav-ss could you share more information on the deployment of the server? Docker or native? How much resources are allocated (CPU/GPU, Ram). Also could you share the log from the service? |
Thanks for the prompt response. It is a native deployment. We were using Unfortunately I haven't retained logs of grobid service itself when this failed. I can try running this again and reproduce the error. |
For real-time grobid conversion in application, we are using |
Got the error in one of our real-time services:
|
Got one more log with
|
Hello @bhargav-ss |
Our grobid version: We are running grobid server as a systemd service. |
java --version
)?Error Stack Trace
We are running a pipeline which processes large number of PDF files and extracts TEI XML via grobid service. I have observed this behaviour where after a certain point, the service starts giving BAD_INPUT_DATA error on a lot of requests. Once I destroy the server and spawn a fresh grobid instance, the service give successful extraction on same PDF file where it gave
BAD_INPUT_DATA
earlier.The text was updated successfully, but these errors were encountered: