[Mailman-Users] {Disarmed} Re: unable to access admin interface

[Chad Rebuck]

It has been months at least (maybe even back to 2013) since I've attempted
to access the pending moderator requests, but it has worked before.

I stopped mailman, confirmed no python processes exist, and deleted all
files from the locks dir.  I could access the admin page, but not the
pending moderator requests.

[root at pogo locks]# ll
total 8.0K
-rw-rw-r-- 2 http mailman 52 Jul 23  2014 a2-16v-list.lock
-rw-rw-r-- 2 http mailman 52 Jul 23  2014 a2-16v-list.lock.pogo.25650.0
[root at pogo locks]#





On Wed, Jul 23, 2014 at 11:10 AM, Mark Sapiro <mark at msapiro.net> wrote:

> On 07/23/2014 06:54 AM, Chad Rebuck wrote:
> > I installed it with a package on my arch system using
> >
> > pacman -Syu
>
>
> Did it ever work?
>
>
> > [root at pogo chadr]# ll /var/lib/mailman/locks/
> > total 16K
> > -rw-rw-r-- 1 http    mailman 52 Jul 23 03:52
> a2-16v-list.lock.pogo.22018.0
> > -rw-rw-r-- 1 http    mailman 52 Jul 23 04:45
> a2-16v-list.lock.pogo.22205.0
> > -rw-rw-r-- 2 mailman mailman 46 Jul 24  2014 master-qrunner
> > -rw-rw-r-- 2 mailman mailman 46 Jul 24  2014 master-qrunner.pogo.341
> >
> > Then I tried to access
> >
> > http://mail.a2-16v.com/mailman/admindb/a2-16v-list and waited for the
> > 504 error to appear in the browser
> >
> >
> > [root at pogo chadr]# ll /var/lib/mailman/locks/
> > total 24K
> > -rw-rw-r-- 2 http    mailman 52 Jul 23  2014 a2-16v-list.lock
> > -rw-rw-r-- 1 http    mailman 52 Jul 23 03:52
> a2-16v-list.lock.pogo.22018.0
> > -rw-rw-r-- 1 http    mailman 52 Jul 23 04:45
> a2-16v-list.lock.pogo.22205.0
> > -rw-rw-r-- 2 http    mailman 52 Jul 23  2014
> a2-16v-list.lock.pogo.25275.0
> > -rw-rw-r-- 2 mailman mailman 46 Jul 24  2014 master-qrunner
> > -rw-rw-r-- 2 mailman mailman 46 Jul 24  2014 master-qrunner.pogo.341
>
>
> I don't think the issue is lock contention because it appears that your
> CGI process was PID 25275 and it acquired the lock. Either that or
> something is really hosed and the CGI attempts to lock the list twice.
>
> Also, there's something weird about the clock on your system because 4
> of the above 6 files have time stamps in the future.
>
> I don't know if there are multiple runner issues or not, and they
> shouldn't affect CGIs anyway, but see the "You need to stop all Mailman
> processes and then start Mailman once only." section in the FAQ at
> <http://wiki.list.org/x/_4A9>. Do this up to the point of starting
> Mailman, but before starting Mailman remove all files from the
> /var/lib/mailman/locks/ directory and then try the web interface again
> without first starting Mailman.
>
> --
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
>