We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Docker
Process timeout exceeded
0.36.5
No response
http://10.27.24.136:5003/pdf-to-word
docker run -d \ --name stirling-pdf \ -p 5003:8080 \ -v "/app/StirlingPDF/trainingData:/usr/share/tessdata" \ -v "/app/StirlingPDF/extraConfigs:/configs" \ -v "/app/StirlingPDF/customFiles:/customFiles/" \ -v "/app/StirlingPDF/logs:/logs/" \ -v "/app/StirlingPDF/pipeline:/pipeline/" \ -e DOCKER_ENABLE_SECURITY=false \ -e INSTALL_BOOK_AND_ADVANCED_HTML_OPS=false \ -e LANGS=en_GB \ stirlingtools/stirling-pdf:latest
05:23:26.316 [qtp311765759-141] INFO s.s.SPDF.utils.ProcessExecutor - Running command: soffice --headless --nologo --infilter=writer_pdf_import --convert-to docx --outdir /tmp/output_13112729105463121359 /tmp/input_5109299371218741226.pdf 05:23:26.320 [qtp311765759-161] WARN o.e.j.ee10.servlet.ServletChannel - handleException /api/v1/convert/pdf/word java.io.IOException: Process timeout exceeded.
The text was updated successfully, but these errors were encountered:
Does this problem have anything to do with the Chinese Internet? Do you need to call Google's services?
Sorry, something went wrong.
If you check settings yml at the bottom we have set timeout times for each operation type that might need it
No branches or pull requests
Installation Method
Docker
The Problem
Process timeout exceeded
Version of Stirling-PDF
0.36.5
Last Working Version of Stirling-PDF
No response
Page Where the Problem Occurred
http://10.27.24.136:5003/pdf-to-word
Docker Configuration
Relevant Log Output
Additional Information
No response
Browsers Affected
No response
No Duplicate of the Issue
The text was updated successfully, but these errors were encountered: