R
RunPod6mo ago
jax

worker no execute

this worker "ir6fwdhb34ujm7" run but no execute, why????
13 Replies
digigoblin
digigoblin6mo ago
What does "no execute" mean? What do the logs say?
jax
jaxOP6mo ago
No description
No description
jax
jaxOP6mo ago
The 1st one executed nothing I canceled it manually, the 2nd one canceled it after a timeout and it looks like it was not assigned to a GPU
nerdylive
nerdylive6mo ago
Where is the message that made it look like it was not assigned to a gpu? Copy texts, not screenshots please
jax
jaxOP6mo ago
nerdylive
nerdylive6mo ago
whats your base docker image? is that the full logs? yeah i see no "cuda" or "pytorch" signs meaning the gpu can be not loaded
jax
jaxOP6mo ago
Here's the full log, docker image templates id 98y63mu2ic, multiple wokers are allowed at the same time and only this worker has problems
nerdylive
nerdylive6mo ago
Try to contact support via the website with your endpoint id contact button on the left
digigoblin
digigoblin6mo ago
Its probably issue with the worker itself, not a RunPod issue I would log a Github isssue on the repo you're using before contacting RunPod support
jax
jaxOP6mo ago
Is the process that complicated? I've promoted runpod to countless people before because I thought it had prompt customer service, but why is the process so complicated
nerdylive
nerdylive6mo ago
It could be many possibility thats causing that issue, best to check workers code too but the way the current way of contacting official staffs is my email or ticket
digigoblin
digigoblin6mo ago
Its definitely the worker code if 1 single person has an issue If multiple people have issues, then it can be a RunPod issue
nerdylive
nerdylive6mo ago
Yep
Want results from more Discord servers?
Add your server