-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Christopher,
>> [2016-09-26T08:02:16.582] Terminate signal (SIGINT or SIGTERM) >> received > > So that's some external process sending one of those two signals > to slurmctld, it's not something it's choosing to do at all. We've > never seen this. We get the same snippet when our logrotate takes action against the cltdlog: # cron Sep 22 03:16:01 ctld run-parts(/etc/cron.daily)[29373]: starting logrota te Sep 22 03:16:55 ctld run-parts(/etc/cron.daily)[29428]: finished logrota te # ctldlog [2016-09-22T03:16:01.217] Terminate signal (SIGINT or SIGTERM) received HTH, John DeSantis On 09/27/2016 07:38 PM, Christopher Samuel wrote: > > On 26/09/16 17:48, Philippe wrote: > >> [2016-09-26T08:02:16.582] Terminate signal (SIGINT or SIGTERM) >> received > > So that's some external process sending one of those two signals > to slurmctld, it's not something it's choosing to do at all. We've > never seen this. > > One other question - you've got the shutdown log from slurmctld and > the start log of a slurmd - what happens when slurmctld starts up? > > That might be your clue about why yours jobs are getting killed. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJX694GAAoJEEmckBqrs5nBIJ0H/i2QGONJQ4tqMP41LTmtWI7s SXgdNtowJeQQZIW7aewMY8lbhss9zJmCMCKEYaJnjmh4lTfy1ekQHEXNM4C3I2M+ uDmnK51Lepp5ml5U808hXZXojSiIR1exryw8QkzdypbXf8wNm1fCTOuS5sbIQNXj Tzu7rZEFxMYpsdKemuMKx3DN8Z6XqgNKQFsNjsA5sF4BqlzBwQOidT5bpe5Fk4iR 9Q8eEKtyaUvZ1G3fbXSx/BrFAJE1ut5Jqtwu/ufylknmir2o7KCYf3dzIArg2iwa ajyHlbAg5q5TVPtJR3qri6cjgQm97Ekx/Fxarm67Mv7A+iL8ooB87IuXKaU1Kbo= =O3c7 -----END PGP SIGNATURE-----
