Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[task] Не стартуют сервисы #135

Closed
unmyke opened this issue Dec 9, 2020 · 0 comments · Fixed by #134
Closed

[task] Не стартуют сервисы #135

unmyke opened this issue Dec 9, 2020 · 0 comments · Fixed by #134
Assignees
Labels

Comments

@unmyke
Copy link
Contributor

unmyke commented Dec 9, 2020

Окружение:

  • node-14-alpine

Что случилось?

Запуск микросервисов, имеющих модуль персистентности, останавливается без сообщений об ошибках и завершения работы.

Опишите пошагово что сделать, что бы повторить баг

  • запустить любой микосервис, имеющий в зависимостях модуль персистентности
$ docker-compose up -d identity-service
  • посмотреть логи запущенносого микосервиса
$ docker-compose logs --follow identity-service

Attaching to serenity_identity-service_1
identity-service_1  | yarn run v1.22.5
identity-service_1  | $ yarn workspace @identity/service dev
identity-service_1  | $ server-scripts start
identity-service_1  | Compiled with warnings.
identity-service_1  | 
identity-service_1  | /workspace/backend/protos/identity/src/index.ts
identity-service_1  | Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
identity-service_1  | 
identity-service_1  | /workspace/backend/protos/common/src/index.ts
identity-service_1  | Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
identity-service_1  | 
identity-service_1  | Search for the keywords to learn more about each warning.
identity-service_1  | To ignore, add // eslint-disable-next-line to the line before.
identity-service_1  | 
identity-service_1  | Starting the development server...
identity-service_1  | 
identity-service_1  | [Nest] 68   - 12/09/2020, 10:13:09 AM   [NestFactory] Starting Nest application...
identity-service_1  | [Nest] 68   - 12/09/2020, 10:13:09 AM   [InstanceLoader] BusModule dependencies initialized +40ms
identity-service_1  | [Nest] 68   - 12/09/2020, 10:13:09 AM   [InstanceLoader] TypeOrmModule dependencies initialized +0ms
identity-service_1  | [Nest] 68   - 12/09/2020, 10:13:09 AM   [InstanceLoader] TypeOrmModule dependencies initialized +1ms
identity-service_1  | [Nest] 68   - 12/09/2020, 10:13:09 AM   [InstanceLoader] LoggerModule dependencies initialized +0ms
identity-service_1  | [Nest] 68   - 12/09/2020, 10:13:09 AM   [InstanceLoader] BusCoreModule dependencies initialized +1ms

Ожидаемый результат (необязательно)

Должен произойти запуск микросервиса

$ docker-compose up -d identity-service
$ docker-compose logs --follow identity-service

Attaching to serenity_identity-service_1
identity-service_1  | yarn run v1.22.5
identity-service_1  | $ yarn workspace @identity/service dev
identity-service_1  | $ server-scripts start
identity-service_1  | Compiled with warnings.
identity-service_1  | 
identity-service_1  | /workspace/backend/protos/identity/src/index.ts
identity-service_1  | Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
identity-service_1  | 
identity-service_1  | /workspace/backend/protos/common/src/index.ts
identity-service_1  | Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
identity-service_1  | 
identity-service_1  | Search for the keywords to learn more about each warning.
identity-service_1  | To ignore, add // eslint-disable-next-line to the line before.
identity-service_1  | 
identity-service_1  | Starting the development server...
identity-service_1  | 
identity-service_1  | [Nest] 68   - 12/09/2020, 10:13:09 AM   [NestFactory] Starting Nest application...
identity-service_1  | [Nest] 68   - 12/09/2020, 10:13:09 AM   [InstanceLoader] BusModule dependencies initialized +40ms
identity-service_1  | [Nest] 68   - 12/09/2020, 10:13:09 AM   [InstanceLoader] TypeOrmModule dependencies initialized +0ms
identity-service_1  | [Nest] 68   - 12/09/2020, 10:13:09 AM   [InstanceLoader] TypeOrmModule dependencies initialized +1ms
identity-service_1  | [Nest] 68   - 12/09/2020, 10:13:09 AM   [InstanceLoader] LoggerModule dependencies initialized +0ms
identity-service_1  | [Nest] 68   - 12/09/2020, 10:13:09 AM   [InstanceLoader] BusCoreModule dependencies initialized +1ms
identity-service_1  | [Nest] 68   - 12/09/2020, 10:13:09 AM   [InstanceLoader] TypeOrmCoreModule dependencies initialized +69ms
identity-service_1  | [Nest] 68   - 12/09/2020, 10:13:09 AM   [InstanceLoader] PersistenceModule dependencies initialized +1ms
identity-service_1  | [Nest] 68   - 12/09/2020, 10:13:09 AM   [InstanceLoader] ApplicationModule dependencies initialized +0ms
identity-service_1  | [Nest] 68   - 12/09/2020, 10:13:09 AM   [InstanceLoader] ServiceModule dependencies initialized +1ms
identity-service_1  | [Nest] 68   - 12/09/2020, 10:13:09 AM   [NestMicroservice] Nest microservice successfully started +4ms
unmyke added a commit that referenced this issue Dec 9, 2020
affects: @catalog/persistence, @files/persistence, @hits/persistence, @identity/persistence, @mailer/db

ISSUES CLOSED: #135
@TorinAsakura TorinAsakura linked a pull request Dec 9, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants