clonemap_local: No meaningful log for `Caught sig terminated` and docker exit code 137 about clonemap

[kwe712]

Thanks for letting me know!
Can you try setting the environment variable "CLONEMAP_START_MODULES" to true? That should enable a graceful stop for the other containers in the docker-compose at least.

Unfortunately I cannot investigate the cause of the crash (or insert a proper error message in the right place) without more information - the container gets shut down due to a SIGTERM signal, which I cannot trace without knowledge of your system. As for the other two agencies not shutting down, they either didn't start correctly or there is an error in deleteAgency() that doesn't get caught. In this case too it would be helpful to have more info about the agencies running - if you have an idea of which code within your agencies is connected to this, could you share it here? If not, and you're at liberty to, maybe you could send me a .zip via email so I can try to replicate the error

[kwe712]

PS in cases like this where agencies aren't ended gracefully, it is advisable to run $docker container prune every once in a while to clean up the containers that didn't get deleted properly (this ended up solving our issue from renningen...)

[FWuellhorst]

Thanks for the quick response.
So far, the error did not occur again.
I will try with the start-modules flag and see if that helps.
I think the agency that did not terminate as expected was running the agentlib simulator with an FMU. I can't share the code, sadly.

I will also add the docker container prune option before restarting clonemap from now on, thanks!