ollama - 💡(How to fix) Fix minimax-m2.7:cloud unavailable [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
ollama/ollama#15071Fetched 2026-04-08 01:36:33
View on GitHub
Comments
2
Participants
3
Timeline
5
Reactions
0
Timeline (top)
commented ×2labeled ×2closed ×1

Error Message

InternalServerError: Error code: 503 - {'error': 'Service Temporarily Unavailable'}

Code Example

Mar 26 14:17:58 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:17:58 | 503 |  1.185418188s |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:18:01 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:18:01 | 503 |  1.027314585s |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:18:06 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:18:06 | 503 |  1.001037884s |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:18:15 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:18:15 | 503 |  1.395260564s |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:01 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:01 | 503 |          2m1s |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:03 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:03 | 503 |  337.167936ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:08 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:08 | 503 |    337.6667ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:16 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:16 | 503 |  382.861432ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:19 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:19 | 503 |  1.001922589s |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:22 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:22 | 503 |  1.353476943s |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:28 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:28 | 503 |  1.183933585s |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:37 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:37 | 503 |  971.915267ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:37 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:37 | 503 |   402.16817ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:40 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:40 | 503 |  327.355507ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:44 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:44 | 503 |  407.569291ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:53 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:53 | 503 |  621.755998ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:56 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:56 | 503 |  911.276835ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:59 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:59 | 503 |  1.089100814s |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:33:04 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:33:04 | 503 |  945.980079ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:33:13 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:33:13 | 503 |  1.082844302s |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:36:40 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:36:40 | 503 |  396.731729ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:36:42 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:36:42 | 503 |  418.715693ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:36:47 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:36:47 | 503 |   406.28898ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:36:55 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:36:55 | 503 |  366.104932ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:43:54 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:43:54 | 200 |  4.706775343s |       127.0.0.1 | POST     "/v1/chat/completions"
Mar 26 14:44:39 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:44:39 | 503 |   382.35089ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:44:41 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:44:41 | 503 |  381.460501ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:44:46 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:44:46 | 503 |  337.972409ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:44:54 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:44:54 | 503 |  421.261063ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:45:05 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:45:05 | 200 |  9.956120472s |       127.0.0.1 | POST     "/v1/chat/completions"
RAW_BUFFERClick to expand / collapse

What is the issue?

Since a few hours I’ve been getting consistent "The AI service is temporarily overloaded. Please try again in a moment.” from my bot when using Telegram, model ollama/minimax-m2.7:cloud.

From Hermes agent I get: InternalServerError: Error code: 503 - {'error': 'Service Temporarily Unavailable'}

Other models like kimi cloud work fine.

Relevant log output

Mar 26 14:17:58 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:17:58 | 503 |  1.185418188s |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:18:01 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:18:01 | 503 |  1.027314585s |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:18:06 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:18:06 | 503 |  1.001037884s |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:18:15 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:18:15 | 503 |  1.395260564s |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:01 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:01 | 503 |          2m1s |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:03 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:03 | 503 |  337.167936ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:08 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:08 | 503 |    337.6667ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:16 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:16 | 503 |  382.861432ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:19 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:19 | 503 |  1.001922589s |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:22 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:22 | 503 |  1.353476943s |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:28 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:28 | 503 |  1.183933585s |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:37 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:37 | 503 |  971.915267ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:37 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:37 | 503 |   402.16817ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:40 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:40 | 503 |  327.355507ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:44 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:44 | 503 |  407.569291ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:53 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:53 | 503 |  621.755998ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:56 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:56 | 503 |  911.276835ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:32:59 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:32:59 | 503 |  1.089100814s |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:33:04 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:33:04 | 503 |  945.980079ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:33:13 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:33:13 | 503 |  1.082844302s |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:36:40 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:36:40 | 503 |  396.731729ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:36:42 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:36:42 | 503 |  418.715693ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:36:47 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:36:47 | 503 |   406.28898ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:36:55 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:36:55 | 503 |  366.104932ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:43:54 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:43:54 | 200 |  4.706775343s |       127.0.0.1 | POST     "/v1/chat/completions"
Mar 26 14:44:39 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:44:39 | 503 |   382.35089ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:44:41 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:44:41 | 503 |  381.460501ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:44:46 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:44:46 | 503 |  337.972409ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:44:54 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:44:54 | 503 |  421.261063ms |       127.0.0.1 | POST     "/api/chat"
Mar 26 14:45:05 ubuntu-openclaw ollama[787]: [GIN] 2026/03/26 - 14:45:05 | 200 |  9.956120472s |       127.0.0.1 | POST     "/v1/chat/completions"

OS

Linux

GPU

No response

CPU

Intel

Ollama version

0.17.4

extent analysis

Fix Plan

The fix involves implementing a retry mechanism with exponential backoff to handle the 503 Service Temporarily Unavailable error.

  • Modify the API call to include a retry mechanism:

import time import random

def api_call_with_retry(max_retries=5, initial_backoff=0.1): backoff = initial_backoff for attempt in range(max_retries): try: # Make the API call response = requests.post("/api/chat") response.raise_for_status() return response except requests.exceptions.HTTPError as errh: if errh.response.status_code == 503: # If the error is 503, wait for the backoff period before retrying time.sleep(backoff) backoff *= 2 # Exponential backoff backoff += random.uniform(0, 0.1) # Add some jitter to the backoff else: # If the error is not 503, re-raise the exception raise # If all retries fail, raise an exception raise Exception("All retries failed")

*   Increase the timeout for the API call to accommodate the potential delays caused by the retry mechanism.
*   Consider adding logging to track the number of retries and the backoff periods to help diagnose any issues.

### Verification
To verify that the fix worked, you can:

*   Test the API call with the retry mechanism and verify that it successfully completes after a few retries.
*   Monitor the logs to ensure that the retry mechanism is working as expected and that the backoff periods are being applied correctly.
*   Use tools like `curl` or Postman to simulate the API call and verify that the retry mechanism is handling the 503 errors correctly.

### Extra Tips
*   Make sure to adjust the `max_retries` and `initial_backoff` parameters to suit your specific use case.
*   Consider implementing a circuit breaker pattern to detect when the API is consistently returning 503 errors and prevent further requests until it becomes available again.
*   Keep in mind that the retry mechanism should be used judiciously to avoid overwhelming the API with repeated requests.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING