When I try to access the web UI, I get this strange error:
[Fri Oct 01 21:39:52.732148 2021] [cgi:error] [pid 7164] [client
197.232.81.246:1025] AH01215: File "/usr/local/mailman2/scripts/driver",
line 112: /usr/local/mailman2/cgi-bin/admin
[Fri Oct 01 21:39:52.732207 2021] [cgi:error] [pid 7164
On Mon, Dec 1, 2008 at 18:39, Mark Sapiro <[EMAIL PROTECTED]> wrote:
> Something like the following:
Thanks yet again!
Richard
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailma
Richard Hartmann wrote:
>
>For reference, how should the output of dumpdb -p look like if the
>files were OK?
Something like the following:
[- start pickle file -]
<- start object 1 ->
(this section has the raw message text)
<- start object 2 ->
{ '_parsemsg': True,
On Mon, Dec 1, 2008 at 18:24, Mark Sapiro <[EMAIL PROTECTED]> wrote:
> It looks like the files are corrupt. You may be able to see something
> of the contents with 'strings', but Mailman won't be able to process
> them as they are.
>
> If strings allows you to actually recover a message from the f
Richard Hartmann wrote:
>
>> You should
>> dump the file with "bin/dumpdb -p" to make sure it contains both a
>> message and a metadata object before renaming it.
>
># /usr/lib/mailman/bin/dumpdb -p
>/var/lib/mailman/qfiles/shunt/1227775710.928695+a44f4a2c5af5927c529c6c4a5589ab71759a1f86.pck.tmp
>[
On Mon, Dec 1, 2008 at 18:01, Mark Sapiro <[EMAIL PROTECTED]> wrote:
> First of all, your /etc/init.d/mailman script come from plesk or some
> other packager. Our suggested script doesn't attempt to remove lock
> files.
Yes, it's Plesk (unfortunately).
> You should
> dump the file with "bin/dum
Richard Hartmann wrote:
>Even more info (should have stated that in the first email):
>
>This is a NFS share. So it might 'just' be a crappy net connection.
>
>Any thoughts about this patch which I plan to apply locally?
>Beware evil GMail linebreaks..
>
>
>--- /usr/lib/mailman/Mailman/Queue/Switc
Richard Hartmann wrote:
>Further info:
>
>Restarting mailman gives me
>
># /etc/init.d/mailman restart
>Shutting down mailman
>
> done
>rm: cannot remove `/var/lib/mailman/locks/*': No such file or directory
>Starting mailmanrm: cannot remove `/
On Mon, Dec 1, 2008 at 15:14, J.A. Terranson <[EMAIL PROTECTED]> wrote:
> try this:
>
>./mailmanctl stop
>./mailmanctl --stale-lock-cleanup start
Nope, the warnings are still there. I don't really care about those, though.
My main concern is to make Mailman reliably relay list mai
On Mon, 1 Dec 2008, Richard Hartmann wrote:
> Restarting mailman gives me
>
> # /etc/init.d/mailman restart
> Shutting down mailman
>
> done
> rm: cannot remove `/var/lib/mailman/locks/*': No such file or directory
> Starting mailmanrm: cannot
Even more info (should have stated that in the first email):
This is a NFS share. So it might 'just' be a crappy net connection.
Any thoughts about this patch which I plan to apply locally?
Beware evil GMail linebreaks..
--- /usr/lib/mailman/Mailman/Queue/Switchboard.py.orig 2008-12-01
11:46:3
Further info:
Restarting mailman gives me
# /etc/init.d/mailman restart
Shutting down mailman
done
rm: cannot remove `/var/lib/mailman/locks/*': No such file or directory
Starting mailmanrm: cannot remove `/var/lib/mailman/locks/*': No such
f
Hi all,
I have this in my error log:
Nov 27 09:53:19 2008 post(18252): Traceback (most recent call last):
post(18252): File "/usr/lib/mailman/scripts/post", line 69, in ?
post(18252): main()
post(18252): File "/usr/lib/mailman/scripts/post", line 64, in main
post(18252): tolist=1, _
13 matches
Mail list logo
