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

gx_it_proxy not stopped properly #90

Closed
abretaud opened this issue Nov 29, 2022 · 1 comment
Closed

gx_it_proxy not stopped properly #90

abretaud opened this issue Nov 29, 2022 · 1 comment

Comments

@abretaud
Copy link
Contributor

abretaud commented Nov 29, 2022

Hi!
We've upgraded usegalaxy.fr to 22.05 and switched gravity.
I have a little problem for the gx_it_proxy process: it seems like gravity fails to stop it properly.
When I start it, I get these processes:

galaxy   1143118  5.2  0.1 772872 44440 ?        Sl   11:12   0:01 npm exec gx-it-proxy --ip 0.0.0.0 --port 8000 --sessions /foobar/interactivetools_map.sqlite --verbose
galaxy   1143132  0.0  0.0   2608   596 ?        S    11:12   0:00 sh -c gx-it-proxy "--ip" "0.0.0.0" "--port" "8000" "--sessions" "/foobar/interactivetools_map.sqlite" "--verbose"
galaxy   1143133  1.3  0.0 820016 27052 ?        Sl   11:12   0:00 node /blablabla/node_modules/.bin/gx-it-proxy --ip 0.0.0.0 --port 8000 --sessions /foobarinteractivetools_map.sqlite --verbose

Running galaxyctl stop gx-it-proxy kills the first 2 processes, but not the third one.
Any idea what could be wrong?

(It's annoying because I get an error when trying a graceful restart, when it tries to stop/restart the proxy, and fails with "port already in use")

@abretaud
Copy link
Contributor Author

abretaud commented Dec 5, 2022

Adding stopasgroup=true in the generated supervisor conf fixes it (found this in https://stackoverflow.com/questions/67487983/supervisord-not-killing-all-spawned-node-processes-on-stop-command)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants