Fabricio Oliveira wrote: > Hi Mark, > > I see your considerations about permissions, but I don't know are SELinux. > What is this?
SELinux is a security policy manager that can prevent file access based on security policies even though the access would be allowed by file permissions. > I stoped the python's services and I restarted the service with the command > below: > > [EMAIL PROTECTED]:/usr/local/mailman/bin# ./mailmanctl stop > Shutting down Mailman's master qrunner > > [EMAIL PROTECTED]:/usr/local/mailman/bin# ps -fAww |grep python > > [EMAIL PROTECTED]:/usr/local/mailman/bin# ./mailmanctl start > Starting Mailman's master qrunner. > > After restarted the service, the following pid appear: > > [EMAIL PROTECTED]:/usr/local/mailman/bin# ps -fAww |grep python > mailman 27184 1 0 12:54 ? 00:00:00 /usr/bin/python ./mailmanctl > start > mailman 27185 27184 4 12:54 ? 00:00:00 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=ArchRunner:0:1 -s > mailman 27186 27184 56 12:54 ? 00:00:02 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=BounceRunner:0:1 -s > mailman 27187 27184 4 12:54 ? 00:00:00 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=CommandRunner:0:1 -s > mailman 27188 27184 4 12:54 ? 00:00:00 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s > mailman 27189 27184 4 12:54 ? 00:00:00 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=NewsRunner:0:1 -s > mailman 27190 27184 4 12:54 ? 00:00:00 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s > mailman 27191 27184 5 12:54 ? 00:00:00 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=VirginRunner:0:1 -s > mailman 27192 27184 5 12:54 ? 00:00:00 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=RetryRunner:0:1 -s OK, so now Mailman started properly, and the lock file and perhaps qfile problems may be solved. > The page continue with the error: > > Bug in Mailman version 2.1.9 > > We're sorry, we hit a bug! > Please inform the webmaster for this site of this problem. Printing of > traceback and other system information has been explicitly inhibited, but the > webmaster can find this information in the Mailman error logs. This error had nothing to do with the other problems. This error is apparently due to the configuration files for the cartaoberro list being corrupt. The error log entries you posted previously indicate that the data from the /usr/local/mailman/lists/cartaoberro/config.pck and /usr/local/mailman/lists/cartaoberro/config.pck.last files couldn't be loaded. It appears that these files are corrupt. If you have a backup, I suggest you try restoring these files from the backup. Without that, you can try to dump the files with Mailman's bin/dumpdb, but that will probably fail in the same way. If so, the best you may be able to do is use the strings command to try to extract as much information as possible from these files and use it to recreate the list. -- 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
