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
Jun 20 08:58:41 xxx node[1531]: /home/ec2-user/shared_modules/e2abc5edcce458989fffbcdb173d7e727d35f4ee/dist/server/../../modules/binaries/linux_x64/redis-server-selva --port,4003,--protected-mode,no,--dir,/home/ec2-user/services/env-db-sub-manager/tmp,--loadmodule,/home/ec2-user/shared_modules/e2abc5edcce458989fffbcdb173d7e727d35f4ee/modules/binaries/linux_x64/selva.so
Jun 20 08:58:41 xxx node[1531]: env-db-sub-manager-60c6cd: Process exiting with code 1
Jun 20 08:58:41 xxx node[1531]: env-db-sub-manager-60c6cd: exited with 0
Jun 20 08:58:41 xxx node[1531]: env-db-sub-manager-60c6cd: closed with 0
youzi
changed the title
If selva native module exits with error, node process exits with 0
If selva child process exits with error, node process exits with 0
Jul 4, 2023
This is wrong in cases where we are using the exit code to check if service exited with error or not.
I think it's handled incorrect here: server/src/server/index.ts:215
The text was updated successfully, but these errors were encountered: