#710: Can't stop / cleanup simulations that run without a queueing system
Reporter:Erik Schnetter
Status:new
Milestone:
Version:
Type:bug
Priority:minor
Component:SimFactory

Comment (by Roland Haas):

This is still happening even after git hash 0ce61cb "Add submit scripts for workstations, so that simulations can be run in the background there" of simfactory2 which introduced an exec to generic.sub making the PID returned that of the simfactory run process. This still leaves python and bash in between the PID returned and the Cactus executable. Eg for pid 30727 on a Debian system, one has:

systemd(1)───python2(30711)───RunScript(30719)───cactus_sim(30727)─┬─orted(30758)─┬─{orted}(30764)
                                                                   │              ├─{orted}(30765)
                                                                   │              └─{orted}(30766)
                                                                   ├─{cactus_sim}(30768)
                                                                   └─{cactus_sim}(30769)

and after running stop on the simulation this looks like so

systemd(1)───RunScript(30719)───cactus_sim(30727)─┬─orted(30758)─┬─{orted}(30764)
                                                  │              ├─{orted}(30765)
                                                  │              └─{orted}(30766)
                                                  ├─{cactus_sim}(30768)
                                                  └─{cactus_sim}(30769)

ie Python terminated but nothing else. Manually killing RunScript gets rid of just the RunScript and now leaves cactus_sim as a child of systemd.

A fix would be to try and propagate the signal down to cactus_sim (see

--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/710/cant-stop-cleanup-simulations-that-run