This is a rare situation that was seen when long-running ad hoc eHealth discoveries are executing on the system.
The discoveries consume resources on the system and prevent other processes from running.
Although "ad hoc" implies user interaction, the discoveries can be initiated by the Spectrum integration, and thus occur at odd hours.
Although the scheduled jobs fail when this happens, these are maintenance type jobs that will complete the unfinished work next time they run.
eHealth database related jobs failing (Stats Rollup, Stats Index, Delete Database Archive Logs)
Error:"Process m000 died, see its trace file"
Error:"kkjcre1p: unable to spawn jobq slave process"
Error:"Internal Error: Unable to connect to database 'EHEALTH'. (du/DuDatabase::connect)"
Error:"ksvcreate: Process(m000) creation failed"
(Legacy KB ID CNC TS34831 )