R
RunPod11mo ago
maxj

Worker not consuming jobs

I am following this tutorial: https://blog.runpod.io/serverless-create-a-basic-api/ I have submitted a few requests to the API, and the UI shows a worker is running (and I am being billed for the worker) but it doesn't seem to be consuming any jobs. All the jobs remain in the "queued" state indefinitely. There are no logs in the worker logs tab. See attached screenshots. Requested 24gb worker (3090) Any idea what is going on / tips on how to debug further?
RunPod Blog
Serverless | Create a Custom Basic API
RunPod's Serverless platform allows for the creation of API endpoints that automatically scale to meet demand. The tutorial guides you through creating a basic worker and turning it into an API endpoint on the RunPod serverless platform. For this tutorial, we will create an API endpoint that helps us accomplish
No description
No description
3 Replies
ashleyk
ashleyk11mo ago
1. Don't submit multiple jobs while testing your endpoint, wait for a job to complete successfully before submitting additional jobs. 2. Don't click the logs tab, click on the actual worker and then get its logs, there are logs for the worker itself. There will be no logs for your endpoint under the logs tab until the serverless SDK is able to start successfully.
maxj
maxjOP11mo ago
thanks! the logs from clicking the worker revealed the issue - "Exec format error" from docker as the image was built on my ARM MBP. Will try again with an x86 image.
justin
justin11mo ago
U can use builderx a way on docker to build for another platform, windows / linux computer with right architecture, or use depot https://discord.com/channels/912829806415085598/1194693049897463848
Want results from more Discord servers?
Add your server