R
Runpod2y ago
jax

worker no execute

this worker "ir6fwdhb34ujm7" run but no execute, why????
13 Replies
digigoblin
digigoblin2y ago
What does "no execute" mean? What do the logs say?
jax
jaxOP2y ago
No description
No description
jax
jaxOP2y 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
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View
jax
jaxOP2y ago
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View
jax
jaxOP2y 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
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View
digigoblin
digigoblin2y 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
jaxOP2y 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
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View
digigoblin
digigoblin2y 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
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View

Did you find this page helpful?