Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 367406 - Mailman web interface broken
Summary: Mailman web interface broken
Status: RESOLVED WORKSFORME
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: MailingLists (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL: https://dev.eclipse.org/mailman/listi...
Whiteboard:
Keywords:
: 367838 367951 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-12-22 05:35 EST by Benjamin Cabé CLA
Modified: 2012-01-19 15:09 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Cabé CLA 2011-12-22 05:35:16 EST
If I go to e.g. https://dev.eclipse.org/mailman/listinfo/m2m-iwg

I get the following page:

<<
Bug in Mailman version 2.1.14

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.
>>

I'm filing this as CRITICAL since it seems to occur for all the mailing lists, and prevents to browse ML archives and to subscribe.

Benjamin –
Comment 1 Eclipse Webmaster CLA 2012-01-04 11:14:57 EST
*** Bug 367838 has been marked as a duplicate of this bug. ***
Comment 2 Eclipse Webmaster CLA 2012-01-04 11:16:37 EST
This seems to be caused by logrotate.  At this time I've been unable to
determine why logrotate seems incapable of correctly setting the log file
permissions.

-M.
Comment 3 Eclipse Webmaster CLA 2012-01-05 10:16:56 EST
*** Bug 367951 has been marked as a duplicate of this bug. ***
Comment 4 Eclipse Webmaster CLA 2012-01-05 10:21:53 EST
I've tried force running logrotate from the command line and it correctly sets
the ownership and permissions.

I've added a cronjob to try and better replicate it's 'normal' behavior, to see
if that produces anything.

-M.
Comment 5 Eclipse Webmaster CLA 2012-01-19 15:09:53 EST
I'm still unable to explain why logrotate isn't setting the file modes correctly.  I've crafted a script to fix things after logrotate has run, which is the only solution I can find.

-M.