Crashing .psgi is not logged (with --preload-app) about starman HOT 3 OPEN

closing as I cannot reproduce exactly what I saw on production -- my situation was that the app.psgi contained Foo->new->to_app, but the object died during instantiation -- and start_server was in front of starman. I saw nothing at all in the error.log - the process was repeatedly dying and being restarted with no diagnostics at all.

from starman.

reopening, now that I've got a reliable repro case -- the error is logged only if --preload-app is not used.

When --preload-app is included, there is an error to the console but not to the error log. When start_server is put in front of starman, the console output is not captured anywhere, so there is now no information indicating the source of the error (and it's not even that obvious that the app is continually being restarted/crashed/restarted).

from starman.

I'm seeing a related problem where a child will segfault and we get no notice of that whatsoever, whether or not --preload-app is enabled. I'm going to look into this further and see if I can come up with a fix. We've had various problems with Starman's logging in the past and I'd really like to make it more robust.

from starman.