A process for this page is already running and it was still alive 305 seconds agoand refused to run from commandline. Went back to the web-based link from the admin section, this time it said
Running commandline, quitting. We'll find out what to do in the next run.
A process for this page is already running and it was still alive 461 seconds agobut after 20 sec, started processing afresh. But this is somewhat risky when running from a remote machine, because the connection may break during the hour or so taken for processing. The best thing, then, would be to either
Sleeping for 20 seconds, aborting will quit
- run the bounce processing as a cron job (like we do), or
- when troubleshooting, run from inside a screen console, detach the screen when not actively monitoring it, or
- run the web-based link from a local X console, or
- run the web-based link from a VNC X console running on localhost.