mikemajesty / nestjs-microservice-boilerplate-api Goto Github PK

Actual behavior:

Yarn version: 3.5.0

I can't connect to mongo after initialize project.
yarn start:dev

Olá Mike, primeiramente parabéns pelo excelente projeto. Estou fazendo alguns testes com o objetivo de entender o funcionamento e percebi, durante os testes, que não está sendo feito o registro do tracing no Zipkin. Essa implementação está funcional?

I am running on Ubuntu 23. I have cloned the project and then ran
yarn infra
the docker containers are up and running successfully. But while trying to run the command
yarn start:dev i am getting connection error in mongo db.

Help me

Here is the error
[6:41:36 PM] File change detected. Starting incremental compilation...

[6:41:36 PM] Found 0 errors. Watching for file changes.

Tracing terminated
(node:53467) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created)
TRACE [16/11/2023 09:56:38]: CacheMemory connected!
TRACE [16/11/2023 09:56:38]: Redis connected!

[sequelize] Executed (default): SELECT table_name FROM information_schema.tables WHERE table_schema = 'public' AND table_name = 'cats' 4ms
[sequelize] Executed (default): SELECT i.relname AS name, ix.indisprimary AS primary, ix.indisunique AS unique, ix.indkey AS indkey, array_agg(a.attnum) as column_indexes, array_agg(a.attname) AS column_names, pg_get_indexdef(ix.indexrelid) AS definition FROM pg_class t, pg_class i, pg_index ix, pg_attribute a WHERE t.oid = ix.indrelid AND i.oid = ix.indexrelid AND a.attrelid = t.oid AND t.relkind = 'r' and t.relname = 'cats' GROUP BY i.relname, ix.indexrelid, ix.indisprimary, ix.indisunique, ix.indkey ORDER BY i.relname; 3ms
TRACE [16/11/2023 09:56:38]: Sequelize connected!
(node:53467) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created)

/home/nitesh-raj-khanal/Development/nestjs-microservice-boilerplate-api/node_modules/pino-mongodb/node_modules/mongodb/src/sdam/topology.ts:591
const timeoutError = new MongoServerSelectionError(
^
MongoServerSelectionError: Server selection timed out after 5000 ms
at Timeout._onTimeout (/home/nitesh-raj-khanal/Development/nestjs-microservice-boilerplate-api/node_modules/pino-mongodb/node_modules/mongodb/src/sdam/topology.ts:591:30)
at listOnTimeout (node:internal/timers:573:17)
at processTimers (node:internal/timers:514:7)

{"stack":"AggregateError\n at internalConnectMultiple (node:net:1114:18)\n at afterConnectMultiple (node:net:1667:5)\n at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17)","errors":"Error: connect ECONNREFUSED ::1:4318,Error: connect ECONNREFUSED 127.0.0.1:4318","code":"ECONNREFUSED","name":"AggregateError"}
{"stack":"Error: PeriodicExportingMetricReader: metrics export failed (error AggregateError)\n at doExport (/Users/niteshrajkhanal/Desktop/nestjs-microservice-boilerplate-api/node_modules/@opentelemetry/sdk-metrics/build/src/export/PeriodicExportingMetricReader.js:76:23)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async PeriodicExportingMetricReader._doRun (/Users/niteshrajkhanal/Desktop/nestjs-microservice-boilerplate-api/node_modules/@opentelemetry/sdk-metrics/build/src/export/PeriodicExportingMetricReader.js:84:13)\n at async PeriodicExportingMetricReader._runOnce (/Users/niteshrajkhanal/Desktop/nestjs-microservice-boilerplate-api/node_modules/@opentelemetry/sdk-metrics/build/src/export/PeriodicExportingMetricReader.js:55:13)","message":"PeriodicExportingMetricReader: metrics export failed (error AggregateError)","name":"Error"}

Hi Mike,
Thanks for this amazing boilerplate. it would be nice if you can provide minimal documentation explaining the architecture of project. It would be really helpful if you can point out the relevant code sections where particular design pattern is implemented

Thanks