Mark Sapiro wrote:
Dan Szkola wrote:
The python 2.4.1 was compiled from source and is the only python version
on the box.
In a later post, you say it wasn't, but you removed the Sun Gnome
Python 2.3. I hope that fixes it, but I doubt it will.
It did not. It was doubtful mailman
OK, I found something extremely odd. For some reason,
the Utils.pyc in /usr/local/mailman/Mailman/Logging
direcotry is being removed and then the compile of it
seems to fail and I'm left with a 0 byte file. It is
owned by the daemon user and later it gets compiled
and is owned by the mailman user.
Dan Szkola wrote:
OK, I found something extremely odd. For some reason,
the Utils.pyc in /usr/local/mailman/Mailman/Logging
direcotry is being removed and then the compile of it
seems to fail and I'm left with a 0 byte file. It is
owned by the daemon user and later it gets compiled
and is owned
Mark Sapiro wrote:
Dan Szkola wrote:
OK, I found something extremely odd. For some reason,
the Utils.pyc in /usr/local/mailman/Mailman/Logging
direcotry is being removed and then the compile of it
seems to fail and I'm left with a 0 byte file. It is
owned by the daemon user and later it gets
Dan Szkola wrote:
Very odd, I agree. A truss of the persistent queue runner that handled
one of the test mails shows this (12762 is the pid that mailman gets
when sendmail exec's it):
12762: open64(/usr/local/mailman/Mailman/Logging/Utils.so,
O_RDONLY) Err#2 ENOENT
12762:
Mark Sapiro wrote:
Dan Szkola wrote:
You can see it actually unlink the compiled version and then look
for, find, and seemingly reject the traceback.py and traceback.pyc
that it finds. I thought it may be a too many open files problem
or a file descriptor limit problem because the FD returned on
Mark Sapiro wrote:
Dan Szkola wrote (in separate posts):
You could try the following patch to the $prefix/scripts/post script to
print the environment each time it is invoked. Assuming sendmail
doesn't choke on this in the normal case, it should appear in the DSN
in the error case.
Mark Sapiro wrote:
Dan Szkola wrote:
Patched the admin script as suggested. When I saw the error this
morning, I emailed
to the admin address of our test list. Here is what I got:
- Transcript of session follows -
PYTHONPATH /usr/local/mailman
I wouldn't have expected
On 10/19/05 11:14 AM, Dan Szkola [EMAIL PROTECTED] wrote:
Mark Sapiro wrote:
Dan Szkola wrote:
Patched the admin script as suggested. When I saw the error this
morning, I emailed
to the admin address of our test list. Here is what I got:
- Transcript of session follows -
John W. Baxter wrote:
On 10/19/05 11:14 AM, Dan Szkola [EMAIL PROTECTED] wrote:
Mark Sapiro wrote:
Dan Szkola wrote:
Patched the admin script as suggested. When I saw the error this
morning, I emailed
to the admin address of our test list. Here is what I got:
-
Dan Szkola wrote:
John W. Baxter wrote:
On 10/19/05 11:14 AM, Dan Szkola [EMAIL PROTECTED] wrote:
Mark Sapiro wrote:
Dan Szkola wrote:
Patched the admin script as suggested. When I saw the error this
morning, I emailed
to the admin address of our test list. Here is what I
Mark Sapiro wrote:
Dan Szkola wrote:
I am running a Solaris 10 box, with mailman-2.1.6rc4 and sendmail
version 8.13.3. Python version is 2.4.1.
I run sendmail in the following ways:
A normal sendmail daemon listening on port 25:
/usr/lib/sendmail -bd -q15m
A persistent queue runner:
At 8:37 AM -0500 2005-10-18, Dan Szkola wrote:
Is there somewhere I can enable more debugging to help get to the bottom of
this issue? I'm finding next to nothing in the logs that is helpful.
There is no additional debugging that can be enabled. Assuming
you're looking in the right
Mark Sapiro wrote:
Dan Szkola wrote:
I am running a Solaris 10 box, with mailman-2.1.6rc4 and sendmail
version 8.13.3. Python version is 2.4.1.
I run sendmail in the following ways:
A normal sendmail daemon listening on port 25:
/usr/lib/sendmail -bd -q15m
A persistent queue runner:
Dan Szkola wrote (in separate posts):
Is there somewhere I can enable more debugging to help get to the bottom of
this issue? I'm finding next to nothing in the logs that is helpful.
As Brad replied, there are no debugging switches, but I'm not sure that
this would be helpful in this case
Hello all,
We are converting our lists from a different list server to mailman.
I am running a Solaris 10 box, with mailman-2.1.6rc4 and sendmail
version 8.13.3. Python version is 2.4.1.
I run sendmail in the following ways:
A normal sendmail daemon listening on port 25:
/usr/lib/sendmail
Dan Szkola wrote:
I am running a Solaris 10 box, with mailman-2.1.6rc4 and sendmail
version 8.13.3. Python version is 2.4.1.
I run sendmail in the following ways:
A normal sendmail daemon listening on port 25:
/usr/lib/sendmail -bd -q15m
A persistent queue runner:
/usr/lib/sendmail -qp1m
17 matches
Mail list logo
