Description
Emake received the terminal signal described by the text of the message. For example, the user may have typed Ctrl-C. Of course, this messsage is NOT printed for signals that cannot be intercepted, such as Unix/Linux SIGKILL.
After printing this message, emake will attempt to perform a controlled shutdown.
| This message will be printed only the first time a terminal signal is received. Subsequent terminal signals do not hasten the controlled shutdown, nor do they trigger this message. |
ALSO NOTE: This message is only issued in cluster mode. In local mode it would race with other messages, causing ugly interleaving with other build output.
Fixes
If the user did not actually desire to kill their build, then they need to track down who or what sent the signal. The signal description may provide a clue.
This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.