Skip to content

Commit 1b1a7a5

Browse files
SamyOubouazizSamyOubouaziz
authored
docs(gen): add troubleshooting pages MTA-5446 (#4687)
1 parent 44c27f2 commit 1b1a7a5

File tree

8 files changed

+254
-13
lines changed

8 files changed

+254
-13
lines changed

‎pages/object-storage/troubleshooting/cannot-access-data.mdx‎

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
meta:
3-
title: I cannot access my data
4-
description: Troubleshoot issues related to accessing data in Scaleway Object Storage.
3+
title: I cannot access my objects
4+
description: Troubleshoot issues related to accessing objects in Scaleway Object Storage.
55
content:
6-
h1: I cannot access my data
7-
paragraph: Troubleshoot issues related to accessing data in Scaleway Object Storage.
6+
h1: I cannot access my objects
7+
paragraph: Troubleshoot issues related to accessing objects in Scaleway Object Storage.
88
tags: help troubleshooting object storage blocked data locked fail unable impossible
99
dates:
1010
validation: 2024-12-09
@@ -26,6 +26,10 @@ I am experiencing issues while trying to access my buckets and objects stored on
2626

2727
- Go to the [Status page](https://status.scaleway.com/) to see if there is an ongoing incident on the Scaleway infrastructure.
2828

29+
- Make sure that you are using a valid [API key](https://console.scaleway.com/iam/api-keys).
30+
31+
- Make sure that the bearer of the API key (IAM [user](/iam/concepts/#user) or [application](/iam/concepts/#application)) has the appropriate [IAM permission set](/iam/how-to/view-permission-sets/) to perform the desired actions.
32+
2933
- Retrieve the logs of your buckets using any Amazon S3-compatible tool to identify the cause of the problem:
3034
- [Rclone](https://rclone.org/docs/#logging)
3135
- [S3cmd](https://s3tools.org/usage)

‎pages/object-storage/troubleshooting/error-messages-access.mdx‎

Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
---
2+
meta:
3+
title: I get error messages when trying to access a bucket
4+
description: Solve errors encountered while trying to access your bucket with Scaleway Object Storage.
5+
content:
6+
h1: I get error messages when trying to access a bucket
7+
paragraph: Solve errors encountered while trying to access your bucket with Scaleway Object Storage.
8+
tags: help troubleshooting access bucket error message denied deny fail failed
9+
dates:
10+
validation: 2025-03-24
11+
posted: 2025-03-24
12+
categories:
13+
- storage
14+
- object-storage
15+
---
16+
17+
<Macro id="requirements" />
18+
19+
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
20+
21+
22+
## Problem
23+
24+
One of the following messages display when trying to access your bucket using Scaleway Object Storage:
25+
26+
- `Failed to preprocess target Error: S3 error: Access Denied`
27+
- `Error: Shared memory connection was closed.`
28+
- `Failed to upload disk 'shadowSpec>'`
29+
- `Agent failed to process method {DataTransfer.SyncDisk}.`
30+
31+
#### Cause
32+
33+
The application cannot access the Object Storage resource.
34+
35+
#### Solution
36+
37+
If you encounter one or several of the error messages above:
38+
39+
- Check for issues with your API key by following [this procedure](/object-storage/troubleshooting/api-key-does-not-work/).
40+
41+
- Make sure that you have the `ObjectStorageFullAccess` [IAM permission](/iam/concepts/#permission).
42+
43+
- Make sure that there is no [bucket policy](/object-storage/api-cli/bucket-policy/) preventing the application to access your bucket.
44+
45+
## Going further
46+
47+
- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below:
48+
- Object Storage Endpoint (e.g. `s3.fr-par.scw.cloud`)
49+
- Bucket name
50+
- Object name (if the request concerns an object)
51+
- Request type (PUT, GET, etc.)
52+
- HTTP status code
53+
- Date and time (timestamp)
54+
- User-agent (SDK, client, console, etc.)
55+
- Transaction ID (if possible)
56+
- Log / trace of the error (if possible)

‎pages/object-storage/troubleshooting/issues-dns-edge-services.mdx‎

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
meta:
3+
title: I am experiencing DNS/Edge Services issues
4+
description: Learn to troubleshoot issues when using Edge Services or DNS with Scaleway Object Storage.
5+
content:
6+
h1: I am experiencing DNS/Edge Services issues
7+
paragraph: Learn to troubleshoot issues when using Edge Services or DNS with Scaleway Object Storage.
8+
tags: help troubleshooting object storage dns domains edge services cannot does not work
9+
dates:
10+
validation: 2025-03-24
11+
posted: 2025-03-24
12+
categories:
13+
- storage
14+
- object-storage
15+
---
16+
17+
<Macro id="requirements" />
18+
19+
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
20+
21+
## Problem
22+
23+
I am experiencing DNS and/or Edge Services issues when using Scaleway Object Storage.
24+
25+
## Possible cause
26+
27+
There are many factors that can cause DNS and Edge Services issues with Scaleway Object Storage. However, most of the time, the root cause does not come from the Object Storage configuration, but from Domains and DNS, or Edge Services.
28+
29+
## Solutions
30+
31+
According to the type of issue you are experiencing:
32+
33+
- Refer to the [Edge Services troubleshooting documentation](/edge-services/troubleshooting/) for dedicated help pages.
34+
35+
- Refer to the [Domains and DNS troubleshooting documentation](/domains-and-dns/troubleshooting/) for dedicated help pages.
36+
37+
## Going further
38+
39+
If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below:
40+
- Object Storage Endpoint (e.g. `s3.fr-par.scw.cloud`)
41+
- Bucket name
42+
- Object name (if the request concerns an object)
43+
- Request type (PUT, GET, etc.)
44+
- HTTP status code
45+
- Date and time (timestamp)
46+
- User-agent (SDK, client, console, etc.)
47+
- Transaction ID (if possible)
48+
- Log / trace of the error (if possible)

‎pages/object-storage/troubleshooting/request-rate-error.mdx‎

Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
---
2+
meta:
3+
title: I am experiencing request rate errors
4+
description: Solve issues linked to request rate limitations on Scaleway Object Storage.
5+
content:
6+
h1: I am experiencing request rate errors
7+
paragraph: Solve issues linked to request rate limitations on Scaleway Object Storage.
8+
tags: help troubleshooting rate limit throttle error bottleneck slowness slow low performance
9+
dates:
10+
validation: 2025-03-24
11+
posted: 2025-03-24
12+
categories:
13+
- storage
14+
- object-storage
15+
---
16+
17+
<Macro id="requirements" />
18+
19+
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
20+
21+
## Problem
22+
23+
An error message similar to one of the following displays:
24+
25+
- `Error: S3 error: Too Many Requests`
26+
- `Code: Too Many Requests`
27+
- `Shared memory connection was closed.`
28+
- `Agent failed to process method {DataTransfer.SyncDisk}.`
29+
30+
## Cause
31+
32+
Scaleway Object Storage applies a rate limit on PUT operations for safety reasons.
33+
34+
## Solution
35+
36+
Reduce the number of PUT operations sent by your deployment.
37+
38+
<Message type="note">
39+
You may experience reduced throughput due to the limitation.
40+
</Message>
41+
42+
### Going further
43+
44+
Refer to the documentation on [optimizing your Object Storage deployment](/object-storage/reference-content/optimize-object-storage-performance/).
45+
46+
If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below:
47+
48+
- Object Storage Endpoint (e.g. `s3.fr-par.scw.cloud`)
49+
- Bucket name
50+
- Object name (if the request concerns an object)
51+
- Request type (PUT, GET, etc.)
52+
- HTTP status code
53+
- Date and time (timestamp)
54+
- User-agent (SDK, client, console, etc.)
55+
- Transaction ID (if possible)
56+
- Log / trace of the error (if possible)

‎pages/serverless-containers/troubleshooting/cannot-deploy-image.mdx‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
meta:
3-
title: I am unable to deploy my image
4-
description: Troubleshoot errors encountered while deploying images with Scaleway Serverless Containers.
3+
title: I am unable to deploy my container
4+
description: Troubleshoot errors encountered while deploying containers with Scaleway Serverless Containers.
55
content:
6-
h1: I am unable to deploy my image
7-
paragraph: Troubleshoot errors encountered while deploying images with Scaleway Serverless Containers.
6+
h1: I am unable to deploy my container
7+
paragraph: Troubleshoot errors encountered while deploying containers with Scaleway Serverless Containers.
88
tags: serverless containers troubleshooting issue error message deploy image failed
99
dates:
1010
validation: 2025-05-12
@@ -15,7 +15,7 @@ categories:
1515

1616
## Problem
1717

18-
I am unable to deploy my image using Serverless Containers.
18+
I am unable to deploy my container or image using Serverless Containers.
1919

2020
## Possible solutions
2121

‎pages/serverless-containers/troubleshooting/container-error-state.mdx‎

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
meta:
3+
title: My container is in an error state
4+
description: Troubleshoot problems encountered when Serverless Containers are in an error state.
5+
content:
6+
h1: My container is in an error state
7+
paragraph: Troubleshoot problems encountered when Serverless Containers are in an error state.
8+
tags: serverless containers troubleshooting issue error state container status fail
9+
dates:
10+
validation: 2025-04-10
11+
posted: 2024-04-10
12+
categories:
13+
- serverless
14+
---
15+
16+
## Problem
17+
18+
My container is in an error state.
19+
20+
## Cause
21+
22+
There are several factors that can put Serverless Containers in an error state:
23+
24+
- Your container image does not work properly
25+
- Your container image does not contain a webserver
26+
- Your deployment exceeds the [Serverless Containers limitations](/serverless-containers/reference-content/containers-limitations/)
27+
28+
## Possible solutions
29+
30+
- Try to build and run your image locally using [Docker](https://docs.docker.com/get-started/get-docker/).
31+
32+
- Make sure your image embarks a webserver (nginx, Apache, Alpine, etc.) that can process HTTP requests.
33+
34+
- Make sure your deployment does not exceed the [Serverless Containers limitations](/serverless-containers/reference-content/containers-limitations/).
35+
36+
## Going further
37+
38+
Refer to the following troubleshooting pages for other solutions:
39+
40+
- [I am unable to deploy my image](/serverless-containers/troubleshooting/cannot-deploy-image/)
41+
- [My container stopped working after a redeploy](/serverless-containers/troubleshooting/container-stopped-after-redeploy/)

‎pages/serverless-functions/troubleshooting/function-build-error.mdx‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
meta:
3-
title: My function does not build properly
4-
description: Troubleshoot issues with build errors while using Scaleway Serverless Functions.
3+
title: My function does not deploy properly
4+
description: Troubleshoot issues with deployment errors while using Scaleway Serverless Functions.
55
content:
6-
h1: My function does not build properly
7-
paragraph: Troubleshoot issues with build errors while using Scaleway Serverless Functions.
6+
h1: My function does not deploy properly
7+
paragraph: Troubleshoot issues with deployment errors while using Scaleway Serverless Functions.
88
tags: serverless functions troubleshooting issue error build compile package
99
dates:
1010
validation: 2025-02-10

‎pages/serverless-sql-databases/troubleshooting/database-unavailable.mdx‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
meta:
3+
title: My database is unavailable
4+
description: Find solutions for unavailable databases with Serverless SQL Databases.
5+
content:
6+
h1: My database is unavailable
7+
paragraph: Find solutions for unavailable databases with Serverless SQL Databases.
8+
tags: database serverless-sql-database unavailable error state status
9+
dates:
10+
validation: 2025-04-10
11+
posted: 2025-04-10
12+
categories:
13+
- serverless
14+
---
15+
16+
## Problem
17+
18+
My database is unavailable or in an error state.
19+
20+
## Cause
21+
22+
Several factors can put Serverless SQL Databases in an error state:
23+
24+
- Scheduled maintenance operations led by Scaleway
25+
- Incident on the Scaleway infrastructure
26+
- Incident on the Scaleway network
27+
28+
## Possible solutions
29+
30+
1. Using the [Scaleway console](https://console.scaleway.com/), check the status of your Serverless SQL Database from its **Overview** tab to make sure it is in an error state. If it is **Ready to use**, or **Running**, make sure that your [database connection is properly set](/serverless-sql-databases/how-to/connect-to-a-database/).
31+
32+
2. Refer to the [documentation on planned maintenance](/serverless-sql-databases/reference-content/planned-maintenance/) to check if you are currently in a maintenance period.
33+
34+
3. Go to the [Scaleway Status](https://status.scaleway.com/) website to check if an incident is currently ongoing.
35+
36+
4. Wait a few minutes, then check the status of your Serverless SQL Database using the [Scaleway console](https://console.scaleway.com/) again.

0 commit comments

Comments
 (0)