馃悰 [Bug] `factories` server blocks port 4123 in docker-compose
Created by: Tirokk
Authored by roschaefer Closed
馃悰 Bugreport
After #1411 the new service blocks seeding. So when you do
docker-compose exec backend yarn run db:reset && yarn run db:seed
You will see sth. like this:
yarn run v1.17.3
$ cd backend && yarn run db:seed
$ cross-env GRAPHQL_URI=http://localhost:4001 GRAPHQL_PORT=4001 DISABLED_MIDDLEWARES=permissions run-p --race dev db:script:seed
$ nodemon --exec babel-node src/ -e js,gql
$ wait-on tcp:4001 && babel-node src/seed/seed-db.js
[nodemon] 1.19.1
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: *.*
[nodemon] starting `babel-node src/`
Warning: Sentry middleware inactive.
Warning: Disabled "permissions" middleware.
events.js:186
throw er; // Unhandled 'error' event
^
Error: listen EADDRINUSE: address already in use :::4001
at Server.setupListenHandle [as _listen2] (net.js:1228:14)
at listenInCluster (net.js:1276:12)
at Server.listen (net.js:1364:7)
at Function.listen (/home/robert/Development/human-connection/Human-Connection/backend/node_modules/express/lib/application.js:618:24)
at Object.listen (/home/robert/Development/human-connection/Human-Connection/backend/src/index.js:5:5)
at Module._compile (internal/modules/cjs/loader.js:936:30)
at Module._compile (/home/robert/Development/human-connection/Human-Connection/backend/node_modules/pirates/lib/index.js:99:24)
at Module._extensions..js (internal/modules/cjs/loader.js:947:10)
at Object.newLoader [as .js] (/home/robert/Development/human-connection/Human-Connection/backend/node_modules/pirates/lib/index.js:104:7)
at Module.load (internal/modules/cjs/loader.js:790:32)
Emitted 'error' event on Server instance at:
at emitErrorNT (net.js:1255:8)
at processTicksAndRejections (internal/process/task_queues.js:77:11) {
code: 'EADDRINUSE',
errno: 'EADDRINUSE',
syscall: 'listen',
address: '::',
port: 4001
}
[nodemon] app crashed - waiting for file changes before starting...
Seeded Data...
Done in 12.48s.
Interestingly the seeding works, it's just spitting out these error messages.
Expected behavior
No error messages.