1

On Linux, I try to run a fortran executable (or even recompile and then run) and the job is killed immediately. The process just says "Killed". Now, if I copy the whole directory, the program will run just fine in the "new" directory -- but never in the original. This is happening repeatedly, but not universally, and seems random to me. Even though I have a work-a-round, I am still wondering why this happens at all.

nobody
  • 19,814
  • 17
  • 56
  • 77
ABAW
  • 41
  • 3

1 Answers1

1

Run your program with strace to find out what it is doing before it gets killed. Just speculating: But could it be allocating a huge amount of memory? If system memory is exhausted the out-of-memory killer usually kills the process that uses memory most aggressively. Check /var/log/syslog to see if the OOM killer was kicking in.

Also see What killed my process and why? and Will Linux start killing my processes without asking me if memory gets short?.

Martin Konrad
  • 1,075
  • 1
  • 10
  • 20
  • So, it just says "+++ killed by SIGKILL +++", however, I don't have permission to get into /var/log/syslog (this is on a cluster and I am only a user). That being said, I do think it is the memory. I'm not 100% on what to do to fix the way I allocate memory, but I do suspect that this is the problem. Thanks for your time + help! – ABAW Jun 21 '20 at 17:29