From a1d6b246d1ac71ac4869c72738ad0837e0efef1e Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 6 Nov 2024 17:49:09 +0100 Subject: [PATCH 1/9] docs(srv): split troubleshootings into multiple pages MTA-5198 --- menu/navigation.json | 12 +- .../cannot-create-namespace.mdx | 0 .../cannot-inject-secret-variable.mdx | 16 +++ .../troubleshooting/common-errors.mdx | 127 ------------------ .../function-in-error-state.mdx | 0 .../function-stopped-after-redeploy.mdx | 9 ++ .../troubleshooting/handler-not-found.mdx | 44 ++++++ .../troubleshooting/timeout-error.mdx | 0 .../troubleshooting/too-many-retries.mdx | 34 +++++ .../cannot-inject-secret-variable.mdx | 33 +++++ .../cannot-retrieve-external-image.mdx | 28 ++++ .../jobs/troubleshooting/common-errors.mdx | 49 ------- .../troubleshooting/job-in-error-state.mdx | 24 ++++ 13 files changed, 198 insertions(+), 178 deletions(-) create mode 100644 serverless/functions/troubleshooting/cannot-create-namespace.mdx create mode 100644 serverless/functions/troubleshooting/cannot-inject-secret-variable.mdx delete mode 100644 serverless/functions/troubleshooting/common-errors.mdx create mode 100644 serverless/functions/troubleshooting/function-in-error-state.mdx create mode 100644 serverless/functions/troubleshooting/function-stopped-after-redeploy.mdx create mode 100644 serverless/functions/troubleshooting/handler-not-found.mdx create mode 100644 serverless/functions/troubleshooting/timeout-error.mdx create mode 100644 serverless/functions/troubleshooting/too-many-retries.mdx create mode 100644 serverless/jobs/troubleshooting/cannot-inject-secret-variable.mdx create mode 100644 serverless/jobs/troubleshooting/cannot-retrieve-external-image.mdx delete mode 100644 serverless/jobs/troubleshooting/common-errors.mdx create mode 100644 serverless/jobs/troubleshooting/job-in-error-state.mdx diff --git a/menu/navigation.json b/menu/navigation.json index 5eb5a53088..092b891daa 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -3968,8 +3968,16 @@ { "items": [ { - "label": "Common errors", - "slug": "common-errors" + "label": "My job is in an error state", + "slug": "job-in-error-state" + }, + { + "label": "I cannot inject secrets or variables in my job", + "slug": "cannot-inject-secret-variable" + }, + { + "label": "I cannot retrieve external images", + "slug": "cannot-retrieve-external-images" } ], "label": "Troubleshooting", diff --git a/serverless/functions/troubleshooting/cannot-create-namespace.mdx b/serverless/functions/troubleshooting/cannot-create-namespace.mdx new file mode 100644 index 0000000000..e69de29bb2 diff --git a/serverless/functions/troubleshooting/cannot-inject-secret-variable.mdx b/serverless/functions/troubleshooting/cannot-inject-secret-variable.mdx new file mode 100644 index 0000000000..5dc22f4369 --- /dev/null +++ b/serverless/functions/troubleshooting/cannot-inject-secret-variable.mdx @@ -0,0 +1,16 @@ +## My environment variable or secret is not properly injected in my function + +### Cause + +Environment variables or secrets that are too large, contain carriage returns and spread over several lines, as shown below, will not be injected properly. + +``` +"hello +world +. +" +``` + +### Solution + +To avoid issues while injecting environment variables and secrets, we recommend encoding them to `base64`. \ No newline at end of file diff --git a/serverless/functions/troubleshooting/common-errors.mdx b/serverless/functions/troubleshooting/common-errors.mdx deleted file mode 100644 index f72bfef40a..0000000000 --- a/serverless/functions/troubleshooting/common-errors.mdx +++ /dev/null @@ -1,127 +0,0 @@ ---- -meta: - title: Common errors encountered while using Serverless Functions - description: Troubleshoot common errors encountered with Scaleway Serverless Functions. -content: - h1: Common errors encountered while using Serverless Functions - paragraph: Troubleshoot common errors encountered with Scaleway Serverless Functions. -tags: serverless functions troubleshooting issue error message -dates: - validation: 2024-05-08 - posted: 2023-08-23 -categories: - - serveless ---- - -## Handler not found - -### Error Messages - - ``` - Function Handler does not exist, check that you provided the right HANDLER parameter … - ``` - - Or - - ``` - Provided Handler does not exist, or does not export methods properly - ``` - -### Cause - -The systems cannot find the function which will handle the request. It can be related to an error in your code before your `handle` function. - -### Possible solutions - -- Make sure to provide the right handler path. - -- If you used a zip file, make sure the dependencies are present in your [zip package](/serverless/functions/how-to/package-function-dependencies-in-zip/). - -- If you used the Serverless framework, ensure the `.serverless` directory created with `serverless package` contains your zip file. - -- Make sure that the dependencies folders (`node_modules` or `package` in Python) are in package/include. - -- Serverless Functions rely on Alpine Linux, therefore, some C-based libraries (`pandas`, `tensorflow`, `numpy`) will not work. Refer to the official documentation to safely add these libraries to your package. - -## Too Many Retries - -### Error messages - -``` -Too many retries, sub-runtime server did not come up in 10ms seconds -``` - -### Cause - -This error is returned by the runtime when it cannot process the request. It has several different origins. - -### Possible solutions - -- Make sure that you only imported the required dependencies and not the complete libraries. - -- Avoid performing too many initialization operations. - -- Update your function's resources by provisioning more memory and more vCPU. - -## Function in error state - -### Cause - -This error is returned when the function cannot start due to insufficient provisioned resources. - -### Possible solutions - -Update your function's resources by provisioning more memory and more vCPU. - -## Timeout error - -### Cause - -Timeout happens when your function can’t return a results in the defined amount of time. - -### Possible solutions - -- Increase the Timeout parameter in the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-functions/#path-functions-update-an-existing-function). - -- Update your function's resources by provisioning more memory and more vCPU. - -## Failed to create a namespace - -### Cause - -This issue can happen for the following reasons: - -- You created too many namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-functions). - -- You created too many Registry namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#container-registry). - -### Possible solutions - -Make sure that you did not exceed the maximum number of allowed namespaces with the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-functions/#path-namespaces-list-all-your-namespaces). - -## Function stopped working several hours after a redeploy - -### Cause - -The new deploy failed, and the [fallback mechanism has been triggered](/serverless/functions/reference-content/functions-limitations/#versioning-and-rollback). - -### Possible solution - -Identify the element that caused the deployment to fail, fix the error, and deploy the function again. - -## My environment variable or secret is not properly injected in my function - -### Cause - -Environment variables or secrets that are too large, contain carriage returns and spread over several lines, as shown below, will not be injected properly. - -``` -"hello -world -. -" -``` - -### Solution - -To avoid issues while injecting environment variables and secrets, we recommend encoding them to `base64`. diff --git a/serverless/functions/troubleshooting/function-in-error-state.mdx b/serverless/functions/troubleshooting/function-in-error-state.mdx new file mode 100644 index 0000000000..e69de29bb2 diff --git a/serverless/functions/troubleshooting/function-stopped-after-redeploy.mdx b/serverless/functions/troubleshooting/function-stopped-after-redeploy.mdx new file mode 100644 index 0000000000..7eaeca17d6 --- /dev/null +++ b/serverless/functions/troubleshooting/function-stopped-after-redeploy.mdx @@ -0,0 +1,9 @@ +## Function stopped working several hours after a redeploy + +### Cause + +The new deploy failed, and the [fallback mechanism has been triggered](/serverless/functions/reference-content/functions-limitations/#versioning-and-rollback). + +### Possible solution + +Identify the element that caused the deployment to fail, fix the error, and deploy the function again. \ No newline at end of file diff --git a/serverless/functions/troubleshooting/handler-not-found.mdx b/serverless/functions/troubleshooting/handler-not-found.mdx new file mode 100644 index 0000000000..844f4202cd --- /dev/null +++ b/serverless/functions/troubleshooting/handler-not-found.mdx @@ -0,0 +1,44 @@ +--- +meta: + title: Unable to find the function handler + description: Troubleshoot problems with finding the handler when using Scaleway Serverless Functions. +content: + h1: Unable to find the function handler + paragraph: Troubleshoot problems with finding the handler when using Scaleway Serverless Functions. +tags: serverless functions troubleshooting issue error function handler execution run cannot find +dates: + validation: 2024-11-06 + posted: 2024-11-06 +categories: + - serverless +--- + +## Problem + +My serverless Function is unable to find the Handler during its execution, and displays an error message similar to the following: + +``` +Function Handler does not exist, check that you provided the right HANDLER parameter … +``` + +Or + +``` +Provided Handler does not exist, or does not export methods properly +``` + +## Cause + +The systems cannot find the function which will handle the request. It can be related to an error in your code before your `handle` function. + +## Possible solutions + +- Make sure to provide the right handler path. + +- If you used a zip file, make sure the dependencies are present in your [zip package](/serverless/functions/how-to/package-function-dependencies-in-zip/). + +- If you used the Serverless framework, ensure the `.serverless` directory created with `serverless package` contains your zip file. + +- Make sure that the dependencies folders (`node_modules` or `package` in Python) are in package/include. + +- Serverless Functions rely on Alpine Linux, therefore, some C-based libraries (`pandas`, `tensorflow`, `numpy`) will not work. Refer to the official documentation to safely add these libraries to your package. \ No newline at end of file diff --git a/serverless/functions/troubleshooting/timeout-error.mdx b/serverless/functions/troubleshooting/timeout-error.mdx new file mode 100644 index 0000000000..e69de29bb2 diff --git a/serverless/functions/troubleshooting/too-many-retries.mdx b/serverless/functions/troubleshooting/too-many-retries.mdx new file mode 100644 index 0000000000..639e7dc125 --- /dev/null +++ b/serverless/functions/troubleshooting/too-many-retries.mdx @@ -0,0 +1,34 @@ +--- +meta: + title: My function fails after trying too many times + description: Troubleshoot problems with functions trying too many times before failing. +content: + h1: My function fails after trying too many times + paragraph: Troubleshoot problems with functions trying too many times before failing. +tags: serverless functions troubleshooting issue error function retries retry failure +dates: + validation: 2024-11-06 + posted: 2024-11-06 +categories: + - serverless +--- + +## Problem + +My function fails, and the following message displays: + +``` +Too many retries, sub-runtime server did not come up in 10ms seconds +``` + +## Cause + +This error is returned by the runtime when it cannot process the request. It has several different origins. + +## Possible solutions + +- Make sure that you only imported the required dependencies and not the complete libraries. + +- Avoid performing too many initialization operations. + +- Update your function's resources by provisioning more memory and more vCPU. \ No newline at end of file diff --git a/serverless/jobs/troubleshooting/cannot-inject-secret-variable.mdx b/serverless/jobs/troubleshooting/cannot-inject-secret-variable.mdx new file mode 100644 index 0000000000..f60610fd35 --- /dev/null +++ b/serverless/jobs/troubleshooting/cannot-inject-secret-variable.mdx @@ -0,0 +1,33 @@ +--- +meta: + title: My secrets and variables are not injected properly in my job + description: Troubleshoot issues with secrets and environment variables while using Scaleway Serverless Jobs. +content: + h1: My secrets and variables are not injected properly in my job + paragraph: Troubleshoot issues with secrets and environment variables while using Scaleway Serverless Jobs. +tags: serverless jobs troubleshooting issue error image env var environment variables secrets secret manager +dates: + validation: 2024-11-06 + posted: 2024-11-06 +categories: + - serverless +--- + +## Problem + +My environment variables and secrets are not properly injected during my job runs. + +## Cause + +Environment variables or secrets that are too large, contain carriage returns and spread over several lines, as shown below, will not be injected properly. + +``` +"hello +world +. +" +``` + +### Solution + +To avoid issues while injecting environment variables and secrets, we recommend encoding them to `base64`. diff --git a/serverless/jobs/troubleshooting/cannot-retrieve-external-image.mdx b/serverless/jobs/troubleshooting/cannot-retrieve-external-image.mdx new file mode 100644 index 0000000000..cc53cc5394 --- /dev/null +++ b/serverless/jobs/troubleshooting/cannot-retrieve-external-image.mdx @@ -0,0 +1,28 @@ +--- +meta: + title: I am unable to retrieve an external image for my job + description: Troubleshoot errors while retrieving external images while using Scaleway Serverless Jobs. +content: + h1: I am unable to retrieve an external image for my job + paragraph: Troubleshoot errors while retrieving external images while using Scaleway Serverless Jobs. +tags: serverless jobs troubleshooting issue error image retrieve external public registry +dates: + validation: 2024-11-06 + posted: 2024-11-06 +categories: + - serverless +--- + +## Problem + +I am experiencing issues when retrieving an image stored in an external container registry. + +## Cause + +Serverless products support external public registries (such as [Docker Hub](https://hub.docker.com/)), but we do not recommend using them due to uncontrolled rate limiting, which can lead to failures when starting resources, unexpected usage conditions, and pricing changes. + +## Solution + +We recommend using the [Scaleway Container Registry](/containers/container-registry/) instead, as it allows for a seamless integration with Serverless Containers and Jobs at a [competitive price](/faq/containerregistry/#how-am-i-billed-for-scaleway-container-registry). + +Refer to the [dedicated documentation](/serverless/jobs/api-cli/migrate-external-image-to-scaleway-registry/) for more information on how to migrate images to the Scaleway Container Registry. diff --git a/serverless/jobs/troubleshooting/common-errors.mdx b/serverless/jobs/troubleshooting/common-errors.mdx deleted file mode 100644 index a6d923a3ce..0000000000 --- a/serverless/jobs/troubleshooting/common-errors.mdx +++ /dev/null @@ -1,49 +0,0 @@ ---- -meta: - title: Common errors encountered while using Serverless Jobs - description: Troubleshoot common errors in Scaleway Serverless Jobs. -content: - h1: Common errors encountered while using Serverless Jobs - paragraph: Troubleshoot common errors in Scaleway Serverless Jobs. -tags: serverless jobs troubleshooting issue error message -dates: - validation: 2024-10-03 - posted: 2024-03-28 -categories: - - serverless ---- - -## Job run is in an error state - -### Possible solutions - -- Make sure you built your image for an `amd64` architecture, as `arm64` is not supported. See [Architecture](/serverless/jobs/reference-content/jobs-limitations/#Architecture) documentation. - -- Make sure your deployment does not exceed the limitations of [Serverless Jobs](/serverless/jobs/reference-content/jobs-limitations/). - -## Issues when retrieving an external image - -### Cause - -Serverless products support external public registries (such as [Docker Hub](https://hub.docker.com/)), but we do not recommend using them due to uncontrolled rate limiting, which can lead to failures when starting resources, unexpected usage conditions, and pricing changes. - -### Solution - -We recommend using [Scaleway's Container Registry](/containers/container-registry/) instead, as it allows for a seamless integration with Serverless Containers and Jobs at a [competitive price](/faq/containerregistry/#how-am-i-billed-for-scaleway-container-registry). - -## My environment variable or secret is not properly injected in my job - -### Cause - -Environment variables or secrets that are too large, contain carriage returns and spread over several lines, as shown below, will not be injected properly. - -``` -"hello -world -. -" -``` - -### Solution - -To avoid issues while injecting environment variables and secrets, we recommend encoding them to `base64`. \ No newline at end of file diff --git a/serverless/jobs/troubleshooting/job-in-error-state.mdx b/serverless/jobs/troubleshooting/job-in-error-state.mdx new file mode 100644 index 0000000000..e363887d9f --- /dev/null +++ b/serverless/jobs/troubleshooting/job-in-error-state.mdx @@ -0,0 +1,24 @@ +--- +meta: + title: My Job run is in an error state + description: Troubleshoot error states for your Scaleway Serverless Jobs. +content: + h1: My Job run is in an error state + paragraph: Troubleshoot error states for your Scaleway Serverless Jobs. +tags: serverless jobs troubleshooting issue error state message +dates: + validation: 2024-11-06 + posted: 2024-11-06 +categories: + - serverless +--- + +## Problem + +My job run is in an error state. + +## Possible solutions + +- Make sure you built your image for an `amd64` architecture, as `arm64` is not supported. See [Architecture](/serverless/jobs/reference-content/jobs-limitations/#Architecture) documentation. + +- Make sure your deployment does not exceed the limitations of [Serverless Jobs](/serverless/jobs/reference-content/jobs-limitations/). \ No newline at end of file From b44d2dad63af0d200830396b37dfd81a5582d715 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 6 Nov 2024 18:01:30 +0100 Subject: [PATCH 2/9] docs(srv): update --- .../cannot-create-namespace.mdx | 30 +++++++++++++++++++ .../cannot-inject-secret-variable.mdx | 19 +++++++++++- .../function-in-error-state.mdx | 26 ++++++++++++++++ .../function-stopped-after-redeploy.mdx | 23 ++++++++++++-- .../troubleshooting/timeout-error.mdx | 28 +++++++++++++++++ 5 files changed, 122 insertions(+), 4 deletions(-) diff --git a/serverless/functions/troubleshooting/cannot-create-namespace.mdx b/serverless/functions/troubleshooting/cannot-create-namespace.mdx index e69de29bb2..734956d75a 100644 --- a/serverless/functions/troubleshooting/cannot-create-namespace.mdx +++ b/serverless/functions/troubleshooting/cannot-create-namespace.mdx @@ -0,0 +1,30 @@ +--- +meta: + title: I am unable to create a Serverless Functions namespace + description: Troubleshoot problems encountered while creating namespaces for Scaleway Serverless Functions. +content: + h1: My function fails after trying too many times + paragraph: Troubleshoot problems encountered while creating namespaces for Scaleway Serverless Functions. +tags: serverless functions troubleshooting issue error namespace creation unable +dates: + validation: 2024-11-06 + posted: 2024-11-06 +categories: + - serverless +--- + +## Problem + +I cannot create a Serverless Functions namespace. + +### Cause + +This issue can happen for the following reasons: + +- You created too many namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-functions). + +- You created too many Registry namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#container-registry). + +### Possible solutions + +Make sure that you did not exceed the maximum number of allowed namespaces with the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-functions/#path-namespaces-list-all-your-namespaces). \ No newline at end of file diff --git a/serverless/functions/troubleshooting/cannot-inject-secret-variable.mdx b/serverless/functions/troubleshooting/cannot-inject-secret-variable.mdx index 5dc22f4369..63f0884702 100644 --- a/serverless/functions/troubleshooting/cannot-inject-secret-variable.mdx +++ b/serverless/functions/troubleshooting/cannot-inject-secret-variable.mdx @@ -1,4 +1,21 @@ -## My environment variable or secret is not properly injected in my function +--- +meta: + title: My secrets and variables are not injected properly in my function + description: Troubleshoot issues with secrets and environment variables while using Scaleway Serverless Functions. +content: + h1: My secrets and variables are not injected properly in my function + paragraph: Troubleshoot issues with secrets and environment variables while using Scaleway Serverless Functions. +tags: serverless functions troubleshooting issue error env var environment variables secrets secret manager +dates: + validation: 2024-11-06 + posted: 2024-11-06 +categories: + - serverless +--- + +## Problem + +My environment variable or secret is not properly injected in my function during its execution. ### Cause diff --git a/serverless/functions/troubleshooting/function-in-error-state.mdx b/serverless/functions/troubleshooting/function-in-error-state.mdx index e69de29bb2..773de5a27d 100644 --- a/serverless/functions/troubleshooting/function-in-error-state.mdx +++ b/serverless/functions/troubleshooting/function-in-error-state.mdx @@ -0,0 +1,26 @@ +--- +meta: + title: My function is in an error state + description: Troubleshoot issues with Scaleway Serverless Functions being in an error state. +content: + h1: My function is in an error state + paragraph: Troubleshoot issues with Scaleway Serverless Functions being in an error state. +tags: serverless functions troubleshooting issue error state failed fail +dates: + validation: 2024-11-06 + posted: 2024-11-06 +categories: + - serverless +--- + +## Problem + +My Serverless Function is in an error state following its execution. + +## Cause + +This error is returned when the function cannot start due to insufficient provisioned resources. + +## Possible solution + +Update your function's resources by provisioning more memory and more vCPU. \ No newline at end of file diff --git a/serverless/functions/troubleshooting/function-stopped-after-redeploy.mdx b/serverless/functions/troubleshooting/function-stopped-after-redeploy.mdx index 7eaeca17d6..bc29517c5c 100644 --- a/serverless/functions/troubleshooting/function-stopped-after-redeploy.mdx +++ b/serverless/functions/troubleshooting/function-stopped-after-redeploy.mdx @@ -1,9 +1,26 @@ -## Function stopped working several hours after a redeploy +--- +meta: + title: My function stopped working after a redeploy + description: Troubleshoot issues with Scaleway Serverless Functions not working properly following a redeploy. +content: + h1: My function stopped working after a redeploy + paragraph: Troubleshoot issues with Scaleway Serverless Functions not working properly following a redeploy. +tags: serverless functions troubleshooting issue error state failed fail redeploy +dates: + validation: 2024-11-06 + posted: 2024-11-06 +categories: + - serverless +--- -### Cause +## Problem + +My Serverless Function stopped working (up to several hours) after a redeploy. + +## Cause The new deploy failed, and the [fallback mechanism has been triggered](/serverless/functions/reference-content/functions-limitations/#versioning-and-rollback). -### Possible solution +## Possible solution Identify the element that caused the deployment to fail, fix the error, and deploy the function again. \ No newline at end of file diff --git a/serverless/functions/troubleshooting/timeout-error.mdx b/serverless/functions/troubleshooting/timeout-error.mdx index e69de29bb2..e25efc9dec 100644 --- a/serverless/functions/troubleshooting/timeout-error.mdx +++ b/serverless/functions/troubleshooting/timeout-error.mdx @@ -0,0 +1,28 @@ +--- +meta: + title: I am experiencing timeout errors + description: Troubleshoot timeout errors when using Scaleway Serverless Functions. +content: + h1: I am experiencing timeout errors + paragraph: Troubleshoot timeout errors when using Scaleway Serverless Functions. +tags: serverless functions troubleshooting issue error function timeout +dates: + validation: 2024-11-06 + posted: 2024-11-06 +categories: + - serverless +--- + +## Problem + +I am experiencing timeout errors when using Scaleway Serverless Functions. + +### Cause + +Timeout happens when your function can’t return a results in the defined amount of time. + +### Possible solutions + +- Increase the Timeout parameter in the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-functions/#path-functions-update-an-existing-function). + +- Update your function's resources by provisioning more memory and more vCPU. \ No newline at end of file From 985f5c1685ede745efd2848bd848745f6faf8624 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Thu, 7 Nov 2024 11:10:40 +0100 Subject: [PATCH 3/9] docs(srv): update --- menu/navigation.json | 28 ++++++++++++++++++++++++++-- 1 file changed, 26 insertions(+), 2 deletions(-) diff --git a/menu/navigation.json b/menu/navigation.json index 092b891daa..d4fa61a034 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -3706,8 +3706,32 @@ { "items": [ { - "label": "Common errors", - "slug": "common-errors" + "label": "Unable to create a namespace", + "slug": "cannot-create-namespace" + }, + { + "label": "I cannot inject secrets or variables in my job", + "slug": "cannot-inject-secret-variable" + }, + { + "label": "My function is in an error state", + "slug": "function-in-error-state" + }, + { + "label": "My function stopped working after a redeploy", + "slug": "function-stopped-after-redeploy" + }, + { + "label": "Handler not found", + "slug": "handler-not-found" + }, + { + "label": "I am experiencing timeout errors", + "slug": "timeout-errors" + }, + { + "label": "My function fails after too many retries", + "slug": "too-many-retries" } ], "label": "Troubleshooting", From 5a3ebf4ea2fd081f963248c216a43ba21718be60 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Thu, 7 Nov 2024 11:46:26 +0100 Subject: [PATCH 4/9] docs(srv): update --- menu/navigation.json | 20 ++++- .../cannot-create-namespace.mdx | 30 +++++++ .../troubleshooting/cannot-deploy-image.mdx | 37 ++++++++ .../cannot-inject-secret-variable.mdx | 33 +++++++ .../cannot-retrieve-external-image.mdx | 28 ++++++ .../troubleshooting/common-errors.mdx | 85 ------------------- .../container-stopped-after-redeploy.mdx | 26 ++++++ 7 files changed, 172 insertions(+), 87 deletions(-) create mode 100644 serverless/containers/troubleshooting/cannot-create-namespace.mdx create mode 100644 serverless/containers/troubleshooting/cannot-deploy-image.mdx create mode 100644 serverless/containers/troubleshooting/cannot-inject-secret-variable.mdx create mode 100644 serverless/containers/troubleshooting/cannot-retrieve-external-image.mdx delete mode 100644 serverless/containers/troubleshooting/common-errors.mdx create mode 100644 serverless/containers/troubleshooting/container-stopped-after-redeploy.mdx diff --git a/menu/navigation.json b/menu/navigation.json index d4fa61a034..22b61bddc8 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -3888,8 +3888,24 @@ { "items": [ { - "label": "Common errors", - "slug": "common-errors" + "label": "I cannot create a namespace", + "slug": "cannot-create-namespace" + }, + { + "label": "I cannot deploy my image", + "slug": "cannot-deploy-image" + }, + { + "label": "I cannot inject secrets or variables in my job", + "slug": "cannot-inject-secret-variable" + }, + { + "label": "I cannot retrieve external images", + "slug": "cannot-retrieve-external-images" + }, + { + "label": "My container stopped working after a redeploy", + "slug": "container-stopped-after-redeploy" } ], "label": "Troubleshooting", diff --git a/serverless/containers/troubleshooting/cannot-create-namespace.mdx b/serverless/containers/troubleshooting/cannot-create-namespace.mdx new file mode 100644 index 0000000000..94276691f8 --- /dev/null +++ b/serverless/containers/troubleshooting/cannot-create-namespace.mdx @@ -0,0 +1,30 @@ +--- +meta: + title: I am unable to create a Serverless Containers namespace + description: Troubleshoot problems encountered while creating namespaces for Scaleway Serverless Containers. +content: + h1: My function fails after trying too many times + paragraph: Troubleshoot problems encountered while creating namespaces for Scaleway Serverless Containers. +tags: serverless Containers troubleshooting issue error namespace creation unable +dates: + validation: 2024-11-06 + posted: 2024-11-06 +categories: + - serverless +--- + +## Problem + +I cannot create a Serverless Containers namespace. + +### Cause + +This issue can happen for the following reasons: + +- You created too many namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-containers). + +- You created too many Registry namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#container-registry). + +### Possible solutions + +Make sure that you did not exceed the maximum number of allowed namespaces with the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-containers/#path-namespaces-list-all-your-namespaces). \ No newline at end of file diff --git a/serverless/containers/troubleshooting/cannot-deploy-image.mdx b/serverless/containers/troubleshooting/cannot-deploy-image.mdx new file mode 100644 index 0000000000..fa57f6ee00 --- /dev/null +++ b/serverless/containers/troubleshooting/cannot-deploy-image.mdx @@ -0,0 +1,37 @@ +--- +meta: + title: I am unable to deploy my image + description: Troubleshoot errors encountered while deploying images with Scaleway Serverless Containers. +content: + h1: I am unable to deploy my image + paragraph: Troubleshoot errors encountered while deploying images with Scaleway Serverless Containers. +tags: serverless containers troubleshooting issue error message deploy image failed +dates: + validation: 2024-11-07 + posted: 2024-11-07 +categories: + - serveless +--- + +## Problem + +I am unable to deploy my image using Serverless Containers. + +## Possible solutions + +- Make sure the container is listening on the specified PORT for HTTP requests (or use variable `$PORT`). + +- Make sure the container is bound to `0.0.0.0`. + +- Containers cannot start due to insufficient provisioned resources. Update your container's resources by provisioning more memory and more vCPU. + +- Make sure you built your image for an `amd64` architecture, as `arm64` is not supported. See [Architecture](/serverless/containers/reference-content/containers-limitations/#Architecture) documentation. + +- Make sure your deployment does not exceed the limitations of [Serverless Containers](/serverless/containers/reference-content/containers-limitations/). + + + Run the [`docker inspect`](https://docs.docker.com/engine/reference/commandline/inspect/) command to get detailed information on your image: + ``` + docker inspect myimage + ``` + \ No newline at end of file diff --git a/serverless/containers/troubleshooting/cannot-inject-secret-variable.mdx b/serverless/containers/troubleshooting/cannot-inject-secret-variable.mdx new file mode 100644 index 0000000000..0b5a7e5e43 --- /dev/null +++ b/serverless/containers/troubleshooting/cannot-inject-secret-variable.mdx @@ -0,0 +1,33 @@ +--- +meta: + title: My secrets and variables are not injected properly in my container + description: Troubleshoot issues with secrets and environment variables while using Scaleway Serverless Containers. +content: + h1: My secrets and variables are not injected properly in my container + paragraph: Troubleshoot issues with secrets and environment variables while using Scaleway Serverless Containers. +tags: serverless containers troubleshooting issue error image env var environment variables secrets secret manager +dates: + validation: 2024-11-06 + posted: 2024-11-06 +categories: + - serverless +--- + +## Problem + +My environment variables and secrets are not properly injected in my Serverless Container. + +## Cause + +Environment variables or secrets that are too large, contain carriage returns and spread over several lines, as shown below, will not be injected properly. + +``` +"hello +world +. +" +``` + +### Solution + +To avoid issues while injecting environment variables and secrets, we recommend encoding them to `base64`. diff --git a/serverless/containers/troubleshooting/cannot-retrieve-external-image.mdx b/serverless/containers/troubleshooting/cannot-retrieve-external-image.mdx new file mode 100644 index 0000000000..3dc80f6cad --- /dev/null +++ b/serverless/containers/troubleshooting/cannot-retrieve-external-image.mdx @@ -0,0 +1,28 @@ +--- +meta: + title: I am unable to retrieve an external image for my container + description: Troubleshoot errors while retrieving external images while using Scaleway Serverless Containers. +content: + h1: I am unable to retrieve an external image for my container + paragraph: Troubleshoot errors while retrieving external images while using Scaleway Serverless Containers. +tags: serverless containers troubleshooting issue error image retrieve external public registry +dates: + validation: 2024-11-06 + posted: 2024-11-06 +categories: + - serverless +--- + +## Problem + +I am experiencing issues when retrieving an image stored in an external container registry. + +## Cause + +Serverless products support external public registries (such as [Docker Hub](https://hub.docker.com/)), but we do not recommend using them due to uncontrolled rate limiting, which can lead to failures when starting resources, unexpected usage conditions, and pricing changes. + +## Solution + +We recommend using the [Scaleway Container Registry](/containers/container-registry/) instead, as it allows for a seamless integration with Serverless Containers and Containers at a [competitive price](/faq/containerregistry/#how-am-i-billed-for-scaleway-container-registry). + +Refer to the [dedicated documentation](/serverless/containers/api-cli/migrate-external-image-to-scaleway-registry/) for more information on how to migrate images to the Scaleway Container Registry. diff --git a/serverless/containers/troubleshooting/common-errors.mdx b/serverless/containers/troubleshooting/common-errors.mdx deleted file mode 100644 index d2fe6930cc..0000000000 --- a/serverless/containers/troubleshooting/common-errors.mdx +++ /dev/null @@ -1,85 +0,0 @@ ---- -meta: - title: Common errors encountered while using Serverless Containers - description: Troubleshoot common errors in Scaleway Serverless Containers. -content: - h1: Common errors encountered while using Serverless Containers - paragraph: Troubleshoot common errors in Scaleway Serverless Containers. -tags: serverless containers troubleshooting issue error message -dates: - validation: 2024-09-02 - posted: 2023-08-24 -categories: - - serveless ---- - -## Unable to deploy the image - -### Possible solutions - -- Make sure the container is listening on the specified PORT for HTTP requests (or use variable `$PORT`). - -- Make sure the container is bound to `0.0.0.0`. - -- Containers cannot start due to insufficient provisioned resources. Update your container's resources by provisioning more memory and more vCPU. - -- Make sure you built your image for an `amd64` architecture, as `arm64` is not supported. See [Architecture](/serverless/containers/reference-content/containers-limitations/#Architecture) documentation. - -- Make sure your deployment does not exceed the limitations of [Serverless Containers](/serverless/containers/reference-content/containers-limitations/). - - - Run the [`docker inspect`](https://docs.docker.com/engine/reference/commandline/inspect/) command to get detailed information on your image: - ``` - docker inspect myimage - ``` - - -## Failed to create a namespace - -### Cause - -This issue can happen for the following reasons: - -- You created too many namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-containers) -- You created too many Registry namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#container-registry) - -### Possible solutions - -Make sure that you did not exceed the maximum number of allowed namespaces with the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-containers/#path-namespaces-list-all-your-namespaces). - -## Container stopped working several hours after a redeploy - -### Cause - -The new deploy failed, and the [fallback mechanism has been triggered](/serverless/containers/reference-content/containers-limitations/#versioning-and-rollback). - -### Possible solution - -Identify the element that caused the deployment to fail, fix the error, and deploy the container again. - -## Issues when retrieving an external image - -### Cause - -Serverless products support external public registries (such as [Docker Hub](https://hub.docker.com/)), but we do not recommend using them due to uncontrolled rate limiting, which can lead to failures when starting resources, unexpected usage conditions, and pricing changes. - -### Solution - -We recommend using [Scaleway's Container Registry](/containers/container-registry/) instead, as it allows for a seamless integration with Serverless Containers and Jobs at a [competitive price](/faq/containerregistry/#how-am-i-billed-for-scaleway-container-registry). - -## My environment variable or secret is not properly injected in my container - -### Cause - -Environment variables or secrets that are too large, contain carriage returns and spread over several lines, as shown below, will not be injected properly. - -``` -"hello -world -. -" -``` - -### Solution - -To avoid issues while injecting environment variables and secrets, we recommend encoding them to `base64`. \ No newline at end of file diff --git a/serverless/containers/troubleshooting/container-stopped-after-redeploy.mdx b/serverless/containers/troubleshooting/container-stopped-after-redeploy.mdx new file mode 100644 index 0000000000..ac8b4da469 --- /dev/null +++ b/serverless/containers/troubleshooting/container-stopped-after-redeploy.mdx @@ -0,0 +1,26 @@ +--- +meta: + title: My container stopped working after a redeploy + description: Troubleshoot issues with Scaleway Serverless Containers not working properly following a redeploy. +content: + h1: My container stopped working after a redeploy + paragraph: Troubleshoot issues with Scaleway Serverless Containers not working properly following a redeploy. +tags: serverless containers troubleshooting issue error state failed fail redeploy +dates: + validation: 2024-11-06 + posted: 2024-11-06 +categories: + - serverless +--- + +## Problem + +My Serverless Container stopped working (up to several hours) after a redeploy. + +## Cause + +The new deploy failed, and the [fallback mechanism has been triggered](/serverless/containers/reference-content/containers-limitations/#versioning-and-rollback). + +## Possible solution + +Identify the element that caused the deployment to fail, fix the error, and deploy the container again. \ No newline at end of file From 06ee2890c2c33acf910ed1ce78959d234eb3ae24 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Thu, 7 Nov 2024 12:00:04 +0100 Subject: [PATCH 5/9] docs(srv): update --- menu/navigation.json | 156 +++++++++++++++++++++---------------------- 1 file changed, 78 insertions(+), 78 deletions(-) diff --git a/menu/navigation.json b/menu/navigation.json index 22b61bddc8..281ddd7a04 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -3703,40 +3703,6 @@ "label": "API/CLI", "slug": "api-cli" }, - { - "items": [ - { - "label": "Unable to create a namespace", - "slug": "cannot-create-namespace" - }, - { - "label": "I cannot inject secrets or variables in my job", - "slug": "cannot-inject-secret-variable" - }, - { - "label": "My function is in an error state", - "slug": "function-in-error-state" - }, - { - "label": "My function stopped working after a redeploy", - "slug": "function-stopped-after-redeploy" - }, - { - "label": "Handler not found", - "slug": "handler-not-found" - }, - { - "label": "I am experiencing timeout errors", - "slug": "timeout-errors" - }, - { - "label": "My function fails after too many retries", - "slug": "too-many-retries" - } - ], - "label": "Troubleshooting", - "slug": "troubleshooting" - }, { "items": [ { @@ -3790,6 +3756,40 @@ ], "label": "Additional Content", "slug": "reference-content" + }, + { + "items": [ + { + "label": "Unable to create a namespace", + "slug": "cannot-create-namespace" + }, + { + "label": "I cannot inject secrets or variables in my job", + "slug": "cannot-inject-secret-variable" + }, + { + "label": "My function is in an error state", + "slug": "function-in-error-state" + }, + { + "label": "My function stopped working after a redeploy", + "slug": "function-stopped-after-redeploy" + }, + { + "label": "Handler not found", + "slug": "handler-not-found" + }, + { + "label": "I am experiencing timeout errors", + "slug": "timeout-error" + }, + { + "label": "My function fails after too many retries", + "slug": "too-many-retries" + } + ], + "label": "Troubleshooting", + "slug": "troubleshooting" } ], "label": "Functions", @@ -3885,32 +3885,6 @@ "label": "API/CLI", "slug": "api-cli" }, - { - "items": [ - { - "label": "I cannot create a namespace", - "slug": "cannot-create-namespace" - }, - { - "label": "I cannot deploy my image", - "slug": "cannot-deploy-image" - }, - { - "label": "I cannot inject secrets or variables in my job", - "slug": "cannot-inject-secret-variable" - }, - { - "label": "I cannot retrieve external images", - "slug": "cannot-retrieve-external-images" - }, - { - "label": "My container stopped working after a redeploy", - "slug": "container-stopped-after-redeploy" - } - ], - "label": "Troubleshooting", - "slug": "troubleshooting" - }, { "items": [ { @@ -3948,6 +3922,32 @@ ], "label": "Additional Content", "slug": "reference-content" + }, + { + "items": [ + { + "label": "I cannot create a namespace", + "slug": "cannot-create-namespace" + }, + { + "label": "I cannot deploy my image", + "slug": "cannot-deploy-image" + }, + { + "label": "I cannot inject secrets or variables in my job", + "slug": "cannot-inject-secret-variable" + }, + { + "label": "I cannot retrieve external images", + "slug": "cannot-retrieve-external-image" + }, + { + "label": "My container stopped working after a redeploy", + "slug": "container-stopped-after-redeploy" + } + ], + "label": "Troubleshooting", + "slug": "troubleshooting" } ], "label": "Containers", @@ -4005,24 +4005,6 @@ "label": "How to", "slug": "how-to" }, - { - "items": [ - { - "label": "My job is in an error state", - "slug": "job-in-error-state" - }, - { - "label": "I cannot inject secrets or variables in my job", - "slug": "cannot-inject-secret-variable" - }, - { - "label": "I cannot retrieve external images", - "slug": "cannot-retrieve-external-images" - } - ], - "label": "Troubleshooting", - "slug": "troubleshooting" - }, { "items": [ { @@ -4054,6 +4036,24 @@ ], "label": "Additional Content", "slug": "reference-content" + }, + { + "items": [ + { + "label": "My job is in an error state", + "slug": "job-in-error-state" + }, + { + "label": "I cannot inject secrets or variables in my job", + "slug": "cannot-inject-secret-variable" + }, + { + "label": "I cannot retrieve external images", + "slug": "cannot-retrieve-external-image" + } + ], + "label": "Troubleshooting", + "slug": "troubleshooting" } ], "label": "Jobs", From 58c54d01db615eba02acbffcf1a9d32b6848950a Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Thu, 7 Nov 2024 14:25:03 +0100 Subject: [PATCH 6/9] Apply suggestions from code review Co-authored-by: nerda-codes <87707325+nerda-codes@users.noreply.github.com> --- .../troubleshooting/cannot-create-namespace.mdx | 8 ++++---- .../containers/troubleshooting/cannot-deploy-image.mdx | 2 +- .../troubleshooting/cannot-create-namespace.mdx | 8 ++++---- .../functions/troubleshooting/handler-not-found.mdx | 10 +++++----- serverless/functions/troubleshooting/timeout-error.mdx | 2 +- .../functions/troubleshooting/too-many-retries.mdx | 2 +- serverless/jobs/troubleshooting/job-in-error-state.mdx | 4 ++-- 7 files changed, 18 insertions(+), 18 deletions(-) diff --git a/serverless/containers/troubleshooting/cannot-create-namespace.mdx b/serverless/containers/troubleshooting/cannot-create-namespace.mdx index 94276691f8..af4c912da1 100644 --- a/serverless/containers/troubleshooting/cannot-create-namespace.mdx +++ b/serverless/containers/troubleshooting/cannot-create-namespace.mdx @@ -3,7 +3,7 @@ meta: title: I am unable to create a Serverless Containers namespace description: Troubleshoot problems encountered while creating namespaces for Scaleway Serverless Containers. content: - h1: My function fails after trying too many times + h1: I am unable to create a Serverless Containers namespace paragraph: Troubleshoot problems encountered while creating namespaces for Scaleway Serverless Containers. tags: serverless Containers troubleshooting issue error namespace creation unable dates: @@ -21,10 +21,10 @@ I cannot create a Serverless Containers namespace. This issue can happen for the following reasons: -- You created too many namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-containers). +- You have created too many namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-containers). -- You created too many Registry namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#container-registry). +- You have created too many Registry namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#container-registry). ### Possible solutions -Make sure that you did not exceed the maximum number of allowed namespaces with the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-containers/#path-namespaces-list-all-your-namespaces). \ No newline at end of file +Make sure that you have not exceeded the maximum number of allowed namespaces with the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-containers/#path-namespaces-list-all-your-namespaces). \ No newline at end of file diff --git a/serverless/containers/troubleshooting/cannot-deploy-image.mdx b/serverless/containers/troubleshooting/cannot-deploy-image.mdx index fa57f6ee00..cb0ba6e576 100644 --- a/serverless/containers/troubleshooting/cannot-deploy-image.mdx +++ b/serverless/containers/troubleshooting/cannot-deploy-image.mdx @@ -25,7 +25,7 @@ I am unable to deploy my image using Serverless Containers. - Containers cannot start due to insufficient provisioned resources. Update your container's resources by provisioning more memory and more vCPU. -- Make sure you built your image for an `amd64` architecture, as `arm64` is not supported. See [Architecture](/serverless/containers/reference-content/containers-limitations/#Architecture) documentation. +- Make sure you have built your image for an `amd64` architecture, as `arm64` is not supported. See the [Architecture](/serverless/containers/reference-content/containers-limitations/#Architecture) documentation for more information. - Make sure your deployment does not exceed the limitations of [Serverless Containers](/serverless/containers/reference-content/containers-limitations/). diff --git a/serverless/functions/troubleshooting/cannot-create-namespace.mdx b/serverless/functions/troubleshooting/cannot-create-namespace.mdx index 734956d75a..e39fa9d625 100644 --- a/serverless/functions/troubleshooting/cannot-create-namespace.mdx +++ b/serverless/functions/troubleshooting/cannot-create-namespace.mdx @@ -3,7 +3,7 @@ meta: title: I am unable to create a Serverless Functions namespace description: Troubleshoot problems encountered while creating namespaces for Scaleway Serverless Functions. content: - h1: My function fails after trying too many times + h1: I am unable to create a Serverless Functions namespace paragraph: Troubleshoot problems encountered while creating namespaces for Scaleway Serverless Functions. tags: serverless functions troubleshooting issue error namespace creation unable dates: @@ -21,10 +21,10 @@ I cannot create a Serverless Functions namespace. This issue can happen for the following reasons: -- You created too many namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-functions). +- You have created too many namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-functions). -- You created too many Registry namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#container-registry). +- You have created too many Registry namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#container-registry). ### Possible solutions -Make sure that you did not exceed the maximum number of allowed namespaces with the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-functions/#path-namespaces-list-all-your-namespaces). \ No newline at end of file +Make sure that you have not exceeded the maximum number of allowed namespaces with the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-functions/#path-namespaces-list-all-your-namespaces). \ No newline at end of file diff --git a/serverless/functions/troubleshooting/handler-not-found.mdx b/serverless/functions/troubleshooting/handler-not-found.mdx index 844f4202cd..983d6477ef 100644 --- a/serverless/functions/troubleshooting/handler-not-found.mdx +++ b/serverless/functions/troubleshooting/handler-not-found.mdx @@ -15,7 +15,7 @@ categories: ## Problem -My serverless Function is unable to find the Handler during its execution, and displays an error message similar to the following: +My serverless Function is unable to find the handler during its execution, and displays an error message similar to the following: ``` Function Handler does not exist, check that you provided the right HANDLER parameter … @@ -29,16 +29,16 @@ Provided Handler does not exist, or does not export methods properly ## Cause -The systems cannot find the function which will handle the request. It can be related to an error in your code before your `handle` function. +The systems cannot find the function that should handle the request. It can be related to an error in your code before your `handle` function. ## Possible solutions - Make sure to provide the right handler path. -- If you used a zip file, make sure the dependencies are present in your [zip package](/serverless/functions/how-to/package-function-dependencies-in-zip/). +- If you have used a zip file, make sure the dependencies are present in your [zip package](/serverless/functions/how-to/package-function-dependencies-in-zip/). -- If you used the Serverless framework, ensure the `.serverless` directory created with `serverless package` contains your zip file. +- If you have used the Serverless framework, ensure the `.serverless` directory created with `serverless package` contains your zip file. - Make sure that the dependencies folders (`node_modules` or `package` in Python) are in package/include. -- Serverless Functions rely on Alpine Linux, therefore, some C-based libraries (`pandas`, `tensorflow`, `numpy`) will not work. Refer to the official documentation to safely add these libraries to your package. \ No newline at end of file +- Serverless Functions rely on Alpine Linux. Therefore, some C-based libraries (`pandas`, `tensorflow`, `numpy`) will not work. Refer to the official documentation to safely add these libraries to your package. \ No newline at end of file diff --git a/serverless/functions/troubleshooting/timeout-error.mdx b/serverless/functions/troubleshooting/timeout-error.mdx index e25efc9dec..50dac1975c 100644 --- a/serverless/functions/troubleshooting/timeout-error.mdx +++ b/serverless/functions/troubleshooting/timeout-error.mdx @@ -19,7 +19,7 @@ I am experiencing timeout errors when using Scaleway Serverless Functions. ### Cause -Timeout happens when your function can’t return a results in the defined amount of time. +Timeout happens when your function cannot return any result in the defined amount of time. ### Possible solutions diff --git a/serverless/functions/troubleshooting/too-many-retries.mdx b/serverless/functions/troubleshooting/too-many-retries.mdx index 639e7dc125..bf7191b130 100644 --- a/serverless/functions/troubleshooting/too-many-retries.mdx +++ b/serverless/functions/troubleshooting/too-many-retries.mdx @@ -27,7 +27,7 @@ This error is returned by the runtime when it cannot process the request. It has ## Possible solutions -- Make sure that you only imported the required dependencies and not the complete libraries. +- Make sure that you have only imported the required dependencies and not the complete libraries. - Avoid performing too many initialization operations. diff --git a/serverless/jobs/troubleshooting/job-in-error-state.mdx b/serverless/jobs/troubleshooting/job-in-error-state.mdx index e363887d9f..90614acdcb 100644 --- a/serverless/jobs/troubleshooting/job-in-error-state.mdx +++ b/serverless/jobs/troubleshooting/job-in-error-state.mdx @@ -19,6 +19,6 @@ My job run is in an error state. ## Possible solutions -- Make sure you built your image for an `amd64` architecture, as `arm64` is not supported. See [Architecture](/serverless/jobs/reference-content/jobs-limitations/#Architecture) documentation. +- Make sure that you have built your image for an `amd64` architecture, as `arm64` is not supported. See the [Architecture](/serverless/jobs/reference-content/jobs-limitations/#Architecture) documentation for more information. -- Make sure your deployment does not exceed the limitations of [Serverless Jobs](/serverless/jobs/reference-content/jobs-limitations/). \ No newline at end of file +- Make sure that your deployment does not exceed the limitations of [Serverless Jobs](/serverless/jobs/reference-content/jobs-limitations/). \ No newline at end of file From 624ac2094935e644a81bcaadb87174009ffe6769 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Thu, 14 Nov 2024 17:37:15 +0100 Subject: [PATCH 7/9] Update serverless/containers/troubleshooting/cannot-create-namespace.mdx Co-authored-by: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> --- .../containers/troubleshooting/cannot-create-namespace.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/serverless/containers/troubleshooting/cannot-create-namespace.mdx b/serverless/containers/troubleshooting/cannot-create-namespace.mdx index af4c912da1..cfd5a7c025 100644 --- a/serverless/containers/troubleshooting/cannot-create-namespace.mdx +++ b/serverless/containers/troubleshooting/cannot-create-namespace.mdx @@ -21,7 +21,7 @@ I cannot create a Serverless Containers namespace. This issue can happen for the following reasons: -- You have created too many namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-containers). +- You have created too many Serverless Containers namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-containers). - You have created too many Registry namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#container-registry). From 42148467b83839d265eced60db8c9a3fb4f1060a Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Thu, 14 Nov 2024 17:37:23 +0100 Subject: [PATCH 8/9] Update serverless/functions/troubleshooting/handler-not-found.mdx Co-authored-by: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> --- serverless/functions/troubleshooting/handler-not-found.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/serverless/functions/troubleshooting/handler-not-found.mdx b/serverless/functions/troubleshooting/handler-not-found.mdx index 983d6477ef..5a85404b2e 100644 --- a/serverless/functions/troubleshooting/handler-not-found.mdx +++ b/serverless/functions/troubleshooting/handler-not-found.mdx @@ -29,7 +29,7 @@ Provided Handler does not exist, or does not export methods properly ## Cause -The systems cannot find the function that should handle the request. It can be related to an error in your code before your `handle` function. +The systems cannot find the function that should handle the request. It may be related to an error in your code before your `handle` function. ## Possible solutions From e53926509832b8b3f02128d5e3528b237dbaffa2 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Thu, 14 Nov 2024 17:37:30 +0100 Subject: [PATCH 9/9] Update serverless/functions/troubleshooting/cannot-create-namespace.mdx Co-authored-by: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> --- .../functions/troubleshooting/cannot-create-namespace.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/serverless/functions/troubleshooting/cannot-create-namespace.mdx b/serverless/functions/troubleshooting/cannot-create-namespace.mdx index e39fa9d625..55760c1959 100644 --- a/serverless/functions/troubleshooting/cannot-create-namespace.mdx +++ b/serverless/functions/troubleshooting/cannot-create-namespace.mdx @@ -21,7 +21,7 @@ I cannot create a Serverless Functions namespace. This issue can happen for the following reasons: -- You have created too many namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-functions). +- You have created too many Serverless Functions namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-functions). - You have created too many Registry namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#container-registry).