[Mailman-Users] mailman + apache2

[Stefan Fuhrmann]

Am Dienstag, 7. Februar 2006 18:16 schrieben Sie:
> Stefan Fuhrmann wrote:
> >Am Dienstag, 7. Februar 2006 02:45 schrieben Sie:
> >> BTW, I'm not sure why you have the 'cgi-bin/' in the above URL,
> >> Normally, if the ScriptAlias says '/mailman/' the URL uould just be
> >> <http://domain.tld/mailman/create>
> >
> >When I browse this then I get "file not found"
> >dont know what to do here!
>
> In a prior post you said:
> >I set in Vhosts_ispconfig.conf (where the virutual hosts are created)
> > >"ScriptAlias /mailman/ /var/www/web1/cgi-bin/"
>
> If that directive actually applies to domain.tld, then (assuming that
> /var/www/web1/cgi-bin/ is the directory that contains Mailman's
> wrappers) the URL <http://domain.tld/mailman/create> should cause
> Apache to execute the "create" wrapper.
Debian installs mailman to /usr/lib/cgi-bin/mailman. I linked it 
to /var/www/web1/cgi-bin/ 
ScriptAlias is set to 
ScripAlias /mailman/ /var/www/web1/cgi-bin/

this gives the aboves errors

>
> Now it is clear that you do get to Mailman when you go to
> <http://domain.tld/cgi-bin/mailman/create> so there is likely some
> other Alias or ScriptAlias that handles that URL.
>
> What is in Apache's error_log for the attempt to get
> <http://domain.tld/mailman/create>
thats it what is created in apache2 error.log  when I try to access the URL:

"[Fri Feb 10 00:13:00 2006] [notice] Apache/2.0.54 (Debian GNU/Linux) 
mod_python/3.1.3 Python/2.3.5 PHP/4.3.10-16 mod_ssl/2.0.54 OpenSSL/0.9.7e 
mod_perl/1.999.21 Perl/v5.8.4 configured -- resuming normal operations
[Fri Feb 10 00:31:23 2006] [notice] caught SIGTERM, shutting down
[Fri Feb 10 00:31:24 2006] [notice] suEXEC mechanism enabled 
(wrapper: /usr/lib/apache2/suexec2)
[Fri Feb 10 00:31:25 2006] [notice] mod_python: Creating 20 session mutexes 
based on 20 max processes and 0 max threads.
[Fri Feb 10 00:31:31 2006] [notice] Apache/2.0.54 (Debian GNU/Linux) 
mod_python/3.1.3 Python/2.3.5 PHP/4.3.10-16 mod_ssl/2.0.54 OpenSSL/0.9.7e 
mod_perl/1.999.21 Perl/v5.8.4 configured -- resuming normal operations"


>
> In any case, this is not the cause of the "we hit a bug" you get when
> you go to <http://domain.tld/cgi-bin/mailman/create>. That's a Mailman
> message and we need Mailman's error log for that.

I had a look in /var/log/mailman/error -> empty
in /var/log/mailman/qrunner: 
"eb 09 06:27:58 2006 (929) VirginRunner qrunner caught SIGHUP.  Reopening 
logs.
Feb 09 06:27:59 2006 (930) RetryRunner qrunner caught SIGHUP.  Reopening logs.
Feb 09 06:27:59 2006 (918) ArchRunner qrunner caught SIGHUP.  Reopening logs.
Feb 09 06:27:59 2006 (919) BounceRunner qrunner caught SIGHUP.  Reopening 
logs.
Feb 09 06:27:59 2006 (920) CommandRunner qrunner caught SIGHUP.  Reopening 
logs.
Feb 09 06:27:59 2006 (922) IncomingRunner qrunner caught SIGHUP.  Reopening 
logs.
Feb 09 06:27:59 2006 (924) OutgoingRunner qrunner caught SIGHUP.  Reopening 
logs.
Feb 09 06:27:59 2006 (923) NewsRunner qrunner caught SIGHUP.  Reopening logs.
Feb 09 06:28:00 2006 (917) Master watcher caught SIGHUP.  Re-opening log 
files."

but this is not the real log file, or?

I looked also multiple times through the files you meant but was not able to 
find something what is discribing a path to a log file! So, where is it?

tia

stefan
~


-- 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 481 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/20060210/e68933eb/attachment.pgp