12

I have a simple Python code for a machine learning project. I have a relatively big database of spontaneous speech. I started to train my speech model. Since it's a huge database I let it work overnight. In the morning I woke up and saw a mysterious

Killed: 9

line in my Terminal. Nothing else. There is no other error message or something to work with. The code run well for about 6 hours which is 75% of the whole process so I really don't understand whats went wrong.

What is Killed:9 and how to fix it? It's very frustrating to lose hours of computing time...

I'm on macOS Mojave beta if it's matter. Thank you in advance!

Cerniuk
  • 14,220
  • 2
  • 29
  • 27
Hordon
  • 603
  • 2
  • 9
  • 21
  • Signal 9 is UNIX/POSIX signal `SIGKILL`. Check if any other processes on your system could have raised it. On Mac OS, some events (e.g. local notification) can, anecdotally, cause this signal to be raised if the underlying event is not handled. – nanofarad Aug 14 '18 at 03:30
  • Thanks Andrey! Sorry for the noob question but how can I check this? – Hordon Aug 14 '18 at 03:31
  • Unfortunately I'm not well-versed enough with Mac OS to be able to give strong guidance. There's some further discussion in [this post](https://stackoverflow.com/questions/16338884/what-does-exited-abnormally-with-signal-9-killed-9-mean) and you might be able to use a tool such as strace to see what happens in the last moments of the process (at a cost to performance as the process runs). – nanofarad Aug 14 '18 at 03:32
  • I am having very similar issue, also on OSX Mojave. Have you resolved it? – Danijel Oct 24 '19 at 08:40
  • @Danijel Unfortunately I couldn't resolve it. I tried to cool my machine more if it's a thermal throttling problem but it didn't help. I suggest - if it's possible in your case - to split your task into smaller subtasks. – Hordon Oct 25 '19 at 09:05
  • 1
    I resolved my problem. It was internal to the program I was running: it had some kind of a memory leak, so the memory usage would build up to giga bytes, eventualy crashing. Run your task and look into Activity Monitor app to check memory state while running it. – Danijel Oct 25 '19 at 10:24
  • Does this answer your question? [What does "Killed: 9" error mean?](https://stackoverflow.com/questions/33978241/what-does-killed-9-error-mean) – Paul Hankin Jul 30 '21 at 07:21
  • I have noticed the same error while upgrading terraform to higher version by simply copying the executable to /bin location. But I was able to resolve it by first deleting the existing terraform executable and then copying the new one. – user4202236 May 26 '22 at 22:50

3 Answers3

1

I faced this issue when I updated my Mac OS version from Catalina to Big Sur. I was trying to run a binary and facing the Killed: 9 issue.

I was able to resolve this issue by following the steps below (I referred to this Apple StackExchange post for these steps) :-

  1. Download UPX via Homebrew - brew install upx
  2. Then decompress the binary - upx -d /path/to/binary/file
Dhruv Saraswat
  • 858
  • 9
  • 13
0

Try to change the node version. In my case, that helps.

bartosz.K
  • 26
  • 3
  • Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community May 07 '22 at 09:50
0

i've got the same issue when i install mongodb that bebasue it use 'cp' something to your bin path

so enter your bin path

cd /usr/local/bin
open .

then delete the new file

xie Faiz
  • 49
  • 4