ultralytics / hub

Ultralytics HUB tutorials and support
https://hub.ultralytics.com
GNU Affero General Public License v3.0
138 stars 14 forks source link

All my training are going to timeout #887

Open fitzroy-hamilton opened 1 month ago

fitzroy-hamilton commented 1 month ago

Search before asking

HUB Component

Training

Bug

Hello,

I try to train a Yolo11n model with VisDrone and all of my trainings are finishing the same way: disconnected + timeout.

As you can see in attachment, I cannot train my model. And yes, I have only one training at the same time.

Can you help me ?

Thanks, Best regards, Jeremy

Capture d’écran 2024-10-17 à 09 02 03 Capture d’écran 2024-10-17 à 09 02 27

Environment

No response

Minimal Reproducible Example

Launch a training on Yolo11n + VisDrone and wait until timeout

Additional

No response

sergiuwaxmann commented 1 month ago

@fitzroy-hamilton I will investigate this and get back to you. Thank you for understanding!

fitzroy-hamilton commented 1 month ago

Do you have any idea to solve this issue?

pderrenger commented 1 month ago

@fitzroy-hamilton hello Jeremy,

Thanks for reaching out and providing the details. Let's try to resolve this issue together.

  1. Check for Updates: Ensure you're using the latest version of the Ultralytics HUB and YOLO models. Sometimes, updates include important bug fixes.

  2. Network Stability: Since the issue involves disconnection, verify your network stability. A stable connection is crucial for uninterrupted training.

  3. Resource Limits: Confirm that your training doesn't exceed any resource limits set by the platform. You mentioned running one training at a time, which is good.

  4. Logs and Errors: Check the logs for any specific error messages that might indicate the cause of the timeout.

  5. Contact Support: If the issue persists, consider reaching out through the official support channels for more detailed assistance.

Feel free to check the Ultralytics HUB documentation for more insights. Let us know how it goes!

yogendrasinghx commented 1 week ago

@fitzroy-hamilton Thank you for reporting this issue. I can confirm that this is a bug, and I have forwarded the details to the development team. I’ll keep you updated and let you know once we have a fix for this issue. Thank you for your patience!