This log only shows that your method servers (foreground and background) aren't starting up (either at all or in a timely fashion).
You need to examine the method servers logs to actually delve into the problem.
If there are no method server logs, then this points to the method server not even getting far enough to produce logs (in which case there are ways to launch a method server process directly from the command-line to see what goes awry prior to logging being established). I'd hope this is not occurring simply due to a server restart, though -- as this generally implies a serious misconfiguration (e.g. bad command-line parameters, pointing the method server to a non-existant Java executable or the like).