Open
Bug 380732
Opened 18 years ago
Updated 5 years ago
testserver.pl webservergroup validating fails w/some Apache setups
Categories
(Bugzilla :: Installation & Upgrading, enhancement)
Tracking
()
NEW
People
(Reporter: techno_plume-mailbox, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Build Identifier: 3.0
I have Debian Stable installed on a server, using Apache 1.3x as the webserver. I use Debian's 'apache-perl' rather than 'apache' package, because the former has mod_perl statically linked in.
The webserver test in testserver.pl (from Bugzilla 3.0 tarball) fails since the process is named apache-perl. testserver.pl looks for either 'httpd' or 'apache' only.
Result: TEST-WARNING Failed to find the GID for the 'httpd' process, unable
to validate webservergroup.
Renaming 'apache' to 'apache-perl' in testserver.pl allows the script to 'find' the running webserver and complete the test successfully.
Result: TEST-OK Webserver is running under group id in $webservergroup.
It would be nice if the script checked for common alternative names.
Reproducible: Always
Updated•10 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [good first bug]
Comment 1•10 years ago
|
||
:gerv- is this still a worthwhile bug to fix? If so, and if this makes a good first bug, can you link to the code, how to reproduce this problem, and what an ideal fix looks like? This should have a mentor assigned as well.
Flags: needinfo?(gerv)
Comment 2•10 years ago
|
||
testserver.pl line 47:
if ($line =~ /^(?:\S*\/)?(?:httpd|apache?)2?\s+(\d+)$/) {
This should be generalised to make "apache" a prefix.
Reproducing the problem, however, might be tricky without using Debian and apache-perl.
Gerv
Flags: needinfo?(gerv)
Updated•7 years ago
|
Keywords: good-first-bug
Comment 3•6 years ago
|
||
Removing good-first-bug
keyword because team does not have bandwidth to mentor at the moment.
Keywords: good-first-bug
Updated•5 years ago
|
Whiteboard: [good first bug]
You need to log in
before you can comment on or make changes to this bug.
Description
•