SYMPTOM:
After upgrading the AtScale version 2023.4.1, We could see the modeler_backend service is keep restarting and getting below errors in the modeller_backend.stdout file
(node:29662) UnhandledPromiseRejectionWarning: Error: A circular dependency has been detected (property key: "result"). Please, make sure that each side of a bidirectional relationships are using lazy resolvers ("type: () => ClassType").
at SchemaObjectFactory.createNotBuiltInTypeReference (/opt/atscale/versions/2023.4.1.6713/pkg/modeler-backend-2023.4.1.555-linux-amd64/node_modules/@nestjs/swagger/dist/services/schema-object-factory.js:174:19)
at SchemaObjectFactory.createSchemaMetadata (/opt/atscale/versions/2023.4.1.6713/pkg/modeler-backend-2023.4.1.555-linux-amd64/node_modules/@nestjs/swagger/dist/services/schema-object-factory.js:284:25)
at SchemaObjectFactory.mergePropertyWithMetadata (/opt/atscale/versions/2023.4.1.6713/pkg/modeler-backend-2023.4.1.555-linux-amd64/node_modules/@nestjs/swagger/dist/services/schema-object-factory.js:122:21)
at /opt/atscale/versions/2023.4.1.6713/pkg/modeler-backend-2023.4.1.555-linux-amd64/node_modules/@nestjs/swagger/dist/services/schema-object-factory.js:79:35
at Array.map (<anonymous>)
at SchemaObjectFactory.extractPropertiesFromType (/opt/atscale/versions/2023.4.1.6713/pkg/modeler-backend-2023.4.1.555-linux-amd64/node_modules/@nestjs/swagger/dist/services/schema-object-factory.js:78:52)
at SchemaObjectFactory.exploreModelSchema (/opt/atscale/versions/2023.4.1.6713/pkg/modeler-backend-2023.4.1.555-linux-amd64/node_modules/@nestjs/swagger/dist/services/schema-object-factory.js:92:41)
at ResponseObjectFactory.create (/opt/atscale/versions/2023.4.1.6713/pkg/modeler-backend-2023.4.1.555-linux-amd64/node_modules/@nestjs/swagger/dist/services/response-object-factory.js:46:47)
at /opt/atscale/versions/2023.4.1.6713/pkg/modeler-backend-2023.4.1.555-linux-amd64/node_modules/@nestjs/swagger/dist/explorers/api-response.explorer.js:53:101
at /opt/atscale/versions/2023.4.1.6713/pkg/modeler-backend-2023.4.1.555-linux-amd64/node_modules/lodash/lodash.js:13469:38
(Use `node --trace-warnings ...` to show where the warning was created)
(node:29662) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:29662) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
2024-02-21 08:25:22 - Starting modeler_backend
ROOT CAUSE:
This is happening because of the known bug - DEVOPS-4634, Which is fixed in I2024.1.0
RESOLUTION:
As per engineering team, the service is not providing current functionality and can be disabled. The workaround is to remove the service from the service control (supervisord) so it doesn’t start.
Here are the steps to remove the service
Note:- For Clustered AtScale, always follow Clustered AtScale shut down and start up procedures.
$ /opt/atscale/bin/atscale_stop -f
$ cd /opt/atscale/versions/2023.4.1.6713/conf/supervisor/programs/
$ mv program_modeler_backend.conf program_modeler_backend.conf.org
$ /opt/atscale/bin/atscale_start
$ /opt/atscale/bin/atscale_service_control status
agent RUNNING pid 2380231, uptime 0:00:10
coordinator RUNNING pid 2380232, uptime 0:00:10
database RUNNING pid 2380234, uptime 0:00:10
directory RUNNING pid 2380235, uptime 0:00:10
egress RUNNING pid 2380237, uptime 0:00:10
engine RUNNING pid 2380245, uptime 0:00:10
ingress RUNNING pid 2380252, uptime 0:00:10
modeler RUNNING pid 2380260, uptime 0:00:10
orchestrator RUNNING pid 2380268, uptime 0:00:10
service_registry RUNNING pid 2380230, uptime 0:00:10
servicecontrol RUNNING pid 2380276, uptime 0:00:10
By following the above steps when we start all the services at once it'll not start the modeler_backend service.