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
Documenting an issue that happened with t01s and t01x in the TS in ClimateDT.
You run an autosubmit run, and at some point the main process goes to sleep... the children become zombies... and then the children (log retrieval processes) stop retrieving logs, they die, and the parent autosubmit run keeps running, and never responds to autosubmit stop (#2104#2063 ).
Creating this issue just so we have it recorded here for posterity.
Yesterday, talking with @franra9, he reported that this is happening quite frequently for one of his experiments (more so than it happened to me).
He also said something interesting. He had already run the experiment, and then had to setstatus and relaunch it, then the issue happened. Or sometimes he could be launching from start, but that would be after he had once launched the experiment.
So maybe Autosubmit stops in the first execution leaving data (on disk, pickles, DB, etc.) in an inconsistent format, and then the next time Autosubmit runs it is able to read the config, load, but eventually it gets into this inconsistent state and stalls.
Or it could be something else… but given we don't really have a clue where to start looking for this issue, Francesc's comment seemed like a good starting point.
Documenting an issue that happened with t01s and t01x in the TS in ClimateDT.
You run an autosubmit run, and at some point the main process goes to sleep... the children become zombies... and then the children (log retrieval processes) stop retrieving logs, they die, and the parent autosubmit run keeps running, and never responds to autosubmit stop (#2104 #2063 ).
Creating this issue just so we have it recorded here for posterity.
We thought #2041 could fix it, but that didn't.
Now #2097 could help with it, but not sure if it will fix.
The text was updated successfully, but these errors were encountered: