matlab -batch jobs are killed on Ubuntu without trace of reason
8 visualizaciones (últimos 30 días)
Mostrar comentarios más antiguos
I have 28 cores and 384GB RAM and I usually deploy 20 - 25 matlab jobs in parallel, like
matlab -batch "Job1" > output1 &
matlab -batch "Job2" > output2 &
etc.
One thing I don't understand is why these jobs after several hours are terminated before being done. The designated output files leave no trace. How can I ever find out what is wrong? If I restart, it continues because it looks to which results already exist, so it is not due to errors in the code.
The second thing relates to the no trace issue. Why does error messages print in the terminal and not into the designated output file? For example, a particular bug the code runs into returns an error message, which if I haven't left my terminal sessions is shown to me in the terminal window. Other programs put everything into the output file.
0 comentarios
Respuestas (1)
Steven Lord
el 2 de Mzo. de 2023
Are your jobs consuming a lot of memory? I'd check the syslog file to determine if the Out of Memory killer killed MATLAB to try to free up memory for MATLAB. [Yes, I know.]
2 comentarios
Steven Lord
el 3 de Mzo. de 2023
I'm not certain but I don't think the OOM killer gives processes the chance to "speak any last words" before it kills them.
Ver también
Categorías
Más información sobre Startup and Shutdown en Help Center y File Exchange.
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!