I would suspect it's your invocation of strigger regarding your shell; Don't really think it's a Slurm issue. I'd probably do something like follows, but not tested.
`strigger --set --jobid=523 --fini --program="/bin/echo 'job complete' >> /tmp/trigger.txt"` jared On Tue, Jan 18, 2022 at 8:48 AM John Yost <hokiege...@gmail.com> wrote: > whoops, I guess images are not supported, sorry about that! > > Here's what i am seeing: > > $ sbatch simple.slurm > Submitted batch job 523 > $ strigger --set --jobid=523 --fini --program=/bin/echo "job complete" >> > /tmp/trigger.txt > $ strigger --get --jobid=523 > TRIG_ID RES_TYPE RES_ID TYPE OFFSET USER > FLAGS PROGRAM > 2 job 523 fini 0 slurm > /bin/echo > $ > > slurmctld log: > > [2022-01-18T15:19:59.171] _job_complete: JobId=523 done > [2022-01-18T15:20:19.328] trigger uid=1338 type=job:fini exit=1:0 > > Although the trigger is fired, the trigger.txt file is never written, so > it seems to be there is a problem executing the program I've defined, but I > don't see any errors in slurmctld.log. Any ideas? > > Thanks > > --John > >
