[Mailman-Users] Strange errors

[Dan Szkola]

John W. Baxter wrote:

>On 10/19/05 11:14 AM, "Dan Szkola" <szkola at tanis.cso.niu.edu> 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 -----
>>>>PYTHONPATH /usr/local/mailman
>>>>   
>>>>
>>>>        
>>>>
>>>I wouldn't have expected this, but I don't think it should matter.
>>>
>>>What do you get if you add to the patch as follows
>>>
>>>--- admin       2005-10-14 16:31:42.078125000 -0700
>>>+++ admin_patched       2005-10-19 10:21:51.328125000 -0700
>>>@@ -25,8 +25,16 @@
>>>"""
>>>
>>>import sys
>>>+from os import environ
>>>+for env_var in environ:
>>>+    print env_var, environ[env_var]
>>>+for s_path in sys.path:
>>>+    print 'before =', s_path
>>>
>>>import paths
>>>+for s_path in sys.path:
>>>+    print 'after =', s_path
>>>+
>>>from Mailman import mm_cfg
>>>from Mailman import Utils
>>>from Mailman.i18n import _
>>>
>>>
>>> 
>>>
>>>      
>>>
>>   ----- Transcript of session follows -----
>>PYTHONPATH /usr/local/mailman
>>AGENT sendmail
>>before = /usr/local/mailman/scripts
>>before = /usr/local/mailman
>>before = /usr/local/lib/python24.zip
>>before = /usr/local/lib/python2.4/
>>before = /usr/local/lib/python2.4/plat-sunos5
>>before = /usr/local/lib/python2.4/lib-tk
>>before = /usr/local/lib/python2.4/lib-dynload
>>after = /usr/local/mailman/pythonlib
>>after = /usr/local/mailman
>>after = /usr/local/mailman/scripts
>>after = /usr/local/mailman
>>after = /usr/local/lib/python24.zip
>>after = /usr/local/lib/python2.4/
>>after = /usr/local/lib/python2.4/plat-sunos5
>>after = /usr/local/lib/python2.4/lib-tk
>>after = /usr/local/lib/python2.4/lib-dynload
>>after = /usr/local/lib/python2.4/site-packages
>>Traceback (most recent call last):
>>  File "/usr/local/mailman/scripts/admin", line 42, in ?
>>    from Mailman.Queue.sbcache import get_switchboard
>>  File "/usr/local/mailman/Mailman/Queue/sbcache.py", line 19, in ?
>>    from Mailman.Queue.Switchboard import Switchboard
>>  File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 47, in ?
>>    from Mailman.Logging.Syslog import syslog
>>  File "/usr/local/mailman/Mailman/Logging/Syslog.py", line 22, in ?
>>    from Mailman.Logging.StampedLogger import StampedLogger
>>  File "/usr/local/mailman/Mailman/Logging/StampedLogger.py", line 20, in ?
>>    from Mailman.Logging.Logger import Logger
>>  File "/usr/local/mailman/Mailman/Logging/Logger.py", line 25, in ?
>>    from Mailman.Logging.Utils import _logexc
>>  File "/usr/local/mailman/Mailman/Logging/Utils.py", line 18, in ?
>>    import traceback
>>ImportError: No module named traceback
>>554 5.3.0 unknown mailer error 1
>>
>>Oddly, the correct path statement is the only one with a trailing slash.
>>    
>>
>
>
>Have we eliminated the possibility that--due to some unfortunate
>event--there really is no traceback module (or it can't be read)?
>
>What do you get from
>ls -l /usr/local/lib/python2.4/traceback.py
>
>If it is there, does that file have world read permission?
>
>Do you have multiple Python versions installed?
>
>  --John
>  
>
Yep. If it didn't exist or was unreadable, wouldn't the script bail under
 normal circumstances?

Anyway, here is the output of an "ls -l /usr/local/lib/python2.4/tr*":

-rw-r--r--   1 bin      bin        28935 May 27 11:59 
/usr/local/lib/python2.4/trace.py
-rw-r--r--   1 bin      bin        22092 May 27 12:01 
/usr/local/lib/python2.4/trace.pyc
-rw-r--r--   1 bin      bin        22030 May 27 12:01 
/usr/local/lib/python2.4/trace.pyo
-rw-r--r--   1 bin      bin        10464 May 27 11:59 
/usr/local/lib/python2.4/traceback.py
-rw-r--r--   1 bin      bin        11030 May 27 12:01 
/usr/local/lib/python2.4/traceback.pyc
-rw-r--r--   1 bin      bin        11030 May 27 12:01 
/usr/local/lib/python2.4/traceback.pyo

I have also tried copying the traceback.py file into various places that 
make sense and I
get the same error. I know it is getting read because it gets compiled 
into a .pyc file.

The python 2.4.1 was compiled from source and is the only python version 
on the box.

--
Dan Szkola
Sr Unix Systems Programmer
Northern Illinois University