Calling API deployment returns Worker exited prematurely: signal 9 (SIGKILL) Job: XXX error
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 718
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 23
Description
Describe the bug
Calling API deployment returns Worker exited prematurely: signal 9 (SIGKILL) Job: XXX error.
To reproduce
I'm using Docker environment on macOS via Docker Desktop for Mac. I've setup test project as per Start User guide and make a call to API deployment. API call returns this error after some time:
{
"message": {
"execution_status": "ERROR",
"status_api": "/deployment/api/mock_org/b2b-invoice-process/?execution_id=caf99a46-aff6-4648-bdec-6361ca88748e",
"error": "Worker exited prematurely: signal 9 (SIGKILL) Job: 5.",
"result": null
}
}
I did similar installation on two Macs, I've tried Postman and curl calls: result is the same.
Expected behavior
API should return either a processing result or error description good enough to indicate how to resolve the problem.
Environment details
- Version: Docker compose environment. Repo commit hash
9662435635bcb37d77697a6496ee0fff3afa36d3. - macOS: 15.3.2
- Docker desktop: 4.37.2 (179585)
- Docker version 27.4.0
- Docker Compose version v2.31.0-desktop.2
Additional context
Follow exactly the Quick start process up to Making an API call chapter
Screenshots
None. JSON returned from Unstract is above.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue using the Quick start guide through the Making an API call chapter, then inspect the Docker Compose worker logs around the API deployment request and SIGKILL. Done means identifying why the worker exits and making the API return a processing result or an actionable error description.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, python
- Domain
- api, backend, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100