Weird things when executing multiple ssh command in gitlab CI script

Question

I have a gitlab CI pipeline defined in .gitlab-ci.yml. One job is to deploy and start a spring boot application to 2 different machines. I do it by invoking a bash script twice with different machine set as argument to the script, and in the script it will start the spring boot application (already copied to the machine) using ssh command.

A weird thing is that if I have only one machine, this pipeline works fine. However, when I have 2 machines (with 2 invocations of the script as described above), the spring boot application deployed to the first machine will STALL. The process is still there, I can connect to it via visualVM to see the threads are running, but will just do nothing. No response from the http endpoint, no more logs produced at all.

I looks like something happened when the second invocation is started. However, the second invocation goes to the other machine, shouldn't have any impact on the first machine.

Much appreciated if anyone can share any hint of this.

Thanks!

xing · Accepted Answer · 2025-09-24 18:27:31Z

0

Problem solved, it's because of the sharing of one jar file among 2 machines. The jar file was stored in a NFS and shared among multiple machines. Obviously for executables it is not allowed.

answered Sep 24 at 18:27

xing

5049 silver badges18 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Weird things when executing multiple ssh command in gitlab CI script

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related