I converted a large notebook (a ton of code!) into a free-standing WolframScript. When I run the script:
- several warnings of the form
FrontEndObject::notavail: A front end is not available; certain operations require a front end.appear on the screen (as usual, these warnings eventually get suppressed); - the script will hang indefinitely if no X11 display is available (e.g. when it is run on a remote server via a text-only interface).
Of these two problems, the second one is the more serious one, but I suspect that the two are related, and that the first one may be the easier one to diagnose.
Hence, I'd like to find what exactly in my code is resulting in the FrontEndObject::notavail warnings. Since it's a lot of code (and, of course, I can't use the front end for debugging this), I'm looking for ideas to speed up the search.
FWIW, the code, even when run on the front end, sends no output to it. Its job is to read data from some input files, process the data, and write the result to other files.
Exportonly while working interactively, in which case anssh -Xis sufficient to provide an X server (the X server will be running on your machine, not remotely), or more commonly: I just don't useExport. I compute the results and plot them on my laptop. But there are indeed very good reasons to runExporton the server (I was just lucky enough not to have to do that recently). – Szabolcs Dec 12 '16 at 15:29