serverless / serverless/examples

examples/aws-node-rest-api-with-dynamodb-and-offline/ Unable to start DynamoDB Local process!

Open
#359 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
11.5k
Forks
4.4k
Avg merge
2h 55m
Merged PRs (30d)
3

Description

hello i cloned the examples repository and followed the instructions for the above mentioned example. when i run the command serverless offline start , i get the following output:

`Error --------------------------------------------------

Unable to start DynamoDB Local process!

 For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.

Get Support --------------------------------------------
Docs: docs.serverless.com
Bugs: github.com/serverless/serverless/issues
Issues: forum.serverless.com

Your Environment Information -----------------------------
OS: linux
Node Version: 9.11.2
Serverless Version: 1.37.1`

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the examples/aws-node-rest-api-with-dynamodb-and-offline/ example and reproduce the failure using serverless offline start under the reported Linux, Node 9.11.2, and Serverless 1.37.1 environment. Re-run with SLS_DEBUG=* as requested by the error and use the resulting logs to identify why DynamoDB Local does not start; done means the example starts successfully offline.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, javascript, node.js
Domain
cloud, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.