Errors using the lightweight docker container (v0.7.3) #1014
Comments
|
Hi @gjreda, this problem is strange, I've double checked my docker installation and it works fine. Could you give me some more details about your docker installation? Another things that you could do is execute a bash on the existing container and try to run the pdfalto_server:
|
|
Hi @lfoppiano thanks for the quick reply! FWIW I'm on an M1 mac running macOS 13.3.1. I've also allocated 4 CPU and 4 GB of memory to docker. The help menu for pdfalto_server successfully prints as well. Happy to provide any other details that might be helpful! |
|
@gjreda if you change the grobid address in the client configuration to https://kermitt2-grobid.hf.space does it work? could you try to run pdfalto with a document?
and let me know if ti works, you can use any pdf |
This worked!
This did not work and ultimately threw out the following error: Full details below |
|
mmm checking the downloaded file size, there is something weird: This is correct: This is too small: Could you share there result of |
|
|
I'm out of ideas. 🤔 I'll run it on my M1 later and let you know if I encounter any issue. |
|
@gjreda good news. I found the issue and is related to the M1. It seems that the fork mechanism does not work anymore (I did not understand why), anyway I had to add a parameter to the JDK: I've pushed a new image Could you try it out and let me know? I'm sorry, at the moment I'm a bit short of time to provide a proper multiplatform image. |
|
@lfoppiano No need to apologize! I really appreciate your help. The new image, upgrading docker, and enabling Rosetta got it working! I'm still able to cause 500 errors if I request a larger batch - nine pdfs - on the first try, before the models have been loaded. This results in from grobid_client.grobid_client import GrobidClient
server = 'http://localhost:8070'
client = GrobidClient(grobid_server=server, timeout=600)
client.process(
'processHeaderDocument',
input_path='docs',
output='test',
force=True,
verbose=True
)Another error that has popped up is I'll follow up on this thread if I run into any more issues or figure out how to consistently reproduce the Rosetta error, but I think you've solved my issue. Thank you! I really appreciate your work. |
|
@gjreda thanks! I will do more tests in the following weeks and update the documentation accordingly. The support on M1 it's a bit of a grey area also for me too. |
|
I've done some more tests, I could process several PDFs till the servers stopped answering. There is something not working well in the interface with pdfalto and it's only a problem on M1. For the OOM, I suggest you to add 2 more Gb of RAM, in general Grobid should run without problems with 4Gb, but it seems that with rosetta 4Gb are not enough. We could solve all these problems with a arm64 build, however this will take some time. |
|
If you have time please check this #1165 |
Hi grobid team!
I'm running the lightweight version of grobid via the docker container. I'm using 0.7.3.
Starting the container via
docker run -t --rm -p 8070:8070 lfoppiano/grobid:0.7.3works as expected and I'm able to load the web service at localhost:8070. However, when I load a PDF and submit the request, I get the error belowThe docker container outputs the attached errors and stacktrace: upload-errors.txt
Maybe relatedly, when using the python client, the service seems to get called properly, but errors as seen below.
I can also see that the txt files are created in the output directory, though they are empty (makes sense given the errors).
The docker container outputs the attached errors and stacktrace: api-errors.txt
Any idea what the underlying issue is? Am I calling the service improperly? Any help is very much appreciated!
The text was updated successfully, but these errors were encountered: