Maybe change environment variable to include full path to www-browser? But this doesn’t explain intermittent nature
> On May 6, 2021, at 8:00 AM, Nick Folino <n...@folino.us> wrote: > > > That appears to be generated by your OS, not the Apache httpd server. > >> On Thu, May 6, 2021 at 9:53 AM Steve Dondley <s...@dondley.com.invalid> >> wrote: >> I have a script, triggered by cron, that runs every minute that checks >> the status of the localhost's server: >> >> my $status = `sudo apachectl status 2>&1`; >> >> After a freshly restarted apaceh2 daemon, the script works fine and the >> contents of $status get written to a file. >> >> But after several minutes or several hours of humming along, a "failed" >> error message will start creeping into the bottom of the apachectl >> status reports along with suggestions for editing the APACHE_LYNX >> variable: >> >> >> ============================================================================= >> >> Apache Server Status for localhost (via 127.0.0.1) >> >> Server Version: Apache/2.4.38 (Debian) OpenSSL/1.1.1d >> Server MPM: prefork >> Server Built: 2020-08-25T20:08:29 >> __________________________________________________________________ >> >> <snip> >> >> W____._._.___................................................... >> ................................................................ >> ...................... >> >> Scoreboard Key: >> "_" Waiting for Connection, "S" Starting up, "R" Reading Request, >> "W" Sending Reply, "K" Keepalive (read), "D" DNS Lookup, >> "C" Closing connection, "L" Logging, "G" Gracefully finishing, >> "I" Idle cleanup of worker, "." Open slot with no current process >> 'www-browser --dump http://localhost:80/server-status' failed. >> Maybe you need to install a package providing www-browser or you >> need to adjust the APACHE_LYNX variable in /etc/apache2/envvars >> >> ============================================================================= >> >> After a few minutes, the error might go away only to come back stronger, >> fiercer and longer a few hours, or minutes, later. There doesn't seem to >> be any rhyme or reason to when this error occurs except that when they >> do happen, they tend to occur in bursts. Other than that the status >> reports are generated perfectly fine except for the error message at the >> end of them. The error will also sometimes show up sometimes, but not >> always, when "apachectl status" is run directly on the command line. >> >> I've got this line in /etc/apache2/envvars: export >> APACHE_LYNX='www-browser --dump' >> >> I've tried using the command with "-dump" and "--dump" but it doesn't >> seem to make a difference. >> >> Any ideas on what might be causing this error to be generated? >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org >> For additional commands, e-mail: users-h...@httpd.apache.org >>
