Glance sometimes terminates with an error code when nothing is wrong when run on the command line with a config file
This came from Mike Walters. I haven't seen this one in my command line tests with a config file, so there may be some subtle issue with how forking is working differently (if I can't find a way to reproduce on my machine I should do some tests on SSEC servers). Mike said:
Glance terminates abnormally, with the message "Aborting". This occurs when I run reportGen on the command line with a configuration file, which is how I normally run Glance. As far as I can tell, Glance generates the report and performs all of the requested operations successfully. The exit status should be 0 for success, but instead it's 134, which indicates failure. This is a bit of a problem because our cluster software tries to rerun failed jobs, so Glance jobs get run over and over. I can create a workaround if necessary, but that will have side effects. Anyway, I tracked the issue back to the os.fork() and os.waitpid() functions in the plot.py module. I'm not very familiar with forking in Python, so I wasn't able to narrow it down more than that.