You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Aerie sequencing service is crashing when attempting to expand one of our plans. We attempted to expand the plan, observed that the request seems to be hung and the server memory pegged at 93%. We restarted the service and re-submitted the expansion request. Again the request seemed to hang and the service seemed to crash and restart itself. On the third attempt the expansion succeeded.
Reproduction
Has occurred on 2/3 attempts to expand our cruise002 plan.
Logs
This error appears in logs (not sure if related to crash):
2024-11-12 14:48:33.813
at trimPrefix (/app/node_modules/router/index.js:330:13)
2024-11-12 14:48:33.813
at Layer.handleRequest (/app/node_modules/router/lib/layer.js:101:15)
2024-11-12 14:48:33.813
at jsonParser (/app/node_modules/body-parser/lib/types/json.js:110:7)
2024-11-12 14:48:33.813
at next (/app/node_modules/router/index.js:282:5)
2024-11-12 14:48:33.813
at processParams (/app/node_modules/router/index.js:568:12)
2024-11-12 14:48:33.813
at /app/node_modules/router/index.js:291:7
2024-11-12 14:48:33.813
at trimPrefix (/app/node_modules/router/index.js:330:13)
2024-11-12 14:48:33.813
at Layer.handleRequest (/app/node_modules/router/lib/layer.js:101:15)
2024-11-12 14:48:33.813
at file:///app/build/app.js:54:62
2024-11-12 14:48:33.813
at getHasuraSession (file:///app/build/utils/hasura.js:57:11)
2024-11-12 14:48:33.813
Error: Could not determine the user sending the request
2024-11-12 14:48:33.813
ERROR app - Could not determine the user sending the request
Checked for duplicates
No - I haven't checked
Is this a regression?
No - This is a new bug
Version
2.11.2
Describe the bug
The Aerie sequencing service is crashing when attempting to expand one of our plans. We attempted to expand the plan, observed that the request seems to be hung and the server memory pegged at 93%. We restarted the service and re-submitted the expansion request. Again the request seemed to hang and the service seemed to crash and restart itself. On the third attempt the expansion succeeded.
Reproduction
Has occurred on 2/3 attempts to expand our cruise002 plan.
Logs
Full log
Aerie Sequencing Logs-data-2024-11-12 15_31_27.csv
Severity
Critical
The text was updated successfully, but these errors were encountered: