Last weekend our alerts went of because of high cpu. This happened exactly the same time (noon). When we logged into the servers we discovered that updatedb was the cpu hog. We killed the processes, and afterwards nagios started complaining with the same error across several servers:<br />
<br />
bash: no job control in this shell<br />
<br />
We started to investigate and found that there were issues when running certain binaries and shell-scripts. This error also affects init.d scripts, making it a quite severe error that we have to eliminate somehow. We suspect there is an issue when running su commands, and this somehow is related to tty. For example, the error can happen over ssh, but running the same command in console does not always trigger the no job control error.
↧