Dennis Putnam wrote: >OK, now I understand what you are asking. I restarted mailman and let it >run for several minutes with no error in /var/log/mailman/error. Then I >submitted a help to -request. That is when the error occurred. I suppose >it might mot be the help request per se but rather anything that causes >mailman to do something. I tried to run a couple of other commands and >they all do the same thing. I am reluctant to actually send a test to >the list out of fear it might destroy something and make matters worse. >Here is the traceback. > >Oct 24 17:30:09 2008 (5961) Uncaught runner exception: [Errno 13] >Permission denied: >'/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.5961.1' >Oct 24 17:30:09 2008 (5961) Traceback (most recent call last): > File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 112, in _oneloop > self._onefile(msg, msgdata) > File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 170, in _onefile > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/lib/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose > mlist.ArchiveMail(msg) > File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 216, in >ArchiveMail > h.processUnixMailbox(f) > File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 580, in >processUnixMailbox > self.add_article(a) > File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 632, in >add_article > article.parentID = parentID = self.get_parent_info(arch, article) > > File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 664, in >get_parent_info > article.subject) > File "/usr/lib/mailman/Mailman/Archiver/HyperDatabase.py", line 311, >in getOldestArticle > self.__openIndices(archive) > File "/usr/lib/mailman/Mailman/Archiver/HyperDatabase.py", line 251, >in __openIndices > t = DumbBTree(os.path.join(arcdir, archive + '-' + i)) > File "/usr/lib/mailman/Mailman/Archiver/HyperDatabase.py", line 61, in >__init__ > self.lock() > File "/usr/lib/mailman/Mailman/Archiver/HyperDatabase.py", line 77, in >lock > self.lockfile.lock() > File "/usr/lib/mailman/Mailman/LockFile.py", line 243, in lock > self.__write() > File "/usr/lib/mailman/Mailman/LockFile.py", line 422, in __write > fp = open(self.__tmpfname, 'w') >IOError: [Errno 13] Permission denied: >'/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.5961.1' > >Oct 24 17:30:09 2008 (5961) SHUNTING: >1224883807.7050669+416c5717ff6f07bcc5748843bf07afb92dc4b212
ArchRunner is trying to archive a message it found in qfiles/archive/. It has encountered the lock permission denied and moved the message to qfiles/shunt/1224883807.7050669+416c5717ff6f07bcc5748843bf07afb92dc4b212.pck What is the message (use bin/dumpdb or bin/show_qfiles to see it). >Here is the process (shouldn't this be running as 'mailman'?): > >mail 5961 0.1 0.7 11100 7356 ? R 17:28 0:00 >/usr/bin/python /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s How are you starting Mailman. Are you running bin/mailmanctl as root or starting it as a 'service' as root? If so, it should be setting the uid and gid of itself and the runners as those of MAILMAN_USER and MAILMAN_GROUP from Defaults.py/mm_cfg.py and supplemental groups as those associated with MAILMAN_USER. So, if I understand your configuration, MAILMAN_USER:MAILMAN_GROUP are mailman:mail. If that's correct, I would expect the runners to be running as user 'mailman'. That may be the cause of the permissions error. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
