A command line search that was working previously within a few minutes now hangs for a few hours before reporting "FATAL: Unable to read the job status." After simplifying the search I actually got a single event back before getting the same error. The same search works fine in the web-based search.
Has anyone seen this before? Google sure doesn't think so. Any idea what might be going on or where I can start digging in?