From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030401 Description of problem: Upon a fresh install of Shrike, and fresh install of httpd and mailman, when starting mailman via service mailman start, get traceback errors. Version-Release number of selected component (if applicable): mailman-2.1-8 How reproducible: Always Steps to Reproduce: 1.Install mailman 2.Install httpd 3.service mailman start Actual Results: [root@bart root]# service mailman start Traceback (most recent call last): File "/var/mailman/bin/mailmanctl", line 524, in ? main() File "/var/mailman/bin/mailmanctl", line 319, in main check_privs() File "/var/mailman/bin/mailmanctl", line 274, in check_privs gid = grp.getgrnam(mm_cfg.MAILMAN_GROUP)[2] KeyError: getgrnam(): name not found Expected Results: Mailman should start with no errors Additional info: I used to run mailman until a few months ago (no lists to run at the moment). But someone else got this error, so thought I would try it out to see what the problem was. I don't recall ever having to *start* mailman, as it just worked after install.
In /var/mailman/Mailman/mm_cfg.py file, this looks to be the part that is failing.. # Here's where we override shipped defaults with settings # # suitable for the RPM package. # MAILMAN_UID = pwd.getpwnam('mailman')[2] MAILMAN_GID = grp.getgrnam('mailman')[2] Someone posted that this is what they did to get that working.. I ran into this problem also. I believe I worked around it by setting MAILMAN_USER = 'mailman' MAILMAN_GROUP = 'mailman' in my /var/mailman/Mailman/mm_cfg.py file. (There were other values I needed to customize in this file anyway.) The defaults in /var/mailman/Mailman/Defaults.py should probably be changed from MAILMAN_USER = '' MAILMAN_GROUP = '' to the values above. Does this help any?
These problems have been fixed in the current rpm, mailman-2.1.1-3
*** Bug 90052 has been marked as a duplicate of this bug. ***
An errata has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2003-179.html