Skip to content

Latest commit

 

History

History
86 lines (57 loc) · 3.37 KB

PROBLEMS.md

File metadata and controls

86 lines (57 loc) · 3.37 KB
Raw

Common Problems

This document contains potential solutions to common problems and errors. If you do not find the solution here, please feel free to ask around on slack! A table of contents is provided for ease of use:

Anybody is free to add any problems & solutions to this file! Just open a PR following our git workflow.

Database Troubleshooting

The MongoDB is ran in a docker container. You will need to have ports 27017 and 28017 open. See the address/port already in use section to see how to open these. After the database is created, seed data is automatically imported so that testing can be done.

General troubleshooting steps:

  • Ensure docker is installed: docker --version

  • Ensure direnv is set up properly with direnv allow. See the development environment setup if you have not done so already. If nothing else works, at the very least, run source .env.

  • Make sure the database is running by running yarn restart (should see 'Database Connected' in your terminal)

  • Make sure database is seeded by either checking the data in Robo 3T if you downloaded that (see development environment setup) or by trying to log in with Kevin's credentials (check them in the Personas story in the Icebox on Pivotal Tracker)

Problem:

Database connection error { MongoNetworkError: failed to connect to server [127.0.0.1:27017] on first connect [MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017]

Solution: Try here, followed by yarn restart

Address/port already in use

Problem: Error: address already in use

Solution: Free all needed ports with lsof -ti tcp:3000,3001,27017,28017 | xargs kill -9 --no-run-if-empty

Error response from daemon: Container is not running

Problem:

--- Starting new docker container with MongoDB..
--- Started container 38ee6b4af0c4481a137209c70bb64784afbd33f4ab5bbb37735aa9d2ca945bf7
--- Copying seed data to docker container..
--- Adding seed data to MongoDB..
Error response from daemon: Container 38ee6b4af0c4481a137209c70bb64784afbd33f4ab5bbb37735aa9d2ca945bf7 is not running
error Command failed with exit code 1.

Solution:

$ yarn stop
$ docker system prune
$ docker volume prune

Errors

Problem (1): I pulled the latest changes from master and I am now getting an error.

Problem (2): I installed a new dependency with npm install and I am now getting an error.

Problem (3):

$ yarn start
yarn run v1.3.2
$ NODE_ENV=dev npm-run-all --parallel client:watch server:watch
/bin/sh: npm-run-all: command not found
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Solution: yarn

Problem: I am not seeing anything once I view the app at localhost:3000.

Solution: yarn restart

Test Errors

General information about testing can be found in the test docs.