Apache startup warning/error: mailman DocumentRoot?
Hello again,
There's another annoying warning message I get that I'd like to resolve, but I only get it at startup, so I keep forgetting about it. I had to shutdown the server this morning to move it to a new UPS, and saw it again when I started the server up, so now I'm asking. I know there's something obvious I must be missing, but I'm used to getting whacked by 2x4's when asking questions like this so I'm wearing my Spartan warriors helmet.
Anyway, here's the warning/error:
Warning: DocumentRoot [/var/www/localhost/htdocs/mailman] does not exist apache2: Could not reliably determine the servers fully qualified domain name, using ###.###.###.### for ServerName
Now, the path is correct, but there is no mailman directory in the htdocs folder, so the warning is correct - and, to make matters worse, I *do* have this path explicitly set in the /etc/apache2/vhosts.d/lists.example.com config file, although I'm not sure why now.
Everything works fine... I can go to lists.example.com and manage my lists, and all links in the list messages are of the form "...lists.example.com/..." and they all work for managing bounces, etc.
50_mailman.conf contains:
ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/"
<Directory "/usr/local/mailman/cgi-bin/"> AllowOverride None Options None Order allow,deny Allow from all </Directory>
Alias /pipermail/ "/usr/local/mailman/archives/public/"
<Directory "/usr/local/mailman/archives/public/"> AllowOverride None Options ExecCGI FollowSymLinks Order allow,deny Allow from all </Directory>
So, my question is, what should the path in /etc/apache2/vhosts.d/lists.example.com be pointing to? Where *is* the mailman DocumentRoot?
Tia...
-----Original Message-----
Anyway, here's the warning/error:
Warning: DocumentRoot [/var/www/localhost/htdocs/mailman] does not exist ^^^^^^^^^ apache2: Could not reliably determine the servers fully qualified domain name, using ###.###.###.### for ServerName
I *do* have this path explicitly set in the /etc/apache2/vhosts.d/lists.example.com config file, ^^^^^^^^^^^^^^^^^
Everything works fine... I can go to lists.example.com and manage my lists, and all links in the list messages are of the form "...lists.example.com/..." and they all work for managing bounces, etc.
It looks like apache is carping about not being able to find the mailman docroot for localhost (IP addr: 127.0.0.1, usually!)
You then have the path set for the configuration of the IP host lists.example.com in its own config file.
If you set DocumentRoot correctly in the config file for the localhost webserver instance, it should do away with the annoying error message.
Steff
Steff Watkins Natural History Museum, Cromwell Road, London, SW7 5BD Systems programmer Email: s.watkins@nhm.ac.uk Systems Team Phone: +44 (0)20 7942 6000 opt 2
Many were increasingly of the opinion that they'd all made a big mistake in coming down from the trees in the first place. And some said that even the trees had been a bad move, and that no one should ever have left the oceans. - HHGTTG
Tanstaafl wrote:
Now, the path is correct, but there is no mailman directory in the htdocs folder, so the warning is correct - and, to make matters worse, I *do* have this path explicitly set in the /etc/apache2/vhosts.d/lists.example.com config file, although I'm not sure why now.
And this is exactly why you get the warning.
Everything works fine...
Because
ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/"
and
Alias /pipermail/ "/usr/local/mailman/archives/public/"
are all you need
So, my question is, what should the path in /etc/apache2/vhosts.d/lists.example.com be pointing to? Where *is* the mailman DocumentRoot?
Mailman neither has nor needs a DocumentRoot. Just remove it, and if you want http://lists.example.com/ to go to a mailman page, add
RedirectMatch ^[/]+$ http://lists.example.com/mailman/listinfo
to /etc/apache2/vhosts.d/lists.example.com instead.
Alternatively, you could create the /var/www/localhost/htdocs/mailman/ directory and put some appropriate index.html file in it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Just getting back to this, and to close it out...
On 2010-06-02 10:03 AM, Mark Sapiro wrote:
Tanstaafl wrote:
So, my question is, what should the path in /etc/apache2/vhosts.d/lists.example.com be pointing to? Where *is* the mailman DocumentRoot?
Mailman neither has nor needs a DocumentRoot. Just remove it,
That did it, thanks! I don't know why I thought that was needed...
As long as the specific list management pages work, I don't care about the root domain (lists.example.com) itself...
As always, Mark, thanks for your spot on reply... :)
Charles
participants (3)
-
Mark Sapiro -
Steff Watkins -
Tanstaafl