Did the report run fine? or was the error tacked on to the end of the file that already contained a good run of the report?
On Thu, May 6, 2021 at 10:20 AM Steve Dondley <s...@dondley.com.invalid> wrote: > On 2021-05-06 10:13 AM, Steve Dondley wrote: > > On 2021-05-06 10:08 AM, Paul Leo wrote: > > Maybe change environment variable to include full path to www-browser? > But this doesn't explain intermittent nature > > > What's also confusing is that the report gets generated just fine but > there is still an error message at the end. I think there has to be some > kind of race condition going on or something. > > > > > I should have mentioned that I have the apache config set up to non-http > traffic to https. I'm wondering if somehow port 443 gets blocked under > certain conditions when trying to reach http://localhost:80/server-status > <https://localhost:80/server-status>. > >
